XRechnung rejected: narrow down error messages systematically.
Understand why a structured invoice was rejected and prepare the correction in the system that generated it, including another technical test.
Read the German originalKeep the exact response
A rejection may be caused by the file format, a business rule or a recipient requirement. Save the exact message together with the source system version and the time of the attempt. A screenshot without its associated transaction is often insufficient to reproduce the problem.
For invoices to public authorities, information such as the Leitweg-ID may matter. Obtain it from the contracting authority. Peppol describes a transmission route; it does not replace checking the invoice profile and its required information.
Correct the source system
If an exported XML file is changed manually just once, the next invoice may contain the same error. Look for the cause in master data, field mapping or export settings. Original documents and technical test copies must remain distinguishable.
Start with a few examples for the same recipient. If the error pattern and profile match, a shared correction path can be tested. Business amounts and tax information are confirmed by the responsible people, not redefined by a format correction.
Distinguish a test result from acceptance
A correction is followed by another technical test. This shows whether the named rule is satisfied. The recipient may also have its own business requirements. A successful local check therefore does not confirm that the invoice has been accepted into the recipient's processing system.
A limited troubleshooting package provides a traceable diagnosis and a correction path. For recurring workflows, a check before sending can be added afterwards. Provider fees and production transmission are expressly agreed separately.
What does this look like in your work?
We can turn the idea into a sensible next step with you.
XRechnung rejected? Troubleshooting and a correction path · Packages