Convert XRechnung to Excel
Drop the XRechnung XML your customer or supplier sent. Both permitted syntaxes are read, the German-specific fields come along, and what you get back is a spreadsheet instead of a wall of tags.
| # | Description | Qty | Unit | Unit price | VAT % | Net amount |
|---|
| Category | Rate | Taxable base | VAT amount |
|---|
| # | Qualifier | Reference | Amount | Paid |
|---|
| Segment | Element | Value |
|---|
What XRechnung actually is
XRechnung is Germany's national reading of EN 16931, and it is a rule set rather than a file format: the same invoice may arrive as UBL 2.1 or as UN/CEFACT CII, both valid, both looking nothing alike. Public authorities have required it since 2020 and the B2B mandate phases in from 2027, so the file is turning up in ordinary supplier mailboxes now. This page reads both syntaxes and maps them onto identical columns, which is the part that usually costs an afternoon.
What you get out
Every field below is read from the file itself. Nothing is inferred, and a field the invoice does not carry is left empty rather than filled in with a plausible guess.
- Leitweg-ID and buyer reference, the routing fields German authorities insist on
- Invoice number, type code, issue date, due date and currency
- Seller and buyer name, address, VAT number and tax registration
- Every line: number, description, quantity, unit, unit price, VAT rate, net amount
- VAT per rate and category, taxable base, and the totals block down to amount due
- IBAN, BIC, payment terms and payment means code
Questions
Is my file UBL or CII?
You do not need to know. Both are XRechnung, both are read here, and both come out with the same column names. If you are curious, the format pill above the results tells you which one it was after you drop the file.
Does it read XRechnung 3.0?
Yes, and 2.x as well. The differences between versions sit in validation rules rather than in where the data lives, so the extraction is the same.
The Leitweg-ID is missing from my export.
Then it was not in the file. It is mandatory for public-sector invoices but not for B2B ones, so a supplier invoice between two companies often has none. The column stays empty rather than being invented.