For companies with an existing system
Will your invoice be accepted by the recipient?
Send us one of your invoices. We check it with the same procedure the recipients use and tell you within a day what passes and what is missing. Free and without obligation.
Where migrations actually fail
Not on the format. Producing the XML file is the smallest part of the work — the effort sits in the data your system has to supply for it.
- The routing ID (Leitweg-ID) of your public-sector customers is nowhere in the customer record.
- Credit notes need a reference to the original invoice that your system never stored.
- Tax categories work in the standard case but not for reverse charge or intra-community supply.
- Custom fields grown over years do not map onto the EN 16931 standard.
- The recipient accepts the invoice technically but rejects it on substance — and nobody notices until the payment fails to arrive.
This data work happens once. After that the process runs. That is exactly the part we take on.
The readiness check
Free, no registration, and useful even if we never work together.
- Step 1
You send us a sample invoice
A real invoice from your system — as PDF, XML, or both. Plus a note on which system produced it and who it goes to.
- Step 2
We check it against the official rules
Validation against the KoSIT schemas and Schematron business rules — the same procedure public authorities and large recipients use on incoming invoices.
- Step 3
You receive a written finding
Within one working day: what passes, what is missing, which fields are unmaintained in your system — and an honest estimate of the effort.
The finding is yours. You can act on it yourself or hand it to another provider.
Check an invoice yourselfThe integration project
If you would rather not handle the migration yourself: fixed price, fixed timeframe, responsibility for the outcome on our side.
Phase 1Analysis
3–5 daysExisting system, data model, recipient base, and your specific obligation. The result is a clear picture of what actually needs doing.
Phase 2Mapping
5–10 daysYour master data is mapped onto EN 16931: mandatory fields, routing IDs, tax logic, and the edge cases every grown system carries.
Phase 3Integration
5–10 daysTechnical integration into your system, including error handling and retry logic — so a rejected invoice surfaces instead of disappearing.
Phase 4Test operation
3–5 daysValidation against real documents and, where possible, alignment with an actual recipient. Go-live only once that holds.
Phase 5Go-live
2–3 daysCutover during live operation, handover to your team, and documentation of what was mapped where.
Not included
For the fixed price to hold, the scope is clearly bounded. These points are explicitly outside it:
- Changes to the source system beyond the invoice data
- Bookkeeping or tax advice
- Migration of historical records older than twelve months
- Bespoke layout development beyond one template
- Operating your own infrastructure
Whether this is worth it for you
An honest assessment — including where the answer is no.
A fit if
- you run a grown ERP, inventory system, or shop
- you invoice public-sector clients or business customers
- you have little or no in-house development capacity
- a deadline is approaching, or invoices have already been rejected
Not a fit if
- you sell exclusively to consumers — then no obligation applies
- your accounting software already covers the migration completely
- you have an in-house development team that wants to build it
- you issue fewer than twenty invoices a month — a tool will do
Frequently asked questions
- What does the readiness check cost?
- Nothing. We check a sample invoice free of charge and without obligation. The finding is yours — including if you go on to do the work yourself or hire someone else.
- What does an integration project cost?
- Between €6,000 and €15,000 as a fixed price, depending on scope. The range comes from the number of edge cases in your data and how many recipient types need serving. After the readiness check we can say this reliably — before it, any number would be a guess.
- Who is liable if an invoice is rejected anyway?
- Legally, the invoice issuer is always liable — no provider changes that. What we do commit to: if we deliver the integration, we take contractual responsibility for invoices from your system being accepted by the recipient. That is tested against real documents before go-live, not merely asserted.
- Do we have to switch software?
- No. The entire approach is to integrate your existing system rather than replace it. A system migration costs more, takes longer, and carries risks that have nothing to do with e-invoicing.
- How long does the migration take?
- Four to six weeks to go-live, depending on how quickly we get access to systems and contacts. If a recipient has to be involved in the test phase, their response time can set the pace — we plan for that.
- What happens after go-live?
- Ongoing operation carries a monthly service fee for the technical processing. Optionally we continue looking after it: format updates, deadline monitoring, and a named contact when something goes wrong.
Let us start with one invoice
The fastest route to a reliable answer: you send us a real document, we tell you where you stand.
Free, without obligation, findings within one working day.