E
Glossary
E-Invoicing Mandate
An e-invoicing mandate is a legal requirement to issue invoices as structured electronic data and transmit them through a channel the tax authority specifies. Some governments validate each invoice before it becomes legally valid. Others accept the invoice and inspect it later. A PDF sent by email satisfies neither.
Key Takeaways
The mandate governs transmission, not arithmetic. Calculating tax and delivering the document to the government fail separately.
Clearance countries put the state inside the invoice path. Poland's law means a business outside KSeF can't issue a valid sales invoice.
Post-audit countries never see the invoice in flight. Germany requires receipt of EN 16931 invoices from 1 January 2025 and issuance from 1 January 2027 above EUR 800,000 turnover.
France switched on the largest new mandate of 2026 on 1 September, with SMEs following 1 September 2027.
Thresholds move more than start dates. Malaysia's fourth phase covers turnover up to RM5 million from 1 January 2026, yet exempts taxpayers under RM3 million.
What does an e-invoicing mandate actually require you to send?
A mandate is a published specification, usually a schema you validate against, and missing any one part makes the invoice non-compliant even when the amounts are right.
What a mandate pins down:
A format. Structured XML or a hybrid such as Factur-X, usually profiled against EN 16931.
A channel. The government platform in clearance countries (India's Invoice Registration Portal, Italy's Sistema di Interscambio, Poland's KSeF), or an accredited private platform under France's five-corner model.
A deadline. Saudi Arabia clears standard B2B invoices before the buyer sees them, and allows 24 hours to report simplified B2C invoices.
An identifier and an archive. India returns an Invoice Reference Number, and an invoice without one isn't a tax invoice. Local law sets retention.
Calculating the tax and transmitting the invoice are separate duties. A tax engine settles the rate; the mandate decides who else sees the finished document, and in what shape. Different parts of the billing stack own each one.
Which countries have an e-invoicing mandate in force, and which are still scheduled?
Both, and the scheduled ones keep moving: Poland, France, and Malaysia have each been re-timed at least once. I checked every date below against a government or Big Four source on 8 September 2026.
Jurisdiction | Model | Status and date |
Clearance via an Invoice Registration Portal | In force since 1 August 2023, above INR 5 crore turnover | |
Clearance through the Sistema di Interscambio | In force since 1 January 2019 | |
Clearance for standard B2B, 24-hour reporting for simplified B2C | Phase 1 from 4 December 2021, Phase 2 integration in waves since 1 January 2023 | |
Clearance, no valid invoice outside the platform | In force 1 February 2026 above PLN 200 million, 1 April 2026 for other VAT-registered businesses, 1 January 2027 for micro-entrepreneurs | |
Decentralised five-corner, accredited private platforms | In force 1 September 2026 to receive, and to issue for large and mid-cap; 1 September 2027 for SMEs | |
Central validation by the revenue board | In force. Phase 4, turnover up to RM5 million, from 1 January 2026; under RM3 million exempt | |
Post-audit, no platform in the invoice path | Receiving in force since 1 January 2025, issuing 1 January 2027 above EUR 800,000 turnover, all 1 January 2028 | |
Digital reporting layered over national systems | Scheduled. Cross-border B2B reporting from 1 July 2030, national alignment by 1 January 2035 |
Brazil and Mexico run long-established clearance regimes, and I left them out on purpose: neither produced a citable official date in this check.
How do teams keep up when every country writes its own schema?
They stop running each mandate as a country project and treat it as field mapping. Eight jurisdictions means eight schemas asking for overlapping data that already sits in billing records.
What survives more than two mandates:
Capture mandate fields at contract time, not invoice time: buyer tax IDs, an Italian or Polish routing address, a French SIREN, a Malaysian TIN.
Keep the pre-final invoice mutable. Clearance rejection is a correction cycle, and a draft invoice you can fix and resubmit handles it in minutes.
Watch what clearance does to grouping. Schemas expect one document per seller and buyer pair, squeezing consolidated invoicing across a parent and its subsidiaries.
Where the invoice data lives decides how much this hurts. Store line items, tax breakdowns, and tax identifiers as structured records and you have a mapping job. Render straight to PDF and you have a rebuild, which is why invoicing architecture gets revisited when a mandate lands.
Related terms
An e-invoicing mandate sits where billing operations meet tax law, so these come up alongside it.
Billing vs Invoicing draws the line this page rests on: a mandate governs the document, not the calculation behind it.
Tax Engine handles the rate and amount the mandated invoice then carries.
Sales Tax for SaaS covers the US side, where taxability and nexus matter more than transmission rules.
Consolidated Invoicing gets constrained by mandates expecting one document per seller and buyer pair.
Draft Invoice matters here because a rejected submission has to stay editable before you can resubmit it.
Merchant of Record shifts who satisfies the mandate, since the legal seller is on the hook.
FAQ
Is a PDF invoice enough to satisfy an e-invoicing mandate?
No. These mandates require structured data validated against a schema, and a PDF is a rendering, not data. Germany drops unstructured electronic formats from 1 January 2027 above EUR 800,000 turnover. Hybrids like Factur-X pass because they embed the XML inside the file.
Does an e-invoicing mandate apply to a company with no local entity?
Sometimes, and the answer changes by country and date. France defers the issuing obligation to September 2027 for businesses that aren't established there but owe French VAT. Local VAT registration is the trigger to check, not physical presence.
Is e-invoicing the same as e-reporting?
No. E-invoicing changes how you deliver a document to your buyer; e-reporting changes what transaction data you hand the tax authority. France runs both from 1 September 2026, with reporting covering the B2C and cross-border flows its e-invoicing rule excludes.
Back to glossary
