Guide
Markdown exportValidate SAP Business One invoice exports
Validate sample exports before rollout, then use failed-rule output as a mapping checklist for SAP fields.
Export expectations
Prepare SAP Business One invoice exports for structured e-invoice validation and country-specific routing requirements.
Validate the electronic-document output generated by SAP Business One, not an A/R invoice screen or DI API payload before the Electronic Document Service has applied the selected format.
Export signals to inspect
SAP Business One Germany documentation names XRechnung and ZUGFeRD and points setup to Document Settings, Electronic Document Service, and the Electronic Document Import Wizard. Those configuration points determine what the validator actually sees.
Validation checklist
Use these points as the practical checks for this section.
- Record the Electronic Document format/version used for the sample export; stale formats explain many mandate-version failures.
- Compare SAP business partner fields to BT-10, BT-31, BT-48, BT-81, and BT-84 before changing invoice-line logic.
- Validate one standard VAT invoice, one reverse-charge invoice, and one exempt invoice before rollout because each uses different tax breakdown rules.
Export triage table
| Symptom | Likely field or rule | Export-side fix |
|---|---|---|
| Sample XML fails after a mandate/profile update even though invoice master data did not change. | CustomizationID / profile version | Check the SAP Business One electronic document format and EDS setup version before editing invoice data. |
| Customer reference exists in SAP, but exported XML has no buyer reference or VAT ID. | BT-10 / BT-31 / BT-48 | Map business partner and document reference fields into the electronic document format, then regenerate. |
Common validation failures
Project/accounting references may export correctly while EN 16931 buyer references, payment means, and VAT category codes remain unmapped.
Validation workflow after export
Validate sample exports before rollout, then use failed-rule output as a mapping checklist for SAP fields.