E-Invoice 2026+: A requirement for businesses – a strategic opportunity for banks and payment service providers

Classification: Three Target Groups – One Common Data Core

The introduction of the e-invoice is often understood as a pure compliance project: formats, deadlines, receipt obligations. However, this view is too narrow.

The e-invoice creates a standardised data stream that brings invoicing and payment processes together technically – and it is precisely here that its strategic potential lies. The regulatory relevance is now clearly enshrined in law: the Growth Opportunities Act (Wachstumschancengesetz) revised the invoicing provisions in § 14 UStG and established the e-invoice as the new standard for domestic B2B transactions.¹

Three target groups converge on the same “data core”, albeit with different priorities:

• Companies in B2B business must ensure they can receive and process e-invoices. To do so, they must equip their processes and systems accordingly.
• For suppliers to the public sector (B2G), XRechnung, Leitweg-ID, invoice receipt platforms, and Peppol are already established – including typical pitfalls.
• For banks & PSPs (Payment Service Providers), structured invoice data enables the step from pure payment processing to process and data integration.

What Is an E-Invoice – and Why Is It More Than Just a Format?

An e-invoice, in the VAT sense, is not simply an invoice sent electronically, but an invoice in a structured electronic format that enables its automated electronic processing. What is decisive is not that an invoice exists in digital form, but that its contents are transmitted as clearly defined, machine-readable data. Herein lies the difference from the traditional PDF invoice: a PDF can be read visually, but cannot be reliably processed automatically by systems without further effort. A genuine e-invoice, by contrast, can flow into ERP, accounting, approval, and archiving processes without any media discontinuity. This makes it not merely a new file format, but a building block for end-to-end, data-driven business processes.²’³

Important: An e-invoice is therefore not a “PDF with a better name”. It is a structured data record that transforms invoices from a mere document into an operationally usable event within a digital process. For companies, this means: the real added value is not created at the point of sending, but where invoice data is checked, approved, posted, reconciled, and archived. It is precisely at this interface that a regulatory obligation becomes a lever for automation, data quality, and process integration.

Normative Basis in Europe: EN 16931

The European foundation for the e-invoice is the standard EN 16931. It does not define a single file format, but a uniform semantic data model for electronic invoices. Simply put, the standard establishes which substantive contents an e-invoice must contain and how these are to be understood, so that different systems can interpret the same invoice data consistently. EN 16931 thereby creates the basis for interoperability across company, system, and national boundaries. National implementations and technical syntaxes can build upon this foundation without losing the common substantive core.⁴’⁵

Relevant Formats in Germany – Practically Important

In Germany, three formats or implementation forms are of particular practical relevance:

• XRechnung is the established standard in Germany, particularly for invoices to public-sector clients. XRechnung is a purely structured XML standard without a required visual PDF component and is consistently designed for machine processing. In the B2G environment, the format has been practically relevant for years and has generated considerable experience with validation, routing, and master data quality.⁶
• ZUGFeRD is a hybrid format that combines a visual PDF/A-3 presentation with embedded structured invoice data. It is therefore particularly attractive in the B2B environment because it bridges two worlds: specialist departments can continue to view the invoice in readable form, whilst systems simultaneously process the structured data section automatically. It is essential to note that the structured section is authoritative for machine processing.⁷
• Peppol BIS Billing 3.0 is a specification widely used across Europe for the interoperable exchange of invoices via the Peppol network. Peppol BIS Billing 3.0 is a CIUS based on EN 16931 and thus creates a standardised framework for cross-border and cross-platform invoice exchange. For banks and PSPs, this is particularly relevant because here not only the invoice format, but also routing, identifiers, and network capability gain in importance.⁸

Legal Obligations & Deadlines in Germany: What Comes When?

The Growth Opportunities Act resolved the mandatory introduction of e-invoicing in the German B2B sector. The introduction is being phased to give companies time to adapt their processes and systems.

Timeline for E-Invoicing (Germany, B2B)

