[Docs D-26] Troubleshooting — Common validation errors and fixes

[nielsdrost7]

Wiki section: Troubleshooting
Tier: 4 — Troubleshooting
Publish when: InvoicePlane v1.8.0 is released
Related issues: #11 — French PDP rules · #13 — Endpoint fields · #15 — Routing codes

---

EN 16931 / general Peppol rules

Rule	Message	Cause	Fix
BR-50	Payment means must contain IBAN or account	user_iban is empty	Fill IBAN in Settings → User
BR-61	Credit transfer requires financial account	Payment type 30 but no IBAN	Fill IBAN or remove payment type 30
BR-CO-27	BIC must be present if financial institution is present	Bank name set but no BIC	Fill user_bic or remove user_bank
BR-CL-25	Endpoint schemeID not in EAS code list	Invalid client_eas_code or user_eas_code	Check EAS code reference and use a valid code
BR-01	Invoice must have a payment due date	invoice_date_due is null	Set due date on the invoice
BR-04	Invoice must have a seller name	user_company is empty	Fill company name in Settings → User
BR-07	Invoice must have a buyer name	client_company is empty	Fill company name on client record
BR-31	Each line must have a line total	Calculated as 0 due to quantity or price	Check line item data

---

French PDP specific (Factur-X)

Rule	Message	Cause	Fix
BR-FR-01	Invalid GuidelineID	Old extended profile URN still set	Config must use urn:cen.eu:en16931:2017 — see issue #11
BR-FR-02	Invoice ID contains invalid characters	Invoice number has ., #, @, or spaces	Change numbering scheme to use -, _, / only
BR-FR-03	Missing PMT / PMD / AAB notes	French legal payment notes absent	Add PMT, PMD, AAB to invoice terms
BR-FR-04	Seller SIREN missing (BT-30)	user_siren custom field not filled	Fill user_siren in Settings → User → Custom fields

---

German XRechnung

Rule	Message	Cause	Fix
BR-DE-1	BuyerReference (Leitweg-ID) is mandatory	invoice_routing_code_1 is null	Add Leitweg-ID to invoice E-Invoicing section
BR-DE-2	Seller endpoint required	user_tax_code is empty	Fill tax_code in Settings → User
BR-DE-15	Invoice note must not be empty if present	Empty note element	Remove note or fill it

---

Belgian UBL.BE

Rule	Message	Cause	Fix
ubl-BE-01	Two AdditionalDocumentReference required	Config is missing the DocumentReference option	Use the standard Ublciusv131be.php config which includes this
ubl-BE-02	DocumentType must be CommercialInvoice or CreditNote	Generator not setting document type	Verify invoice_sign field is set on the invoice
ubl-BE-15	TaxCategory/Name missing or invalid	VAT rate not in TaxName mapping	Use only 21, 12, 6, or 0% on Belgian invoices
ubl-BE-10	TaxSubtotal/TaxCategory/Name not in BTCC list	Same as above	Same fix

---

Dutch NLCIUS / SI-UBL

Rule	Message	Cause	Fix
BR-NL-1	Seller legal entity identifier required (KvK or OIN)	user_tax_code empty	Fill KvK number in Settings → User
BR-NL-5	AllowanceChargeReasonCode present	Config does not have NoReasonCode: true	Ensure Nlciusciiv10.php or Ublsi20nl.php is used unmodified
SI-specific	PaymentMeansCode name attribute present	Config does not have NoPaymentMeansName: true	Ensure Ublsi20nl.php is used unmodified

---

Polish KSeF

Rule	Message	Cause	Fix
FA-3 schema error	Invalid VAT rate	Rate not 23, 8, or 5%	Only use supported Polish VAT rates
FA-3 schema error	Missing PLN exchange rate	Foreign currency invoice but no exchange rate	Fill pln_exchange_rate custom field
FA-3 schema error	Corrective invoice not supported	You are generating a credit note	KSeF generator does not support corrective invoices yet

---

General debugging tips

1. Extract the XML first — for embedded formats, extract the XML from the PDF before validating (see Validation guide)
2. Validate against the right profile — make sure the validator is set to the same profile as your GuidelineSpecifiedDocumentContextParameterID
3. Check empty fields — most validation failures trace to a missing or empty InvoicePlane field; use the Data mapping reference to find which field feeds which element
4. Test with a simple invoice — one line item, no global discount, standard VAT rate; add complexity only after the base case passes

