The Complete Guide to E-Invoicing: From Paper to Digital

Whether you're a CFO building a business case, an IT leader evaluating integration options, or an AP manager preparing your team for compliance deadlines, this guide provides the foundation you need.

Pigeon AI Pigeon AI
September 17, 2025 13 min read

Everything You Need to Know About Electronic Invoicing

Updated: November 2025 | Reading Time: 25 minutes

Introduction: Why E-Invoicing Matters Now

Electronic invoicing—or e-invoicing—has evolved from a nice-to-have efficiency tool into a compliance imperative for businesses across Europe and beyond. With Germany's landmark B2B e-invoicing mandate now in effect as of January 2025, and the EU's VAT in the Digital Age (ViDA) initiative reshaping the regulatory landscape, organizations that haven't yet embraced structured electronic invoicing face mounting pressure to act.

This comprehensive guide explains everything you need to know about e-invoicing: its history and evolution, the tangible benefits it delivers, the global adoption landscape, the technical formats that make it work, the transmission methods available, and—crucially—the specific compliance requirements in Austria, Germany, and Switzerland.

Whether you're a CFO building a business case, an IT leader evaluating integration options, or an AP manager preparing your team for compliance deadlines, this guide provides the foundation you need to navigate the e-invoicing transition successfully.

Chapter 1: What is E-Invoicing?

Defining Electronic Invoicing

An electronic invoice (e-invoice) is an invoice that is issued, transmitted, and received in a structured electronic format that allows for automatic and electronic processing. This definition is critical: a PDF sent via email is not a true e-invoice under modern regulatory standards, even though it's digital.

The key distinction lies in the word "structured." A structured e-invoice contains data in a machine-readable format (typically XML) that can be automatically imported into the recipient's accounting or ERP system without manual data entry. This is fundamentally different from image-based formats like scanned PDFs, which require optical character recognition (OCR) or manual transcription to extract invoice data.

E-Invoice vs. PDF: Understanding the Difference

Characteristic PDF Invoice Structured E-Invoice
Format Image/document file XML data file (UBL, CII)
Machine-Readable No (requires OCR) Yes (fully automated)
Manual Processing Required Not required
Error Rate High (manual entry errors) Very low
Processing Time Days to weeks Minutes to hours
Compliance (2025+) Non-compliant in many jurisdictions Fully compliant

Key Takeaway: Under Germany's 2025 mandate and similar regulations, a PDF sent via email no longer qualifies as a compliant e-invoice. Only structured, machine-readable formats meet the new requirements.

Chapter 2: The Evolution of E-Invoicing

The history of electronic invoicing spans six decades of technological innovation, regulatory development, and gradual business adoption. Understanding this evolution provides context for why e-invoicing has reached its current inflection point.

Timeline: From EDI to PEPPOL

  • 1965: The first Electronic Data Interchange (EDI) message—a shipping manifest—was sent by Holland-America Line using telex technology, marking the birth of electronic business document exchange.

  • 1970s: IBM's Financial Accounting System enabled early electronic invoicing for large corporations. File Transfer Protocol (FTP) in 1975 simplified data sharing over networks.

  • 1980s: Enterprise software emerged (SAP, Oracle) alongside desktop accounting packages. Email adoption enabled invoice distribution as PDF attachments.

  • 1990s: Large corporations increased EDI adoption, enabling automated document exchange with trading partners. However, EDI remained expensive and complex for smaller businesses.

  • 2001: EU Directive 2001/115/EC modernized VAT legislation to accommodate electronic formats, providing legal recognition for e-invoices.

  • 2005-2010: Latin American countries (Brazil, Mexico) implemented e-invoicing mandates to combat tax fraud, pioneering government-mandated electronic invoicing.

  • 2008: The PEPPOL (Pan-European Public Procurement Online) project launched, funded by the European Commission to standardize cross-border electronic procurement.

  • 2014: EU Directive 2014/55/EU mandated that public sector entities accept e-invoices, accelerating B2G (business-to-government) adoption across Europe.

  • 2017: The European Standard EN 16931 was published, establishing a common semantic data model for electronic invoices across the EU.

  • 2019: Italy became the first EU country to mandate B2B e-invoicing through its Sistema di Interscambio (SdI) clearance platform.

  • 2022: The European Commission published the VAT in the Digital Age (ViDA) proposal, signaling EU-wide e-invoicing and real-time reporting requirements.

  • 2025: Germany's B2B e-invoicing mandate takes effect, requiring all businesses to receive structured e-invoices from January 1, 2025.

