Global E-Invoicing Made Simple

Global or multi-country e-invoicing means sending and receiving compliant electronic invoices across many countries, each with its own formats, networks and tax rules. Some countries use the Peppol network, others require continuous transaction controls (CTC) where invoices are cleared by the tax authority in real time, and several run their own national platforms. A multi-country e-invoicing API abstracts these differences so a business can reach every market through one integration.

Yes. With GoRoute you integrate one REST API and send invoices in a single input format. GoRoute detects each destination, converts to the required country format and profile, validates it, and routes it over the correct network or clears it with the tax authority. This replaces building and maintaining separate integrations for Peppol, DBNAlliance and each national CTC system.

Peppol is a four-corner post-audit network: invoices travel directly from the sender's Access Point to the receiver's Access Point, and tax authorities audit afterwards. CTC (Continuous Transaction Controls) or clearance models, such as Saudi Arabia's ZATCA and Oman's Fawtara, require the invoice to be submitted to the tax authority, which validates and stamps it before or as it reaches the buyer. GoRoute supports both models through one API so you do not have to build each one separately.

Many jurisdictions are phasing in mandatory e-invoicing through roughly 2026 to 2028, and the exact dates, thresholds and scope differ by country and change over time. Frequently cited examples include France, Belgium, Poland, Germany, Malaysia, Saudi Arabia, the UAE and others, but you should confirm each country's current rules on its dedicated country page or 2026 mandate tracker. GoRoute tracks these changes and updates support so your integration stays compliant without code changes.

You send your invoice once as JSON or EN 16931-compliant UBL. GoRoute maps that data to the format the destination requires, such as a Peppol PINT country profile, Germany's XRechnung, Italy's FatturaPA, France's Factur-X, or a ZATCA clearance document. You maintain one internal invoice format while GoRoute handles the translation layer for every market.

EN 16931 is the European semantic standard that defines the core data model of an electronic invoice, and most Peppol and national profiles build on it. UBL (Universal Business Language) is a common XML syntax used to express invoices; Peppol BIS Billing 3.0 is expressed in UBL 2.1. Working from an EN 16931-aligned model makes it far easier to map one invoice to many country-specific profiles.

Peppol BIS Billing 3.0 is the established European billing specification, expressed in UBL 2.1. PINT (Peppol International) is the newer international invoice model designed to support country-specific profiles on a common base, including PINT A-NZ for Australia and New Zealand, PINT AE for the UAE, PINT OM for Oman and PINT JP for Japan. These profiles are distinct and not automatically interchangeable, so GoRoute produces and validates against the correct profile for each destination.

Every invoice is checked against EN 16931 and the destination's Schematron and business rules before it is delivered or submitted for clearance. This pre-flight validation catches missing fields, tax mistakes and profile violations early, so invoices are not rejected by the receiver or the tax authority. You receive clear error details when something needs to be corrected.

GoRoute implements the country's required format and profile, its Schematron and business rules, any signing or QR requirements, and its network or clearance channel. That capability is exposed through the same REST API you already use, so adding a country generally means no new integration work on your side. As mandates and profiles change, GoRoute updates the mapping and validation centrally.

GoRoute maintains a complete audit trail of the original invoice, converted formats, validation results, signatures, delivery receipts and tax authority responses. Data is handled in line with GDPR, and some jurisdictions require in-country storage, which GoRoute supports through regional hosting options. Because retention and residency rules vary by country, you should confirm the specific requirement for each market you operate in.

A single provider is enough when it connects to the networks and clearance systems your trading partners use and keeps pace with changing mandates. GoRoute is a Peppol certified Access Point and SMP (POP000991), a DBNAlliance participant, and supports national CTC systems, which covers most B2B and B2G destinations through one integration. For a country with a niche local requirement, GoRoute maps and validates to that country's profile rather than asking you to add another vendor.

No. You keep one internal format and send it to GoRoute, which converts it to whatever each destination needs. This means your finance or engineering team is not maintaining FatturaPA, XRechnung, Factur-X, PINT and ZATCA templates in parallel. The conversion, profile selection and validation happen inside GoRoute's platform.

Yes. GoRoute registers your participant identifiers on Peppol and other networks and supports two-way exchange. Incoming invoices are normalised to a consistent format of your choice and delivered to your webhook endpoint, regardless of the original source format. The same audit trail applies to both directions.

GoRoute connects to the Peppol network using AS4 with Peppol BIS Billing 3.0 and PINT country profiles, the DBNAlliance exchange in the United States, and national CTC clearance systems such as ZATCA Fatoora, Oman Fawtara and Poland's KSeF. It also supports national platforms including Italy's SDI (FatturaPA), France's PPF (Factur-X) and Finland's Finvoice. All of this is available through one REST API.

A Peppol Access Point is a certified gateway that connects your business to the Peppol network so you can send and receive invoices with any other participant. To exchange invoices over Peppol you connect through an Access Point rather than joining the network directly. GoRoute is a certified Peppol Access Point and SMP provider (POP000991), so using GoRoute gives you that connectivity as part of the same global API.

Start by integrating the GoRoute REST API and sending test invoices from the free sandbox. Map your invoice data once, choose the destinations you need, and GoRoute handles conversion, validation and routing per country. You can expand to new countries later without re-integrating, because the same API covers Peppol, DBNAlliance and national CTC systems. See our guide to choosing a Peppol Access Point to compare providers.