Skip to main content

Standardized Invoice Formats

If you have invoices in a standardized format currently not supported (see section Supported Electronic Invoice Formats for supported standardized invoice formats) a manual mapping is required. Manual mapping involves the process of mapping the data fields of your invoices to the corresponding data fields in our system. This process is necessary to ensure that the information from your invoices is accurately captured and processed by our system. The more data you provide for the Kaunt algorithm, the more benefit you will gain from Kaunt.

Electronic invoices​

In addition to the invoice format defined by Kaunt in PostedInvocies and InvoiceCodingProposals, you can also send electronic invoices directly to Kaunt thus making the need for manually mapping from the structured invoice format to the format defined by Kaunt in PostedInvoices and InvoiceCodingProposals obsolete.

How it works​

When you POST an electronic invoice to the Kaunt API on either the InvoiceCodingProposals/e-invoice endpoint or the PostedInvoices/e-invoice endpoint, the Kaunt API will internally transform the invoice by mapping the relevant fields of the XML invoice into an internal Kaunt-specific format.

Supported Electronic Invoice Formats:​

  • OASIS UBL 2.0 (Invoice + CreditNote)
  • OASIS UBL 2.1 (Invoice + CreditNote)
  • OIOUBL 2.0 (Invoice + CreditNote)
  • OIOUBL 2.1 (Invoice + CreditNote)
  • OIOXML 0.71 PIE + PCM (Invoice + CreditNote)
  • TEAPPSXML 3.0 (Invoice + CreditNote)
  • cXML 1.2.011+ (Invoice + CreditNote)
  • UN/CEFACT Cross Industry Invoice (Invoice + CreditNote)

The list of supported invoice formats grows day-by-day. If you have an abundance of invoices in a format not listed above and want to try out Kaunt, do not hesitate to contact us to hear about the possibilities for us to support your format.

Attachments in Electronic Invoices​

A lot of standard invoice formats allows for the possibilty to e.g. embed a .pdf version of the invoice inside of the XML-invoice. There is no need for you to remove these attachments before sending them our way. If the attachment is of a supported mimetype we will extract relevant information from the attachment and use it in our AI-engine as well.

Supported attachment mimetypes:​

  • application/pdf
  • image/tiff
  • image/png
  • image/jpeg

Non-standardized Invoice Formats

Non-standardized invoice formats - usually in the form of .PDF's, TIFF etc. should be mapped to the format as described in PostedInvoices as well as InvoiceCodingProposal. You are highly encouraged to map as much of the data as you possibly can. The more data you provide for the Kaunt algorithm, the more you will benefit from the Kaunt AI.

It's important to note that our platform is not an OCR (Optical Character Recognition)/Capture solution. Our platform is designed to complement existing OCR solutionsby leveraging the data extracted through the OCR process. If you do not have an existing capture solution and are unable to map the unstructured invoice formats into the Kaunt format, we also offer a document text extraction endpoint. See Document Text Extraction for more information.

By utilizing our platform on top of an OCR solution or the Document Text Extraction endpoint, users can benefit from the accuracy and efficiency of OCR technology while receiving InvoiceCodingProposals for account coding proposals for each invoice line.