Validation

EN 16931 validation

Every invoice processed by Rekivo is automatically validated against the European norm EN 16931. This ensures compliance with legal requirements and catches errors before they reach your accounting system.

XML schema validation ensures the document is technically well-formed.
Required field checks verify that all mandatory business fields are present.
Amount calculation checks recalculate line totals, net amounts, and tax sums.
Cross-field consistency checks detect contradictions in the data.

Validation statuses

Each invoice receives one of four validation statuses:

Valid — The invoice passes all validation checks and is fully EN 16931 compliant.

Warning — The invoice is technically valid but has minor issues that should be reviewed (e.g., missing optional fields).

Invalid — The invoice has errors that violate EN 16931 rules. Review the error details for specifics.

Pending — Validation is still in progress. This typically resolves within a few seconds.

Understanding validation errors

When an invoice fails validation, Rekivo displays detailed error messages referencing the specific business terms (BT) or business groups (BG) from EN 16931. Each error includes the field identifier, a human-readable description, and the expected vs. actual value where applicable.

Info: Common errors include missing invoice numbers (BT-1), missing seller names (BT-27), and amount calculation mismatches (BR-CO-10, BR-CO-15).

ZUGFeRD PDF verification

For ZUGFeRD invoices, Rekivo extracts the embedded XML data from the PDF and validates it separately. The PDF is stored alongside the XML data so you can view the visual representation. Rekivo also verifies that the embedded XML matches the ZUGFeRD profile declared in the document.