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. |
| End of 2026 | Sweden | Maventa: Autogiro, the Swedish direct debit scheme, is planned to become available for consumer invoicing. Details | — |
| By end of Q4 2026 | Germany | Maventa: Invoices between German companies that fall back to email delivery get an automatically generated ZuGFeRD attachment, and German companies can receive ZuGFeRD invoices by email. Details | — |
Cross-border invoicing
Every country handles e-invoicing a little differently. How a cross-border invoice is delivered depends on the recipient’s country and, in some countries, on the sender’s country too.
If the recipient is also a Maventa customer, the invoice is usually delivered through Maventa’s internal network. Otherwise, the route depends on the countries involved:
- Most countries - Maventa connects to no local network, so cross-border invoices go through the Peppol network.
-
Finland, Sweden, and Denmark - Maventa also connects to a local network alongside Peppol: the Finnish operator and bank networks, the Swedish operator network (
Nätverket för Elektroniska Affärstransaktioner - the Swedish network for electronic business transactions ), and the DanishDenmark's national e-business infrastructure for exchanging electronic documents between businesses and public authorities through Sproom. Recipients in these countries can be reached through their local network even when the sender is from another country. See sending to Finland, Sweden, and Denmark. - Italy, Poland, and France - These countries have a national e-invoicing platform, and the platform also shapes cross-border sending. See the Italy, Poland, and France pages for details.
If no electronic delivery is possible, email and print are used as fallback options.
Sending to Finland, Sweden, and Denmark
Routing to recipients in these countries follows the recipient’s country, so senders from other countries use the same channels as domestic senders.
Maventa can find the recipient’s e-invoicing address and operator itself from its address registry, Peppol, or the local network, so they are not required on the invoice. If you know them, adding both is recommended. Maventa then delivers the invoice straight to that operator, so it reaches the recipient through the channel they have chosen. When both are given, Maventa uses only that route and does not fall back to other channels, such as Peppol, Nemhandel, email, or print. To send through Peppol, set the operator code PEPPOL in the sending metadata, which also skips the internal network.
For the identifiers and channels used in each country, see the Finland, Sweden, and Denmark pages.
Two channels depend on the sender:
- Finnish bank network - Activated automatically for Finnish companies. If a company from another country needs to send invoices to Finnish recipients who receive them through their bank, the bank sending connection can be set up for that company. Contact support.maventa@visma.com.
- InExchange roaming operators - Used only for Swedish senders. They give access to the wider Swedish operator network, so recipients who can only be reached this way can’t receive invoices from senders in other countries.
Formats and Peppol identifiers
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 through Peppol, 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. If you also set the operator code PEPPOL in the sending metadata, the invoice is sent only through Peppol, and the internal network and other channels are skipped.
| Country | Peppol scheme | Based on | Example endpoint ID | Local network or national platform |
|---|---|---|---|---|
| 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 | 0211 |
VAT number | 0211: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, in Finland, Sweden, and Denmark, the 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.