top of page

XRechnung and ZUGFeRD in SAP: Why E-Invoices Are Still Reviewed Manually

Nov 13
4 min read

Most accounts payable teams in Germany have by now received their first structured invoices, and many have discovered an uncomfortable truth: the invoice arrives as data, but someone still opens it, reads it and types it into SAP. The promise of e-invoicing was straight-through processing. In practice, manual invoice review remains the default, and for teams working with XRechnung in SAP, the reasons are more technical than most people expect.

The pressure to fix this is real. Since 1 January 2025, businesses in Germany have been required to be able to receive e-invoices, and from 1 January 2027, businesses with prior-year turnover above €800,000 must also issue them for in-scope domestic B2B transactions, subject to statutory exceptions and applicable transitional rules. The reference for that threshold is the prior-year turnover, which means 2026 figures decide who has to issue from next January. Whatever your own issuing obligation, the receiving side is already live, and the invoices are already coming in. See the German e-invoicing timeline and guidance on mandatory e-invoicing in Germany.

Why XRechnung in SAP Is Harder Than It Looks

An XRechnung is a pure XML file with no visual layer. It follows the European standard EN 16931 and is built in one of two XML syntaxes, so the first problem is simply that finance users need a suitable viewer to read it. Finance teams cannot review an XML invoice in SAP the way they review a PDF without suitable tooling, so they ask for a human-readable copy, and that copy becomes the thing people check. The structured data, the whole point of the exercise, ends up ignored. For SAP teams, handling an XML invoice means someone has to parse it, map every field to the right place and decide what happens when the data does not fit the system.

ZUGFeRD in SAP: The Hybrid Trap

ZUGFeRD brings a different problem. It is a hybrid format that embeds structured XML data inside a human-readable PDF. That sounds ideal, but it creates a trap for ZUGFeRD in SAP. If the process only treats the file as a PDF, it falls back to OCR or manual keying and never touches the embedded data. Worse, the visible PDF and the embedded XML can disagree. The structured XML is the authoritative part for VAT purposes, yet the PDF is what the reviewer sees. A team that reads one and processes the other has built a risk into its invoice receipt. Read more about Germany’s e-invoicing mandate and structured invoice processing.

Why Validating an E-Invoice Is the Real Bottleneck

To validate an e-invoice properly takes more than checking that a file opens. A sound approach works in layers. The first layer is syntax: is the XML well formed and does it follow the schema? The second layer is the business rules of EN 16931 and the German specification, such as mandatory fields, correct totals, tax category logic and valid references. The third layer is what only your own system can know: does the supplier exist in the vendor master, does the purchase order match, are the tax codes plausible, is this a duplicate? Most manual review in AP exists because the third layer is missing. A file can be technically valid and still be wrong for your company.

That gap explains a pattern many finance leads recognize. The invoice passes a basic format check, but someone still has to confirm the amounts against the order, the supplier against the vendor record and the tax treatment against the booking rules. Because nobody trusts the automatic result, the review is done by hand every time, even for the clean invoices that make up the large majority.

Moving to Review by Exception

A more useful goal for SAP invoice receipt is review by exception. In a good setup, an incoming invoice, whether XRechnung, ZUGFeRD or another structured format, is picked up from the channel where it arrives and validated across all three layers. If it passes, it moves into SAP without anyone touching it. If it fails, the reviewer gets a clear reason, such as a missing purchase order reference or a total that does not reconcile, instead of a file to inspect from scratch. The original XML is kept alongside the booking, so the audit trail points to the real invoice and not to a copy.

Getting there does not require replacing SAP. It requires deciding where validation happens, how the XML invoice in SAP is matched to master and order data, and which cases genuinely need a person. Teams that start by measuring how many of their current invoices are really reviewed because of a data problem, and how many only because of habit, usually find that most manual work can be removed.

What to Do Before the Volume Grows

With the issuing obligation expanding in 2027 and the general transition ending in 2028, subject to statutory exceptions, the sensible time to fix invoice receipt is before the volume of structured invoices grows. Manual review was an acceptable bridge while e-invoices were rare. It will not scale once they are the norm.

See it working on your own invoices

If you want to find out where your SAP invoice receipt loses automation, a short walkthrough with your real XRechnung and ZUGFeRD files is the fastest way. Book a demo with Docnova and we will show you validation, matching and exception handling on your own invoice samples.

For invoice processing inside SAP ECC and SAP S/4HANA, explore the Melasoft SAP e-invoicing Add-On.

Source for German VAT invoicing and retention requirements: Federal Ministry of Finance e-invoicing FAQ.

 
 
 

Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page