How to Validate E-Invoices: Ensuring Compliance

Validating electronic invoices before submission is one of the most important steps in the e-invoicing process. A single missing field, an incorrect tax calculation, or a structural error in the XML can cause an invoice to be rejected by the recipient's system, delaying payment and creating unnecessary administrative overhead. Validation ensures that your e-invoice conforms to the required technical standard, contains all mandatory data elements, and passes the business rules defined by the applicable format specification. Whether you are sending XRechnungen to German public authorities or ZUGFeRD invoices to business partners, proper validation is essential for smooth, error-free invoice processing.

E-invoice validation typically operates on multiple levels. The first level is schema validation, which checks whether the XML structure of the invoice conforms to the technical specification, such as the UBL or CII syntax used by XRechnung and ZUGFeRD respectively. The second level is schematron validation, which applies business rules to verify that the data content is logically consistent. For example, schematron rules check that the sum of line item amounts matches the invoice total, that the correct tax category codes are used, that mandatory fields like the seller's VAT ID are present, and that conditional rules are satisfied. A third level of validation may be performed by the receiving platform, such as the ZRE, which checks for recipient-specific requirements like a valid Leitweg-ID.

Common validation errors that lead to invoice rejection include missing or malformed buyer and seller references, incorrect ISO currency or country codes, tax amounts that do not match the calculated values based on the net amount and tax rate, missing payment means information, and line items with zero or negative quantities where not permitted. For XRechnung specifically, a missing or invalid Leitweg-ID is one of the most frequent causes of rejection when invoicing federal authorities. Another common issue is using an outdated version of the XRechnung specification, as the KoSIT (Koordinierungsstelle fuer IT-Standards) updates the format regularly and older versions may no longer be accepted.

Several tools are available for validating e-invoices. The KoSIT provides an open-source validation tool that checks XRechnung files against the current specification and can be integrated into existing workflows. The ZRE platform also offers a built-in validation check upon invoice submission. For ZUGFeRD invoices, the FeRD community provides validation resources and the Mustang library offers programmatic validation capabilities. EasyInvoice takes a proactive approach by validating your invoices automatically during creation, catching errors before they can cause problems. This built-in validation ensures that every invoice you generate meets the required standard without you needing to use separate tools or understand the technical details of XML validation.

Best practices for e-invoice validation include validating every invoice before sending, even if your software has built-in checks. Keep your invoicing software up to date to ensure it supports the latest format versions and business rules. Maintain a log of any validation errors and their resolutions to identify recurring issues in your process. Test your invoicing workflow with a small batch of invoices before rolling it out at scale, especially when switching to a new format or platform. Finally, stay informed about updates to the XRechnung and ZUGFeRD specifications, as changes to business rules or mandatory fields can affect previously valid invoice templates.