Mandatory e invoicing has moved from a handful of pioneers to a global norm. Tax authorities on every continent now require, or are phasing in, invoices that are created in a structured electronic format and reported to, or cleared by, the authority itself. The programmes differ in names, dates and thresholds, but the technical pattern behind them is remarkably consistent, and it is a systems project rather than a change of invoice template.
Two models, one direction
In a clearance model the invoice is sent to the tax authority's platform and validated before it is legally valid and shared with the customer. In a reporting model the invoice is issued to the customer and its data is transmitted to the authority within a defined period. Many countries combine the two: clearance for business to business invoices, reporting for retail receipts. Either way, the authority sees every invoice, and the company's system must be able to talk to it.
What the requirements have in common
A structured format, usually XML based on an international standard rather than a PDF. A unique identifier per invoice. Some form of authentication: a digital signature, a cryptographic stamp or a code issued by the platform. Often a link between consecutive invoices so that none can be deleted unnoticed, and a QR code on the human readable copy. Registration of the software or device that issues invoices, with certificates that expire and must be renewed. And retention of the electronic invoice for the statutory period in a form that can be retrieved and presented.
What that means for your ERP
Few ERP systems produce compliant invoices out of the box, and those that do often require a recent version and country specific configuration. There are two practical routes: upgrade and configure the ERP, or place an integration layer between the ERP and the authority that takes the invoice data, builds and signs the document, submits it and writes the result back. The right choice depends on the ERP version, the invoice volume and how many systems in the group issue invoices.
The onboarding steps that are underestimated
Obtaining the certificates, passing the authority's compliance tests with sample invoices of every type, and repeating the process for each issuing system and each legal entity. Certificates then expire on a schedule the business does not control. A plan with owners and dates for every entity and every system, made well before the deadline, is what separates a calm go live from a scramble.
Rejections are the daily reality
Every submission is validated. Invoices are rejected for missing fields, wrong tax categories, inconsistent totals or a broken chain. A working integration is not one that submits; it is one that shows every rejection to a person, with the reason, and lets them correct and resubmit before the customer or the deadline is affected. Without that, errors accumulate silently until the tax filing.
Archiving is part of the mandate
The signed electronic invoice, its readable copy and the submission result must be kept, per entity, for years, and be searchable when the authority or an auditor asks. Many ERP systems do not store the signed file at all, so the archive has to be designed rather than assumed.
A checklist that works in any country
Know your deadline and threshold. List every system that issues invoices in every entity. Confirm what each can produce today. Choose between upgrade and integration layer. Plan the certificate and testing steps with dates. Decide who handles rejections and how. Decide where the archive lives, who can search it and how long it is kept. None of these steps is difficult on its own; the difficulty is doing all of them, for every entity, before the date.
A note on what ADVITECS does
ADVITECS does not provide an e invoicing solution. This article is general guidance for companies planning for the requirement. Where we help is around it: the process study before the project, the selection and oversight of the vendor that implements it, the integration of your systems, and the reporting that shows whether the numbers are right.
Key takeaways
- Mandates differ by country but share one technical pattern: structured format, authentication, reporting and archiving.
- Most ERP systems need an upgrade or an integration layer to comply.
- Certificates, compliance tests and rejections need owners and dates per entity.
- The archive of signed invoices has to be designed; the ERP may not keep it.
Want to apply this in your company?
A conversation costs nothing and usually clarifies a lot. We will tell you honestly whether and how we can help.
