One Year of Mandatory E-Invoicing: Why the B2B Standard Is Drowning in ZUGFeRD Chaos

Note: This article covers the German e-invoicing mandate (E-Rechnungspflicht). The requirements are specific to companies operating in Germany.

Earlier this year, I published a summary of what SMEs need to know about mandatory e-invoicing. Reception mandate since January 2025, sending mandate from 2027, EN 16931 formats. Straightforward enough in theory.

Now, more than a year after the reception mandate took effect, it’s time for an honest assessment: The reality on the ground is catastrophic. E-invoicing is one of the most pressing topics in my consulting on compliance and regulatory requirements.

E-Invoicing Mandate in Practice: What Is Going Wrong in Accounting Departments

What I currently see in consulting projects is sobering. The e-invoicing mandate was formally introduced, but the operational implementation at many mid-market companies is nothing more than a patchwork of workarounds.

Typical scenes from daily operations:

• A ZUGFeRD PDF arrives by email. The accounting team opens the PDF, reads the visible invoice – and manually enters the data into the ERP system. The embedded XML is ignored entirely.
• The ERP system can technically import ZUGFeRD. In practice, the import fails on every third invoice because mandatory fields are missing or the format deviates slightly from the specification.
• Supplier A sends XRechnung, Supplier B sends ZUGFeRD in BASIC profile, Supplier C sends a plain PDF and calls it an “e-invoice.” The accounting team treats all three the same way: manual entry.

The result: e-invoicing exists on paper. In practice, nothing has improved for many companies – in fact, the workload has increased.

ZUGFeRD Problems: Profiles, Validation, and ERP Import Failures

ZUGFeRD was designed as a pragmatic solution: a PDF that humans can read, with machine-readable XML embedded inside. A hybrid approach. It sounded good. In reality, this dual structure is exactly what causes the problems.

The Profile Confusion

ZUGFeRD defines multiple profiles: MINIMUM, BASIC WL, BASIC, EN 16931 (COMFORT), and EXTENDED. The full specification is maintained by the Forum elektronische Rechnung Deutschland (FeRD). Not every profile contains enough data for automated processing. A supplier delivering in the MINIMUM profile formally complies with the mandate – but provides so little structured data that the recipient can’t do anything useful with it.

The Validation Gap

There is no mandatory validation mechanism on the sender side. This means companies send out XML files that are technically malformed – incorrect tax categories, missing bank details, invalid country codes. The recipient only discovers this at import time. Then the back-and-forth begins: inquiry, correction, resend.

ERP Systems That Only Pretend

Many ERP vendors marketed ZUGFeRD import as a feature. What they shipped is often a minimal parser that breaks on non-standard profiles or edge cases. Error handling amounts to a cryptic message in the log file. The accounting team falls back on the tried-and-true method: copy and paste.

The Hidden Costs of Non-Functioning E-Invoicing

Anyone who thinks this is just a temporary teething problem is underestimating the financial impact.

Time spent: Every manually processed e-invoice costs 5-10 minutes – time that automation was supposed to save. At 500 incoming invoices per month, that adds up to 40-80 hours of manual rework.

Error rates: Manual entry means typos. Incorrect account assignments. Missed early payment discounts. These aren’t minor issues – they’re real costs that never appeared in any e-invoicing implementation business case.

GoBD compliance risk: Anyone who ignores the XML and only archives the PDF has a compliance problem. Germany’s GoBD regulations require retention of the original digital format. That’s the XML, not the PDF.

Fixing E-Invoicing: Four Steps for SMEs

The good news: these problems are solvable. But not with the next software update – with a systematic approach.

1. Implement Sender-Side Validation

Before an e-invoice leaves your organization, it must be validated against the ZUGFeRD schema. Free tools like the KoSIT validator check conformity. It costs nothing and eliminates 80% of import problems on the recipient side.

2. Test Your ERP Import Realistically

What matters is not the vendor’s feature checklist, but the real-world test. Take 20 actual incoming invoices from different suppliers and test the import. Document what works and what doesn’t. Then talk to your ERP vendor – with specific failure cases, not vague complaints.

3. Communicate Profile Requirements

Define which ZUGFeRD profile you require from your suppliers. EN 16931 (COMFORT) is the sensible minimum standard for automated processing. MINIMUM and BASIC WL are not sufficient. Communicate this proactively – ideally as a supplement to your purchasing terms.

4. Review Your Archiving

Make sure your DMS or archiving solution stores both the PDF and the XML in an audit-proof manner. Not one or the other – both belong together.

Bottom Line

The e-invoicing mandate was the right move. But implementation has stalled halfway at many companies. Anyone still manually entering data that should be processed automatically is wasting money and risking compliance issues.

The solution isn’t a new tool – it’s process work: implement validation, honestly test your ERP import, clearly communicate requirements to suppliers, and set up proper archiving. Companies that tackle this in the coming weeks will be far better positioned for the 2027 sending mandate than average.

Next Step

Stuck in ZUGFeRD chaos? I help with the assessment, optimize your ERP import, and get your e-invoicing process in shape — pragmatically, not theoretically.

→ Book a free consultation

→ Or read more first: DATEV Integration Audit