BR-DE-TMP-32:An invoice should specify when goods were delivered or services performed....
An invoice should specify when goods were delivered or services performed. This can be done via the actual delivery date field, an invoicing period at document level, or invoice line periods on each line item. At least one of these date specifications should be present.
Engine Classification
Business data required · Explicit input workflow · No assumptions made
Required input: Actual Delivery Date (BT-72), Period Start Date (BT-73), Period End Date (BT-74)
What is BR-DE-TMP-32?
BR-DE-TMP-32 is a warning validation rule defined in the XRechnung (Germany) specification (DEU national rules). It checks whether an invoice should specify when goods were delivered or services performed.....
This is a soft validation failure. The invoice may pass initial transmission, but non-compliant values in this field can cause problems during tax audits, buyer-side processing, or downstream VAT reconciliation.
Why This Error Matters
Invoice may be rejected or flagged for review. German public sector recipients typically require clear indication of when goods/services were provided for proper accounting and VAT treatment.
BR-DE-TMP-32 is a soft failure. The invoice may pass initial validation, but the non-compliant field can cause issues at the receiving end — tax authorities may flag it during audits, buyer ERP systems may fail to process it, or VAT reconciliation may produce mismatches. Fixing warnings before they accumulate prevents larger compliance gaps.
Validator Behavior
- ·Generates validation warning
- ·Rejected by XRechnung endpoints
- ·Error returned: BR-DE-TMP-32
- ·Specification: XRechnung (Germany)
Before / After
<cac:Delivery> <cac:DeliveryPeriod><!-- invalid or missing value --></cac:DeliveryPeriod> </cac:Delivery>
<cac:Delivery> <cac:DeliveryPeriod>correct-value</cac:DeliveryPeriod> </cac:Delivery>
Technical Reference
Common Causes
- ·No delivery date, invoicing period, or line periods specified
- ·ERP system does not populate delivery date fields
- ·Service invoice without service period defined
- ·Goods invoice missing actual delivery date
- ·Date fields exist in source but not mapped to invoice export
Seeing this in production? The API handles BR-DE-TMP-32 automatically. See the fix response →
Related Errors
Last updated: 27 February 2026
Handle BR-DE-TMP-32 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.