DMS for E-Invoicing 2026: Receive, Archive & Workflow with Docuflair

The e-invoicing mandate has been reality since 2025. What remains for many companies is the pressure: How do we reliably receive XRechnung files? How do we archive in a GoBD-compliant way? And how do we integrate everything into our accounting workflow without introducing five new isolated tools?

The answer is not another specialised piece of software, but a document management system (DMS) as the hub. This article shows why the DMS is the natural integration layer for e-invoices, how Docuflair maps the full process from Peppol to DATEV, and what you should additionally have on your radar for 2026.

From compliance topic to workflow topic

Why the mandate is only the beginning

2024 was the year of the retrofitting panic. 2025 brought the receipt obligation — and many companies frantically introduced an XRechnung viewer tool or repurposed their e-mail inbox as an archive. Both are stopgaps, not processes.

From 2026, the conversation shifts. The mandate itself is no longer in question — the topic becomes how invoice reception scales and integrates with accounting:

Volume: Companies with 500+ incoming invoices per month can no longer manually review and route XRechnung files.
Approval processes: The four-eyes principle, cost-centre coding, and project allocation need to be digital — not printed onto a desk.
Archiving: 10 years of GoBD-compliant storage in the original format — a network drive will not meet that requirement.
Retrieval: During a tax audit or in day-to-day business, invoices must be findable in seconds, including full-text search over the XML.

This is the point where the "mandate" turns into a productivity lever. Companies that cleanly digitise invoice receipt shorten turnaround times, reduce lost cash discounts, and noticeably relieve accounting.

The decisive question: Do I stitch together five individual tools (Peppol access + viewer + approval tool + archive + ERP link), or do I use one DMS that covers all five roles?

How Docuflair DMS processes e-invoices

The 5-step workflow from receipt to ERP

1. Multi-channel reception

E-invoices arrive not only via Peppol — they come by e-mail (as an XML attachment or ZUGFeRD PDF), through supplier portals of large customers, or as OCR-based PDF scans from legacy processes. Docuflair Capture monitors all channels simultaneously:

Peppol Access Point output (XML from the access point folder)
E-mail inboxes (IMAP, Exchange) with filter rules by sender and attachment type
SFTP and network drive input folders for EDI partners
Upload portals for suppliers without Peppol access

2. Format detection & validation

Docuflair automatically detects whether the file is an XRechnung, ZUGFeRD, a PDF, or a scanned document, and runs the appropriate validation:

XRechnung: Schema validation against XRechnung 3.0 / UN/CEFACT
ZUGFeRD: Profile detection (MINIMUM, BASIC, EN 16931, EXTENDED), XML extraction from PDF/A-3
PDF without XML: OCR with structured data extraction (invoice number, date, amounts, VAT ID)
VAT ID validation: Automatic verification against VIES for EU suppliers (integrated with the Docuflair VAT validation tool)

3. Coding & approval workflow

Based on the extracted data, each invoice is automatically assigned to the right clerk, cost centre, or project. Configurable rules drive the approval process:

Amount thresholds for single, dual, and management approval
Cost-centre owners by supplier or project number
Escalation paths if an approval remains untouched for too long
Mobile approval via web interface or e-mail link

4. GoBD-compliant archiving

Each e-invoice is stored in its original format — XRechnung as XML, ZUGFeRD as the complete PDF/A-3 file. In addition, Docuflair Archive creates:

SHA-256 hash at the time of archiving (integrity proof)
Qualified timestamp (optional via trust service provider)
Audit trail with all access, approvals, and modifications
Full-text index including XML fields for instant retrieval
Automatic 10-year retention with a legally compliant deletion concept

More on the archiving side: E-invoice archiving: GoBD-compliant retention.

5. Handover to ERP / DATEV

After approval, Docuflair hands the structured data over to your accounting system — without manual re-keying:

DATEV: Direct handover to DATEV Unternehmen Online via XML interface
SAP: IDoc INVOIC01 / INVOIC02 with a reference to the archived original
Microsoft Dynamics 365 / Business Central: Web service binding
Sage, Addison, Lexware: CSV or XML export per customer mapping

Integration with your existing system landscape

Docuflair as the layer between reception and accounting

A DMS for e-invoicing has to fit into an existing landscape — very few companies start from scratch. Docuflair acts as an integration layer between input channels (Peppol, e-mail, EDI) and target systems (ERP, finance, line-of-business applications):

Target system	Integration type	What is handed over?
DATEV Unternehmen Online	Native XML interface	Invoice data + original document (PDF/A or XML)
SAP S/4HANA / ECC	IDoc INVOIC, ArchiveLink	Posting data + archive link to the original document
Microsoft Dynamics 365	REST API, OData	Structured invoice data, document reference
Agenda, ADDISON, Lexware	CSV / XML export mapping	Posting records in the customer's chart of accounts
LoB applications (RA-MICRO, ADVOKAT, legal software)	File handover, web service	Case allocation, client reference

The big win: your accounting team continues to work in DATEV or SAP — Docuflair handles reception, validation, approval, and archiving in the background. The accounting software receives exactly what it needs: clean, verified posting data with a link to the audit-proof original.

