The invoice is now a rail
Under a mandatory e-invoicing regime, the tax authority authorizes an invoice before it takes legal effect. A growing number of markets use one. The business prepares a structured file in a prescribed schema, submits it through a designated channel, and then waits for an acknowledgment that everything else depends on. Until that acknowledgment comes back, the document is not an invoice, whether for the buyer, the tax authority, or a court.
The link to payment collection runs through the receivable: the invoice creates it, and settlement extinguishes it. When no valid invoice exists, the money received is a movement of funds with no legal basis, tied to no obligation of the customer. Four consequences follow. The accounting entry matches no receivable, payment reminders have nothing to point to, the buyer loses its right to deduct the tax, and any commercial dispute is argued without an enforceable document.
The model originated in Latin America, where tax authorities grew used to authorizing a transaction before it happens. Italy brought it to Europe on January 1, 2019, becoming the first EU country to mandate e-invoicing between taxable persons established on its territory (Legislative Decree 127/2015). The list has grown every year since. Saudi Arabia, Poland, and India each chose a different control architecture. No single invoicing tool covers all three markets.
- Numbering no longer belongs to the seller. An identifier issued by the authority, or by a third party it accredits, becomes the invoice's legally binding reference, and often the key for matching the payment.
- The data collected at the point of sale changes: the buyer's tax ID, tax address, the exact nature of the transaction, and the tax treatment. A checkout flow designed for another market does not ask for it.
- Invoice status becomes something to monitor, just like payment status, with its own rejections, resubmissions, and processing times.
- The timeline is set by regulation. It cannot be negotiated or pushed back. A missed deadline is not a project delay: it means the business cannot invoice, and so cannot lawfully collect payment.
Clearance, post-audit, and network: three ways to check an invoice
A control architecture defines when an invoice is checked for tax purposes, who performs the check, and what the check produces. Practitioners distinguish two main families. In the post-audit model, invoices flow freely between the parties, and the tax authority checks them later, during an audit. This was historically the regime in Europe, the US, and much of Africa and Asia. The burden falls on archiving. Years later, the taxable person must still be able to prove the authenticity of the document's origin, the integrity of its content, and its legibility.
In the clearance model, the tax authority steps in at or before issuance, and approves or rejects the document. The tax check stops being a deferred risk and becomes a real-time dependency of the sales process. A third model has gained ground more recently: the interoperable network, in which the invoice travels from one accredited provider to another and the authority receives a report rather than the document itself. Peppol works this way. Launched as an EU pilot project in 2008, the network has been governed since 2012 by OpenPeppol AISBL, a nonprofit association based in Brussels. Its topology borrows the four-corner model already used by card networks. The sender hands its invoice to its access point, which routes it to the recipient's access point. Each party contracts only with its own provider.
| Market | Regime and operator | Control architecture | What happens if the check fails |
|---|---|---|---|
| Brazil | Nota Fiscal Eletrônica (NF-e), established by Ajuste SINIEF 07/05; authorization issued by the state SEFAZ | Prior authorization, one transaction at a time, before the taxable transaction takes place | The taxable transaction cannot legally take place; the goods cannot move |
| Mexico | CFDI, stamped by the SAT (Mexico's tax authority) or a Proveedor Autorizado de Certificación (PAC) | Certification by an accredited third party at issuance | The invoice does not exist for tax purposes; the buyer cannot deduct the tax |
| Italy | Sistema di Interscambio (SdI), Agenzia delle Entrate | Mandatory routing through a government channel, with format and consistency checks | The invoice is deemed never issued, whatever copies the parties exchanged |
| Saudi Arabia | Fatoora program, Zakat, Tax and Customs Authority (ZATCA) | Compliant generation, then integration of the invoicing system with the authority's | The document is not an e-invoice under the regime |
| Poland | Krajowy System e-Faktur (KSeF), Ministerstwo Finansów (Ministry of Finance) | Government platform for issuing, transmitting, receiving, and storing invoices | No KSeF number is assigned: submission, and therefore issuance, cannot be proven |
| India | Invoice Registration Portal (IRP), GST regime | Registration: the IRP returns an Invoice Reference Number (IRN) and a QR code to print on the invoice | The document is not a valid GST invoice; the buyer's input tax credit is at risk |
From a distance, these six regimes look alike, but they impose different architectural constraints. Three criteria set them apart, and they are enough for scoping. The first is the timing of the check, before or after the taxable transaction. The second is the authority that performs it: the tax administration itself or an accredited private operator. The third is the output it produces: an acknowledgment, an identifier, a signature, or the full document.
Latin America: the invoice comes before the sale
The Nota Fiscal Eletrônica is Brazil's electronic tax document for the movement of goods. Established by Ajuste SINIEF 07/05 of CONFAZ, the council of Brazil's state finance secretaries, it becomes valid only after two successive steps. The first is the issuer's digital signature. The second is an authorization for use granted by the state tax authority. This authorization must be obtained before the taxable transaction takes place. As soon as it arrives, the issuer sends the NF-e file and its authorization protocol to the recipient.
Mexico chose delegation over a single government channel. A Mexican invoice exists for tax purposes only once it has been stamped. The stamp, meaning the certification, is applied by the SAT itself or by a *Proveedor Autorizado de Certificación (PAC), an accredited private operator. The Comprobante Fiscal Digital por Internet moved to version 4.0 on January 1, 2022. It has been the only valid version since its coexistence with version 3.3 ended on March 31, 2023*. The regime also distinguishes payment in full from deferred or installment payment. In the latter case, collecting the payment triggers a payment receipt document, separate from the original invoice and also subject to certification.
Europe: Italy's SdI and Poland's KSeF
The Italian regime is built on the requirement to route every invoice through a government-operated channel. The obligation applies to the channel, not to an archiving format or an enhanced PDF. The invoice is an XML file in FatturaPA format, submitted to the Sistema di Interscambio run by the Agenzia delle Entrate, Italy's tax agency. The SdI checks that mandatory fields are present, that the VAT numbers exist in the anagrafe tributaria (the national tax register), that the recipient's electronic address is valid, and that the tax adds up. It then accepts or rejects the document.
An SdI rejection is called a ricevuta di scarto, and it has a specific legal consequence: the invoice is deemed never issued. To fix the error, the seller resubmits the invoice with its original date and number; only the file name changes. A fattura immediata (immediate invoice) must be transmitted within 12 days of the transaction, and a fattura differita (deferred invoice) by the 15th of the following month. Electronic storage with evidential value runs for 10 years. Since January 1, 2024, every taxable person established in Italy has been covered; the forfettari flat-rate micro-businesses were the last to join.
Poland chose a government platform with a broader scope than Italy's channel. The Krajowy System e-Faktur (National e-Invoicing System) centralizes issuance, transmission, receipt, and storage, so the recipient retrieves the invoice from the system instead of receiving it. The issuer uploads a structured invoice and gets back a KSeF number, which serves as proof of submission. The rollout comes in phases that cover different obligations. Receiving invoices through KSeF becomes mandatory for everyone on February 1, 2026. The obligation to issue applies first, on that same date, to businesses whose 2024 sales, including tax, exceeded PLN 200 million, then to all others on April 1, 2026. The smallest businesses, with invoiced sales of no more than PLN 10,000 a month, switch over on January 1, 2027.
| Sistema di Interscambio (Italy) | KSeF (Poland) | |
|---|---|---|
| Operator | Agenzia delle Entrate | Ministerstwo Finansów |
| Role of the channel | Checks the invoice and routes it to the recipient | Centralizes issuance, receipt, and storage |
| Proof of issuance | Ricevuta di consegna (delivery receipt), showing the date of receipt | KSeF number assigned on submission |
| If delivery fails | Ricevuta di impossibilità di recapito: the invoice is validly issued and placed in the recipient's reserved area | Not applicable: the recipient retrieves the invoice from the system |
| Entry into force | January 1, 2019; extended to all established taxable persons on January 1, 2024 | Receipt from February 1, 2026; issuance phased in through January 1, 2027 |
| Retention | 10 years with evidential value; free storage service for invoices routed through the SdI | Handled by the platform itself |
Spain and Portugal run on separate timelines, and a team covering the Iberian Peninsula has to track them separately. Spain is building its regime around *Verifactu and a B2B mandate whose deadlines will run from a ministerial order that has yet to be published. Portugal's timeline, by contrast, is set. Plain PDFs stop counting as electronic invoices after December 31, 2026. From January 1, 2027, a qualified electronic signature or seal and the structured CIUS-PT** format become the rule.
Gulf and Asia: integration in Saudi Arabia, registration in India
Saudi Arabia split its reform into two phases under the Fatoora brand, run by the Zakat, Tax and Customs Authority. The first phase, known as the generation phase, has applied since December 4, 2021. It requires invoices and notes to be generated and stored using a compliant electronic solution. It covers all taxable persons except nonresidents, as well as any third party issuing invoices on behalf of a VAT-registered supplier.
The second phase, known as the integration phase, began on January 1, 2023. It requires invoices, credit notes, and debit notes to be exchanged and processed in a structured electronic format, through a technical connection to the authority's systems that includes its security requirements. It is phased in. ZATCA rolls it out in waves, one group of taxpayers at a time, with at least six months' notice before each wave. That notice period is the time between a taxpayer group being notified and the date the obligation becomes binding on it. It therefore sets the real window for the integration project, and lost time cannot be made up.
India's regime is based on registering the invoice with a portal that does not deliver it to the buyer. Under the GST (goods and services tax) regime, businesses with aggregate annual turnover of ₹5 crore or more have had to register their B2B invoices on an Invoice Registration Portal since August 1, 2023 (GST Notification 10/2023). The IRP receives the invoice data, registers it, and returns an Invoice Reference Number with a QR code that must appear on the invoice. The parties still exchange the document directly.
ViDA: what the EU requires, and by when
Until 2025, a member state that wanted to mandate e-invoicing had to request a derogation from the Council under Article 395 of the VAT Directive. Italy had obtained one. Council Implementing Decision (EU) 2024/3150 of December 10, 2024 extended that authorization to December 31, 2027. The authorization includes an early-termination clause that applies if the EU adopts a general e-invoicing regime in the meantime. Council Directive (EU) 2025/516 of March 11, 2025, part of the VAT in the Digital Age package, removes the derogation step. Each member state can now mandate e-invoicing on its territory without prior authorization.
The directive's first effect was immediate: national announcements multiplied as soon as it was adopted. The second, more far-reaching effect is deferred to July 1, 2030, when e-invoicing becomes the default regime in the VAT Directive itself. Article 217 redefines the electronic invoice. Article 218 makes it the standard, and Article 232 removes the requirement for the recipient's prior consent where the invoice complies with the European standard set under Directive 2014/55/EU. Some national leeway remains: member states are still free to allow other standards for purely domestic transactions.
The third effect concerns reporting, and it matters most for groups operating in several member states. Article 262 is replaced, and recapitulative statements (EC Sales Lists) give way to transaction-by-transaction digital reporting of intra-EU transactions. Existing national systems will have to converge on this common framework, with alignment due by January 1, 2035. The Italian, Polish, and Spanish regimes are therefore steps toward that common framework, not its end state.
How mandatory e-invoicing affects payment collection
The first impact is on the checkout flow and the data it collects. A cleared invoice requires information that payment does not: the customer's tax ID, tax address, the classification of the transaction, and sometimes the tax treatment or a standardized product code. This data must be available at the time of sale, not at the accounting close. A flow designed for a post-audit market does not collect it. Adding it late in the checkout hurts conversion, and capturing it carelessly generates rejections at scale.
The second impact concerns reconciliation, and it comes down to an architecture decision that is cheap if made early. The legally binding reference for a sale becomes the identifier issued by the authority or its delegate, not the internal order number. The whole reconciliation chain, from the batch through payout and accounting entry to the payment reminder, benefits from being anchored on that key rather than on a reference the tax authority does not know. A third impact affects services, where tax becomes due on payment under several regimes. The reportable event is then the payment, not the issuance of the invoice.
BR chave de acesso NF-e + protocolo de autorizacao
-> proof of the authorization for use issued by the state SEFAZ
MX UUID (folio fiscal) of the stamped CFDI
-> proof of certification by the SAT or an accredited PAC
IT identificativo SdI + ricevuta di consegna
-> proof of issuance; the ricevuta shows the date of receipt
PL numer KSeF
-> proof of submission, assigned by the platform on submission
IN Invoice Reference Number (IRN) + QR code
-> proof of registration on the Invoice Registration Portal
Operating rule: store this identifier alongside the order reference
and the payment reference, not instead of them. Each of the three
serves a different audience.| Market | When the tax check happens | Impact on the checkout flow | Most common failure point |
|---|---|---|---|
| Brazil | Before the taxable transaction takes place | The invoice gates the sale: the order of steps is reversed | Invoicing module triggered after payment capture |
| Mexico | At issuance, by the SAT or a PAC | Availability depends on an accredited private provider | PAC outage not treated as a payment incident |
| Italy | At transmission, within 12 days of the transaction | Document status must be tracked, and rejected invoices resubmitted | Unmonitored ricevute di scarto: invoices silently void |
| Poland | On submission to the government platform | The KSeF number becomes the proof of issuance to keep | Phased timeline misread: issuance required a quarter sooner than planned |
| India | At registration on the IRP | The IRN must appear on the document sent to the buyer | Invoice without an IRN: the corporate buyer withholds payment |
| Saudi Arabia | Compliant generation, then integration by wave | Start date depends on the taxpayer group notified | Wave notice ignored: no project window left |
Running a clearance regime day to day
Running a clearance regime means continuously processing the responses returned by the tax platform. That flow starts at go-live. Unlike the integration project that precedes it, it never stops. Monitoring it uses the same metrics as a clearing queue: expected volume, rejection rate, age of the oldest unresolved rejection, and average time to resubmit.
- Monitor responses daily, with an on-call rotation. An unresolved rejection gets older, and some regimes cap the time allowed to resubmit.
- Never renumber on resubmission where the regime forbids it: in Italy, the resubmitted invoice keeps its original date and number, and only the file name changes.
- Treat the accredited provider's availability as an operational risk: a fallback plan, an alert threshold, and a contract clause on availability and reversibility.
- Keep a register of proof identifiers (protocol, UUID, identificativo, number, IRN) that the collections and disputes teams can access, not just accounting.
- Archive according to local rules, which set their own retention period and format: 10 years with evidential value in Italy, with free storage for invoices routed through the SdI.
- Tie regulatory deadlines to the resource plan, checking them with the relevant authority rather than in a summary written for another market.
Scope is the set of flows a regime makes mandatory, and it varies significantly from country to country. Italy includes sales to consumers and, since July 1, 2022, has folded cross-border transaction reporting into the SdI, with document types dedicated to self-billing and intra-EU acquisitions. India covers only B2B above a threshold. Poland phases in by company size and date. Mapping the scope therefore means looking at four flows, each of which can fall under a different obligation in the same country: domestic B2B, B2C, cross-border, and transactions with the public sector.