• 01.01.2025: General obligation to receive for all companies – e-invoices must be capable of being received and processed; the question of the obligation to issue remains separate and must be examined on a case-by-case basis.
• 01.01.2027: General obligation to issue for companies with annual turnover exceeding €800,000; however, explicit exemptions apply to certain transactions, particularly in areas involving VAT-exempt supplies.
• 01.01.2028: General obligation to issue for all companies in the B2B sector (regardless of size/turnover); explicit exemptions also apply here, particularly in connection with VAT-exempt transactions.

What Companies Really Need to Deliver Now (Beyond “Receipt”)

In many organisations, attention is initially focused on technical receipt capability. However, what is decisive in practice is whether the downstream processes function reliably and operations are set up robustly.

For mere “receipt” to become genuine automation, the following are generally required:

• a clearly defined receipt channel including responsibilities (e.g. e-mail gateway, Peppol endpoint, platform),
• a human-readable presentation of structured invoices (for specialist departments, approvals, clarification cases),
• processes for checking, approving, and posting (including exception handling/workflows), and
• audit-proof archiving of the original data (not merely “PDF filing”).

Technical Requirements & Standards

For e-invoices to deliver their full benefit, certain technical requirements must be met – from structured data preparation to audit-proof archiving. The central foundation is the European standard EN 16931; in Germany, additional requirements apply to processing and archiving, in particular under the GoBD (Principles for the Proper Keeping and Storage of Books, Records and Documents in Electronic Form).

Key requirements are:

• Structured data (usually XML-based): amounts, taxes, payment terms, etc. are automatically retrievable;
• Conformity with EN 16931: prerequisite for standardised interpretation – including cross-border;
• Machine evaluability: the aim is Straight-Through Processing rather than manual data entry;
• Audit-proof archiving (GoBD): immutability, traceability, and availability over retention periods.⁹

Practical Perspective from the B2G Environment – Lessons from Real Projects

The public sector can serve as a blueprint: e-invoicing has been mandatory there for years – and clearly illustrates where projects actually fail in practice. The problems usually lie not in the “XML” itself, but in unambiguous identification, routing, data quality, and clean mapping.

Typical stumbling blocks have proved to be:

• The unambiguous identification of the invoice recipient is a fundamental prerequisite for correct delivery and processing of e-invoices. In practice, this is done, for example, via a Leitweg-ID in the public sector environment or via a Peppol-ID in network-based scenarios. If this assignment is missing or incorrect, the invoice is technically sent but does not reliably reach the correct organisational or systemic destination.
• Equally important is the maintenance, clear responsibilities, and binding rules for these identifiers. For Leitweg-IDs, Peppol-IDs, or other endpoint data to function reliably in day-to-day operations, master data must be kept current, responsibilities clearly regulated, and changes properly tracked. Otherwise, typical problems arise such as misrouting, returns, or unnecessary manual clarification cases, even though the actual invoice format is correct.
• Transport routes and routing are also critical in practice. Invoices travel, depending on the target scenario, via platforms, portals, or networks such as Peppol; in addition, status information is important – for example, whether an invoice has been received, formally validated, or rejected. It is precisely at these handover points that it becomes apparent whether a process is truly robustly set up or whether transparency and traceability are lacking.
• A further critical point is data quality and the clean mapping of content. This includes, for example, ensuring that mandatory fields are correctly populated, tax matters are accurately reflected, and special cases are unambiguously assigned to the appropriate attributes. Even minor inconsistencies can lead to invoices failing formally, being misinterpreted, or only being processable with additional manual effort.

Why the E-Invoice Is Strategically Relevant for Banks and PSPs

This is where the real shift in perspective occurs: in traditional payment transactions, the bank sees only the payment itself. With the e-invoice, the underlying business transaction now comes into focus for the first time – even before the payment is made.

Structured invoice data makes amounts, due dates, payment terms, and references available in machine-readable form – and thus becomes the data anchor for Invoice-to-Pay, Cash Visibility, and Automated Reconciliation.

