Resource · Readiness checklist
The e-invoicing readiness checklist.
Plain-English checklist for getting your business ready for global e-invoicing mandates, Peppol, ZATCA, EN 16931 alignment. Use it to audit where you are, what you need, and who is accountable.
Dates that matter
Key deadlines, by region.
Confirm with your local tax authority, these are accurate as of writing but mandates move.
UAE, Peppol PINT AE
- ·1 Jul 2026, Pilot phase opens (voluntary, FTA-selected participants)
- ·31 Jul 2026, ASP appointment deadline for businesses ≥ AED 50M revenue
- ·1 Jan 2027, Mandatory for large businesses (Phase 1)
- ·31 Mar 2027, ASP appointment deadline for all other VAT-registered persons
- ·1 Jul 2027, Phase 2 mandatory: e-invoicing for everyone in scope
Singapore, InvoiceNow
- ·1 Nov 2025, Mandatory for new GST registrants
- ·Apr–Jun 2026, Existing GST-registered businesses follow in waves
EU, ViDA + national mandates
- ·Italy, France (B2B 2026), Spain, Poland, Belgium, already mandated or scheduled
- ·2030, Cross-border B2B mandatory under ViDA across EU
Saudi Arabia, ZATCA
- ·Live in waves since 2021, Phase 2 (integration) ongoing for businesses by revenue band
The four readiness pillars
What to fix before the mandate fixes you.
Each of these is a small project. Done together, they're the difference between a clean go-live and a fire drill.
Master data & chart of accounts
- Every customer, supplier, and product has a clean, unique record
- Tax IDs (TRN, VAT number, GSTIN, EORI, etc.) captured on every counterparty
- Tax codes mapped to the correct treatment (standard, reduced, zero, exempt, out-of-scope)
- Chart of accounts reviewed against the e-invoice spec your jurisdiction uses (PINT AE, PINT SG, EN 16931, ZATCA, etc.)
Invoice content + format
- All mandatory fields present in your accounting output
- UUID generation in place per invoice and credit note
- Currency, rounding, and line-level tax breakdown match your jurisdiction's spec
- Credit notes correctly reference original invoice IDs
- Discounts, surcharges, and shipping handled the way the network expects
Access Point + transmission
- Accredited Service Provider / Access Point appointed before your jurisdiction's deadline
- Peppol endpoint registered under your legal entity (where applicable)
- Outbound flow tested end-to-end through the ASP sandbox
- Inbound flow configured for invoices from suppliers
- Failover plan if your ASP has an outage on a tax-sensitive day
Process + controls
- Sign-off on who issues, amends, and cancels invoices
- Retention policy for XML payloads aligned to your jurisdiction's archive rules
- Reconciliation between ERP, ASP, and tax authority records
- Staff trained on the new issue-and-clear flow
- Monitoring + alerting if invoices fail validation or transmission
If your ERP needs sorting first
That's an Odoo conversation.
Most e-invoicing readiness work comes back to clean master data and a properly configured accounting backbone. We do that.