← All guides · EN 16931 & validation
Cross-border invoices: when seller and buyer VAT identifiers are required
By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
Convert an invoice free
Put this guide into practice now: convert one invoice free — validated UBL 2.1 XML plus a Factur-X PDF, with the acceptance checker for your client’s country. See pricing for bulk conversion, country rule packs and monitored clients.
Short answer
On a cross-border B2B e-invoice, the seller's VAT identifier is always required — validation fails without it. The buyer's VAT identifier is additionally required whenever a line uses reverse charge (category AE), because that identifier evidences the buyer's self-accounting. Both identifiers belong in your client and seller records, collected at onboarding, recorded exactly, and present on every invoice the rules touch.
What are the VAT identifier requirements?
Two rules in this product's validator govern identifiers. BR-CO-26: 'Cross-border B2B invoices require the seller's VAT identifier (BT-31)' — triggered when seller and buyer countries differ. BR-AE-02: 'Reverse charge (AE) across borders requires the buyer's VAT identifier (BT-48)' — triggered when countries differ and any line uses category AE. The engine compares the party countries on the invoice to apply them.
Why identifiers became load-bearing
In the PDF era, a VAT identifier was a line of small print — nice to have, rarely checked, often stale. Structured invoicing promotes it to a routing and evidence field: the receiving system reads it as data, matches it against the party it expects, and (for reverse charge) builds the buyer's VAT self-accounting on it. A wrong or missing identifier is no longer a cosmetic flaw; it is a failed check at intake, or worse, a booking against the wrong tax identity.
The rules' design reflects that promotion. They are conditional — triggered by the cross-border fact pattern, not demanded on every domestic invoice — because the identifier's evidentiary job exists specifically where two tax jurisdictions meet. Understand the trigger and the rules stop feeling arbitrary: wherever VAT responsibility crosses a border on paper, the identifiers of both parties must be on that paper.
The seller's identifier: BR-CO-26
The seller's duty is the broader of the two: any cross-border B2B invoice — seller country different from buyer country — requires the seller's VAT identifier (BT-31), whatever the lines' VAT categories. Standard-rated export-style lines, intra-EU supplies, reverse charge: the seller's identifier anchors the supply's origin in the buyer's records and in both countries' VAT logic.
Compliance is trivially systematised: your identifier lives permanently in your seller template. It should never be typed per invoice — per-invoice typing is how transposed digits are born. Set it once, verify it against your own registration documents character by character, and let every cross-border invoice inherit it. The rule then passes silently forever, which is the correct fate of a well-designed check.
The buyer's identifier: BR-AE-02 and the reverse-charge link
The buyer's identifier is required in the specific case where the invoice asks the buyer to do something: account for the VAT under reverse charge. Category AE lines plus differing countries trigger the demand for BT-48. The logic is evidentiary — the buyer can only self-account as an identified taxable person — and the validator enforces it before the file exists, because discovering the gap at the client's intake means the invoice round-trips while payment waits.
Buyers in mandate countries are accustomed to stating their identifier early; it appears on their purchase orders, their supplier onboarding forms and their email signatures' legal blocks. Collect it at engagement, store it in the client record beside their Peppol ID where they have one, and treat 'identifier on file' as a completeness gate: an engagement is not fully onboarded until the identifiers that its invoices will need are present.
Exactness: the unglamorous virtue
Identifiers fail by transcription more often than by absence: a digit transposed, a country prefix dropped, a letter O where a zero belongs. Structured systems compare strings, not intentions, so exactness is the whole game. Copy identifiers from the client's own documents — their invoice to you, their official paperwork, their onboarding form — never from a phone call's dictation or a screenshot's retyping, and re-copy rather than repair when a value looks doubtful.
The same discipline applies to your own identifier in your template, and to party countries, since the rules trigger on the country comparison: a buyer recorded in the wrong country can trigger duties that do not apply or, worse, fail to trigger duties that do. Client records are legal infrastructure in the structured era. Treat their creation with the care once reserved for bank details — because functionally, identifiers have joined that category.
Domestic invoices and other identifiers
Where seller and buyer share a country, these two cross-border rules do not fire — domestic law may still want identifiers on invoices (and most invoicing practice includes them anyway), but the EN 16931 core checks implemented here reserve the hard failure for the cross-border case. Including your VAT identifier on domestic invoices remains good practice: it costs nothing, it matches your clients' expectations, and it keeps one invoice format for all trade.
Note also what the identifiers are not: they are not the Peppol ID, though a Peppol ID is often derived from a business identifier. An invoice can satisfy BR-CO-26 and BR-AE-02 perfectly and still need the recipient's Peppol ID for its network send — different layer, different field, same onboarding conversation. Collect both in the same breath and both layers stop generating correspondence.
Identifier readiness in 5 steps
- Put your own VAT identifier in your seller template permanently — verify it once, character by character, against your registration.
- Collect every cross-border client's VAT identifier at engagement, copied from their own documents.
- Record the client's Peppol ID in the same conversation if they send or receive over Peppol.
- Gate onboarding on completeness: no identifier on file, no 'ready to invoice' status.
- Before converting a cross-border invoice, confirm the countries are right — they are what triggers the identifier rules.
Worked example: two rules, one onboarding form
A consultancy onboards a Spanish client (standard size) for a EUR 6,500.00 engagement. The onboarding form captures the client's VAT identifier and country. The first invoice is cross-border B2B services, reverse charge: both rules are in play. BR-CO-26 checks the seller's identifier — present from the template. BR-AE-02 checks the buyer's — present from onboarding. Validation passes first time; tax EUR 0.00 on the AE lines; payable EUR 6,500.00.
A second client, onboarded by phone with the identifier 'to follow', produces the counter-example: conversion stops at BR-AE-02, an email chase begins, and the invoice issues two days late. The rules did not change between the clients. The onboarding did.
Frequently asked questions
Is the seller's VAT ID required on every invoice?
The hard validation rule (BR-CO-26) triggers on cross-border B2B invoices. Including your identifier on domestic invoices too is standard practice and costs nothing.
When is the buyer's VAT ID required?
When the invoice crosses a border and any line uses reverse charge (AE) — rule BR-AE-02. The identifier evidences the buyer's self-accounting.
What if the countries on the invoice are wrong?
The rules trigger on the seller-country vs buyer-country comparison, so a wrong country can create or conceal duties. Record party countries as carefully as the identifiers themselves.
Is the VAT identifier the same as the Peppol ID?
No. A Peppol ID is a network address, often tied to a business identifier; the VAT identifier is a tax registration. Invoices need the VAT identifiers; Peppol sending needs the Peppol ID. Collect both at onboarding.
Can I add the identifier after the invoice is sent?
Not to the same document — the sent invoice is a fixed record. A missing-identifier invoice that was rejected gets corrected data and a clean resend; one that was somehow booked needs your accountant's correction route (credit note or corrected invoice). Prevention at onboarding is cheaper.
Keep going
Run the free tool this guide is about: convert an invoice · acceptance checker · pricing · about EInvoice Translator · all guides
Related guides
- Reverse charge VAT on e-invoices: category AE, 0%, and the identifier rule
- VAT categories explained: S, Z, E, AE, K, G and O on an e-invoice line
- Peppol ID explained: your business address on the Peppol network
- My e-invoice was rejected: how to read the error and fix the real cause
- Freelancers invoicing EU clients: the e-invoicing playbook