---

Migrated from InvoicePlane/InvoicePlane-e-invoices#50.

[BruceWayner31]

eally useful table — a rule-ID-to-fix mapping is exactly what's missing from the
official docs.
I've been working with the CEN EN 16931 validation artefacts (the Schematron/XSLT from
ConnectingEurope/eInvoicing-EN16931,
UBL binding v1.3.13), and I extracted the full rule catalogue from them to check some
wording. A few IDs above look shifted — worth fixing before publish, since a wrong ID
sends people hunting for the wrong field:

Row	Official text (UBL 1.3.13)	Suggested
BR-01	An Invoice shall have a Specification identifier (BT-24).	The due-date rule is BR-CO-25 — "In case the Amount due for payment (BT-115) is positive, either the Payment due date (BT-9) or the Payment terms (BT-20) shall be present."
BR-04	An Invoice shall have an Invoice type code (BT-3).	Seller name is BR-06 — "An Invoice shall contain the Seller name (BT-27)."
BR-31	Each Document level allowance (BG-20) shall have a Document level allowance amount (BT-92).	Line net amount is BR-24 — "Each Invoice line (BG-25) shall have an Invoice line net amount (BT-131)."
BR-CO-27	—	I can't find this one in the UBL binding. Is it from XRechnung or a national rule set? Genuinely asking — I may have missed it.
BR-07, BR-50, BR-61 and BR-CL-25 all match. For exact phrasing, BR-CL-25 is
"Endpoint identifier scheme identifier MUST belong to the CEF EAS code list".
One thing that might save some writing: the VAT-category families (BR-S-*, BR-Z-*,
BR-E-*, BR-AE-*, BR-IC-*, BR-G-*, BR-O-*, plus BR-IP-* and BR-IG-*) are the
same ten positions repeated per category:

• -01 no matching VAT breakdown for that category
• -02/03/04 seller VAT identifier required (line / allowance / charge)
• -05/06/07 the VAT rate constraint (must be 0, must be > 0, or must be absent —
  depends on the category)
• -08 taxable base doesn't match the lines carrying that category
• -09 VAT amount ≠ taxable base × rate
• -10 exemption reason required (or, for S and Z, must not be present)
  That's ~90 rules you can generate from a template rather than write out by hand. Same for
  BR-DEC-* ("max 2 decimals on ") and BR-CL-* (" must come from ").
I have the full 226-rule catalogue extracted with plain-English explanations. Happy to
drop it here as a table or CSV if that's useful for this page — it's derived from the
public artefacts, so no strings.

[nielsdrost7]

@BruceWayner31

Happy to
drop it here as a table or CSV if that's useful for this page

Yes, that would be great, thank you

[BruceWayner31]

@nielsdrost7
Here you go — all 226, grouped by family. Collapsed so it doesn't swamp the thread.

EN 16931 business rules in plain English (226 rules)

### Calculations and conditions

Rule	What it means
BR-CO-03	The VAT point date and the VAT point date code are mutually exclusive — provide one, not both.
BR-CO-04	An invoice line has no VAT category code. Every line needs cac:Item/cac:ClassifiedTaxCategory/cbc:ID.
BR-CO-05	The document-level allowance reason code and the reason text describe different things — make them agree.
BR-CO-06	The document-level charge reason code and the reason text describe different things — make them agree.
BR-CO-07	An invoice line allowance's reason code and reason text describe different things.
BR-CO-08	An invoice line charge's reason code and reason text describe different things.
BR-CO-09	A VAT identifier isn't prefixed with a country code. VAT numbers must start with the two-letter country code, e.g. 'BG123456789', not '123456789'.
BR-CO-10	The sum of your invoice lines doesn't match the subtotal declared in cac:LegalMonetaryTotal/cbc:LineExtensionAmount.
BR-CO-11	The declared sum of document-level allowances (BT-107) doesn't equal the individual allowance amounts added together.
BR-CO-12	The declared sum of document-level charges (BT-108) doesn't equal the individual charge amounts added together.
BR-CO-13	The total without VAT (BT-109) doesn't equal the line subtotal minus allowances plus charges.
BR-CO-14	The invoice total VAT amount (BT-110) doesn't equal the sum of the VAT category amounts in the breakdown.
BR-CO-15	The total with VAT (BT-112) doesn't equal the total without VAT (BT-109) plus the VAT amount (BT-110).
BR-CO-16	The amount due for payment (BT-115) doesn't equal the total with VAT minus any prepaid amount.
BR-CO-17	A VAT breakdown's tax amount doesn't equal its taxable amount × its rate ÷ 100, rounded to two decimals.
BR-CO-18	The invoice has no VAT breakdown at all. Add at least one cac:TaxTotal/cac:TaxSubtotal.
BR-CO-19	An invoicing period is present but empty. Give at least a start date or an end date.
BR-CO-20	An invoice line period is present but empty. Give at least a start date or an end date.
BR-CO-21	A document-level allowance must carry a reason, a reason code, or both.
BR-CO-22	A document-level charge must carry a reason, a reason code, or both.
BR-CO-23	An invoice line allowance must carry a reason, a reason code, or both.
BR-CO-24	An invoice line charge must carry a reason, a reason code, or both.
BR-CO-25	The invoice is payable but says nothing about when. Add cbc:DueDate, or cac:PaymentTerms/cbc:Note.
BR-CO-26	The seller can't be identified. Provide at least one of: seller identifier, seller legal registration identifier, or seller VAT identifier.

