errorbusinessEN 16931

BR-AE-01:Missing reverse charge VAT summary

Fix: Review your Invoice XML structure and correct the issue described by this rule. Check relevant cbc: and cac: elements per EN 16931.

Your invoice has line items marked as reverse charge (VAT category AE), but the VAT summary section is missing the corresponding reverse charge breakdown. When any item uses the reverse charge mechanism, the invoice must include a VAT breakdown line showing the reverse charge totals with a zero tax amount.

Severity
Fatal
Rule set
EN 16931
Country
All EU
Fix type
BLOCKED
Category
tax

Engine Classification

Financial or legal field · Modification blocked by policy

What is BR-AE-01?

BR-AE-01 is a fatal validation rule defined in the EN 16931 specification. It validates the ID — EN16931 rule BR-AE-01. At least one line has taxCategory=AE but no TaxSubtotal with categoryCode=AE exists. element under TaxSubtotal > TaxCategory in the UBL invoice XML.

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

Target path: XPath: cac:TaxTotal/cac:TaxSubtotal/cac:TaxCategory/cbc:ID — EN16931 rule BR-AE-01. At least one line has taxCategory=AE but no TaxSubtotal with categoryCode=AE exists.

This error requires manual correction — financial fields are protected by policy.

Why This Error Matters

Invoice will be rejected by validation. Reverse charge invoices require proper VAT breakdown for tax compliance and buyer's VAT self-assessment.

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

Without the reverse charge VAT breakdown, the invoice is structurally incomplete. Tax authorities cannot verify the reverse charge treatment. The invoice will be rejected by validation systems and Peppol Access Points.

Validator Behavior

  • ·Causes invoice rejection
  • ·Error returned: BR-AE-01
  • ·Specification: EN 16931

How to Fix It

1.

Confirm the reverse charge treatment

Verify with your accountant that reverse charge (VAT category AE) is the correct tax treatment for these items.

2.

Add the VAT breakdown

Add a TaxSubtotal to the TaxTotal section with category code AE, Percent = 0, the correct TaxableAmount, TaxAmount = 0, and an exemption reason code like VATEX-EU-AE.

3.

Update the totals

The TaxExclusiveAmount and TaxInclusiveAmount should reflect the reverse charge items.

Before / After

Failing XML
<Invoice>
  <!-- Issue: An Invoice with reverse charge items must have exactly one V -->
</Invoice>
Corrected XML
<Invoice>
  <!-- Issue resolved per EN 16931 -->
</Invoice>

Technical Reference

XPathXPath: cac:TaxTotal/cac:TaxSubtotal/cac:TaxCategory/cbc:ID — EN16931 rule BR-AE-01. At least one line has taxCategory=AE but no TaxSubtotal with categoryCode=AE exists.
SpecEN 16931
StrategyAdding a reverse charge VAT breakdown requires confirming the tax classification — this involves tax liability decisions that must be made by the invoice issuer

Code Example

<cac:TaxCategory>
  <cbc:ID>AE</cbc:ID>
  <cbc:TaxExemptionReasonCode>VATEX-EU-AE</cbc:TaxExemptionReasonCode>
  <cbc:TaxExemptionReason>Reverse charge - VAT due by buyer under Article 194</cbc:TaxExemptionReason>
  <cac:TaxScheme>
    <cbc:ID>VAT</cbc:ID>
  </cac:TaxScheme>
</cac:TaxCategory>

Common Causes

  • ·ERP system creates reverse charge lines but omits the VAT summary
  • ·Tax calculation module does not generate a zero-rate breakdown for AE
  • ·Manual invoice creation without tax summary section

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

Commonly Seen In

All invoicing software

Frequently Asked Questions

When using VAT category AE (reverse charge), the reason must be stated.

Review your Invoice XML structure and correct the issue described by this rule. Check relevant cbc: and cac: elements per EN 16931. This error involves a protected field — Invoice Navigator flags it in your pipeline so your team can correct it at the source.

Yes, BR-AE-01 is a critical error that will cause invoice rejection. It must be fixed before submission to ensure your invoice is accepted by the recipient's system.

BR-AE-01 involves a financial or legal field that cannot be auto-modified by policy. Invoice Navigator detects and flags this error immediately, but the correction must be made manually in your ERP or invoicing software.

BR-AE-01 is commonly seen in exports from All invoicing software. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.

Related Errors

BR-AE-02Reverse charge requires both VAT IDsBR-AE-05Reverse charge invoice line must have 0% VAT rateBR-AE-08Reverse charge taxable amount doesn't add up

Related Content

Learn
Free EN 16931 ValidatorValidate EN 16931 Invoices for germany
Glossary
Evidence Packe-Reporting
Errors
Invoice must have an issue dateMissing invoice type code
Answers
What is the difference between B2G and B2B e-invoicing?
Regulations
EN 16931

Last updated: 3 March 2026

Share this guide:

Validate your invoice

Drop your XML here to check for BR-AE-01

Detect BR-AE-01 before submission

This error involves a financial field that can't be auto-modified. We'll flag it with a clear diagnosis so you can fix it at the source.

Fix it nowAutomate via API