errorbusinessEN 16931

BR-CL-06:Value added tax point date code MUST be coded using a restriction of UNTDID...

Fix: The VAT Point Date Code (BT-8) is not a valid UNTDID 2005 code. Valid codes indicate when VAT becomes due (e.g., 35=delivery date, 432=payment date). Upload your invoice to fix this automatically.

The VAT Point Date Code (BT-8) is not a valid UNTDID 2005 code. Valid codes indicate when VAT becomes due (e.g., 35=delivery date, 432=payment date).

Severity
Fatal
Rule set
EN 16931
Country
All EU
Fix type
AUTO-FIX
Confidence
85%
Category
codelist

Engine Classification

Normalize VAT point date code to valid UNTDID 2005 value

Confidence: 85% · Applied automatically in pipeline

What is BR-CL-06?

BR-CL-06 is a fatal validation rule defined in the EN 16931 specification. It validates the DescriptionCode element in the UBL invoice XML.

When this rule fires, the invoice is rejected by Peppol access points and never reaches the buyer.

Target path: //cac:InvoicePeriod/cbc:DescriptionCode

Why This Error Matters

Invoice rejected. VAT timing code must be from the standard code list.

BR-CL-06 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.

Invoice Navigator can automatically correct this error in your pipeline. The fix is applied with full audit evidence, so your compliance trail remains intact.

Validator Behavior

  • ·Causes invoice rejection
  • ·Error returned: BR-CL-06
  • ·Specification: EN 16931

How to Fix It

1.

Find the incorrectly formatted value

Check cbc:DescriptionCode at //cac:InvoicePeriod/cbc:DescriptionCode. The current value does not match the required format.

2.

Apply the correct format

The VAT Point Date Code (BT-8) is not a valid UNTDID 2005 code. Valid codes indicate when VAT becomes due (e.g., 35=delivery date, 432=payment date).

3.

Update your export settings

If this occurs consistently, check your invoicing software's locale and format settings for XML export. Re-validate to confirm BR-CL-06 is resolved.

Before / After

Failing XML
<cbc:InvoicePeriod>
  <cbc:DescriptionCode>INVALID_CODE</cbc:DescriptionCode>
</cbc:InvoicePeriod>
Corrected XML
<cbc:InvoicePeriod>
  <cbc:DescriptionCode>VALID_CODE</cbc:DescriptionCode>
</cbc:InvoicePeriod>

Technical Reference

XPath//cac:InvoicePeriod/cbc:DescriptionCode
SpecEN 16931
Operationnormalize
StrategyNormalize VAT point date code to valid UNTDID 2005 value

Common Causes

  • ·Tax point date code not from UNTDID 2005
  • ·Invalid code for VAT point date determination
  • ·Custom date code used instead of standard
  • ·Code value outside allowed restriction (3, 35, 432)
  • ·TaxPointDate code field contains date instead of code

Seeing this in production? The API handles BR-CL-06 automatically. See the fix response →

Frequently Asked Questions

The VAT Point Date Code (BT-8) is not a valid UNTDID 2005 code. Valid codes indicate when VAT becomes due (e.g., 35=delivery date, 432=payment date).

The VAT Point Date Code (BT-8) is not a valid UNTDID 2005 code. Valid codes indicate when VAT becomes due (e.g., 35=delivery date, 432=payment date). You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

Yes, BR-CL-06 is a critical error that will cause invoice rejection. It must be fixed before submission.

Many instances of BR-CL-06 can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.

Related Errors

Related Content

Last updated: 14 April 2026

Share this guide:

Validate your invoice

Drop your XML here to check for BR-CL-06

Auto-fix BR-CL-06 in seconds

Upload your invoice and we fix this error automatically. Financial fields are never touched.