Code lists

Rule	What it means
BR-CL-01	Document type code isn't an accepted code. It has to come from invoice and credit note related code lists of UNTDID 1001.
BR-CL-03	CurrencyID isn't an accepted code. It has to come from ISO code list 4217 alpha-3.
BR-CL-04	Invoice currency code isn't an accepted code. It has to come from ISO code list 4217 alpha-3.
BR-CL-05	Tax currency code isn't an accepted code. It has to come from ISO code list 4217 alpha-3.
BR-CL-06	Value added tax point date code isn't an accepted code. It has to come from UNTDID 2005.
BR-CL-07	Object identifier identification scheme identifier isn't an accepted code. It has to come from UNTDID 1153.
BR-CL-08	Invoiced note subject code isn't an accepted code. It has to come from UNCL4451.
BR-CL-10	Any identifier identification scheme identifier isn't an accepted code. It has to come from one of the ISO 6523 ICD list.
BR-CL-11	Any registration identifier identification scheme identifier isn't an accepted code. It has to come from one of the ISO 6523 ICD list.
BR-CL-13	Item classification identifier identification scheme identifier isn't an accepted code. It has to come from one of the UNTDID 7143 list.
BR-CL-14	Country codes in an invoice isn't an accepted code. It has to come from ISO code list 3166-1.
BR-CL-15	Country codes in an invoice isn't an accepted code. It has to come from ISO code list 3166-1.
BR-CL-16	Payment means in an invoice isn't an accepted code. It has to come from UNCL4461 code list.
BR-CL-17	Invoice tax categories isn't an accepted code. It has to come from UNCL5305 code list.
BR-CL-18	Invoice tax categories isn't an accepted code. It has to come from UNCL5305 code list.
BR-CL-19	Coded allowance reasons isn't an accepted code. It has to come from UNCL 5189.
BR-CL-20	Coded charge reasons isn't an accepted code. It has to come from UNCL 7161.
BR-CL-21	Item standard identifier scheme identifier isn't an accepted code. It has to come from ISO 6523 ICD.
BR-CL-22	Tax exemption reason code identifier scheme identifier isn't an accepted code. It has to come from CEF VATEX.
BR-CL-23	The unit of measure code isn't valid. It must come from UN/ECE Recommendation 20 (with the Rec 21 extension) — use 'C62' for a plain piece or unit.
BR-CL-24	Mime code isn't an accepted code. It has to come from MIMEMediaType.
BR-CL-25	Endpoint identifier scheme identifier isn't an accepted code. It has to come from CEF EAS.
BR-CL-26	Delivery location identifier scheme identifier isn't an accepted code. It has to come from ISO 6523 ICD.

Core invoice rules

