R
SendingIn the standard unit
- Tested
- KSeF 2.0 · ANAF · Peppol access point · French platform
- Status
- One event format for every route
- Delivery
- Signed webhook, file drop or queue
Choose
The route and provider, named in the scope.
Sending
Sent over the country's own route, with the receipt back.
We do not run a network. We connect your invoices to the right one: a certified Peppol access point, a French Plateforme Agréée, or the government’s own API where the country allows direct integration, as KSeF and RO e-Factura do. The route is named in the scope before work starts.
Sending
What sending covers
- 01
The route, chosen per country
Government API, Peppol access point or approved platform, whichever the country and you need. We name the provider in the scope.
- 02
Test environment first
Every route is run in its test environment before a live invoice goes out.
- 03
One status format
KSeF, ANAF, Peppol and the French platforms all answer differently. You get one event: received, validated, submitted, accepted or delivered, or the reason it failed.
- 04
The legal ID
Where the route issues one, it comes back with the status: the KSeF number, ANAF's upload index or the platform's invoice ID.
- 05
Credentials stay with you
Certificates, tokens and taxpayer authorisations are issued to you. Our evidence records that they exist, never the secret.
- 06
Rejections with their code
A refused invoice comes back with the platform's own code and message.
Sending
What each route sends back
| Country | Route | What comes back |
|---|---|---|
| Poland | KSeF 2.0 API | The KSeF number and UPO, or an error code such as 440 |
| Romania | RO e-Factura (ANAF) | An upload index, then the state: ok, or nok with the error |
| Belgium | Peppol access point | Sent or failed, and the buyer's response where one is given |
| France | Plateforme Agréée | Lifecycle codes, from 200 Déposée to 213 Rejetée |
| Germany | Agreed channel | Whatever the channel agreed with the buyer returns |
| Greece | myDATA provider | The MARK registration number |
What we need from you
What we need from you
- Test credentials, certificates or authorisation, issued to you
- The chosen route, with its test environment active
- A callback URL, file location or queue for the status
What you get back
- Test invoices sent and confirmed in the route's test environment
- The route's ID and status for each invoice
- Status events in one format, whatever the route
KSeF number 7443889269-20260926-9AC1F4000000-9D.
Issued by the KSeF 2.0 test environment on 26 September 2026, with its UPO. A second copy of the same invoice was rejected as a duplicate (440), as it should be.
See the evidenceSteps
From test to live
Questions
Sending
Are you a Peppol access point or an approved platform?
No. We send through a certified access point or approved platform, or through the government API where the country allows direct integration. The provider is named in the scope.
Who pays the platform's fees?
Platform and licence fees are not part of the standard unit price. They are passed through at cost and named in the scope.
Contact
Tell us the country and the ERP.
We will name the route we would use, what it sends back and what you need to authorise.
- Your ERP and version
- The first country route and legal entity
- A representative invoice and where the credentials stand
E-mail
[email protected]30-minute call
Choose a time