Maventa services and reach
Maventa supports e-invoicing and digital document exchange in Nordics and multiple European countries, covering both domestic and cross-border use cases. Our goal is to make it easy to build one integration that works across markets, without having to deal with country-specific complexity in your own systems or at least keeping it in minimum.
E-invoicing works a bit differently in every country. Local regulations, supported networks, document formats, and delivery methods can all vary. In the section you will find country-specific information such as which networks are supported (for example Peppol and local networks), what invoicing scenarios are available (B2B, B2G, B2C), and any special requirements that may affect how you integrate or onboard customers.
Our reach is continuously expanding, especially as the EU’s
Use the map below to see where Maventa currently operates. Each country section gives a quick overview of the most important details, with links to more in-depth documentation.
Maventa on the map
Upcoming changes
These are the next changes coming up in the countries Maventa serves. See all dates on the upcoming changes page.
| When | Country | Change | What you need to do |
|---|---|---|---|
| 15th of November 2026 | Norway |
Maventa: The activation API responses for Norwegian consumer invoicing change. The RESERVED status is no longer returned, and some activation and disable responses change. Details
|
On SOAP, test for OK instead of OK: Email sent to <signer_email> on a successful activation. |
| Autumn 2026 | Lithuania | Maventa: Identity verification, Peppol registration and AutoScan become available for Lithuanian companies. Details | — |
| End of 2026 | Sweden | Maventa: Autogiro, the Swedish direct debit scheme, is planned to become available for consumer invoicing. Details | — |
Cross-border invoicing
While each country has its own local networks and routing rules for domestic invoicing, cross-border delivery between countries always goes through the Peppol network. Local networks — such as the Finnish operator and bank networks, the Swedish operator network (
Maventa’s internal network is always tried first in the routing order. If both sender and receiver are Maventa customers, the invoice is delivered internally regardless of country. If the recipient is not a Maventa customer, Peppol is the next electronic channel for cross-border delivery. Providing the operator code PEPPOL in the sending metadata forces delivery through Peppol and skips the internal network. If neither internal nor Peppol delivery is possible, email and print are available as fallback options.
When a company is registered as a Peppol receiver through Maventa, Peppol BIS Billing 3.0 is always registered as a supported document type — along with any applicable national Peppol document profiles. Peppol BIS 3.0 is the standard format for cross-border invoicing. Some national formats, such as XRechnung (Germany) and SI-UBL (Netherlands), are restricted to domestic Peppol traffic only. When sending, Maventa selects an output format that the recipient accepts and that Maventa supports, and converts the invoice automatically if needed — see format selection and conversion.
When sending cross-border, always provide the recipient’s full Peppol endpoint ID including the scheme prefix — for example 0007:5511111111 for a Swedish recipient or 9930:DE123456789 for a German recipient. For Finnish senders in particular, a plain Business ID only triggers domestic operator and bank network lookups — Peppol is not attempted without the full endpoint ID.
| Country | Peppol scheme | Based on | Example endpoint ID | Domestic-only networks |
|---|---|---|---|---|
| Finland | 0216 |
OVT code | 0216:003712345678 |
Operator network, bank network |
| Sweden | 0007 |
Organisation number | 0007:5511111111 |
Operator network (NEA), InExchange |
| Norway | 0192 |
Organisation number | 0192:987654321 |
— |
| Denmark | 0184 |
CVR number | 0184:31000000 |
Nemhandel (Sproom) |
| Germany | 9930 |
VAT number | 9930:DE123456789 |
— |
| Netherlands | 0106 |
KVK number | 0106:12345678 |
— |
| Belgium | 0208 |
CBE/KBO number | 0208:0471000000 |
— |
| Estonia | 9931 |
VAT number | 9931:EE123456789 |
— |
| Latvia | 9939 |
VAT number | 9939:LV12345678901 |
— |
| Iceland | 0196 |
Kennitala | 0196:5555555559 |
— |
| Poland | 9945 |
VAT/NIP number | 9945:PL1234567890 |
|
| Italy | 9906 |
VAT number | 9906:IT12345678901 |
|
Companies with establishments in several countries
When a company has a fixed establishment, such as a branch or a permanent place of business, in another country, that establishment needs its own e-invoicing identity. In countries with national e-invoicing or reporting mandates, the establishment is treated as a separate taxable party under its own local VAT number, and its invoices must be sent and received under that number.
In Maventa, this means that each establishment needs its own company account, with its own:
- VAT number or other local company identifier
- Country
- E-invoicing address
Why one account cannot serve several countries
Each Maventa company account is set up for one country. In countries with a national e-invoicing platform, that country decides whether the account’s invoices go through the platform. For example:
-
Italy: All invoices go through the national exchange system
Sistema di Interscambio — Italy's national clearance platform that validates and routes all electronic invoices between businesses and the tax authority . See e-invoicing in Italy. -
Poland: Invoices go through the national system
Krajowy System e-Faktur — Poland's national e-invoicing system for issuing, receiving, and storing structured electronic invoices . See e-invoicing in Poland. - France: Domestic invoices go through the French regulated e-invoicing network, and every company must be registered in the French e-invoicing directory. Receiving is live, and sending follows in a later phase. See e-invoicing in France.
- Other countries: There is no national platform, so Maventa routes each invoice based on the recipient, over Peppol or the applicable local network. More countries are introducing national platforms, and the list will grow.
Because routing follows the company account, an establishment cannot send or receive invoices through the account of its parent company in another country. Its invoices would go through the wrong channel and would not meet the local requirements. There are other reasons to keep the identities separate as well:
- Peppol: Each company account is registered on Peppol under its own identifier, and received invoices are delivered to the account that matches the receiver identifier in the message envelope. An establishment that uses its parent company’s account can’t be reached under its own local identifier.
-
Reporting: Countries with reporting mandates expect transactions to be reported under the identity of the establishment that made them. Under
VAT in the Digital Age — an EU initiative to modernize VAT reporting through mandatory e-invoicing and real-time digital reporting across member states , from July 2030, intra-EU invoices will also be reported under the VAT number used for each transaction.
If your customer has establishments in several countries, create a separate company account for each establishment in its own country, using its local identifier. Each account is then registered to the right networks and national platforms for that country.