Guide
Markdown exportValidate DATEV invoice exports
Use Invoice Converter to validate the exported invoice package, repair review fields, and generate XRechnung/ZUGFeRD output.
Export expectations
Check DATEV export files for complete buyer references, VAT breakdowns, payment data, and structured attachment readiness.
Validate the exported package, not only the booking view: PDF evidence, structured XML where available, and customer/export fields used for e-invoice dispatch.
Export signals to inspect
DATEV exports often separate accounting master data from document evidence. Inspect whether e-invoice recipient fields, dispatch flags, supplier numbers, and the actual XML/PDF artifact travel together.
Validation checklist
- Open the exported XML and confirm BuyerReference contains the Leitweg-ID for public-sector invoices, not only a note in the PDF.
- Check VAT category mapping line by line: standard, exempt, reverse charge, and zero-rated lines must each produce matching VAT breakdowns.
- Confirm payment means 58 includes a clean IBAN in BT-84 and that payment terms or due date satisfy BR-CO-25.
Export triage table
| Symptom | Likely field or rule | Export-side fix |
|---|---|---|
| Public-sector receiver rejects routing although the PDF contains a Leitweg-ID. | BT-10 / BR-DE-15 | Move the routing ID into the exported BuyerReference field, not a PDF-only note. |
| The invoice has bank details visually, but validation reports missing payment account. | BR-61 / BT-84 | Export the IBAN as structured payment account data for payment means 58. |
Common validation failures
Missing Leitweg-ID, incomplete VAT category mapping, or PDF attachment without structured invoice data.
Validation workflow after export
Use Invoice Converter to validate the exported invoice package, repair review fields, and generate XRechnung/ZUGFeRD output.