Rule	What it means
BR-01	The invoice is missing a specification identifier. Add cbc:CustomizationID — for plain EN 16931 that's 'urn:cen.eu:en16931:2017'.
BR-02	The invoice has no invoice number. Add cbc:ID.
BR-03	The invoice has no issue date. Add cbc:IssueDate, in YYYY-MM-DD form.
BR-04	The invoice has no type code. Add cbc:InvoiceTypeCode — 380 is a normal commercial invoice.
BR-05	The invoice has no currency. Add cbc:DocumentCurrencyCode, e.g. EUR.
BR-06	The seller's registered name is missing. Add cac:AccountingSupplierParty/cac:Party/cac:PartyLegalEntity/cbc:RegistrationName.
BR-07	The buyer's registered name is missing. Add cac:AccountingCustomerParty/cac:Party/cac:PartyLegalEntity/cbc:RegistrationName.
BR-08	The seller's postal address is missing.
BR-09	The seller's country code is missing. Add cac:AccountingSupplierParty//cac:Country/cbc:IdentificationCode with a two-letter ISO code.
BR-10	The buyer's postal address is missing.
BR-11	The buyer's country code is missing. Add cac:AccountingCustomerParty//cac:Country/cbc:IdentificationCode with a two-letter ISO code.
BR-12	The sum of line net amounts (BT-106) is missing. Add cac:LegalMonetaryTotal/cbc:LineExtensionAmount.
BR-13	The total without VAT (BT-109) is missing. Add cac:LegalMonetaryTotal/cbc:TaxExclusiveAmount.
BR-14	The total with VAT (BT-112) is missing. Add cac:LegalMonetaryTotal/cbc:TaxInclusiveAmount.
BR-15	The amount due for payment (BT-115) is missing. Add cac:LegalMonetaryTotal/cbc:PayableAmount.
BR-16	The invoice has no lines. At least one cac:InvoiceLine is required.
BR-17	You've given a payee that isn't the seller, so the payee's name is required. Add cac:PayeeParty/cac:PartyName/cbc:Name.
BR-18	A seller tax representative is present, so their name is required.
BR-19	A seller tax representative is present, so their postal address is required.
BR-20	The seller tax representative's address needs a country code.
BR-21	An invoice line has no identifier. Add cac:InvoiceLine/cbc:ID (just number them 1, 2, 3…).
BR-22	An invoice line has no quantity. Add cbc:InvoicedQuantity.
BR-23	An invoice line quantity has no unit of measure. Add the unitCode attribute — 'C62' means 'unit/piece'.
BR-24	An invoice line has no net amount. Add cbc:LineExtensionAmount.
BR-25	An invoice line has no item name. Add cac:Item/cbc:Name.
BR-26	An invoice line has no unit price. Add cac:Price/cbc:PriceAmount.
BR-27	An item's unit price is negative. Prices must be zero or positive — use a credit note for negative values.
BR-28	An item's gross price is negative. Prices must be zero or positive.
BR-29	The invoicing period end date is before its start date.
BR-30	A line invoicing period ends before it starts.
BR-31	A document-level allowance has no amount. Add cac:AllowanceCharge/cbc:Amount.
BR-32	A document-level allowance has no VAT category code.
BR-33	A document-level allowance needs a reason. Add cac:AllowanceCharge/cbc:AllowanceChargeReason, or a reason code.
BR-36	A document-level charge has no amount. Add cac:AllowanceCharge/cbc:Amount.
BR-37	A document-level charge has no VAT category code.
BR-38	A document-level charge needs a reason. Add cac:AllowanceCharge/cbc:AllowanceChargeReason, or a reason code.
BR-41	An invoice line allowance has no amount. Add cac:AllowanceCharge/cbc:Amount.
BR-42	An invoice line allowance needs a reason or a reason code.
BR-43	An invoice line charge has no amount. Add cac:AllowanceCharge/cbc:Amount.
BR-44	An invoice line charge needs a reason or a reason code.
BR-45	A VAT breakdown entry has no taxable amount. Add cac:TaxSubtotal/cbc:TaxableAmount.
BR-46	A VAT breakdown entry has no tax amount. Add cac:TaxSubtotal/cbc:TaxAmount.
BR-47	A VAT breakdown entry has no category code. Add cac:TaxCategory/cbc:ID — S, Z, E, AE, K, G or O.
BR-48	A VAT breakdown entry has no rate. Add cac:TaxCategory/cbc:Percent — required unless the invoice isn't subject to VAT.
BR-49	A payment instruction needs a payment means code. Add cac:PaymentMeans/cbc:PaymentMeansCode — 30 is credit transfer.
BR-50	Credit transfer details are present, so a payee account identifier is required (usually the IBAN).
BR-51	A full card number must never appear on an invoice. Show at most the last four digits.
BR-52	An additional document reference has no identifier. Add cac:AdditionalDocumentReference/cbc:ID.
BR-53	A VAT accounting currency is declared, so the total VAT amount in that currency is required.
BR-54	An item attribute needs both a name and a value.
BR-55	A preceding invoice reference has no identifier.
BR-56	A seller tax representative must have a VAT identifier.
BR-57	The deliver-to address has no country code. Add cac:Delivery//cac:Country/cbc:IdentificationCode.
BR-61	The payment means is a credit transfer, so a payee account identifier is required. Add cac:PayeeFinancialAccount/cbc:ID.
BR-62	The seller's electronic address is missing. Add cac:AccountingSupplierParty/cac:Party/cbc:EndpointID with a scheme identifier.
BR-63	The buyer's electronic address is missing. Add cac:AccountingCustomerParty/cac:Party/cbc:EndpointID with a scheme identifier.
BR-64	An item standard identifier has no scheme. Add the schemeID attribute (e.g. '0160' for GTIN).
BR-65	An item classification identifier has no scheme. Add the listID attribute.
BR-66	An invoice may contain at most one payment card account.
BR-67	An invoice may contain at most one payment mandate.

