On Sept. 1st, 2026, France’s e-invoicing reform will reach its first mandatory phase. From that date, every business established in France must be able to receive structured e-invoices, and large enterprises and mid-sized companies must additionally issue e-invoices and transmit e-reporting data.
Whether or not you’re established in France, the country’s reform reminds us that the e-invoicing landscape is constantly evolving. Mandates are now spreading to more than 80 countries across EMEA, LATAM and APAC, each with its own format, model, and deadline. For a full breakdown of how those models and formats work, see our complete guide to e-invoicing.
Many CFOs at high-growth software companies have filed e-invoicing away as a non-urgent tax item. But for scaling businesses, e-invoicing can impact revenue recognition, collections, and audit readiness, and determine how quickly you can launch a new market.
CFOs often under-scope e-invoicing because they don’t understand how it touches their business or the consequences of getting it wrong. Use the six questions below to assess your own exposure and avoid costly mistakes.
What e-invoicing actually is, and why it’s spreading
An e-invoice is structured, machine-readable data transmitted to a defined endpoint, such as a government platform or your buyer’s e-invoicing endpoint, usually as XML. A PDF, a scan, or an emailed Word file doesn’t qualify, a person or an OCR tool still has to read those.
We cover the four regulatory models and how e-invoicing actually works, step by step, in our guide. Here, we’re focused on what it means for your business.
Since Chile launched the first clearance-based system in the early 2000s, e-invoicing has spread to more than 80 countries, and mandates keep arriving. That makes it as much a monitoring problem as a build problem. The first step is understanding if, and where, you’re in scope, which is what the questions below help you answer.
Are we sure e-invoicing applies to us?
E-invoicing requirements are determined by who you sell to and your established presence in a country.
Business-to-government (B2G) transactions will trigger e-invoicing almost everywhere. A single government customer can pull you into a mandate years before B2B or B2C transactions would. B2B is the fastest-expanding sector, with countries like the UK and Spain recently introducing new B2B e-invoicing mandates. B2C is the least commonly mandated sector, with exceptions for digital services.
Most governments require e-invoicing for businesses established in their country. You can qualify as established if you’ve incorporated a subsidiary in that country or if you have enough real presence (an office, staff, infrastructure) that local tax law treats you as being there. Note that certain countries, like France, require established companies to receive e-invoices even if they don’t have any to issue.
E-invoicing requirements aren’t the same as VAT registration. In most countries today, if you collect and remit tax because you sell to customers there, but have no people or premises, you are not required to e-invoice. But your first acquisition, office, or local hire can put you in scope. Taiwan is one example, sell digital services to Taiwanese consumers and you’re in scope for e-invoicing regardless of whether you’re established.
Which model applies, and what does it do to our order-to-cash?
E-invoices run on one of four models: post-audit, real-time reporting, pre-clearance, and post-clearance. All of which differ based on when the government inspects the invoice relative to it reaching your buyer. What matters here is what that timing does to your order-to-cash.
CFOs need to be aware of which e-invoicing models they’re operating under as e-invoicing inspections can impact order-to-cash. Under pre-clearance, you shouldn’t deliver goods or services until the invoice is validated. Under post-clearance, you can’t recognize the revenue cleanly until the invoice has been approved. In these circumstances, e-invoicing becomes a blocker on delivery and revenue recognition.
Is our billing stack ready for e-invoicing?
Unlike traditional invoicing, e-invoices have to be complete and correct at issuance, not reconciled at month-end. Under clearance models, a missing buyer tax ID means the invoice fails validation and never reaches your customer at all. You have to fix it and resubmit before the invoice legally exists.
Invoices that have already cleared are more complex. A cleared e-invoice can’t be amended or withdrawn, the original stays on the tax authority’s records permanently. To correct it, you must issue a credit note that reverses it and references its clearance ID, then submit a replacement invoice with a new sequential number referencing both. For one adjustment, you’re required to create three linked legal documents, each needing the right country-specific type code and reference field, and each cleared in its own right.
That’s why exposure scales with billing complexity rather than revenue. A company billing on API calls with monthly true-ups generates corrections continuously. A seat-based company at identical revenue barely generates any.
Speed to address e-invoice amendments also matters. Hungary has an amendment deadline of 4 days, Romania 5 working days, Italy 12 days. Missing an amendment deadline leads to another penalty on top of the underlying error.
Certain billing methods can also create e-invoicing obligations. In Poland, for example, purchase of a prepaid credit triggers a tax obligation, requiring an advance invoice for the period the payment lands.
The ability to support these mandates isn’t just a tax question but a billing infrastructure question. The system producing e-invoices must be able to hold the complete dataset, including tax determination, buyer identifiers, clearance IDs, and document lineage. If these assets sit in different systems, it becomes nearly impossible to produce compliant corrections at scale.
What’s the cost of getting e-invoicing wrong?
Managing e-invoicing across countries can feel like juggling ten balls at once. And the cost of errors extends beyond tax implications.
Under clearance models, non-compliant e-invoices aren’t delivered to customers, so there’s nothing for them to pay against. When a defective invoice does reach the customer, it doesn’t just cost you a fine, it also costs customers their input VAT deduction. This turns a tax error into a short-paid invoice, a disputed balance, and a damaged customer relationship.
Failing to submit e-invoices correctly also carries penalties. France fines €50 per invoice up to an annual limit of €15,000 per company. Poland, on the other hand, will charge up to 100% of the VAT shown, or up to 18.7% of the total where no VAT is shown, from 1 January 2027.
E-invoicing errors can create audit implications, especially under real-time reporting models. In a real-time e-invoicing country, the tax authority gets the details of an e-invoice as it’s issued, often ahead of month-end close. When you later file a VAT return, the authority compares it to your past e-invoices and your customers’ filings. Any discrepancies you would previously have caught and quietly fixed during reconciliation are now visible externally the moment it occurs, before anyone internally has reviewed it.
Will our e-invoices reconcile with our VAT returns?
E-invoicing runs on the same transaction data as your tax calculations and returns. When e-invoicing and VAT are managed in two separate systems, you need to check that both agree. As this workflow often isn’t part of the month-end routine, any mismatches can go unnoticed until an auditor finds them.
Under real-time models, in particular, tax authorities hold transaction level data before you complete month-end close, meaning that any mismatches between what’s e-invoiced and what’s filed appear to them first.
Global organizations benefit by managing tax calculations, returns, and e-invoices in a single system. With all workflows based on the same source of truth, there’s no need to reconcile tax calculations against invoicing. Anrok, for example, issues compliant e-invoices from the same transaction data behind your tax calculations, so you meet mandates without adding another tool.
Would our compliance posture survive diligence?
CFOs at VC-backed companies are building in preparation for a future fundraise, acquisition, or IPO event. Reviewing indirect tax is a standard part of diligence during these cycles, and unfiled returns and uncollected tax commonly affects purchase price and creates escrow holdbacks.
E-invoicing errors impact investor diligence in two ways. First, they leave a record of penalties and invalid invoices in named jurisdictions, making it easy for a buyer’s advisors to price. Second, it can undermine revenue reporting. If you’re unable to show compliant invoices for the required retention period, it affects your ability to support revenue claims.
Ability to handle e-invoicing in future can also influence investor decision-making. Global expansion is a key path for revenue growth. But if you don’t have the e-invoicing infrastructure required to operate in markets like France, Spain, or Germany, it may hinder your ability to meet the expansion expectations of investors and fellow leadership.
Automate e-invoicing with modern infrastructure
E-invoicing isn’t a filing task to complete at end-of-quarter. It’s a set of workflows that needs to run inside your financial infrastructure, not alongside it.
The companies managing e-invoicing smoothly are investing in an automation platform that runs e-invoices on the same data as tax calculations and filing. That means each country’s format and model gets handled without guesswork or manual checks. It’s not solved with point solutions and extra headcount for every new country.
E-invoicing mandates are expanding quickly, with new countries introducing requirements and existing frameworks maturing. Anrok monitors these developments closely and updates its coverage and this guidance as the rules change. Because Anrok pairs automation with an in-house team of tax experts, the details behind each country’s format and model are checked, not just generated.
If you expect an e-invoicing requirement in a market you sell into, talk to our team about what compliance looks like there.
