Invoice XML & content

XML in e-invoicing

XML presents invoice data in a structured way. Maventa e-invoicing supports wide variety of XML based standard invoice formats and automatically converts the invoices from one format to another when needed. See the supported formats and xml examples below.

Supported XML formats

See all example XML files from here.
Please notice that Finvoice examples have two different files, one uses SOAP envelope and one uses MessageTransmissionDetails. Finvoice 2.0 has also version 2.01.

Supported attachment filetypes

  • .tif
  • .tiff
  • .jpg
  • .jpeg
  • .png
  • .gif
  • .txt
  • .xml
  • .xls
  • .xsl
  • .xlsx
  • .html
  • .htm
  • .pdf
  • .aix
  • .doc
  • .docx
  • .ods

These are the attachment types supported by Maventa SOAP and REST API.

Note that there might be also format and operator specific limitations. Remember check limitations from format’s documentation, e.g. PEPPOL support only these MimeCodes.

Invoice Image handling (Example PDF with Modern template)

When sending e-invoices, a PDF version of the invoice is always sent and if no such PDF exists, it will be created using Maventa PDF templates. It is recommended that ERP generates and sends the invoice image in PDF format with the XML, in that way the user knows which template will be used for PDF viewing of the invoice.

The image can be sent as embedded attachment within xml or within a zip file depending on the invoice format that is used. If the invoice image is sent as an attachment within a zip file, the invoice xml and invoice image file within the zip need to be named the same way for Maventa to recognize the attachment as the invoice image. For example 12345.xml and 12345.pdf.

PDF is filled with corresponding Finvoice tags to make it clear which tag is visualised where.

Download fullsize image

Invoice validation & Autovalidator

Some of the routes invoices are sent to, such as PEPPOL or net bank require validation of the invoice data. The purpose of the validation is to ensure data is structurally correct and the content is in alignment within an invoice, for example the invoice total amounts match the line amounts. If the route where invoice is going to requires validation, Maventa does this before distributing the invoice and returns an error if the invoice is not valid. If you are interested of validation on your system side, contact your integration contact point or Maventa to discuss the tools we have to offer.