Hi everyone,
I'm using EspoCRM with the Sales Pack and generating XRechnung-compliant e-invoices (UBL 2.1). I've run into an issue with the EN 16931 tax mapping and would appreciate any input.
The Problem
For invoices with tax category AE (Reverse Charge, e.g. §13b UStG in Germany), EN 16931 business rule BR-AE-10 requires either:
BT-120 (VAT exemption reason text), or
BT-121 (VAT exemption reason code, e.g. VATEX-EU-AE)
However, the current Sales Pack tax mapping UI only exposes the tax category code — there is no field available to set the exemption reason text or exemption reason code. As a result, the generated UBL XML is missing these mandatory elements, which causes the XRechnung to fail official schema validation.
My Setup
EspoCRM: 9.2.5
Sales Pack: 4.0.1
Invoice format: UBL 2.1 (XRechnung)
Tax category used: AE (Reverse Charge)
My Question
Is there a built-in way (e.g. a hidden field, a metadata setting) to set BT-120 or BT-121 in the tax mapping?
If not — is the recommended approach to implement a Custom Preparator as described here?
https://forum.espocrm.com/forum/deve...-in-sales-pack
Any guidance or confirmation that a feature request would be appropriate would be very helpful.
Thanks in advance!
I'm using EspoCRM with the Sales Pack and generating XRechnung-compliant e-invoices (UBL 2.1). I've run into an issue with the EN 16931 tax mapping and would appreciate any input.
The Problem
For invoices with tax category AE (Reverse Charge, e.g. §13b UStG in Germany), EN 16931 business rule BR-AE-10 requires either:
BT-120 (VAT exemption reason text), or
BT-121 (VAT exemption reason code, e.g. VATEX-EU-AE)
However, the current Sales Pack tax mapping UI only exposes the tax category code — there is no field available to set the exemption reason text or exemption reason code. As a result, the generated UBL XML is missing these mandatory elements, which causes the XRechnung to fail official schema validation.
My Setup
EspoCRM: 9.2.5
Sales Pack: 4.0.1
Invoice format: UBL 2.1 (XRechnung)
Tax category used: AE (Reverse Charge)
My Question
Is there a built-in way (e.g. a hidden field, a metadata setting) to set BT-120 or BT-121 in the tax mapping?
If not — is the recommended approach to implement a Custom Preparator as described here?
https://forum.espocrm.com/forum/deve...-in-sales-pack
Any guidance or confirmation that a feature request would be appropriate would be very helpful.
Thanks in advance!

Comment