# Validate Lexware invoice exports

Use the review step to fill missing EN 16931 fields before final validation and download.

## Export expectations

Review Lexware export settings for XRechnung-ready references, tax treatment, line detail, and payment terms.

Validate the downloaded XRechnung XML or ZUGFeRD/Factur-X file directly; a PDF preview or invoice list is not proof that the structured payload is complete.

## Export signals to inspect

Lexware states that XRechnung XML can be downloaded and that supported products cover XRechnung and ZUGFeRD profiles. The useful check is whether recipient-specific fields survive into that downloaded file.

## Validation checklist

- For B2G invoices, confirm the Leitweg-ID appears as BuyerReference and is not only stored in the customer address or project text.
- Check that payment terms, due date, and IBAN are in structured fields before final validation.
- For tax-exempt or reverse-charge invoices, verify the exported XML includes VATEX reason code/text and buyer/seller VAT IDs as applicable.

## Export triage table

| Symptom | Likely field or rule | Export-side fix |
| --- | --- | --- |
| XRechnung download exists, but the authority portal reports missing buyer reference. | BT-10 / BR-DE-15 | Set the authority contact/routing data before generating the XML, then download and inspect BuyerReference. |
| Tax-exempt invoice validates as missing exemption reason. | BT-120 / BT-121 / BR-E-08 | Add exemption text/code in the tax treatment before regenerating the e-invoice. |

## Common validation failures

Buyer reference, payment terms, tax exemption text, and reverse-charge VAT IDs are common export gaps.

## Validation workflow after export

Use the review step to fill missing EN 16931 fields before final validation and download.

## Official/vendor documentation

- [Lexware XRechnung overview](https://www.lexware.de/wissen/faktura-warenwirtschaft/xrechnung/)
- [Lexware eRechnung overview](https://www.lexware.de/wissen/faktura-warenwirtschaft/e-rechnung/)