How do I fix BR-CL-06?

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.

Is BR-CL-06 a critical error?

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

Can BR-CL-06 be automatically fixed?

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.

errorEN 16931

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

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%

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 non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach the buyer.

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

Get API Access Test This Error ↓

Why This Error Matters

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

BR-CL-06 is a hard failure. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.

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

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 →

Related Errors

BR-CO-03

VAT point date and VAT point date code are mutually exclusive

Last updated: 27 February 2026

Share this guide:

Handle BR-CL-06 Automatically in Your Pipeline

The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.

Get API Access View API Documentation

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