Chapter 3: The Business Case for E-Invoicing

Beyond compliance requirements, e-invoicing delivers substantial operational and financial benefits that justify investment even in voluntary adoption scenarios.

Cost Reduction

Research consistently shows that processing a paper invoice costs between €10-30 per invoice, while a fully automated e-invoice costs €1-3. This 60-90% cost reduction comes from eliminating:

  • Paper and printing costs
  • Postage and delivery
  • Manual data entry labor
  • Error correction and rework
  • Physical storage and retrieval

For organizations processing thousands of invoices monthly, annual savings quickly reach six or seven figures.

Faster Processing & Improved Cash Flow

Manual invoice processing typically takes 5-15 days from receipt to payment approval. E-invoicing reduces this to hours or even minutes through automatic validation, matching, and routing.

Faster processing means:

  • Earlier payment capability
  • Ability to capture early payment discounts
  • Improved supplier relationships
  • Better cash flow predictability for suppliers

Reduced Errors & Exceptions

Manual data entry error rates typically range from 1-5%. These errors cause:

  • Invoice exceptions requiring investigation
  • Payment delays
  • Vendor disputes
  • Costly rework

Structured e-invoices eliminate data entry entirely, reducing error rates to near zero. Automated validation catches format and content issues before invoices enter the AP system.

Enhanced Compliance & Audit Readiness

E-invoicing creates complete digital audit trails with:

  • Timestamps for all actions
  • Routing and approval records
  • Complete document history
  • Automated compliance checks

This simplifies compliance with VAT regulations, internal controls, and external audits. In jurisdictions with real-time reporting requirements, e-invoicing provides the technical foundation for continuous transaction control (CTC) compliance.

Environmental Sustainability

Each paper invoice consumes approximately 10 grams of CO2 equivalent when accounting for paper production, printing, and postal delivery. Organizations processing 100,000 invoices annually can reduce their carbon footprint by 1,000+ kg CO2 simply by switching to e-invoicing—supporting ESG goals and corporate sustainability commitments.

Chapter 4: Global E-Invoicing Adoption

E-invoicing adoption has accelerated dramatically in recent years, driven by government mandates, interoperability standards like PEPPOL, and the EU's ViDA initiative.

European Union

The EU has been the global leader in e-invoicing standardization:

  • Since April 2019: All EU public sector entities must accept e-invoices conforming to EN 16931
  • Italy (2019): First EU country to mandate B2B e-invoicing
  • Germany (2025): B2B mandate now in effect
  • France (2026): B2B mandate scheduled
  • Belgium (2026): B2B mandate for VAT-registered businesses
  • Poland: KSeF system implementation underway

The ViDA directive (Council Directive EU 2025/516) will require near-real-time e-reporting for intra-EU B2B transactions by 2030.

PEPPOL Network Growth

The PEPPOL network has expanded from its European origins to become a global standard:

  • 40+ countries now participate in the PEPPOL network
  • Regions include Europe, Asia-Pacific, and beyond
  • "Connect once, connect to all" approach drives rapid adoption
  • Single Access Point connection enables exchange with all network participants

Asia-Pacific Expansion

  • Singapore: InvoiceNow network (PEPPOL-based) launched 2019; mandatory GST e-invoicing via network now implementing
  • Japan: PEPPOL Authority established 2021; "Qualified Invoice" system launched 2023
  • Australia & New Zealand: PEPPOL embraced for B2G and B2B transactions
  • Malaysia: E-invoicing mandate rolling out via MyInvois platform

Chapter 5: Understanding E-Invoice Formats

E-invoicing success depends on using the right format for your trading partners and jurisdictions. Three main standards dominate the European market, unified under the EN 16931 semantic model.

EN 16931: The European Standard

EN 16931 is the European Standard for e-invoicing, defining a core semantic data model that specifies what information an e-invoice must contain. It doesn't prescribe a specific technical format but rather ensures that regardless of syntax used, invoices contain consistent, interoperable data.

This standard was mandated by EU Directive 2014/55/EU for public procurement.

UBL 2.1 (Universal Business Language)

