Two missing words can undo an intra-Community triangulation. In an A-B-C chain across three EU Member States (supplier A, intermediary B, customer C, goods shipped directly from A to C), Article 141 of the VAT Directive lets B avoid registering for VAT in C's country, with C accounting for the VAT under the reverse charge. The condition: B's invoice to C must say "Reverse charge". In Luxury Trust Automobil (C-247/21) the Court of Justice of the EU held that without that mention C is not validly designated as liable, and that adding it later has no retroactive effect. This guide covers the conditions, the ruling, and how to put the mention into the ERPNext print format so it never depends on someone remembering.
The failure is quiet: the deal closes, the goods move, and the VAT exposure appears at an audit, when the invoice can no longer be fixed retroactively. I am Manoj, and I lead ERPNext and Frappe work at MithTech, a team of Frappe specialists in Bengaluru. We build the invoice side; the VAT treatment of your chain is for your EU VAT adviser.
Does the simplification apply to your chain?
Article 141 is a simplification with conditions, and all of them must hold. Miss one structural condition and the chain doesn't qualify; miss the wording and — as the ECJ made clear — it doesn't qualify either.
Interactive
Triangulation Conditions Decider
Toggle the mandatory conditions to see whether the Article 141 triangulation simplification applies, including the reverse-charge wording that Luxury Trust made substantive.
The structural conditions in Article 141(a)–(e): B is not established in C's Member State but is VAT-identified in another one; B acquires the goods for a later supply in C's Member State; the goods go directly to C from a Member State other than B's; C is VAT-identified in its Member State; and C is designated under Article 197 as liable. B must also report the supply on its recapitulative statement (Articles 42(b), 262 and 265). The decider separates out the "Reverse charge" mention because teams treat it as cosmetic, and the CJEU treated it as decisive.
The two words the case turned on
Luxury Trust Automobil (Case C-247/21, judgment of 8 December 2022) is the ruling a triangulation setup has to respect. The Court held that C is validly designated as liable for the VAT only if B's invoice carries the "Reverse charge" mention under Article 226(11a) (para 56). Adding it later is not a correction but the first issue of the required invoice, with no retroactive effect (para 61).
Interactive
Invoice Legend Checker
Pick the wording on B's invoice to C to see whether it secures the simplification after the Luxury Trust ruling.
The practical result: an invoice reading "Exempt intra-Community triangular transaction", which sounds reasonable, was not sufficient. The words "Reverse charge" must be there. Because the omission can't be corrected retroactively, you can't fix it at an audit years later. The exposure is fixed when the wrong invoice is issued.
How do you build it into ERPNext?
ERPNext has no built-in triangulation feature. You model it with the standard tax setup and, above all, the print format, so the "Reverse charge" mention prints by rule rather than by hand.
Code recipe
Configure · Legend · Report · Prevent
Copy-paste the zero-rated tax configuration, the exact print-format legend wording, the EC Sales List triangulation flag, and the controls that keep the omission from ever happening.
0 of 4 steps done
Tick a step’s number when it is done; the ticks stay on this device.
Configure the tax as zero-rated for the B-to-C leg
Create a zero-rated Sales Taxes and Charges Template for the triangulation supply: B charges no VAT because C accounts for it. Drive it from a Tax Category so the right template is picked automatically. Keep A, B and C as separate parties with valid EU VAT IDs on their masters.
Print the reverse-charge legend automatically
Add a conditional block to the sales invoice print format that prints "Reverse charge. Intra-Community triangular transaction, Art 141 and 197 Directive 2006/112/EC. VAT to be accounted for by the recipient." Have your adviser confirm the wording for the Member States involved. Trigger it on the triangulation tax category so it appears on every qualifying invoice.
Flag the transaction on the EC Sales List
B reports the onward supply on its EC Sales List (recapitulative statement) marked as a triangular transaction, not an ordinary intra-Community supply. Build it from a custom report over the triangulation-tagged invoices, or a regional EU VAT app, and reconcile it monthly.
Validate the VAT numbers up front
Check all three EU VAT numbers in VIES before raising the invoice. An invalid number for A, B or C can sink the simplification as surely as a missing mention.
When sales owns the deal and finance owns the VAT
In a group running EU cross-border chains, sales closes the A-B-C deal and finance owns the VAT treatment. The salesperson sees a normal sale; the exposure sits in a line on the invoice that neither thinks about at closing. That gap is where "Reverse charge" gets dropped.
The control takes the wording out of human hands. Tag triangular supplies at the tax-category level, print the mention from that tag, and check the three VAT IDs when the masters are set up. Then check that the invoice mention and the EC Sales List flag always agree; if one shows a triangular supply and the other doesn't, something slipped. Because the omission can't be corrected after issue, the mention has to be right before the invoice goes out.
Draft policy for your finance and tax leads to ratify. Every qualifying intra-Community triangular supply is tagged at the tax-category level, and the "Reverse charge" mention (citing Art 141 and 197, Directive 2006/112/EC) is printed automatically from that tag, never added by hand. All three parties' EU VAT numbers are VIES-validated before the invoice is raised. Triangular supplies are flagged on the EC Sales List and reconciled monthly against the invoices, with the legend and the ESL flag audited for agreement. Because the reverse-charge mention cannot be corrected retroactively, it is treated as a pre-issue control. Confirm each chain with an EU VAT adviser before adoption.
Print format or manual entry?
| Legend prints automatically on every triangular supply | Someone must remember to add the wording each time |
| Gated on the tax category, so it can't be forgotten | One busy day and 'Reverse charge' is missing |
| The required wording is always present | A missing mention can't be fixed retroactively |
| ESL flag and invoice legend reconcile | Divergence between the two goes unnoticed |
| Outcome: the invoice condition is met | Outcome: risk of VAT, interest and penalties for B |
At a glance
| Aspect | What to know |
|---|---|
| Rule | Art 141 and 197, Directive 2006/112/EC |
| Invoice mention | "Reverse charge" (Art 226(11a)); a later fix has no retroactive effect (C-247/21) |
| In ERPNext | Zero-rated tax template, Tax Category, conditional print-format block |
| Reporting | Recapitulative statement (EC Sales List) marked triangular |
FAQ: what do people ask most?
What is EU triangulation simplification?
It is a rule in Article 141 of the VAT Directive for an A-B-C chain across three Member States, where goods ship directly from A to C. Normally the intermediary B would have to register for VAT in C's country; the simplification lets B avoid that, with its acquisition treated as taxed and C accounting for the VAT under the reverse charge.
Why does the invoice have to say 'Reverse charge'?
Because Article 226(11a) requires it, and the CJEU's Luxury Trust judgment (Case C-247/21) held that without the "Reverse charge" mention C is not validly designated as liable, so the simplification doesn't apply. The Court treated the mention as a mandatory condition, not a formality.
Can I add the reverse-charge wording to the invoice later?
No. The Court held the omission can't be corrected afterwards: adding the mention later is issuing the required invoice for the first time, with no retroactive effect, so it doesn't repair the original transaction. The mention must be there when the invoice is first issued.
Which countries does triangulation simplification apply to?
It applies across the EU under Directive 2006/112/EC, where the Article 141 conditions are met. Member States implement it in national law, so confirm the local reporting details (and the EC Sales List treatment) with an adviser in the countries involved.
What happens if we get the triangulation invoice wrong?
The simplification doesn't apply. In Luxury Trust the Court said B then owes VAT on the acquisition in its Member State of identification (Article 41); B may also have to register and account for the acquisition and onward supply in C's country, with interest and penalties. Your EU VAT adviser should assess the exposure. Because the wording can't be fixed retroactively, the cost is set when the wrong invoice is issued.
Does ERPNext handle EU triangulation out of the box?
Not as a dedicated feature. You model it with the standard tax setup (a zero-rated Sales Taxes and Charges Template driven by a Tax Category), a custom print-format block for the "Reverse charge" mention, and a custom report or regional app for the EC Sales List triangulation flag.
What related issues might you hit?
- ZATCA Phase 2 clearance vs reporting: where a required invoice element decides validity.
- ERPNext multi-currency and multi-company setup: running EU entities across Member States in one group.
See also: OSS and IOSS in ERPNext, the consumer side of EU VAT: which scheme covers online sales to consumers in other member states, and what ERPNext records for the return.
What is the bottom line?
Triangulation is one of the few places where two words on an invoice decide whether VAT is due in another country. After Luxury Trust, "Reverse charge" is required and can't be fixed retroactively. Put the mention in the print format, drive it from the tax category, and reconcile it against the EC Sales List. Leave it to memory and one busy afternoon can leave B with a VAT bill in another Member State. See ERPNext for how we work.
Comments & ratings
No comments yet. Start a new discussion.
Manoj · Published on 3 August 2026
Worked with us? Leave a Google review