# ERP export validation guides

Use these guides to check export completeness before converting or validating invoices against EN 16931 profiles.

## How to use these guides

Use these guides to check export completeness before converting or validating invoices against EN 16931 profiles.

The focus is export validation: identify missing fields, weak mappings, and profile gaps before invoices reach customers or authorities.

## Export guides

- [Validate DATEV invoice exports](/resources/erp-export-validation/datev) (DATEV): Check DATEV export files for complete buyer references, VAT breakdowns, payment data, and structured attachment readiness.
- [Validate Lexware invoice exports](/resources/erp-export-validation/lexware) (Lexware): Review Lexware export settings for XRechnung-ready references, tax treatment, line detail, and payment terms.
- [Validate SAP Business One invoice exports](/resources/erp-export-validation/sap-business-one) (SAP Business One): Prepare SAP Business One invoice exports for structured e-invoice validation and country-specific routing requirements.
- [Validate Odoo invoice exports](/resources/erp-export-validation/odoo) (Odoo): Check Odoo invoice exports and localization modules for EN 16931 field completeness before sending.
- [Validate Microsoft Dynamics invoice exports](/resources/erp-export-validation/microsoft-dynamics) (Microsoft Dynamics): Validate Dynamics invoice exports, electronic reporting configurations, and field mappings before customer rollout.
