1 Start here1.4
How a go-live runs
The steps from a complete client list to the monthly care service, and who does what.
- In the sandboxreadiness gate
- Plannedno go-live has run yet
In plain words
A go-live is one fixed piece of work for one legal entity, one export from its ERP (its business software), one country route and one outbound invoice family. It starts when the client's list is complete, runs to a first valid test invoice and 14 days of fixes, then goes on as a monthly care service. No go-live has run for a client yet, so this page is the plan, not a record.
What one go-live covers
- One legal entity, with its tax ID in the country of the route.
- One ERP export. Business Central and SAP Business One are mapped (see mapping versions).
- One route: Germany, Peppol, France, Poland or Romania (see routes and countries).
- One outbound invoice family: the invoices the client issues. Receiving invoices is not included (see what eurinvoice does not do).
Anything beyond that is agreed and quoted separately. Prices are in the partner offer, not in these docs.
Who does what is agreed in writing for each case. The lists below show the usual split: the partner owns the ERP configuration and the conversation with the client, and eurinvoice owns the mapping, the country checks, the route and the handover. A client who buys directly has no partner, so its own team takes the partner's part.
The client's list is complete
The client brings the list on what the client brings: a sample export that covers every invoice variant, working access to the source, a route with an active sandbox, a credential for the route's network or authority, written tax decisions, a named technical owner and a place for returned status. We run the readiness check and record GO or NO-GO. The clock starts at GO, not at contract signature.
Note
Some steps sit outside the clock: platform onboarding and identity checks, taxpayer authorisation, the client's own acceptance testing and third-party availability.
- Client: brings the list and the written decisions.
- Partner: names the technical owner for the work window.
- eurinvoice: runs the readiness check and records GO or NO-GO.
The first valid test invoice
The target is a first valid test invoice within two working days after readiness. We map the client's export and run dry runs until a test invoice passes every check for the route. A dry run sends nothing. When a check fails, the answer names the field in the client's export and says who fixes it: us for our mapping, the partner or client for the ERP data (see errors).
Note
Sandbox
A valid test invoice passes every check and the legal file is built. The hosted sandbox holds no rail credential yet, so nothing is sent to a rail (the network or tax platform that carries the invoice) and no authority or access point sees the invoice there.
- Client: answers questions about its data and corrects what a finding names.
- Partner: fixes the ERP configuration that a finding points at.
- eurinvoice: maps the export, runs the dry runs and fixes the findings that are ours.
Fourteen days of defect fixes
For 14 days after the first valid test invoice, we fix defects in the mapping and in the files we build. Production keys follow the go-live checks (see sandbox and production).
- Client: tests its own invoice variants and reports what looks wrong.
- Partner: collects the reports and passes them on.
- eurinvoice: fixes the defects and issues the production key after the go-live checks.
Rejection Care, every month
After go-live, a monthly service owns the failed invoices. An invoice the route rejects for good lands on the care list: what is wrong, which field, and who acts. We never send a rejected file again as it is. The data is fixed in the ERP and a corrected invoice is submitted. The service level is in the contract, not in these docs.
- Client: fixes its own data when a rejection names it.
- Partner: fixes the ERP configuration and tells the client.
- eurinvoice: goes through each rejection, says who acts and fixes what is ours.
What a go-live does not include
- We rent the rails. We are not a Peppol access point and not a French Plateforme Agréée, and we are not the client's legal archive.
- The rail's own onboarding and identity checks stay with the client, and they run on the rail's time.