A supplier invoice with no VAT on it, and yet a VAT entry to post: that is everyday life with the reverse charge. In a poorly configured ERP, that entry does not exist, or only half of it does. The result is a wrong VAT return, lost input VAT, or forgotten output VAT that a tax audit will eventually find.
This guide focuses on the reverse charge mechanism itself: who accounts for what, and how to translate it into tax codes, accounts and controls. If you are choosing a tax engine (Avalara, SOVOS, Vertex), see our comparison of indirect tax automation solutions, which we do not repeat here.
Disclaimer. This article describes general mechanisms and is not individual tax advice. Rules vary by type of transaction, by country and by each company’s situation. Validate your configuration with your accountant or tax adviser, and check the legislation in force at the date of your project. The legal references and examples below are mainly French; where other member states apply the same EU mechanism, the configuration logic is the same but the details differ.
The principle: who accounts for VAT, and why one entry is not enough
Under the normal regime, the supplier charges VAT, pays it to the tax authority, and the customer deducts it. With the reverse charge, the burden of accounting for VAT shifts: the customer (the recipient) becomes liable for the tax. The supplier issues an invoice without VAT, with an explicit mention, and the customer accounts for the tax itself.
The EU VAT Directive (Directive 2006/112/EC) provides for this mechanism in several places: Article 196 makes the taxable recipient liable for B2B services covered by Article 44, and Article 199 lets member states apply it to certain construction operations. The reverse charge mention on the invoice is provided for in Article 226 of the same directive.
For the ERP, the consequence is simple but demanding. A single transaction generates two VAT movements on the same accounting document:
- output VAT (credited to an output VAT account),
- input VAT (debited to an input VAT account),
with a zero cash impact if the customer has a full right of deduction. If the ERP produces only one of the two movements, the VAT return is unbalanced. If the supplier invoice is entered with an ordinary “zero rate” tax code, neither entry appears: the tax base vanishes from the return.
That is why the reverse charge must be a tax code in its own right, never a simple “0%”.
The main use cases
| Case | Legal basis (France) | Direction of the transaction | Who accounts for VAT |
|---|---|---|---|
| Intra-EU acquisition of goods | Article 256 bis of the French tax code (CGI), Directive 2006/112/EC art. 2 | Purchase from a taxable supplier in another member state | The French acquirer |
| B2B services received from abroad | Article 283-2 CGI, Directive art. 44 and 196 | Purchase of services from a supplier established outside France | The French taxable customer |
| Construction subcontracting | Article 283-2 nonies CGI | Building work performed by a subcontractor | The main contractor |
| Other sector-specific cases | Varies by country | Varies | Varies |
The legal references above are those that official French documentation associates with each case. Always check the wording in force on Légifrance before freezing your configuration.
Intra-EU acquisitions of goods
A French company buys goods from a taxable supplier located in another member state. The supplier delivers without VAT, the transaction being exempt on their side under conditions (the customer’s VAT number, dispatch to another member state). For the acquirer, the transaction is taxable in France if the goods arrive there, and they account for the VAT themselves (service-public.fr, goods exchanges within the EU, in French).
In the ERP, this flow touches the purchasing and inventory modules: receipts of goods from the EU must be linked to an intra-EU acquisition tax code, which produces the acquisition base and the two VAT movements. The same transaction also feeds the goods exchange declaration, covered in our guide on Intrastat and EMEBI.
Cross-border B2B services
A French company receives a consulting, software licence or hosting service invoiced by a supplier established in another country. For most B2B services, the place of taxation is where the recipient is established, and the recipient accounts for the VAT of the country of consumption. On the French VAT return (CA3), these purchases appear on a dedicated line in the section for transactions carried out, covered by Article 283-2 CGI (purchases of services from a taxable person not established in France).
Be careful: this is the case most often forgotten in ERPs, because it usually goes through the “standard” supplier flow (service invoices, expense claims, SaaS subscriptions) and not through the goods flow.
Construction subcontracting (France)
Since 1 January 2014, building work entrusted to a subcontractor falls under the reverse charge (Article 283-2 nonies CGI, introduced by Article 25 of the 2014 Finance Act; tax authority guidance relayed by Legifiscal, in French). The subcontractor invoices without VAT, shows the reverse charge mention in place of the VAT line, and the main contractor accounts for the tax. Readers in the UK will recognise the logic of the domestic reverse charge for construction services, which applies to supplies within the Construction Industry Scheme; the principle is the same, the scope and conditions are not.
Three points of caution come up repeatedly in the BOFiP (French tax doctrine):
- the scheme targets the subcontractor, whatever their rank in a chain of subcontracting;
- the direct contract between the main contractor and the final client remains invoiced with VAT;
- where a single subcontracting contract mixes services under the reverse charge with others that would not be, the administration states that all transactions under the contract should be reverse-charged.
The second point has a direct consequence for the ERP: the same construction company issues invoices with VAT (to the end client) and receives invoices without VAT (from subcontractors). For progress billing, retention and direct payment, see our article on construction ERP progress billing.
Other sector-specific cases in the EU
Member states may extend the reverse charge to other sectors or transactions within the framework set by the directive (Article 199 is an example for construction). These cases vary from country to country and change over time. We deliberately do not list them here: for every country where you have an entity or a filing obligation, ask your local adviser for the up-to-date list and have it validated before you configure anything.
Configuration: tax codes, accounts, accounting groups and invoice wording
One tax code per case, not a generic zero rate
Create a separate tax code for each reverse charge case:
- intra-EU acquisition of goods,
- services received from the EU,
- services received from outside the EU,
- construction subcontracting.
Each code must carry: the theoretical VAT rate that applies (the local rate the customer must apply), the VAT return box to feed, and the associated output VAT and input VAT accounts. The rate matters: the ERP has to calculate the VAT amount to self-assess even though the invoice contains none.
Output and input VAT accounts
On the same document, the ERP must automatically generate:
- an output VAT line as a credit (reverse charge output VAT account);
- an input VAT line as a debit (input VAT account on goods and services), depending on the right of deduction.
Keep accounts separate from those of ordinary VAT: they make it easier to reconcile with the VAT return and to maintain the audit trail. If your company does not have a full right of deduction (mixed activities, partial exemption), the non-deductible part must follow your usual apportionment rules, a point to have validated by your accountant.
Product and partner accounting groups
Most ERPs determine the tax code from the combination of partner group x product group (and sometimes the delivery country). This matrix is the source of most errors:
- the partner group distinguishes domestic supplier, EU supplier, non-EU supplier, and construction subcontractor subject to the reverse charge;
- the product group distinguishes goods, services and building work.
By way of illustration, in general terms and without claiming to be exhaustive (check the documentation for your version):
- SAP: VAT tax codes are determined through the tax procedure configuration and can carry a reverse charge indicator. Accounts are linked to the tax code through configuration.
- Odoo: “reverse charge” taxes rely on taxes with invoice distribution: a positive line and a negative line on two VAT accounts, driven by the partner’s fiscal positions.
- Microsoft Dynamics 365: sales tax groups (item and partner) combined with tax codes flagged as reverse charge or equivalent, depending on the localisation.
In all three cases the principle is the same: the partner carries the fiscal position, the product carries the nature of the transaction, and the tax code follows from them. Consult the documentation for your version and your local localisation before configuring: the exact labels differ.
Legal wording on invoices
On issued invoices (we are the supplier of a customer who self-assesses), the “reverse charge” mention must appear, with the customer’s VAT number where applicable. On received invoices, a construction subcontracting or intra-EU purchase invoice without this mention should be treated as an anomaly to investigate before payment. Configure sales invoice templates with a conditional mention depending on the tax code: the mention must come out automatically, not through free-text entry.
Control: VAT return, EC Sales List and consistency of entries
The VAT return
The reverse charge shows up in two places on the French VAT return (form CA3): the net tax base in the section for transactions carried out (for example, line A3 for services received from a taxable person not established in France, line B2 for intra-EU acquisitions, according to the official documentation), and the gross VAT and deductible VAT in the section for tax payable and deductible. Line numbers change with the form: always use the one for the current year. Other countries use their own boxes (in the UK, for example, the reverse charge feeds both the output and input boxes of the return), so map each entity’s tax codes to its local return.
The control to industrialise: for each period, the reverse-charged base in the ERP must equal the declared base, and the output VAT on the reverse charge must equal the matching input VAT (before apportionment).
Goods exchange declarations and EC Sales List
Sales of goods to the EU feed the VAT recapitulative statement (Articles 262 ter and 289 B CGI, service-public.fr, in French), and goods exchanges fall under the goods exchange declaration depending on the applicable thresholds: see our article on Intrastat and EMEBI for the mechanics and the thresholds to check. Likewise, the B2B services that you invoice to EU customers must be reported in the EU services declaration: the ERP must therefore distinguish these service sales.
Consistency checks
Three reconciliations to automate every month:
- Reverse-charge output VAT balance = reverse-charge input VAT balance (before apportionment).
- VAT return base = accounting base of the relevant expense and fixed asset accounts.
- EU/foreign supplier invoices without a reverse charge code: an exceptions list at zero before closing.
Impact of e-invoicing and ViDA
In France, the e-invoicing and e-reporting reform changes how these flows are transmitted to the administration: transactions with foreign counterparties and B2C transactions fall under e-reporting, and certain transaction and payment data are transmitted in addition to the invoice. The entry-into-force dates by company category are set officially and have already shifted: check the calendar published by the administration before planning, and read our review of French e-invoicing in production.
At European level, the ViDA package (VAT in the Digital Age) provides for real-time digital reporting of cross-border transactions between taxable persons, with the same effect on reverse charge flows: more structured data, earlier. Our article ViDA: ERP impact and action plan 2026-2030 details the timeline and what it implies for configuration. Remember this for the reverse charge: the cleaner your VAT data at entry (tax code, base, rate, VAT number of both parties), the less rework you will face when e-reporting becomes the norm.
Common mistakes and countermeasures
| Mistake | Consequence | Countermeasure |
|---|---|---|
| Partner default tax code applied to an invoice without VAT | Base missing from the return, no reverse charge entry | Blocking control: a zero-VAT supplier invoice requires an explicit reverse charge code or a justified exemption |
| Wrong place of supply (service entered as goods, or the reverse) | Wrong return box, wrong rate | Mandatory “goods / services / works” product group, validated when the item is created |
| Invoice without reverse charge mention (received or issued) | Risk of adjustment, non-compliant invoice | Conditional mention in the template, check on receipt of invoices |
| Mixed construction contract handled line by line | Inconsistent with the doctrine, which calls for reverse-charging the whole contract | The tax code is set at subcontracting contract level, not line level |
| Reverse charge without verifying the right of deduction | Output VAT without a symmetrical deduction | Apportionment rule tested on a mixed-activity case |
| Partner without a valid VAT number | Transaction requalified | Check the intra-EU VAT number at partner creation (European Commission VIES service) |
Acceptance tests: 8 scenarios before go-live
Before switching over, run at least these eight scenarios, each with an expected accounting document, VAT return base and control report:
- Purchase of goods from an EU supplier: acquisition base, output VAT and input VAT generated, goods exchange declaration fed where applicable.
- Purchase of a B2B service from an EU supplier (e.g. consulting, subscription): reverse charge and base on the dedicated return line.
- Purchase of a service from a non-EU supplier: same control, separate tax code.
- Construction subcontracting invoice without VAT: reverse charge by the main contractor, mention checked.
- Mixed construction contract: consistent treatment across the whole contract.
- Sales invoice under the reverse charge (we are the supplier): automatic mention, recapitulative statement fed.
- Credit note on a reverse-charged invoice: both movements are reversed, the return base is corrected.
- Mixed activity with apportionment: input VAT follows the apportionment rule, output VAT remains in full.
A ninth reflex, though not a scenario in itself: replay a past period’s VAT return with the new codes and compare it with what was filed. If the gap is unexplained, do not go live.
Going further
The reverse charge is a matter of configuration and acceptance testing, not only of tax law: each case needs its tax code, its mention and its control. To structure your tests, use our ERP acceptance testing (UAT go-live) checklist and add the eight scenarios above. For the regulatory context, also read our analysis of indirect tax engines and our ViDA action plan. And to receive our upcoming checklists, subscribe to the newsletter.