Routes and countries
The five routes, what is checked and which rail carries each.
- In the sandboxvalidation
- Not in the sandbox yetsending
In plain words
A route is the way an invoice reaches a buyer or a tax authority, and there are five: Germany, the Peppol network, France, Poland and Romania. This page says what we check on each, when an invoice counts as final and which rented connection carries it. Sending is built and has run against the rails' test systems, but the hosted sandbox holds no rail credential yet, so no route sends from there. Dates come from official sources, last verified on 26 September 2026, and must be checked again before anyone relies on them.
A route is the way an invoice reaches the buyer or the authority. Each row says what the service checks today, when an invoice counts as final, and what kind of rail carries it.
The five routes
| Route | The invoice is final when | What the service checks today | Rail |
|---|---|---|---|
DE-XRECHNUNG | The file passes the format rules. No authority answers. | The KoSIT validator (1.6.3). It also builds a ZUGFeRD PDF in the XRechnung profile and checks it with veraPDF. | None for the format. Delivery goes by Peppol or email. |
PEPPOL | An access point delivers it. | UBL schema, EN 16931 rules, and Peppol BIS 3.0.21. | A rented Peppol access point. |
FR-PA | A Plateforme Agréée delivers it, and the buyer's statuses follow. E-reporting runs alongside. | UBL schema and EN 16931 rules. The French BR-FR rules stay on the Plateforme Agréée. | A rented Plateforme Agréée. |
PL-KSEF | KSeF gives it a number, or rejects it. | The FA(3) schema, checked with libxml, and KSeF's file and date rules. | KSeF, through its public API. |
RO-EFACTURA | ANAF's state is ok, or nok and it is rejected. | UBL schema, the CIUS-RO rules and the RO e-Factura rules. | ANAF's API. |
A JSON invoice starts with the canonical schema check on every route, and a failure there stops the run before the route validator starts. A finished XML file sent to POST /invoices/xml skips the canonical schema check but gets the XML safety check and the route's validators (see submit XML).
Warning
Dates were verified on 26 Sep 2026 against the official source linked beside each. Germany, France and Poland were checked again on 7 Oct 2026, and no date had changed; the Polish bill that would move the penalties is still a draft. Check a date again before relying on it.
Sending
Not in the sandbox yetsendingSending is built for Peppol, France, Poland and Romania. It has run against the test systems of a Peppol access point, a French platform and KSeF. Romania's upload follows ANAF's documentation and has not been tried; only its validators have run. Germany has no rail: the invoice ends at ready, and the partner delivers the file. No route is connected to a rail on the hosted sandbox yet, and a route that has no credential reaches submitted without anything being sent. Production sending needs the client's own access to each rail (see rail credentials).
Germany: DE-XRECHNUNG
In the sandboxvalidation
Receiving an e-invoice has applied since 1 Jan 2025. Issuing applies from 1 Jan 2027 if the previous year's turnover was over EUR 800,000, and to everyone from 1 Jan 2028. Source: BMF FAQ, with the basis in §14 UStG.
No platform is required. The invoice goes to the buyer through any channel the two agree. Peppol is one channel for a German B2B invoice, not a requirement, and email of an XRechnung or ZUGFeRD file is also lawful (see the BMF source above). The service checks the file. The invoice ends at ready, and the partner delivers it. Peppol reports delivered; an email gives only that it was sent.
More at eurinvoice.com: Germany.
Peppol: PEPPOL
In the sandboxvalidation
The buyer's participant id and its scheme are required, as buyer.endpoint. The service checks the scheme code. It does not check that the buyer is registered on Peppol. An access point reports a buyer it cannot reach, and that is a rejection (see statuses); this has not been seen on a live access point.
Self-billing is a separate Peppol profile and is not supported.
Belgium is the Peppol example: all VAT-registered B2B invoices from 1 Jan 2026, with Peppol as the default (tolerance ended 31 Mar 2026). Source: efactuur.belgium.be. More at eurinvoice.com: Belgium.
France: FR-PA
In the sandboxvalidation
Every French business receives e-invoices from 1 Sep 2026. Large and mid-size companies issue from 1 Sep 2026, and SMEs and micro-enterprises from 1 Sep 2027. E-reporting follows the same calendar. Source: impots.gouv.fr.
The invoice goes through a Plateforme Agréée, which the client chooses. Four lifecycle statuses are mandatory in the DGFiP specification (v3.2, section 3.6.4): 200 Déposée, 210 Refusée, 212 Encaissée and 213 Rejetée. A buyer without an address on a platform is expected to be a failure, not a delivery; the sandbox has not confirmed that.
The client's own platform account, its consent, and the platform's identity and company checks come before its address is registered. They sit outside our clock (see before go-live). More at eurinvoice.com: France.
Poland: PL-KSEF
In the sandboxvalidation
Receiving applies from 1 Feb 2026. Issuing applies from 1 Feb 2026 to large companies (2024 sales over PLN 200 million) and from 1 Apr 2026 to everyone else. Invoices up to PLN 10,000 gross a month may stay outside KSeF until 31 Dec 2026. Penalties start on 1 Jan 2027 by law. A draft bill of 23 Sep 2026 would move them to 1 Jan 2028, and it is not law yet. Source: ksef.podatki.gov.pl and the Ministry's notice.
The invoice counts as issued on the day it is sent to KSeF, and as received when KSeF assigns the number (art. 106na of the VAT Act). KSeF has no buyer statuses and cannot cancel or delete an invoice: a wrong buyer NIP is fixed with a correction to zero and a new invoice.
Sending is capped (see limits). More at eurinvoice.com: Poland.
Romania: RO-EFACTURA
In the sandboxvalidation
RO e-Factura has applied to B2B invoices since 2024 (Law 296/2023). An invoice goes to ANAF within five working days of its issue date (OUG 89/2025); see limits for how the clock is counted. Source: Law 296/2023 and OUG 89/2025.
Upload needs the client's authorisation of our ANAF application (see rail credentials). More at eurinvoice.com: Romania.