Invoicing formats
XML presents invoice data in a structured way. 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.
In general, we recommend using the Peppol BIS 3.0 format for invoice exchange. The format is widely supported and is well suitable for sending and receiving invoices across countries.
If you are planning to operate in the Finnish market only and have a need to send consumer invoices, we recommend Finvoice 3.0 or TEAPPSXML. Both of the formats can handle both B2B and B2C invoicing.
All three formats fully support the European
Supported XML formats
Recommended formats
Peppol BIS 3.0
International standard for cross-border invoicing. Widely supported across Europe.
Finvoice 3.0
Finnish standard supporting both B2B and B2C invoicing. EN16931 compliant.
TEAPPS 3.0
Finnish XML format supporting B2B and B2C invoicing. EN16931 compliant.
Finvoice 3.0 is also available with MessageTransmissionDetails wrapper for direct operator delivery.
Other supported formats
Finnish formats
-
Finvoice — the Finnish e-invoicing standard maintained by Finance Finland, widely used for B2B and B2C invoicing via banks and operator networks
(example xml) -
Finvoice 2.0 — includes version 2.01, the most widely adopted Finvoice version in Finnish B2B invoicing
(example xml) -
Finvoice 3.0 — the latest version, adding support for EU e-invoicing standard EN16931 and enhanced B2C capabilities. Uses SOAP.
(example xml) -
TietoEnator Application XML — a Finnish invoice format originally developed by TietoEnator (now Tietoevry), widely used in Finnish ERP integrations
(example xml) -
Liinos — a Finnish ERP-specific invoice format used by the Liinos software family
(example xml)
Visma formats
-
Visma XML — Visma's proprietary invoice format used across Visma ERP products in the Nordics
(example xml) -
Visma XML 6.0 — the latest version of Visma's proprietary XML format with expanded field support
(example xml) -
Visma UBL — Visma's UBL-based invoice format combining UBL structure with Visma-specific extensions
(example xml) -
Visma UBL 3.0 — the latest Visma UBL version, aligned with Peppol BIS 3.0 and EN16931
(example xml)
Nordic & international
-
Peppol BIS 2.0 — the previous version of the Peppol Business Interoperability Specification for cross-border e-invoicing
(example xml) -
Simplerinvoicing UBL — a Dutch e-invoicing profile based on UBL, used for domestic Peppol traffic in the Netherlands.
Versions: 1.0, 1.2, and 2.0.
(example xml 2.0) -
Elektronisk Handelsformat — the Norwegian standard for electronic business documents, based on UBL and aligned with Peppol BIS.
Versions: 1.0 and 2.0.
(example xml 2.0) -
A Swedish e-invoice format based on UBL, historically used for domestic invoicing in Sweden before Peppol BIS adoption
(example xml) -
SEDI — a Danish e-invoice format used in the Danish market for electronic document interchange
(example xml)
See all example XML files from maventa/invoicexmlexamples.
Document types
This section is under construction.
Maventa supports several document types beyond standard invoices. The document type is determined by fields within the invoice XML — the exact field depends on the format used.
- Invoice — A standard invoice requesting payment for goods or services.
- Credit note — Reverses or corrects a previously sent invoice. The total amount is negative. Used when an invoice needs to be cancelled or adjusted after it has been sent.
- Self-billing invoice — An invoice created by the buyer on behalf of the seller. Supported through the Peppol network with a dedicated profile.
How each format identifies the document type varies. For example, in Peppol BIS 3.0, invoices and credit notes use separate XML root elements (Invoice and CreditNote). In Finvoice, the InvoiceTypeCode field determines the type (e.g., INV01 for a standard invoice, INV02 for a credit note). In TEAPPSXML, the INVOICE_TYPE field is used.
Routing and delivery work the same way for all document types. The recipient must support the specific document type — for example, when sending via Peppol, the recipient’s Peppol registration must include CREDIT_NOTE as a supported document type.
When registering to receive invoices via Peppol through Maventa, the INVOICE_AND_CREDIT_NOTE profile automatically registers both the invoice and credit note document types:
| Document type | Document identifier |
|---|---|
| Peppol BIS Billing UBL Invoice V3 | urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1 |
| Peppol BIS Billing UBL Credit Note V3 | urn:oasis:names:specification:ubl:schema:xsd:CreditNote-2::CreditNote##urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0::2.1 |
Both use the process identifier urn:fdc:peppol.eu:2017:poacc:billing:01:1.0.