Electronic Tax Invoice Regulations: Formats, Signatures, and Archiving

Electronic tax invoice regulations require businesses to create, transmit, and store invoices in structured digital formats that tax authorities can read and validate electronically. Dozens of countries now enforce some form of mandatory e-invoicing, and the obligations fall into a predictable set of categories: what data your invoice must contain, how you send it to the tax authority, whether that authority has to approve it before your buyer sees it, and how long you keep the record afterward. What varies, and what matters most for your compliance workflow, is which country’s rules apply to each transaction.

Clearance and Post-Audit Compliance Models

Every e-invoicing system falls into one of two broad categories, and knowing which one governs a transaction determines almost everything else.

Under a clearance model, you submit the invoice to the tax authority before it becomes legally valid. The authority reviews it in real time or near real time, checks the data, and either approves or rejects it. Only after approval can the invoice be delivered to your buyer. Italy’s Sistema di Interscambio is the best-known European example: since January 2019, every VAT-registered business in Italy must route invoices through this government platform for B2B, B2C, and B2G transactions.¹ Brazil, Mexico, Saudi Arabia, and India use variations of this approach. It gives tax authorities complete visibility into every transaction as it happens, which is why it has become the dominant choice for countries focused on closing VAT gaps.

Under a post-audit model, you issue the invoice directly to your buyer without government pre-approval. The tax authority can request and review your records later during an audit. This is the traditional approach in most of Western Europe, Australia, and the United States. It offers more operational flexibility but less real-time control for authorities. Several countries that started here are migrating toward clearance or hybrid systems as real-time validation becomes more practical.

Where E-Invoicing Is Mandatory

Latin American countries were early adopters. Brazil’s Nota Fiscal Eletrônica system has been mandatory since 2011, and Mexico, Chile, Colombia, and Peru followed within a few years. In Asia, India requires GST e-invoicing for businesses above certain turnover thresholds, and Malaysia completed its phased rollout in January 2026, when all businesses regardless of revenue became subject to the requirement.² Saudi Arabia’s ZATCA began enforcing its generation phase in December 2021 and has been rolling out integration with government systems in waves since January 2023.³

Europe is expanding fast. Italy has required full e-invoicing since 2019.¹ Germany began requiring all businesses to accept e-invoices in the EN 16931 format as of January 2025, with mandatory issuance for businesses above €800,000 in turnover starting January 2027 and all businesses by January 2028.⁴ France is mandating B2B e-invoicing starting September 2026. Belgium, Croatia, and Poland also have mandates taking effect in 2026. Above all of this, the EU adopted its VAT in the Digital Age (ViDA) package in March 2025, which will progressively introduce standardized e-invoicing and real-time digital reporting for cross-border B2B transactions across member states.⁵

Most countries begin with Business-to-Government (B2G) transactions, then extend to B2B, usually phased by company size. Malaysia started with businesses earning over RM100 million annually in August 2024 and worked down to all businesses by January 2026.² Germany set its phased B2B issuance threshold at €800,000 in turnover.⁴ B2C mandates are less common; Italy is a notable exception, requiring e-invoicing for all domestic transactions.¹

The United States

The U.S. has no federal e-invoicing mandate for B2B or B2C transactions, no deadline on the horizon, and no penalties for not using e-invoicing domestically. The IRS does impose detailed recordkeeping requirements: your system must clearly show income and expenses, and you bear the burden of substantiating every entry, deduction, and statement on your tax returns.⁶ If you sell to trading partners in countries that mandate e-invoicing, you will need to comply with those countries’ rules for invoices you send them, regardless of U.S. law.

Required Data Fields and Formats

At a minimum, expect to include tax identification numbers for both seller and buyer, legal names, registered addresses, a line-by-line breakdown of goods or services with applicable tax rates, the total tax amount, and a unique invoice identifier. That identifier prevents duplicate submissions and creates the audit trail tax authorities rely on.

The technical format matters as much as the content. Most systems require structured, machine-readable files rather than PDFs or scanned images. The two dominant formats globally are XML and Universal Business Language (UBL). UBL 2.1 was approved as an international standard (ISO/IEC 19845) in 2015, making it the de facto standard for government e-invoicing worldwide.⁷ JSON representations of UBL documents also exist and are accepted in some newer systems. The EU’s technical standard, EN 16931, defines the semantic data model for e-invoices and specifies compliance at three levels: the invoice document must contain all mandatory information with amounts calculated correctly, senders and receivers must be technically capable of creating and processing compliant invoices, and any country-specific customization must remain a subset of the core rules.⁸

Compliant accounting software typically populates these fields automatically. The real risk is feeding the system bad data. An incorrect tax identification number, a mismatched address, or a tax rate calculated at an outdated percentage will trigger a rejection and delay the transaction.

Transmission and Validation

How an invoice gets from your system to the tax authority depends on the compliance model and the jurisdiction’s technical infrastructure. In clearance systems, businesses connect to the government platform either directly through API integrations or through certified service providers. Italy’s SDI checks formatting before forwarding the invoice; India’s Invoice Registration Portal validates the data and returns a digitally signed invoice with a unique registration number and QR code.

