A Valid Invoice with Hidden Risk
This example illustrates how an invoice can pass technical checks yet still carry tax risk.
Invoice Summary
INV-2026-00417
Supplier
Beispiel GmbH
Buyer
Musterkunde UG
Net Amount
€4,800.00
VAT (19%)
€912.00
Total
€5,712.00
Format
XRechnung 3.0
FiscalLayer Decision
Findings
VAT amount does not match calculated value at line level
The total VAT amount matches the expected value (€4,800.00 × 0.19 = €912.00). However, one line item shows a VAT amount that deviates by €0.02 due to rounding.
Why it matters
German tax authorities may reject VAT deductions when invoice totals do not reconcile exactly with line-item calculations. A €0.02 discrepancy is unlikely to trigger rejection on its own, but combined with other issues, it increases audit scrutiny.
Buyer reference field is empty
The invoice does not contain a buyer reference (Bestellnummer or internal reference).
Why it matters
Many organisations require a buyer reference for internal processing. More importantly, for B2G invoices (public sector), a missing Leitweg-ID or reference can cause the invoice to be rejected or delayed. For B2B, absence of this field may slow down payment or complicate reconciliation.
Why This Example Matters
This invoice would pass most ERP import checks. The XML is valid. The format is correct. The amounts are plausible.
But the rounding inconsistency and missing reference are exactly the kind of issues that surface during tax audits — months after the invoice was booked.
FiscalLayer makes these risks visible at the moment of receipt, so you can decide whether to book, request a correction, or flag for review.
This is a fictional example for illustration purposes. No real company data is represented.