Decimal places

Rule	What it means
BR-DEC-01	Document level allowance amount (BT-92) has too many decimal places. EN 16931 allows at most 2 — round the value before sending.
BR-DEC-02	Document level allowance base amount (BT-93) has too many decimal places. EN 16931 allows at most 2 — round the value before sending.
BR-DEC-05	Document level charge amount (BT-99) has too many decimal places. EN 16931 allows at most 2 — round the value before sending.
BR-DEC-06	Document level charge base amount (BT-100) has too many decimal places. EN 16931 allows at most 2 — round the value before sending.
BR-DEC-09	Sum of Invoice line net amount (BT-106) has too many decimal places. EN 16931 allows at most 2 — round the value before sending.
BR-DEC-10	Sum of allowanced on document level (BT-107) has too many decimal places. EN 16931 allows at most 2 — round the value before sending.
BR-DEC-11	Sum of charges on document level (BT-108) has too many decimal places. EN 16931 allows at most 2 — round the value before sending.
BR-DEC-12	Too many decimal places on the sum of line net amounts — EN 16931 allows at most two.
BR-DEC-13	Invoice total VAT amount (BT-110) has too many decimal places. EN 16931 allows at most 2 — round the value before sending.
BR-DEC-14	Too many decimal places on the total with VAT — EN 16931 allows at most two.
BR-DEC-15	Invoice total VAT amount in accounting currency (BT-111) has too many decimal places. EN 16931 allows at most 2 — round the value before sending.
BR-DEC-16	Paid amount (BT-113) has too many decimal places. EN 16931 allows at most 2 — round the value before sending.
BR-DEC-17	Rounding amount (BT-114) has too many decimal places. EN 16931 allows at most 2 — round the value before sending.
BR-DEC-18	Too many decimal places on the amount due for payment — EN 16931 allows at most two.
BR-DEC-19	VAT category taxable amount (BT-116) has too many decimal places. EN 16931 allows at most 2 — round the value before sending.
BR-DEC-20	VAT category tax amount (BT-117) has too many decimal places. EN 16931 allows at most 2 — round the value before sending.
BR-DEC-23	Invoice line net amount (BT-131) has too many decimal places. EN 16931 allows at most 2 — round the value before sending.
BR-DEC-24	Invoice line allowance amount (BT-136) has too many decimal places. EN 16931 allows at most 2 — round the value before sending.
BR-DEC-25	Invoice line allowance base amount (BT-137) has too many decimal places. EN 16931 allows at most 2 — round the value before sending.
BR-DEC-27	Invoice line charge amount (BT-141) has too many decimal places. EN 16931 allows at most 2 — round the value before sending.
BR-DEC-28	Invoice line charge base amount (BT-142) has too many decimal places. EN 16931 allows at most 2 — round the value before sending.

Italian split payment

Rule	What it means
BR-B-01	The "Split payment" VAT category is only valid on domestic Italian invoices.
BR-B-02	"Split payment" can't be mixed with standard-rated items on the same invoice.

VAT: exempt

