errorEN 16931

BR-AF-03:When document level allowances use the IGIC VAT category, the seller must...

When document level allowances use the IGIC VAT category, the seller must have a proper tax identifier.

Severity
Fatal
Rule set
EN 16931
Country
All EU
Fix type
INPUT REQUIRED

Engine Classification

Business data required · Explicit input workflow · No assumptions made

Required input: Seller VAT/Tax ID

What is BR-AF-03?

BR-AF-03 is a fatal validation rule defined in the EN 16931 specification. It checks whether when document level allowances use the igic vat category, the seller must....

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.

Why This Error Matters

Invoice will be rejected by validation. IGIC allowances require seller identification for tax compliance.

BR-AF-03 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.

Validator Behavior

  • ·Causes invoice rejection
  • ·Error returned: BR-AF-03
  • ·Specification: EN 16931

Before / After

Failing XML
<Invoice>
  <cac:AllowanceCharge>INVALID_CODE</cac:AllowanceCharge>
</Invoice>
Corrected XML
<Invoice>
  <cac:AllowanceCharge>VALID_CODE</cac:AllowanceCharge>
</Invoice>

Technical Reference

SpecEN 16931
StrategyRequires user input: Seller tax identifier must be provided. Same requirements as BR-AF-02 apply to document level allowances.

Common Causes

  • ·Allowance marked IGIC but seller identifier missing
  • ·Seller tax registration not included
  • ·Document level allowance added without checking identifier requirements
  • ·ERP does not enforce identifier rules for IGIC allowances
  • ·Seller identifier removed or not populated

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

See Also

Related Errors

Last updated: 27 February 2026

Share this guide:

Handle BR-AF-03 Automatically in Your Pipeline

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