What's new in 2026?

Issuance obligation, Peppol growth, and the ViDA outlook

Issuance obligation for large enterprises

Since 1 January 2025 all German companies have had to be able to receive e-invoices. From 2026 the issuance obligation begins in stages: companies with more than EUR 800,000 in prior-year revenue must issue B2B invoices as XRechnung or ZUGFeRD. From 2027 this obligation applies to every company, regardless of size.

The consequence: if you have only covered the receiving side today, you need to digitise outbound invoicing in 2026/27 as well. A DMS is doubly valuable here — it stores both incoming and outgoing invoices in one unified archive.

Peppol as the de-facto standard

The Peppol network is becoming the dominant transport channel for B2B e-invoices in 2026. More and more large enterprises and public authorities require Peppol delivery; some explicitly exclude e-mail as a reception channel. If you haven't integrated Peppol yet, 2026 is the year to act.

Background: Receiving and processing e-invoices: channels and workflows.

ViDA: the European perspective

The EU initiative "VAT in the Digital Age" (ViDA) takes concrete shape in 2026. A cross-border digital reporting system for intra-Community transactions is planned from 2030 — in simple terms: invoice data must not only be exchanged but also reported to tax authorities in near real time. Companies that build a structured data foundation in their DMS today are prepared for ViDA; those sticking with paper and PDF storage will have to migrate again in 2030.

Updated XRechnung 3.0 & Factur-X 1.07

On the technical side, XRechnung 3.0 has established itself as the stable version; ZUGFeRD/Factur-X evolves regularly (the current profile set has been extended to cover logistics and leasing scenarios). Your DMS should be able to apply format updates without customer intervention — Docuflair ships format schemas centrally.

Why Docuflair DMS — and not a standalone tool?

A DMS that does e-invoicing versus an e-invoicing tool with a mini-archive attached

Criterion	Docuflair DMS	Standalone e-invoicing tool
Document scope	All documents (invoices, contracts, correspondence, HR, construction files, legal case files)	Incoming invoices only
Archive capabilities	Full GoBD archive with audit trail, hash, timestamp	Usually "archive-light"; data is lost after handover to the ERP
Workflow engine	Freely configurable approval processes for all document types	Invoices only
Deployment	On-premises or private cloud — data stays in-house	Mostly SaaS with data held in the vendor's cloud
Integration depth	DATEV, SAP, Dynamics, Agenda, ADDISON, line-of-business apps	Often limited to DATEV or a single ERP family
Future-proofing	Grows with new document types and processes	Fixed scope — each new requirement needs a new tool

The DMS model scales: what you set up today for e-invoices will carry your contracts, HR files, customer correspondence, and outgoing invoices tomorrow. A standalone tool solves one problem — and creates five new silos.

E-invoicing 2026 without the patchwork

Docuflair combines reception, validation, GoBD archiving, and DATEV/SAP handover in one on-premises solution. In a 15-minute demo we'll walk you through the complete workflow using a real Peppol example.

Request free demo Explore Docuflair Archive

Frequently Asked Questions

Answers to the most important questions about DMS and e-invoicing 2026

Is a DATEV connection enough, or do I also need a DMS for e-invoicing?

DATEV handles the accounting logic but does not replace audit-proof document storage. A DMS like Docuflair Archive stores e-invoices in their original format (XML or PDF/A-3) in a GoBD-compliant way, creates audit trails, and provides full-text search across all years. DATEV and DMS complement each other: DATEV for accounting, DMS for legally compliant archiving and workflow.

What changes in 2026 compared to 2025 for the e-invoicing mandate?

Since 1 January 2025, German companies must be able to receive e-invoices. In 2026, the active issuance obligation begins in B2B for companies with more than EUR 800,000 in prior-year revenue; from 2027 it applies to all companies. In addition, the EU initiative ViDA (VAT in the Digital Age) is taking shape — a cross-border digital reporting system is planned from 2030.

Does the DMS have to provide the Peppol connection itself?

Not necessarily. Peppol Access Points are often operated by specialised service providers. The DMS needs to reliably receive, validate, and archive the XML files delivered by Peppol — in Docuflair this happens via a configurable input folder or API endpoint. Companies without Peppol access can also receive e-invoices via e-mail or a supplier upload portal; Docuflair processes all input channels uniformly.

How can incoming invoice approval (four-eyes principle) be mapped in the DMS?

Docuflair Workflow offers configurable approval processes with roles (clerk, cost-centre owner, finance lead). Each e-invoice is automatically assigned to the responsible reviewer after receipt, notified by e-mail, and, once approved, forwarded to DATEV or the ERP. All approval steps are logged in the audit trail.

Is Docuflair DMS on-premises or cloud?

Docuflair is a pure on-premises / private-cloud solution — invoice data never leaves your infrastructure. Especially for e-invoicing, with its sensitive supplier and amount data, this is a decisive difference compared to US cloud providers when it comes to GDPR compliance, tax audits, and IT security.

DMS for E-Invoicing 2026