Rule	What it means
BR-E-01	Something on this invoice is marked "exempt from VAT", but there's no matching VAT breakdown for it. Add a cac:TaxTotal/cac:TaxSubtotal entry with that category.
BR-E-02	A line marked "exempt from VAT" requires the seller's VAT identifier (or the tax representative's).
BR-E-03	A document-level allowance marked "exempt from VAT" requires the seller's VAT identifier.
BR-E-04	A document-level charge marked "exempt from VAT" requires the seller's VAT identifier.
BR-E-05	On a line marked "exempt from VAT", the VAT rate must be 0.
BR-E-06	On a document-level allowance marked "exempt from VAT", the VAT rate must be 0.
BR-E-07	On a document-level charge marked "exempt from VAT", the VAT rate must be 0.
BR-E-08	The taxable amount for the "exempt from VAT" breakdown doesn't match the lines, allowances and charges carrying that category. Recalculate it as (sum of line amounts) − allowances + charges for this category only.
BR-E-09	The VAT amount for the "exempt from VAT" breakdown doesn't equal its taxable amount multiplied by its rate.
BR-E-10	The "exempt from VAT" VAT breakdown needs an exemption reason. Add cbc:TaxExemptionReason or cbc:TaxExemptionReasonCode.

VAT: export outside the EU

Rule	What it means
BR-G-01	Something on this invoice is marked "export outside the EU", but there's no matching VAT breakdown for it. Add a cac:TaxTotal/cac:TaxSubtotal entry with that category.
BR-G-02	A line marked "export outside the EU" requires the seller's VAT identifier (or the tax representative's).
BR-G-03	A document-level allowance marked "export outside the EU" requires the seller's VAT identifier.
BR-G-04	A document-level charge marked "export outside the EU" requires the seller's VAT identifier.
BR-G-05	On a line marked "export outside the EU", the VAT rate must be 0.
BR-G-06	On a document-level allowance marked "export outside the EU", the VAT rate must be 0.
BR-G-07	On a document-level charge marked "export outside the EU", the VAT rate must be 0.
BR-G-08	The taxable amount for the "export outside the EU" breakdown doesn't match the lines, allowances and charges carrying that category. Recalculate it as (sum of line amounts) − allowances + charges for this category only.
BR-G-09	The VAT amount for the "export outside the EU" breakdown doesn't equal its taxable amount multiplied by its rate.
BR-G-10	The "export outside the EU" VAT breakdown needs an exemption reason. Add cbc:TaxExemptionReason or cbc:TaxExemptionReasonCode.

VAT: IGIC (Canary Islands)

Rule	What it means
BR-IG-01	Something on this invoice is marked "IGIC (Canary Islands)", but there's no matching VAT breakdown for it. Add a cac:TaxTotal/cac:TaxSubtotal entry with that category.
BR-IG-02	A line marked "IGIC (Canary Islands)" requires the seller's VAT identifier (or the tax representative's).
BR-IG-03	A document-level allowance marked "IGIC (Canary Islands)" requires the seller's VAT identifier.
BR-IG-04	A document-level charge marked "IGIC (Canary Islands)" requires the seller's VAT identifier.
BR-IG-05	On a line marked "IGIC (Canary Islands)", the VAT rate must be zero or greater.
BR-IG-06	On a document-level allowance marked "IGIC (Canary Islands)", the VAT rate must be zero or greater.
BR-IG-07	On a document-level charge marked "IGIC (Canary Islands)", the VAT rate must be zero or greater.
BR-IG-08	The taxable amount for the "IGIC (Canary Islands)" breakdown doesn't match the lines, allowances and charges carrying that category. Recalculate it as (sum of line amounts) − allowances + charges for this category only.
BR-IG-09	The VAT amount for the "IGIC (Canary Islands)" breakdown doesn't equal its taxable amount multiplied by its rate.
BR-IG-10	The "IGIC (Canary Islands)" VAT breakdown must not carry an exemption reason — remove it.

VAT: intra-community supply

