1 Start here1.1
What eurinvoice is
What the service takes in, checks, builds and records.
- In the sandbox
In plain words
eurinvoice takes a client's invoices from its ERP (its business software), checks them against the rules of one country, builds the legal file and records what happens next. The connection to the tax authority or the invoice network is rented, because we are not an access point or a platform ourselves. Today it runs as a sandbox in Frankfurt, on sample data.
eurinvoice is one Java service. It takes a client's invoice from an ERP, checks it, builds the legal file and records what happens next.
What goes in
Three kinds of input. Each arrives by API call or as a file in a drop directory (see file drop):
- An ERP export. Business Central and SAP Business One are mapped.
- Canonical JSON, our own invoice model.
- A finished UBL, CII or FA(3) XML file.
What it does
- Checks the invoice against the canonical schema and the rules of the route.
- Builds the file the route needs: UBL, CII, FA(3), or a ZUGFeRD PDF for Germany.
- Queues the invoice.
- Records the result as status events.
A finished XML file skips the canonical check and the build. It gets a safety check and the route's own validators, then goes to the queue (see submit XML).
Five routes are checked: Germany (XRechnung and ZUGFeRD), Peppol, France (Plateforme Agréée), Poland (KSeF) and Romania (e-Factura). Routes and countries lists what each one runs.
What one engagement covers
The unit is one legal entity, one ERP export, one country route and one outbound invoice family. After go-live, a monthly care retainer covers rejected invoices. Prices are in the partner offer, not in these docs.
Where it runs
In the sandboxsandboxThe sandbox runs on AWS in Frankfurt, on sample data (see hosting and data). It holds no rail credential yet, so a route there that needs one reaches submitted and nothing is sent to a rail. What eurinvoice does not do says more.