UBL is an OASIS standard XML format widely used across Europe and beyond:

  • PEPPOL BIS Billing 3.0 is based on UBL 2.1
  • Defines comprehensive XML schemas for business documents
  • Includes invoices, purchase orders, credit notes, and more
  • De facto standard for cross-border European e-invoicing

CII (Cross-Industry Invoice)

UN/CEFACT CII is an alternative XML syntax also supported under EN 16931:

  • Less prevalent than UBL in the PEPPOL ecosystem
  • Forms the foundation for ZUGFeRD/Factur-X hybrid formats
  • Popular in Germany and France
  • Important for organizations trading with German partners

Country-Specific Formats

Format Country Description
XRechnung Germany German CIUS of EN 16931; mandatory for B2G, accepted for B2B. Pure XML format.
ZUGFeRD 2.x Germany Hybrid format embedding XML data within a PDF/A-3 document. Human and machine readable.
Factur-X France/Germany French equivalent of ZUGFeRD; technically identical since version 1.0.06/2.2.
ebInterface Austria Austrian national format for B2G e-invoicing. Versions 4.3+ are EN 16931 compatible.
PEPPOL BIS 3.0 International UBL 2.1-based standard for PEPPOL network. Global interoperability standard.
swissDIGIN Switzerland Swiss e-invoicing standard. ZUGFeRD/Factur-X also recommended by Swiss authorities.

Chapter 6: E-Invoice Transmission Methods

Getting e-invoices from sender to receiver requires reliable, secure transmission infrastructure. Several methods exist, each with distinct advantages.

The PEPPOL Network

PEPPOL has emerged as the dominant infrastructure for B2B and B2G e-invoice exchange in Europe and increasingly worldwide. Organizations connect to PEPPOL through certified Access Points—service providers authorized by PEPPOL Authorities to transmit documents on the network.

The Four-Corner Model

