errorbusinessEN 16931

BR-CL-17:Invoice tax categories MUST be coded using UNCL5305 code list

Fix: A VAT Category Code is not a valid UNCL5305 code. Valid codes: S=standard, Z=zero, E=exempt, AE=reverse charge, K=intra-community. Upload your invoice to fix this automatically.

A VAT Category Code is not a valid UNCL5305 code. Valid codes: S=standard, Z=zero, E=exempt, AE=reverse charge, K=intra-community.

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

Engine Classification

Suggest VAT category based on rate and context: 0% could be Z or E, standard rates suggest S. User must confirm due to tax compliance implications.

Confidence: 90% · Applied automatically in pipeline

What is BR-CL-17?

BR-CL-17 is a fatal validation rule defined in the EN 16931 specification. It validates the ram:CategoryCode 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: ram:ApplicableTradeTax/ram:CategoryCode

Why This Error Matters

Invoice rejected. Tax categories must use standard codes for VAT reporting.

BR-CL-17 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-17
  • ·Specification: EN 16931

How to Fix It

1.

Find the incorrectly formatted value

Check ram:CategoryCode at ram:ApplicableTradeTax/ram:CategoryCode. The current value does not match the required format.

2.

Apply the correct format

A VAT Category Code is not a valid UNCL5305 code. Valid codes: S=standard, Z=zero, E=exempt, AE=reverse charge, K=intra-community.

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-17 is resolved.

Before / After

Failing XML
<Invoice>
  <!-- Issue: Invoice tax categories MUST be coded using UNCL5305 code lis -->
</Invoice>
Corrected XML
<Invoice>
  <!-- Issue resolved per EN 16931 -->
</Invoice>

Technical Reference

XPathram:ApplicableTradeTax/ram:CategoryCode
SpecEN 16931
Operationnormalize
StrategySuggest VAT category based on rate and context: 0% could be Z or E, standard rates suggest S. User must confirm due to tax compliance implications.

Common Causes

  • ·VAT category code not from UNCL 5305 list
  • ·Custom tax category code used instead of standard
  • ·Tax type stored as description not code (S, Z, E, etc.)
  • ·Invalid VAT category code for EN16931
  • ·National tax code not mapped to UNCL 5305

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

Frequently Asked Questions

A VAT Category Code is not a valid UNCL5305 code. Valid codes: S=standard, Z=zero, E=exempt, AE=reverse charge, K=intra-community.

A VAT Category Code is not a valid UNCL5305 code. Valid codes: S=standard, Z=zero, E=exempt, AE=reverse charge, K=intra-community. You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

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

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

Related Content

Last updated: 14 April 2026

Share this guide:

Validate your invoice

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

Auto-fix BR-CL-17 in seconds

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