Rule	What it means
BR-IC-01	Something on this invoice is marked "intra-community supply", but there's no matching VAT breakdown for it. Add a cac:TaxTotal/cac:TaxSubtotal entry with that category.
BR-IC-02	Intra-community supply requires both the seller's and the buyer's VAT identifiers.
BR-IC-03	A document-level allowance marked "intra-community supply" requires the seller's VAT identifier.
BR-IC-04	A document-level charge marked "intra-community supply" requires the seller's VAT identifier.
BR-IC-05	On a line marked "intra-community supply", the VAT rate must be 0.
BR-IC-06	On a document-level allowance marked "intra-community supply", the VAT rate must be 0.
BR-IC-07	On a document-level charge marked "intra-community supply", the VAT rate must be 0.
BR-IC-08	The taxable amount for the "intra-community supply" breakdown doesn't match the lines, allowances and charges carrying that category. Recalculate it as (sum of line amounts) − allowances + charges for this category only.
BR-IC-09	The VAT amount for the "intra-community supply" breakdown doesn't equal its taxable amount multiplied by its rate.
BR-IC-10	The "intra-community supply" VAT breakdown needs an exemption reason. Add cbc:TaxExemptionReason or cbc:TaxExemptionReasonCode.
BR-IC-11	An invoice with "intra-community supply" items needs a delivery date or an invoicing period.
BR-IC-12	An invoice with "intra-community supply" items needs the deliver-to country code.

VAT: IPSI (Ceuta and Melilla)

Rule	What it means
BR-IP-01	Something on this invoice is marked "IPSI (Ceuta and Melilla)", but there's no matching VAT breakdown for it. Add a cac:TaxTotal/cac:TaxSubtotal entry with that category.
BR-IP-02	A line marked "IPSI (Ceuta and Melilla)" requires the seller's VAT identifier (or the tax representative's).
BR-IP-03	A document-level allowance marked "IPSI (Ceuta and Melilla)" requires the seller's VAT identifier.
BR-IP-04	A document-level charge marked "IPSI (Ceuta and Melilla)" requires the seller's VAT identifier.
BR-IP-05	On a line marked "IPSI (Ceuta and Melilla)", the VAT rate must be zero or greater.
BR-IP-06	On a document-level allowance marked "IPSI (Ceuta and Melilla)", the VAT rate must be zero or greater.
BR-IP-07	On a document-level charge marked "IPSI (Ceuta and Melilla)", the VAT rate must be zero or greater.
BR-IP-08	The taxable amount for the "IPSI (Ceuta and Melilla)" breakdown doesn't match the lines, allowances and charges carrying that category. Recalculate it as (sum of line amounts) − allowances + charges for this category only.
BR-IP-09	The VAT amount for the "IPSI (Ceuta and Melilla)" breakdown doesn't equal its taxable amount multiplied by its rate.
BR-IP-10	The "IPSI (Ceuta and Melilla)" VAT breakdown must not carry an exemption reason — remove it.

VAT: not subject to VAT

Rule	What it means
BR-O-01	Something on this invoice is marked "not subject to VAT", but there's no matching VAT breakdown for it. Add a cac:TaxTotal/cac:TaxSubtotal entry with that category.
BR-O-02	A line marked "not subject to VAT" requires the seller's VAT identifier (or the tax representative's).
BR-O-03	A document-level allowance marked "not subject to VAT" requires the seller's VAT identifier.
BR-O-04	A document-level charge marked "not subject to VAT" requires the seller's VAT identifier.
BR-O-05	On a line marked "not subject to VAT", the VAT rate must be omitted entirely.
BR-O-06	On a document-level allowance marked "not subject to VAT", the VAT rate must be omitted entirely.
BR-O-07	On a document-level charge marked "not subject to VAT", the VAT rate must be omitted entirely.
BR-O-08	The taxable amount for the "not subject to VAT" breakdown doesn't match the lines, allowances and charges carrying that category. Recalculate it as (sum of line amounts) − allowances + charges for this category only.
BR-O-09	The VAT amount for the "not subject to VAT" breakdown doesn't equal its taxable amount multiplied by its rate.
BR-O-10	The "not subject to VAT" VAT breakdown needs an exemption reason. Add cbc:TaxExemptionReason or cbc:TaxExemptionReasonCode.
BR-O-11	An invoice with out-of-scope items must not contain any other VAT category.
BR-O-12	An invoice with out-of-scope items must not contain any line with a different VAT category.
BR-O-13	This invoice has a "not subject to VAT" VAT breakdown, so document-level allowances must all use that same category — one of them doesn't.
BR-O-14	This invoice has a "not subject to VAT" VAT breakdown, so document-level charges must all use that same category — one of them doesn't.