After submission, you receive either a validation code confirming acceptance or a rejection notice explaining what went wrong. Common rejection reasons include invalid tax identification numbers, formatting errors, and calculation mismatches. That confirmation code matters: in many jurisdictions, your buyer cannot claim tax deductions or input credits without a validated invoice.

Cross-Border Transactions and the Peppol Network

A business trading across borders faces a patchwork of national standards, formats, and legal requirements that do not naturally talk to each other. The UN Economic and Social Commission for Asia and the Pacific describes the global e-invoicing landscape as “fragmented,” with “incompatible data structures, differing communication mechanisms, and disparate integration practices” creating significant barriers for cross-border operations.⁹ Your domestic system may generate invoices in a format your foreign buyer’s tax authority does not accept. Your digital signature may not be recognized across borders.

The Peppol network is the leading framework addressing this. Peppol standardizes how information is structured and exchanged, providing a shared digital language across jurisdictions.¹⁰ It operates on a four-corner model: the sender transmits the invoice to a certified access point, that access point routes it to the receiver’s certified access point, and the receiver’s access point delivers it to the final recipient. Automated discovery registries identify which access point each recipient uses, so businesses do not need to negotiate technical connections with every trading partner individually.⁹ Without such a framework, a business trading with partners in five countries might need five separate technical integrations. Peppol reduces that to a single connection through one access point. The network introduced its International Invoice (PINT) specification in 2023 as a further step toward global interoperability.

Digital Signatures and Authentication

Many regimes require a digital signature or electronic certificate to verify that the invoice was issued by the claimed sender and has not been altered after creation. Brazil requires XML invoices to be signed with the company’s digital certificate before submission. India’s Invoice Registration Portal digitally signs each validated invoice and generates a QR code. Mexico uses Authorized Certification Providers to certify digital tax receipts. Peru requires digital certificates issued by providers meeting specific national standards.

In the EU, EN 16931 addresses authenticity and integrity but leaves implementation details to member states. Some require qualified electronic signatures under the eIDAS regulation; others accept alternative methods like secure transmission channels or internal business controls. If your jurisdiction requires a digital signature, your e-invoicing software or service provider will typically handle the cryptographic process, but you are responsible for maintaining valid certificates and renewing them before they expire.

Record Retention and Archiving

Every jurisdiction that mandates e-invoicing also specifies how long you must keep the records. The ranges vary widely:

3 to 7 years in the United States, varying by record type. The IRS requires employment tax records for at least four years and other records for as long as needed to prove deductions.⁶
5 years in Australia, Brazil, and Singapore.
10 years in Germany, where the retention period for electronic invoices matches that for paper invoices. Italy and France also require 10-year retention for fiscal records.¹¹

Records must stay in their original digital format. You cannot print an XML invoice, store the paper copy, and discard the file. The digital signature, metadata, and structured data in the original are what make the record verifiable during an audit. Converting to a different format or stripping metadata can render the record legally invalid. Germany’s ZUGFeRD format, for instance, uses PDF/A-3 with embedded XML, and the two components must be archived together.

Your storage system also needs to guarantee immutability: any changes to archived invoices must be logged with a full audit trail. Whether you use cloud storage or local servers, the records must remain accessible and readable for tax inspectors on request. Failing to produce records during an audit can result in financial penalties and the disallowance of tax deductions you previously claimed.

Preparing Your Business

If a mandate is coming to your jurisdiction, or you trade with countries that already have one, the preparation work is straightforward but takes longer than most businesses expect.

Start by identifying which mandates apply to you. That means checking not just your home country but every country where you have buyers or suppliers. A U.S. company selling to German buyers will need to comply with Germany’s reception requirements even though the U.S. imposes none of its own.

Evaluate your accounting and ERP systems next. Your software needs to generate invoices in the required structured format, connect to the relevant government platform or Peppol access point through API integration, and handle validation responses. Many legacy systems cannot do this without upgrades or middleware. In a clearance jurisdiction, your workflow changes fundamentally: you cannot issue an invoice until the tax authority has validated it, which means building government approval into your accounts receivable process rather than treating compliance as a back-office afterthought.

Clean your master data. The most common rejection reason across every e-invoicing system is bad data: outdated tax identification numbers, inconsistent address formats, incorrect tax rate codes. Run an audit of your customer and vendor records before go-live, not after your first hundred invoices bounce back.

Plan for archiving from day one. Your storage solution must maintain records in their original format for the full retention period, with access controls that prevent tampering while still allowing retrieval during audits. Building this infrastructure retroactively is far more expensive than getting it right at the outset.

1
European Commission. eInvoicing in Italy
2
Hasil. LHDNM e-Invoice General FAQs
3
ZATCA. What is e-invoicing
4
European Commission. eInvoicing in Germany
5
European Commission. VAT in the Digital Age (ViDA)
6
Internal Revenue Service. Recordkeeping
7
OASIS. OASIS Universal Business Language (UBL) TC
8
European Commission. EN 16931 Compliance
9
United Nations ESCAP. A Guide on Adoption of Cross-border Electronic Invoicing
10
Peppol. Peppol
11
E-Rechnung in der Bundesverwaltung. Retention Period for E-Invoices in Years