The PEPPOL network operates on a "four-corner model" involving four participants:

  1. Corner 1 (Sender): The business sending the invoice
  2. Corner 2 (Sender's Access Point): Translates the invoice to PEPPOL format and transmits it
  3. Corner 3 (Receiver's Access Point): Receives the invoice and translates it for the recipient
  4. Corner 4 (Receiver): The business receiving the invoice

The Five-Corner Model

A "five-corner model" extends the four-corner model by adding tax authorities as a fifth corner, enabling:

  • Real-time reporting to government
  • Continuous transaction controls (CTC)
  • Invoice validation/clearance before delivery

Countries implementing or planning this model include Belgium, France, and others with CTC requirements.

Key PEPPOL Components

  • Service Metadata Publisher (SMP): Decentralized registry providing information about access points and supported message types
  • Service Metadata Locator (SML): Central registry defining which SMP contains each participant's information
  • PEPPOL ID: Unique identifier for each network participant

Direct EDI Connections

Traditional EDI (Electronic Data Interchange) remains common for high-volume trading relationships:

  • Protocols: AS2, SFTP, OFTP2
  • Enables direct, encrypted document exchange
  • Effective for established relationships
  • Requires individual connection setup per trading partner
  • Less scalable than network-based approaches

Government Portals

Many countries provide centralized portals for B2G e-invoicing:

  • Austria: e-Rechnung.gv.at (via USP)
  • Germany: ZRE/OZG-RE platforms (now consolidated)
  • Support direct upload, API submission, and PEPPOL delivery

Vendor Invoice Portals

Self-service vendor portals offer an alternative for suppliers who cannot send structured e-invoices:

  • Web-based platforms for invoice creation
  • Guided forms for data entry
  • Automatic conversion to compliant e-invoice format
  • Bridges the gap for suppliers using legacy processes

TAPR AI's Vendor Invoice Portal exemplifies this approach, enabling organizations to achieve e-invoicing benefits even with suppliers not yet e-invoice capable.

Chapter 7: E-Invoicing Compliance in Austria, Germany & Switzerland

The DACH region presents a varied e-invoicing landscape, from Germany's comprehensive B2B mandate to Switzerland's primarily B2G focus. Understanding each country's requirements is essential for regional compliance.

Germany: The B2B E-Invoicing Mandate

Germany has implemented the most significant e-invoicing reform in the DACH region through the Wachstumschancengesetz (Growth Opportunities Act), passed on March 22, 2024.

Timeline & Requirements

Date Requirement
January 1, 2025 All businesses must be able to RECEIVE e-invoices. Paper/PDF invoices still permitted for sending (with recipient consent during transition).
January 1, 2027 Businesses with turnover >€800,000 must ISSUE e-invoices for domestic B2B transactions. EDI without EN 16931 extraction no longer permitted.
January 1, 2028 ALL businesses must issue e-invoices for domestic B2B transactions. Full mandate in effect.

Scope & Exemptions

The mandate applies to domestic B2B transactions where both supplier and recipient are established in Germany (registered office, place of management, or permanent establishment).

Key exemptions:

  • Invoices under €250 gross amount
  • Travel tickets functioning as invoices
  • VAT-exempt transactions under UStG §4 No. 8-29
  • Foreign businesses with German VAT registration but no fixed establishment

Accepted Formats

Germany requires e-invoices conforming to EN 16931:

  • XRechnung (German CIUS)
  • ZUGFeRD from version 2.0.1 (EXTENDED profile)
  • Factur-X 1.0.06+
  • PEPPOL BIS Billing 3.0

Important: The Federal Ministry of Finance confirmed that providing an email address is sufficient to meet reception requirements—no dedicated e-invoice mailbox is mandatory.

Archiving Requirements

  • Retention period: 8 years
  • Format: Original structured format (XML is legally binding element)
  • Standards: Must meet GoBD requirements for integrity, authenticity, and accessibility

Austria: B2G E-Invoicing Pioneer

Austria was among Europe's earliest e-invoicing adopters, mandating B2G e-invoicing at the federal level since January 1, 2014. However, B2B e-invoicing remains voluntary.

B2G Requirements

All suppliers to Austrian federal government entities must submit e-invoices electronically, mandated by:

  • IKT Konsolidierungsgesetz §5
  • BVergG 2018 §368

Foreign suppliers with the technical capability are also required to comply.

Submission channels:

  • e-Rechnung.gv.at platform (via USP Unternehmensserviceportal)
  • PEPPOL network

Accepted Formats

  • ebInterface versions 4.3, 5, and 6 (national XML format)
  • PEPPOL BIS Billing 3.0 (for cross-border and PEPPOL submissions)
  • UBL variants

Austria maintains two CIUS (Core Invoice Usage Specifications):

  • CIUS AT NAT: For B2B use
  • CIUS AT GOV: Additional rules for government invoicing

B2B Landscape

No B2B e-invoicing mandate exists in Austria. Common voluntary methods include:

  • EDI for established trading relationships
  • PDF invoices with electronic signatures
  • PEPPOL for partners already on the network

Austria is monitoring the EU's ViDA initiative for potential future B2B requirements.

Archiving

  • Standard retention: 7 years
  • Immovable property: 22 years
  • Digital archiving permitted with integrity, authenticity, and accessibility maintained

Switzerland: B2G Focus with QR-Bill Innovation

Although not an EU member, Switzerland has implemented e-invoicing requirements aligned with European standards for government transactions while maintaining a voluntary approach for B2B.

B2G Requirements

Since January 1, 2016, suppliers contracting with Swiss federal administration must issue e-invoices for contracts valued at CHF 5,000 or more.

Unlike Austria and Germany, Switzerland does not provide a centralized government portal—businesses must use certified service providers or connect via PEPPOL Access Points.

Accepted Formats

Switzerland accepts multiple formats:

  • swissDIGIN (recommended national standard)
  • ZUGFeRD/Factur-X (recommended by Swiss authorities)
  • UBL 2.0 and CII XML
  • PEPPOL BIS formats
  • eCH-0200 format

The Swiss Federal Tax Administration recommends hybrid formats combining PDF with embedded XML data.

The QR-Bill

Since October 1, 2022, Switzerland mandates the QR-bill for payment slips, replacing traditional orange and red payment slips.

Features:

  • Swiss QR code with all payment information
  • Enables automated payment initiation
  • Can complement e-invoices with QR reference and QR-IBAN data
  • Updated Implementation Guidelines 2.3 (November 2025) require structured addresses only

B2B & Future Outlook

B2B e-invoicing remains entirely voluntary in Switzerland. However, Swiss companies trading with EU partners should monitor the ViDA directive, which will require near-real-time e-reporting for cross-border B2B transactions by 2030.

Archiving

  • Retention period: 10 years
  • Requirements: Technical procedures guaranteeing document integrity
  • Timestamp: Must be applied as proof of storage date
  • Regulation: Federal Act on Electronic Signatures (ZertES)

DACH Region: Compliance Comparison

Requirement Germany Austria Switzerland
B2G Mandate Yes (federal since 2020) Yes (federal since 2014) Yes (CHF 5,000+ since 2016)
B2B Mandate Yes (2025-2028 rollout) No (voluntary) No (voluntary)
Primary Format XRechnung, ZUGFeRD ebInterface, PEPPOL BIS swissDIGIN, ZUGFeRD
PEPPOL Support Yes (via KoSIT) Yes (primary channel) Yes (no central portal)
Retention Period 8 years (GoBD) 7 years (22 for property) 10 years
Real-Time Reporting Planned (post-2028) No current requirement No current requirement

Chapter 8: Getting Started with E-Invoicing

Implementing e-invoicing requires thoughtful planning across technology, processes, and trading partner relationships. Here's a practical roadmap:

Step 1: Assess Your Current State

  • Audit your current invoice volumes, formats, and processing workflows
  • Identify which trading partners already send/receive structured e-invoices
  • Evaluate your ERP/accounting system's e-invoicing capabilities
  • Determine which compliance requirements apply to your business

Step 2: Define Your Requirements

  • Which countries and jurisdictions must you support?
  • What formats do your trading partners require?
  • Do you need both inbound and outbound e-invoicing?
  • What integration with existing systems is required?

Step 3: Select Your Solution Approach

Approach Best For
Native ERP functionality Organizations with ERP systems (like MS Dynamics 365) that have built-in e-invoicing support
E-invoicing platform Organizations needing format conversion, validation, and multi-channel transmission
Managed service provider Organizations preferring full-service handling of compliance, connections, and maintenance
Vendor portal solution Onboarding suppliers who cannot send structured e-invoices

Step 4: Plan Your Vendor Onboarding

  • Segment vendors by e-invoice readiness and volume
  • Develop communication plans for each segment
  • Consider AI-powered PDF conversion for vendors sending traditional invoices
  • Establish self-service portals for low-tech vendors

Step 5: Implement & Test

  • Start with a pilot group of cooperative trading partners
  • Validate format compliance using XML validators
  • Test matching and approval workflows end-to-end
  • Monitor exception rates and optimize processes

Conclusion: The Time to Act is Now

E-invoicing has evolved from an efficiency initiative to a compliance imperative. Germany's 2025 mandate affects businesses across Europe, and the broader ViDA directive will expand requirements further. Organizations that implement e-invoicing proactively gain competitive advantages:

  • Lower costs (60-90% reduction in processing costs)
  • Faster processing (hours instead of days)
  • Fewer errors (near-zero data entry errors)
  • Compliance readiness (prepared for future regulations)

The technology ecosystem has matured significantly. PEPPOL provides global interoperability, EN 16931 ensures format consistency, and solutions like TAPR AI bridge the gap for vendors not yet e-invoice capable through AI-powered PDF conversion and self-service portals.

Whether you're facing an imminent mandate or pursuing voluntary adoption for its benefits, the path forward is clear: assess your requirements, select the right solution approach, and begin your e-invoicing journey. The transition from paper to PEPPOL represents one of the most significant opportunities to modernize financial operations in decades.

Ready to Start Your E-Invoicing Journey?

TAPR AI offers a comprehensive e-invoicing solution including:

  • ✅ PEPPOL connectivity
  • ✅ XML validation
  • ✅ AI-powered PDF conversion
  • ✅ Vendor self-service portal
  • ✅ Deep MS Dynamics 365 integration

Contact us for a personalized demo and compliance assessment →

Related Articles

Last Updated: November 2025

SEO Metadata

Meta Title: Complete E-Invoicing Guide: From Paper to PEPPOL (2025)

Meta Description: Complete e-invoicing guide: Learn about PEPPOL, formats (UBL, EN16931, XRechnung), and compliance requirements in Germany, Austria & Switzerland for 2025.

Target Keywords:

  • Primary: e-invoicing guide, what is e-invoicing, electronic invoicing explained
  • Secondary: PEPPOL e-invoicing, EN 16931, XRechnung, ZUGFeRD, Germany e-invoice mandate 2025
  • Long-tail: e-invoicing Austria requirements, e-invoicing Switzerland B2G, UBL vs CII format