Automation in the Payments Backbone (STP Instead of Clarification Cases)

E-invoices enable end-to-end integration of invoicing and payment processes:

• Straight-Through Processing (STP): invoice data flows into payment and posting processes without manual steps.
• Automatic payment reconciliation: unambiguous linkage of invoice and payment (matching).
• Fewer manual clarification cases: higher data quality reduces reconciliation effort.

Concrete Starting Points for Banks & PSPs (Service Logic)

Added value for the corporate customer from the e-invoice arises where banks and PSPs supplement the resulting data stream with appropriate services, for example:

• Invoice-to-Pay Services: payment initiation directly from the e-invoice, including due date and payment terms;
• Smart Matching & Exception Handling: workflow-based reconciliation of invoices and payments with clarification case management;
• Identifier Services: management and validation of Leitweg-IDs, Peppol-IDs, and electronic endpoints;
• Peppol Enablement as a Managed Service: connectivity, routing, status tracking for corporate clients;
• Compliance & Archiving Solutions: audit-proof archiving of structured invoice data as a supplementary bank service;
• Data-Driven Cash Management Services: forecasts, alerts, and analyses based on real invoice data.

Strategic Opportunities Beyond Pure Efficiency

Furthermore, structured invoice data opens up new business models and integration points:

• Integration with SEPA & Instant Payment: seamless end-to-end processes by combining invoice data and real-time payments.
• Embedded Finance models: financial services directly within the invoicing/procurement process (e.g. payment options, financing).
• Supply Chain Finance & Dynamic Discounting: discount and financing models along the supply chain on the basis of transparent invoice data.
• Data-driven liquidity services: more precise forecasts, cash management value-added services.

Consulting Roadmap: How Banks, PSPs, and Companies Should Proceed Sensibly Now

To turn “obligation” into a competitive advantage, a pragmatic roadmap is helpful.

Roadmap for Companies (B2B)

1. Operationalise e-invoicing capability: receipt channel, presentation, process, archive.
2. Prioritise data quality & mapping: comply with standards, handle special cases cleanly.
3. Rethink Invoice-to-Pay: leverage automation potential along the entire workflow.

Roadmap for Banks & Payment Service Providers

1. Define the data anchor: which invoice data is needed when (due date, references, terms)?
2. Set up product logic: Invoice-to-Pay, matching, Peppol enablement, ID services, archive/compliance.
3. Integration into client systems: ERP/TMS connectivity, workflows, real-time payments as the execution layer.

Is the E-Invoice Also Worthwhile for Companies with Predominantly VAT-Exempt Turnover?

For companies with predominantly VAT-exempt turnover, the question of benefit is particularly pertinent. From a regulatory perspective, the starting position is nuanced: for many VAT-exempt supplies under § 4 No. 8 to 29 UStG, there is no obligation to issue an e-invoice. At the same time, the general obligation to receive has applied to companies since 2025, provided they are acting as taxable persons.

This means: even those who frequently do not need to issue mandatory e-invoices themselves will encounter the topic in purchasing and in the processing of incoming invoices.

Whether voluntary use is worthwhile is therefore primarily a question of the company’s practical starting position. The decisive factors are in particular the invoice volume, the number of business partners involved, and the degree of standardisation in existing workflows. The more invoices are regularly processed and the more companies work with different counterparties, the more a structured electronic approach may be beneficial. Conversely, the benefit is usually smaller where the volume of documents is low, processes remain straightforward, and little system support is required.

Where Voluntary E-Invoicing Creates Clear Added Value

Efficiency in invoice receipt: incoming structured invoices can be more easily validated, assigned, and archived, thereby reducing duplicate entries and manual errors.

Standardisation vis-à-vis business partners: those who voluntarily adopt structured formats reduce workarounds in exchange with suppliers, customers, and service providers, and create more uniform workflows.

