E-invoicing is often described as a compliance trend. In reality, it represents a structural shift in how businesses interact with tax authorities — one that exposes the limits of legacy processes, fragmented data ownership, and over-simplified assumptions about what “readiness” means.
This third article in our e-invoicing series examines the internal challenge: why e-invoicing is not a tax project, not an IT upgrade, and not something businesses can afford to misunderstand. Earlier articles mapped the three principal compliance models and the regional landscape of mandates:
Overview of the Issues
There is a widely held assumption in many organizations that at its core e-invoicing is a technical problem with a technical solution: buy or upgrade the right software, connect it to the relevant tax authority platform, and the compliance obligation is met. It is an understandable assumption, but it is wrong.
E-invoicing mandates do not simply require businesses to change how they generate and transmit invoices. They require businesses to ensure that the data contained in those invoices is accurate, complete, and consistent with other information already held by the tax authority, in real time or near-real time, with limited tolerance for error and, in many jurisdictions, no opportunity to correct a rejected invoice without triggering a compliance event. Meeting that requirement reliably across multiple jurisdictions is not a technology project. It is a cross-functional transformation, and organizations that treat it as anything less will find the gap between expectation and reality closing fast.
The urgency is not abstract. For the many e-invoicing mandates coming into force in 2026 and 2027, the realistic timeline for a large organization to scope, procure, configure, test, and deploy the necessary system changes is 12 to 18 months at a minimum. For businesses that have not yet begun, the window for comfortable preparation has already narrowed. And for businesses that believe they have begun, the more important question is often whether what they have begun is the right thing.
The Assumption That Creates the Risk
Many organizations are not aware of e-invoicing. However, most senior tax and finance professionals know mandates are proliferating and that action is required. The risk lies in misdiagnosis: believing the mandate is smaller, simpler, or more contained than it actually is.
Three assumptions create the greatest exposure:
- An ERP upgrade will solve it: Vendors or compliance technology providers can support compliance but they cannot redesign internal processes, remediate data quality, or align cross-functional governance.
- Existing VAT compliance is sufficient: E-invoicing introduces real-time obligations that legacy VAT processes were not built to meet.
- Mandates will be delayed again: Some jurisdictions have delayed e-invoicing mandates one or more times, others have accelerated them. Delay is not a strategy.
Each assumption contains just enough plausibility to lull organizations into under-preparation — and into discovering complexity only when timelines are already compressed.
Why This Is Not a Tax Project
Tax is the first function to witness an e-invoicing mandate and the right function to lead the compliance response. But tax does not own the underlying data, systems, or workflows.
E-invoicing compliance requires that a specific set of data fields — defined by the relevant tax authority, often to a high degree of technical specificity — be present, accurate, and correctly formatted on every invoice in real time. In most organizations, those data points originate in multiple systems and functions: customer master data comes from CRM, product and service classifications from procurement or operations, entity and registration data from finance, and contractual and pricing data from sales. Tax does not own those systems or that data.
E-invoicing is therefore a cross-functional transformation touching:
- IT — systems configuration, integrations, monitoring
- Finance — entity data, reporting integrity
- Procurement — supplier onboarding, procure-to-pay (P2P) validation
- Sales operations — customer data, pricing, contract alignment
- Logistics and fulfilment — transaction accuracy in complex supply chains
Coordinating these functions toward a single compliance deadline is a program management challenge, not a tax filing challenge.
The ERP Question: Where Complexity Becomes Visible
ERP systems sit at the center of the e-invoicing obligation. These systems must generate structured invoices, transmit them through the correct protocol, handle real-time responses, and maintain auditable records of every transaction. In practice, this often requires configuration changes, new integrations, and sometimes fundamental redesign of how invoice data flows through the system.
For multinationals, complexity compounds:
- Global templates limit jurisdiction-specific changes — a change required for one jurisdiction may interact with configurations required for another.
- Multiple ERP instances can create inconsistent data flows.
- In-process ERP migrations or upgrades force difficult decisions: implement on the legacy system, the new system, or both.
- Testing must cover not only new requirements but interactions with existing processes.
The strategic takeaway: Changes of this magnitude take time to plan, resource, test, and deploy, and ERP timelines are longer than compliance timelines. Leadership must understand this mismatch early.
Order-to-Cash and Procure-to-Pay: Where Compliance Meets Reality
E-invoicing cuts directly across order-to-cash (O2C) and procure-to-pay (P2P) — the processes that define how money moves through the business.
- Outbound (O2C): Every outbound invoice must meet the jurisdiction’s standard before it is transmitted. This requires not only system configuration but a review of invoicing workflows, approval processes, credit note and cancellation procedures, and the handling of exceptions. In clearance-model regimes, a rejected invoice is not a valid invoice, meaning that the sale is not legally documented. The implications for revenue recognition, collections, and customer relationships are significant and often not considered in early-stage compliance planning.
- Inbound (P2P): Businesses must receive and process inbound e-invoices in the correct format, validate them against purchase orders and receipts, and ensure that only compliant invoices are used to support input VAT recovery claims. Increasingly, tax authorities cross-reference supplier-reported invoice data against buyer-reported deduction. Discrepancies trigger scrutiny.
The message: O2C and P2P are even more tax-relevant processes. Their integrity affects compliance in real time with tax authorities able to identify discrepancies before a VAT return been filed.
Data Quality: The Hidden Dependency that Determines Success
Data quality is the single most under-estimated determinant of readiness. E-invoicing demands accuracy at the point of transaction rather than at the point of return preparation.
Most data issues uncovered during e-invoicing implementation (e.g., incorrect customer master data, missing or incorrect tax registration numbers, imprecise product or service classifications, etc.) are long-standing inconsistencies that legacy VAT processes could absorb. E-invoicing exposes them.
A credible readiness plan requires:
- Identification of required data fields by jurisdiction;
- A full audit of current data quality;
- A remediation program; and
- Governance to maintain quality over time.
This work must begin before technical implementation, not during it.
E-Archiving: The Overlooked Obligation
Archiving — a requirement in most e-invoicing jurisdictions — is often treated as an afterthought. It should not be. Archiving requirements include retaining e-invoices and, sometimes transmission records, validation responses, and audit trails for defined periods, in defined formats, and sometimes in defined locations. Retention periods can extend beyond 10 years.
Multinationals face additional complexity, such as:
- Data residency rules;
- Multi-system archives;
- Long retention periods; and
- Auditability time.
Implementing e-invoicing without a robust archiving solution is a compliance risk creation masquerading as compliance fulfillment.
Governance and Controls: The New Compliance Perimeter
Real-time visibility changes the nature of compliance risk. Errors are visible as they occur, not months later during return preparation. For example, in a periodic VAT return environment, errors can often be identified and corrected before they become a formal compliance issue, whereas in a real-time or near-real-time e-invoicing environment, errors are visible to the tax authority when they occur. The tolerance for errors is lower, the consequences of systematic noncompliance are more immediate, and the ability to self-correct before scrutiny is reduced.
Organizations need:
- Automated validation of invoice data before transmission;
- Real-time monitoring of rejection and error patterns;
- Clear exception escalation; and
- Regular cross-jurisdiction compliance reviews.
These controls do not exist in most organizations today because they were not previously required.
The governance dimension also has implications for internal audit and the finance function more broadly. E-invoicing compliance is increasingly a matter of financial reporting integrity, as well as tax compliance, and the control framework that supports it should be designed and owned accordingly.
The Right Starting Point
Organizations that succeed begin with a structured readiness assessment:
- Jurisdiction-specific requirements;
- Current-state capability mapping;
- Gap analysis across tax, IT, finance, procurement, and operations; and
- A prioritized, realistic roadmap.
The next article in this series will examine Continuous Transaction Controls, the most advanced expression of the e-invoicing trend, and the direction in which most of the world’s tax authorities are moving.
Visit BDO’s International Indirect Tax Services page for more information on how BDO can help.