VAT: reverse charge

Rule	What it means
BR-AE-01	Something on this invoice is marked "reverse charge", but there's no matching VAT breakdown for it. Add a cac:TaxTotal/cac:TaxSubtotal entry with that category.
BR-AE-02	Reverse charge requires both the seller's and the buyer's VAT identifiers.
BR-AE-03	A document-level allowance marked "reverse charge" requires the seller's VAT identifier.
BR-AE-04	A document-level charge marked "reverse charge" requires the seller's VAT identifier.
BR-AE-05	On a line marked "reverse charge", the VAT rate must be 0.
BR-AE-06	On a document-level allowance marked "reverse charge", the VAT rate must be 0.
BR-AE-07	On a document-level charge marked "reverse charge", the VAT rate must be 0.
BR-AE-08	The taxable amount for the "reverse charge" breakdown doesn't match the lines, allowances and charges carrying that category. Recalculate it as (sum of line amounts) − allowances + charges for this category only.
BR-AE-09	The VAT amount for the "reverse charge" breakdown doesn't equal its taxable amount multiplied by its rate.
BR-AE-10	The "reverse charge" VAT breakdown needs an exemption reason. Add cbc:TaxExemptionReason or cbc:TaxExemptionReasonCode.

VAT: standard rated

Rule	What it means
BR-S-01	Something on this invoice is marked "standard rated", but there's no matching VAT breakdown for it. Add a cac:TaxTotal/cac:TaxSubtotal entry with that category.
BR-S-02	A line marked "standard rated" requires the seller's VAT identifier (or the tax representative's).
BR-S-03	A document-level allowance marked "standard rated" requires the seller's VAT identifier.
BR-S-04	A document-level charge marked "standard rated" requires the seller's VAT identifier.
BR-S-05	On a line marked "standard rated", the VAT rate must be greater than zero.
BR-S-06	On a document-level allowance marked "standard rated", the VAT rate must be greater than zero.
BR-S-07	On a document-level charge marked "standard rated", the VAT rate must be greater than zero.
BR-S-08	The taxable amount for the "standard rated" breakdown doesn't match the lines, allowances and charges carrying that category. Recalculate it as (sum of line amounts) − allowances + charges for this category only.
BR-S-09	The VAT amount for the "standard rated" breakdown doesn't equal its taxable amount multiplied by its rate.
BR-S-10	The "standard rated" VAT breakdown must not carry an exemption reason — remove it.

VAT: zero rated

Rule	What it means
BR-Z-01	Something on this invoice is marked "zero rated", but there's no matching VAT breakdown for it. Add a cac:TaxTotal/cac:TaxSubtotal entry with that category.
BR-Z-02	A line marked "zero rated" requires the seller's VAT identifier (or the tax representative's).
BR-Z-03	A document-level allowance marked "zero rated" requires the seller's VAT identifier.
BR-Z-04	A document-level charge marked "zero rated" requires the seller's VAT identifier.
BR-Z-05	On a line marked "zero rated", the VAT rate must be 0.
BR-Z-06	On a document-level allowance marked "zero rated", the VAT rate must be 0.
BR-Z-07	On a document-level charge marked "zero rated", the VAT rate must be 0.
BR-Z-08	The taxable amount for the "zero rated" breakdown doesn't match the lines, allowances and charges carrying that category. Recalculate it as (sum of line amounts) − allowances + charges for this category only.
BR-Z-09	The VAT amount for the "zero rated" breakdown doesn't equal its taxable amount multiplied by its rate.
BR-Z-10	The "zero rated" VAT breakdown must not carry an exemption reason — remove it.

Two notes on using it:

• The meaning column is my rewording; the official Schematron text is the
  authority. I have a version with both columns side by side if you'd rather show
  the standard's own wording next to each one — it's about twice the size, so I
  left it out here.
• Also available as CSV if that's easier to transform into your page format.
  If it's useful, I'm happy to open a PR against this repo with it as a proper
  troubleshooting page rather than you copy-pasting out of a comment — just say
  which format and where it should live, and I'll match your existing structure.
  Generated from the artefacts, so it stays correct when CEN bumps the version.

[nielsdrost7]

@BruceWayner31 thanks, man!
Don't worry about it for now.

Format will be Markdown.

Thanks for now