Better connectivity to accounting, DMS, and ERP: even without a statutory obligation, the e-invoice improves integration into digital processes and facilitates subsequent automation steps.

Cleaner governance and archiving: structured data supports GoBD-compliant filing, increases traceability, and improves subsequent auditability.

When the Added Value Is Limited

For companies with very low invoice volumes, few B2B relationships, and largely straightforward processes, the direct benefit may be limited. Where outgoing invoices are only rarely created, internal processes remain largely manual, and no system integration is planned, voluntary introduction initially creates primarily transitional effort: selecting appropriate software, adapting templates, organisational responsibilities, testing, and where necessary, training. In such constellations, a lean receipt and archiving capability may be more economically sensible than a complete overhaul of the outgoing invoice process.

Weighing Up VAT Exemption: Useful Lever or Avoidable Complexity?

The e-invoice is not automatically an end in itself for companies with predominantly VAT-exempt turnover.

It is most beneficial when a company, despite VAT-exempt outgoing transactions, processes many incoming invoices, works with professional B2B partners, wishes to advance digitalisation in accounting, or requires scalable processes going forward.

A comprehensive voluntary introduction is less beneficial where the volume of documents is low, processes function stably on a manual basis, and the technical transition effort clearly outweighs the process benefits.

Specific Added Value for Insurance Companies and Banks

For insurance companies and banks, the added value is most apparent in invoice receipt and adjacent control processes. Although many of the outgoing transactions of these organisations are VAT-exempt and therefore frequently not subject to the obligation to issue e-invoices, they process large volumes of incoming invoices internally from IT, facilities management, consultancy, marketing, claims management, external services, and intra-group recharges. It is precisely here that a more standardised e-invoice processing approach can help to reduce media discontinuities, accelerate approvals, identify duplicates and formal errors earlier, and improve traceability for audit, compliance, and inspection purposes.

Based on general benchmarks for AP automation and e-invoice processing, an estimated reduction in operational processing costs in the invoicing process of approximately 15% to 35% appears realistic for these sectors, where predominantly manual or PDF-driven workflows currently prevail.

With regard to processing times, an estimated reduction of approximately 20% to 50% appears realistic, particularly for standardisable, recurring invoices with clear approval rules. In more fragmented or exception-intensive processes, the effect will usually be at the lower end of these ranges; with higher volumes, good master data management, and close ERP/workflow integration, it is more likely to be at the upper end.

Important: These figures are expressly to be understood as estimates and not as reliable case study values for any individual institution. They are derived from cross-industry benchmarks for invoice and AP automation, which frequently show significantly higher savings at mature digitalisation levels.

For banks and insurers, a more conservative range has been deliberately derived from this, because there additional review steps, governance requirements, complex cost centre logic, regulatory controls, and a higher proportion of exceptions typically limit the full automation effect. Put differently: the estimate is not based on the assumption of a fully automatic “touchless” target scenario for all invoices, but on a realistic partial automation of invoice receipt, validation, approval workflows, and archiving in a heavily regulated environment.

The pragmatic recommendation is therefore: for these companies, at least a robust receipt, visibility, and archiving solution is advisable. A complete voluntary overhaul of the outgoing invoice process is only worthwhile where a clearly measurable operational benefit arises from standardisation, automation, and system connectivity.

Conclusion: The Decisive Question Is Not “Fulfil the Obligation” but “Choose Your Role”

For companies subject to VAT, the e-invoice is initially a regulatory requirement. Even for companies not subject to VAT, it can be a lever for more efficient processes.

For banks and PSPs, it is a new data anchor in transaction banking and payments – with the potential to prepare payment processes, not merely execute them.

Those who understand and utilise invoice data can bring automation forward, improve cash visibility, industrialise matching, and integrate more deeply into the value chains of corporate clients – moving away from being a pure payment processor, towards becoming a data-driven financial partner.

The central question for banks and PSPs is therefore not “How do we fulfil the e-invoicing obligation?” but “What role do we wish to play as a bank in a world of structured invoice data?”