R
How it worksDelivery sequence
- 01
- Scope
- 02
- Map
- 03
- Validate
- 04
- Test
- 05
- Go live
- 06
- Monitor
E-mail
[email protected]How it works
From one case to accepted invoices.
Six steps, one written scope and a clear line between what you own, what we own and what the network owns. The two-working-day target starts when readiness is complete, not when the contract is signed.
E-invoice flow
How an e-invoice travels
Your ERP's invoice is converted, checked and sent over the country's network, and a receipt comes back. In Poland, KSeF must accept each invoice and give it a number.
- 01
Your ERP
Creates the invoice as it does today.
- 02
Mapping
Each field goes into the format the country requires.
- EN 16931
- FA(3)
- XRechnung
- Factur-X
- CIUS-RO
- 03
Validation
The file is checked against the official rules before it is sent.
- XSD
- Schematron
- 04
Sending
It travels over the country's own route.
- Peppol
- KSeF 2.0
- Plateformes Agréées
- myDATA
- SdI
- RO e-Factura
- 05
Receipt
Status, ID and any rejection come back to your ERP.
How it works
Six steps, and who does what in each
- 01
Scope
One call on the ERP, the country, the entity and the volumes. The scope and the price are then put in writing.
- Your team
- Brings the case and the entity’s details
- EurInvoice
- Checks it against the standard unit
- 02
Map
The ERP's invoice data matched to EN 16931 and the country's format.
- Your team
- Gives access and representative invoices
- EurInvoice
- Builds the mapping table
- 03
Validate
Every variant checked against the official rules.
- Your team
- Decides tax codes and identifiers
- EurInvoice
- Runs the rule sets and fixes the mapping
- 04
Test
Invoices sent through the route's test environment.
- Your team
- Arranges the test credentials
- EurInvoice
- Sends, confirms and maps the status
- 05
Go live
The first live invoices sent and confirmed.
- Your team
- Runs UAT and signs off
- EurInvoice
- Watches the first live invoices
- 06
Monitor
Rejections handled, and a report every month.
- Your team
- Fixes data at source when asked
- EurInvoice
- Triage, mapping fixes and the monthly report
Readiness inputs
What starts the clock
The first valid test invoice is due two working days after all seven of these are in place.
Outside the clock: platform onboarding and KYC, taxpayer authorisation, UAT and the availability of third parties.
- 01A representative set of invoices, covering every variant in scope
- 02Working access to the source, or a stable file or API handoff
- 03Test credentials, certificates and taxpayer authorisation, issued to you
- 04The route chosen, with its test environment active
- 05A technical owner on your side, available during the window
- 06Written decisions on tax codes, exemptions, payment data and identifiers
- 07A callback, file location or queue for the returned status
Integration boundary
Who owns what
Your team
- Tax decisions: codes, exemptions and identifiers
- The ERP licence, its configuration and the source data
- Approvals, UAT and go-live sign-off
EurInvoice
- Mapping, validation and the route integration
- Returned status and rejection detail
- Handover, and Rejection Care if chosen
The network
- Carrying the invoice to the buyer or the tax platform
- Its accreditation as access point, approved platform or government system
- Its own fees, onboarding and KYC
Returned result
The status your ERP gets back
Every route answers differently. We turn each answer into one event the ERP can read, with the route's own code kept alongside.
- Received
- Validated
- Submitted
- Accepted
- Delivered
Or, when something failsSource errorValidation failedRejected
Contact
Start with the scoping call.
Thirty minutes on the ERP, the country and the entity. You leave with a written scope, or a clear reason it does not fit.
- Your ERP and version
- The first country route and legal entity
- A representative invoice and where the credentials stand
30-minute call
Choose a time