A format changes
Handled inside the ERP
The ERP output is rewritten, regression tested and released.
With Easy-Invois
A mapping change here. The ERP output is not touched.
E-invoicing · multi-country
The mandate changes. Your ERP doesn't.
Easy-Invois generates, validates, submits and archives electronic invoices from the ERP you already run. When a tax authority changes its rules, the change lands here rather than in your finance system.
What is in the box
GenerationInvoices raised from the ERP and business systems you already use
Validation engineRegulatory and business rules checked before anything is sent
SubmissionAuthority portals and e-invoice networks, with status returned
Archive & auditInvoice, submission and acknowledgement kept together
- Existing invoice workflows stay as they are
- Per-country rules configured, not coded
- Every invoice traceable to its acknowledgement
What it does
Every country changes its rules on its own schedule
That is the part finance teams underestimate. The first implementation is a project; the next four years are a series of unannounced format revisions, and the question is where each one lands.
| When it happens | Handled inside the ERP | With Easy-Invois |
|---|---|---|
| A format changes | The ERP output is rewritten, regression tested and released. | A mapping change here. The ERP output is not touched. |
| A rule is added | Discovered when the authority starts rejecting submissions. | Checked before submission, so the error never leaves the building. |
| Something is rejected | Found by someone logging into a portal, then chased by hand. | Status tracked to acknowledgement, with the reason attached to the invoice. |
| A second country | Another project, often another vendor, and a second way of working. | The same path, with that country's rules configured alongside the rest. |
| An audit | Invoices in one system, submissions in another, evidence assembled by hand. | Invoice, submission and acknowledgement archived as one record. |
A rule is added
Handled inside the ERP
Discovered when the authority starts rejecting submissions.
With Easy-Invois
Checked before submission, so the error never leaves the building.
Something is rejected
Handled inside the ERP
Found by someone logging into a portal, then chased by hand.
With Easy-Invois
Status tracked to acknowledgement, with the reason attached to the invoice.
A second country
Handled inside the ERP
Another project, often another vendor, and a second way of working.
With Easy-Invois
The same path, with that country's rules configured alongside the rest.
An audit
Handled inside the ERP
Invoices in one system, submissions in another, evidence assembled by hand.
With Easy-Invois
Invoice, submission and acknowledgement archived as one record.
How it fits together
Beside the ERP, not inside it
Your finance system keeps raising invoices the way it does today. Everything the mandate requires happens after that, and the result comes back as a status your team can see.
Scroll the diagram sideways →
The lifecycle
An invoice is not issued until the authority says so
Under a clearance model the document your customer receives is the one that came back approved. Everything before that point is a draft, which is why validation happens before submission rather than after a rejection.
- RaisedThe ERP posts the invoice exactly as it does now
- ValidatedCountry and business rules applied before anything leaves
- SubmittedSent to the authority portal or the network
- ClearedThe approved reference comes back and is stored with the invoice
- ArchivedInvoice, submission and response kept as one searchable record
Capabilities
Three jobs, one path
Generate it correctly, get it accepted, and be able to prove both a year later.
Generate from the source
We build invoices from the record that already exists in your ERP or billing system, so the numbers on the e-invoice and the numbers in your ledger cannot drift apart.
- Raised from ERP, billing or order systems
- Existing approval workflows left in place
- Exceptions still enterable by hand
Validate before you submit
We apply regulatory and business rules while the invoice is still yours to fix. A rejection from an authority costs a day; a rule caught here costs a click.
- Country rules maintained as configuration
- Business rules applied alongside them
- Failures returned with the field at fault
Keep the evidence together
We archive the invoice, what was submitted, and what came back as one record. An audit question becomes a search rather than a reconstruction across three systems.
- Full status history per invoice
- Acknowledgements stored with the document
- Searchable for audits and internal review
Coverage & deployment
Where it applies, and where it runs
We answer this first, because for e-invoicing the only question that matters early is whether you cover the countries a business actually invoices in.
- MalaysiaMalaysian e-Invoice submission and clearance.
- Saudi ArabiaZATCA e-invoicing requirements.
- European UnionEU VAT rules and the Peppol network.
- ElsewhereCountry-specific formats are added by configuring their rules. Ask us about a jurisdiction not listed.
- NetworksPeppol, plus direct submission to authority portals where a country requires it.
Under the hood
What it connects with
Standard interfaces into your systems, and the formats each jurisdiction actually requires on the way out.
Into your systems
Reads what you already use
Standard interfaces into the ERP, finance and billing tools your team already runs.
REST APIsERP connectors
Out to authorities
Delivers what the mandate expects
The formats, portals and networks each jurisdiction actually requires on the way out.
PeppolCountry-specific formatsAuthority portals
Who uses it
Four teams, one path
It is deployed in retail, distribution, manufacturing and services, where invoice volume is high enough that a rejection rate becomes a cash flow problem.
Finance & accounting
Invoices go out and get accepted, without anyone learning a new way to raise them.
Submission queueIT & integration
One connector to maintain, and a mandate change that does not become an ERP release.
ConnectorsCompliance & tax
Rules held in one place, and evidence that can be produced without a project.
Rules & archiveOperations
Rejections visible while they can still be fixed, rather than at the month-end review.
Status trackingQuestions
Answers before you ask
Malaysia, Saudi Arabia and the EU through Peppol are the ones we are asked for most often. The honest answer for anywhere else is that adding a country format is configuration work, so the question is how much a specific jurisdiction takes, and that is worth a direct conversation rather than a claim on a page.
Get started
Request a demo
Tell us which countries you invoice in and what raises the invoice today. We will schedule a short walkthrough of Easy-Invois.
- A submission and a clearance, end to end
- What a rejection looks like before it reaches the authority
- A sequenced plan with effort ranges, written for your team