The shift in 2026: Global tax authorities are moving from post-audit compliance to Continuous Transaction Controls (CTC) — every invoice validated by the state in real time before it's legally valid. For multinational cloud providers, this is no longer a document formatting problem. It's a core infrastructure challenge.
- → Structured e-invoicing mandatory for all intra-EU B2B by July 1, 2030
- → Buyer consent for e-invoices eliminated — paper/PDF no longer legal standard
- → Real-time transaction data feeds replace periodic VAT returns
- → Platforms become deemed suppliers for accommodation & transport from July 2028
- → Must collect and remit VAT — split transaction model
- → Requires classifying VAT status of thousands of underlying suppliers
- → One-Stop-Shop expanded to cover more transaction types
- → Reduces need for local VAT registrations across 27 member states
- → Simplifies cross-border B2C compliance
| Country | System | Model | Key Date | Status | Format |
|---|---|---|---|---|---|
| 🇫🇷 France | PPF / PDP | Y-Model (Clearance) | Sep 1, 2026 | Transitional | Factur-X / UBL |
| 🇵🇱 Poland | KSeF 2.0 | Central Clearance | Feb 1, 2026 ✓ | Live | FA(3) XML |
| 🇩🇪 Germany | EN 16931 | Post-Audit → CTC | Jan 1, 2027 | Upcoming | XRechnung / ZUGFeRD |
| 🇷🇴 Romania | RO e-Factura | Central Clearance | Jul 1, 2026 (SMEs) | Transitional | XML UBL |
| 🇮🇹 Italy | SdI v1.9.1 | Central Hub | May 15, 2026 ✓ | Live | FatturaPA XML |
| 🇲🇾 Malaysia | MyInvois | Pre-Clearance API | Jan 1, 2026 ✓ | Transitional | JSON / XML |
| 🇵🇭 Philippines | EIS | Real-Time API + JWS | Dec 31, 2026 | Upcoming | JSON (signed) |
| 🇻🇳 Vietnam | GDT / Decree 70 | Central Clearance | Jun 1, 2025 ✓ | Live | XML |
| 🇸🇬 Singapore | InvoiceNow | Peppol Network | Apr 1, 2026 ✓ | Live | Peppol BIS |
| 🇲🇽 Mexico | CFDI + Rule 2.9.21 | Pre-Clearance + DB Access | Apr 1, 2026 ✓ | Critical | XML (SAT) |
| 🇧🇴 Bolivia | SIAT | Online Clearance | Apr 1, 2026 ✓ | Live | XML |
EU ViDA (VAT in the Digital Age), formally adopted March 2025, is the most ambitious tax reform since the single market. Three pillars: Digital Reporting, Platform Economy liability, and Single Registration. The catch: member states are implementing independently — creating a fragmented patchwork before 2030 harmonization.
- Mandate confirmed by 2026 Finance Bill (Feb 2026). Sep 1, 2026: all French-established companies must be capable of receiving e-invoices.
- Y-Model: businesses choose between the government PPF portal or a certified private PDP platform. Both must connect to the same network.
- Issuance deadlines: Large enterprises & mid-caps must issue e-invoices + submit e-reporting from Sep 2026. SMEs and micro-enterprises follow in 2027.
- E-reporting scope (critical for cloud providers): covers international B2B, B2C, and intra-community acquisitions. Foreign sellers without French establishment shift the obligation to the French buyer.
- Formats accepted: Factur-X, UBL 2.1, CII. Must carry SIREN/SIRET, buyer VAT number, routing ID of target PDP/PPF.
- Archiving: 10 years, readable format, accessible to tax authority.
- KSeF 2.0 is fully operational. Large taxpayers (turnover >PLN 200M) mandated from Feb 1, 2026. All others by Apr 1, 2026.
- FA(3) schema introduced mandatory KSeF invoice reference fields in JPK_VDEK (SAF-T VAT return). ERP extractors must be updated.
- All invoices pre-cleared through the KSeF platform — no clearance, no valid invoice.
- Archiving: KSeF stores invoices for 10 years. Companies still need own retention for audit trail.
- Key risk: ERP systems not yet updated to capture KSeF IDs will generate invalid JPK_VDEK submissions.
- Since Jan 1, 2025: all domestic businesses must be able to receive structured e-invoices.
- Issuance staggered by turnover: €800K+ turnover → Jan 1, 2027; all others → Jan 1, 2028.
- 2025–2026 transition: businesses may still issue paper or PDF invoices with buyer consent, but receiving capability is mandatory now.
- Formats: XRechnung (pure XML) and ZUGFeRD (hybrid PDF+XML). Both comply with EN 16931.
- No central clearance — decentralized model unlike France/Poland.
- B2C mandate effective Jan 1, 2025. B2B mandate live since 2024 for large enterprises.
- SMEs (turnover below threshold) given extended deadline to Jul 1, 2026.
- Mandate extended to supplies to non-resident VAT-registered customers in Romania — still must send invoice traditionally in addition to RO e-Factura submission.
- Rejection window: 5 working days to resubmit a rejected invoice. Finance and Tax teams need defined escalation paths.
- Transmission deadlines standardized across B2B and B2C in early 2026.
- SdI v1.9.1 effective May 15, 2026: refined data coding for AltriDatiGestionali block, updated control codes for reverse charge scenarios.
- Cloud fiscalization (2025 Budget Law): B2C retailers must virtually link telematic cash registers (RT) with POS terminals through the government portal.
- Italy is a global leader in fiscal digitization — SdI has been operational since 2014. Serves as a model for other EU states.
- Format: FatturaPA XML. All invoices pass through the central SdI hub for validation and routing.
APAC pattern: High-growth economies skipped legacy post-audit models entirely. The region is API-first — authenticated connections to government platforms, real-time or near-real-time clearance, and cryptographic signing. These systems require more IT depth than their European counterparts.
- Phased rollout by revenue. Jan 1, 2026: businesses with annual turnover RM 1M–5M must implement. Full enforcement Jul 2026.
- Relaxation period through Jun 30, 2026: RM 1M-5M bracket must implement but won't face penalties for consolidated invoice workflows during transition.
- Consolidated e-invoices now permitted for construction materials. Still prohibited for motor vehicles and specific telecom services.
- Format: JSON or XML. Submitted directly to LHDN (Inland Revenue Board) MyInvois portal via API for pre-clearance before invoice is valid.
- QR code must appear on invoice for customer verification.
- BIR extended Stage 1 deadline — large taxpayers, e-commerce, CAS users — to Dec 31, 2026.
- Technically unique: uses JSON Web Signatures (JWS). Each invoice payload must be digitally signed by the taxpayer's private key; BIR validates via public keys.
- Submission within 3 calendar days of transaction.
- Requires robust key management infrastructure — private keys must be stored securely and rotated per BIR requirements.
- Regional pioneer — e-invoicing mandatory since 2022. Decree 70/2025 effective Jun 1, 2025 extends obligations.
- Now explicitly covers foreign digital service providers and e-commerce platforms.
- As of early 2026, e-invoicing required for sales at petrol stations.
- All e-invoices submitted through General Department of Taxation (GDT) system.
- From Apr 1, 2026: all new voluntary GST registrants must transmit invoice data electronically via InvoiceNow (Peppol).
- Gradual path toward 2031 mandatory adoption for all GST-registered businesses.
- Based on the Peppol framework — interoperable with European systems using the same standards.
- Least disruptive APAC mandate — decentralized, no pre-clearance required.
LATAM second-generation controls: Latin America pioneered e-invoicing a decade ago. In 2026, the focus has shifted to direct access to taxpayer systems and expanded withholding obligations. Mexico's Rule 2.9.21 is the most aggressive move globally — granting the tax authority permanent real-time database access.
- Rule 2.9.21 (2026 Miscellaneous Tax Resolution): mandates digital service providers and marketplaces to grant SAT permanent, real-time online access to transactional databases from Apr 1, 2026.
- "Notice of Access" (Ficha 168/CFF) must be submitted by Apr 30, 2026 — includes login credentials and technical manual for the database environment.
- Data must be available no later than T+1 (day after transaction) and include granular details: buyer/seller info, amount, payment method, platform fee.
- Withholding expansion (Jan 1, 2026): platforms must withhold 50% VAT + 2.5% income tax for B2B sales by Mexican legal entities with RFC. For foreign sellers without permanent establishment: 16% VAT + 25% income tax.
- Most invasive mandate globally — requires dedicated database interface to SAT standards.
- SIN (National Tax Service) extended Groups 9–12 deadline to Apr 1, 2026 for transition to assigned online invoicing modality.
- Digital tax documents issued through SIAT portal.
- Border controls enhanced — digital invoices required for import/export documentation at customs checkpoints.
For a global cloud/SaaS provider, these mandates are not a document formatting problem. They fundamentally alter how every transaction is processed, validated, and reported — in real time, by a third party (the tax authority). Non-compliance means the invoice doesn't legally exist.
SAT requires permanent real-time access to transactional databases from April 1, 2026. Platforms must expose a database interface with T+1 data availability. This is unprecedented in scope — failure means operating illegally in Mexico.
Many mandates restrict e-invoice issuance to "established" entities — but definition of "fixed establishment" (SMPD) is increasingly scrutinized. Even non-established businesses must receive e-invoices in France and Germany. Tax authorities are expanding scope.
SAP ECC to Oracle NetSuite migrations take 9–15 months for multi-entity operations. Attempting to replicate legacy, country-specific workarounds in the new system is a common failure pattern. ERP go-live must align with mandate deadlines — duplicative work is the worst outcome.
ViDA Pillar II makes platforms liable for VAT on accommodation and transport transactions from 2028. The platform must classify the VAT status of thousands of underlying suppliers accurately. Data burden is massive.
For cross-border B2B and B2C transactions into France, if a foreign seller isn't established in France, the French buyer holds the e-reporting obligation. Cloud providers selling into France must understand which obligations shift to their customers.
Real-time clearance systems reject invoices instantly for invalid VAT IDs, SIREN numbers, or TINs. Without automated validation at point of entry, rejection rates will be high and invoice workflows will break.
Separate internal business data from country-specific compliance logic. Don't build each country as an isolated IT project — that leads to fragmentation and duplicated cost.
Leverage native ERP workflows. Simplified approval chains. Audit readiness means proving reporting data matches internal transactional reality at any point in time.
Mexico's T+1 requirement is the floor. Design systems so transaction data is immediately available for government access. Build for T+0 to give buffer.
The window to prepare for 2026 mandates is closing. Organizations that adjust early move from reactively chasing mandates to strategically managing digital tax as a competitive advantage.
Conduct a gap analysis of current ERP and billing stacks. Can they generate structured e-invoices (XML/JSON) that meet EN 16931 or national standards like FA(3), FatturaPA, or MyInvois JSON? This determines the scope of technical work needed.
Partner with a centralized e-invoicing provider to manage format transformation and transmission to fragmented national portals. Don't build bespoke connectors for each country's API — centralize the compliance logic.
Implement automated validation controls for VAT IDs, SIREN numbers, and TINs at the point of data entry. Real-time clearance systems will reject invoices instantly for invalid data — bad master data directly causes operational failures.
Rule 2.9.21 requires a database interface supporting SAT's permanent access requirements with T+1 data availability. This is Mexico-specific but the architecture pattern applies globally. Build it now before the Apr 30, 2026 Notice of Access deadline.
Align any ECC → NetSuite or similar ERP migration with 2026 mandates in France (Sep), Poland (live), and Malaysia (Jul). Migrations take 9–15 months. Duplicative compliance work during a live migration is the worst-case scenario.
Establish clear ownership between Tax, Finance Ops, and IT for government rejections, token renewals, and resubmissions. Romania allows 5 working days. France's PDP system has its own SLAs. Each country has different windows — document and assign ownership now.
Fill in progress % based on internal gap analysis
Assign owners and deadlines per country