Why NetSuite’s VAT Setup Does Not Match French Requirements, and What To Configure

Contents

1. The rule that breaks the template: cash-basis VAT on services
2. The reverse-charge traffic a US-owned subsidiary generates
3. The currency wrinkle: USD group, EUR return
4. A configuration blueprint that holds up
5. A worked month, to make it concrete
6. Beyond 20%: the rates, and where they hide in a B2B setup
7. Credit VAT: getting your money back
8. The declarations around the return
9. The rhythm of a VAT month
10. A catalogue of the errors we correct most
11. Before the module: is the registration itself right?
12. The reliable audit trail: the requirement around the requirements
13. Related Expand CPA guides

French VAT is not exotic. What is exotic, from an ERP’s point of view, is when French VAT becomes due. US sales tax logic, and NetSuite’s default posture, treats tax as a property of the invoice. French law, for services, ties the tax point to the payment . That single difference, multiplied by a USD reporting currency and a monthly EUR return, is where standard configurations quietly produce wrong numbers that reconcile to nothing.

The rule that breaks the template: cash-basis VAT on services

Under article 269 of the CGI, VAT on supplies of goods becomes chargeable at delivery, effectively invoice-driven. VAT on services becomes chargeable at collection : when the customer pays, including any advance. A services subsidiary that declares VAT from its invoice ledger is declaring too early when customers pay late, and too late on advances, both of which are errors, one of which costs cash.

Flow	Tax point (default)	What the return needs
Sale of goods	Delivery / invoice	Output VAT from invoices of the period
Sale of services	Collection of payment, advances included	Output VAT from payments received in the period
Services with option for débits	Invoice date, by formal election	Invoice-driven, closer to ERP defaults, but the option must actually be elected
Purchases of services from French suppliers	Supplier’s tax point mirrors the same rule	Input VAT deductible when the supplier’s VAT falls due, i.e. when you pay them

There is a legal escape hatch: the option for débits , an election that makes VAT on services chargeable at invoicing. Many French services companies elect it precisely to keep their ERP simple, and the invoice must then say so. What is not available is the accidental middle ground: declaring on invoices without having opted, which is the position most unconfigured ERP setups produce.

What this means inside NetSuite

• Standard tax codes post output VAT to a collected-VAT account at invoicing. For collection-basis services you need VAT parked in a pending account (TVA sur encaissements) at invoicing and moved to VAT collected only as payments land, pro rata on partial payments.
• Advance payments and deposits are taxable events for services; a customer deposit workflow that books no VAT is understating the return.
• Credit memos and write-offs must unwind the pending VAT correctly; a bad-debt write-off is not a taxable collection.
• The France localization’s VAT reports help, but they report what your postings say. If the postings are invoice-basis without the option, the report is precisely, reliably wrong.

The reverse-charge traffic a US-owned subsidiary generates

A French subsidiary of a US group deals with more self-assessed VAT than a purely domestic French company, because its purchase flows cross borders constantly:

Flow	Mechanism	NetSuite implication
Management fees and royalties from the US parent	Reverse charge: subsidiary self-assesses French VAT, deducts it the same return	Needs tax codes posting both output and input legs; a missing leg breaks the return
Intra-EU purchases of goods	Intra-Community acquisition, self-assessed, and the intra-Community VAT number must be valid	Wrong or missing VAT numbers push transactions into the wrong boxes
Imports from outside the	Import VAT is reverse-	Your books must match
EU	charged on the CA3 automatically, prefilled by customs data	the prefilled figures, which means capturing import documents in the ERP
Sales of services to EU businesses	Generally reverse-charged to the customer, reported on the European services declaration	Zero-rate codes must still drive the recapitulative statement

Each of these is routine for a French accountant and each needs a deliberately built tax code in NetSuite. The failure pattern is quiet: transactions landing in no box at all, discovered when the CA3 stops reconciling to the general ledger.

The currency wrinkle: USD group, EUR return

French VAT is declared and paid in euros, from euro amounts. When the transaction or reporting currency is USD, three practical rules keep you out of trouble:

• The VAT amount on a foreign-currency invoice is fixed in EUR using the applicable conversion at the tax point, and that EUR figure, not a re-translated one, is what the return and the FEC must carry.
• Revaluation must never touch VAT accounts. If your month-end FX revaluation, see our guide to French FX rules, sweeps 445 accounts, your declared VAT drifts from your booked VAT with every rate move.
• Rounding differences between line-level and total-level conversion need a home. One cent per invoice across thousands of invoices is a reconciliation item an auditor will ask about.

A configuration blueprint that holds up

Layer	Decision to make	Good default for a US-owned services sub
Chargeability	Collection basis or option for débits	If ERP simplicity matters, elect the option for débits formally, and print it on invoices
Tax codes	One per real flow, not one per rate	Domestic 20%, reverse-charge purchase (both legs), ICA, import, EU service sale, export
Accounts	Dedicated 445x structure mirroring the return boxes	44571 collected, 44566 deductible, 4458 pending/regularization, mapped once to the CA3
Reporting	France localization VAT report reconciled to GL monthly	Any gap between the report and the 445 balances is an error to clear before filing, not after
E-invoicing	Same master data feeds the e-invoicing mandate in force since September 2026	Fix VAT numbers and rates once, see our e-invoicing guide

A worked month, to make it concrete

Take a services subsidiary, no option for débits, June invoicing of €300,000 plus €60,000 VAT, June collections of €220,000 including €20,000 of advances on July work. The June CA3 does not declare €60,000. It declares output VAT on the €220,000 actually collected, advances included. The €60,000 sits split between VAT collected, for the paid share, and VAT pending, for the open receivables. If the ERP declared from invoices, June VAT is overpaid by tens of thousands, refundable only by correction, and the FEC now shows VAT postings that do not match the returns, the exact cross-check, described in our FEC guide, that audit analytics run first.

Beyond 20%: the rates, and where they hide in a B2B setup

Rate	Applies to (examples)	Trap for a US-owned sub
20% standard	Most goods and services	Default, but do not let it become the only code that exists
10% intermediate	Certain food service, transport, works on housing	Employee benefits and events invoices arrive at 10%; a 20%-only setup misdeducts
5.5% reduced	Most food, books, certain equipment for disabled persons	Office catering and gifts; small amounts, recurring, auditors like them
2.1% super-reduced	Press, certain medicines	Rare in B2B, but subscriptions to French press for the team qualify

The exposure is on the deduction side: your AP clerk in Austin sees French VAT on a supplier bill and needs the right code at the right rate to deduct correctly. Deducting 20% where the invoice carries 10% is a systematic overclaim that the FEC-to-CA3 recomputation, described in the FEC guide, spots mechanically.

Credit VAT: getting your money back

A subsidiary that invests, or exports, or sells mostly with reverse charge, accumulates deductible VAT faster than output VAT and runs a structural credit. The credit is real money, and it does not refund itself:

• Carry-forward is the default. The credit rolls to the next return automatically; groups discover six-figure credits that have rolled for years because nobody asked.
• Refund requests follow thresholds and rhythms : monthly or quarterly claims are possible above modest minimums, annually otherwise, filed with the return itself.
• Refund claims trigger scrutiny. A first significant claim routinely draws an information request or a targeted check: invoices sampled, deduction rights verified. Clean coding upstream is what makes this a formality.
• Intercompany billing changes the math. Whether the parent charges the sub, or the sub recharges the parent, moves the position, one more reason the transfer pricing setup and the VAT setup should be designed together.

The declarations around the return

The CA3 is the headline, but the French VAT ecosystem asks for supporting declarations that your ERP data must be able to feed:

Declaration	Covers	ERP dependency
EMEBI (ex-DEB, statistical survey)	Intra-EU movements of goods, on request	Requires commodity codes, weights and flows NetSuite item data must carry
État récapitulatif TVA	Intra-EU B2B supplies of goods	Customer VAT numbers, validated, per transaction
DES	Intra-EU B2B supplies of services	Service sales flagged by customer country and VAT number
CA3 annexes	Special regimes and adjustments	Correct boxes only exist if the codes upstream distinguish the flows

Each takes minutes when tax codes and master data are right, and each is a recurring incident when they are not. The pattern of this whole article in one sentence: French VAT rewards specificity, and an ERP only does specific when someone configures it.

The rhythm of a VAT month

For a team new to France, the monthly cadence itself is part of the configuration, because the ERP data must be ready when the calendar says so, not when the close finishes:

Moment	What happens	ERP dependency
Early month	Prior month closes; VAT accounts reconciled to the draft return	445 balances clean, pending VAT rolled correctly
A date assigned to your company, between the	CA3 filed and paid electronically, direct	The figure is final; corrections go on next
15th and the 24th	debit from the French bank account	month’s return, documented
Same window	Recapitulative statements filed where due	EU customer VAT numbers validated during the month, not at the deadline
All month	Incoming invoices coded, reverse-charge legs posted	The daily discipline that makes the filing week uneventful

The French administration expects electronic filing and payment, and late VAT attracts surcharges and interest mechanically. A subsidiary whose close lands after the VAT due date has a structural problem no heroics will fix; the close calendar and the VAT calendar must be designed together, which is close-calendar material from the lettrage guide.

A catalogue of the errors we correct most

• The forgotten reverse-charge leg : management fees booked as a plain expense, no output VAT self-assessed. Invisible until an audit recomputes it, then expensive, because the deduction that would have neutralized it must be argued after the fact.
• Advances with no VAT : customer deposits parked in a liability account, VAT declared only at invoicing, months late for a services company.
• The one-code-fits-all instance : every purchase at 20% deductible, including the 10% restaurant bills and the 0% insurance, small errors at industrial volume.
• Credits rolled forever : refundable VAT treated as an untouchable balance; working capital donated to the Treasury.
• EUR-USD re-translation of declared VAT : the return restated from a consolidation currency view, drifting from the euro figures fixed at the tax point.

None of these is sophisticated. All of them are systematic, which is what makes them fixable in configuration and dangerous in production.

Before the module: is the registration itself right?

A configuration audit sometimes finds the problem upstream of the software: the registration footprint no longer matches the business. The French VAT number, FR plus a two-character key plus the SIREN, attaches to a registration whose scope was declared at a point in time. Businesses evolve past their registrations:

• The subsidiary starts warehousing goods in Germany for EU delivery, and now needs registrations, or the OSS one-stop shop, beyond France.
• The US parent itself begins selling into France in its own name, needing its own French registration alongside the subsidiary’s, the situation covered in our foreign-company VAT guide.
• B2C revenue appears, SaaS sold to French consumers, bringing OSS, local rate exposure and the e-reporting side of the e-invoicing reform.
• Acquisitions bolt on a second French entity with its own number, and invoices start flowing under the wrong one.

The ERP can only be as right as the registration map it implements. We re-verify that map annually with clients, it takes an hour, and it has caught more structural VAT exposure than any code review.

The reliable audit trail: the requirement around the requirements

French VAT law asks one more thing of every business that is neither structured e-invoicing nor qualified signature: the piste d’audit fiable , a documented, permanent set of controls showing that each invoice corresponds to a real supply, linking invoice to order, delivery and payment. For an ERP company this sounds free, the links exist in the data model. The requirement is that they be documented as controls : written process, named owners, retrievable evidence. In an audit, the administration can ask you to demonstrate the trail for sampled invoices, and deduction rights on purchases stand or fall with it. The pragmatic NetSuite answer is a short controls memo mapping each requirement to a system feature, order-to-invoice linkage, three-way match, payment application, plus an annual sample test. Half a day to write, and it converts an abstract legal duty into a checklist your auditors, and the DGFiP, can tick.

A closing thought on ownership. VAT is the tax a subsidiary touches most often and understands least well as a group topic, precisely because it feels like plumbing. The configuration described here is a one-time project measured in weeks; the alternative is a permanent low-grade leak measured in corrections, credits left rolling and audits that start on the back foot. Groups that assign French VAT a named owner, with the ERP access to see the postings and the mandate to change the codes, simply stop generating the error catalogue above. The ones that leave it split between a US tax team and a French preparer who never sees NetSuite keep every item on the list alive, at volume, indefinitely.

Related Expand CPA guides

• French VAT registration for foreign companies
• The intra-Community VAT number
• The French e-invoicing mandate and NetSuite
• NetSuite for your French subsidiary

How Expand CPA can help

We configure and operate the French VAT layer around NetSuite for US-owned subsidiaries: chargeability elections, tax code architecture, monthly CA3 preparation and filing, and the reconciliation between returns, general ledger and FEC, as part of the model on our NetSuite France page. If your VAT report and your 445 accounts disagree, that is a solvable problem with a defined method. Talk to us.

Frequently asked questions

Can we just elect the option for débits and forget cash-basis VAT?

For most B2B services companies, yes, and it is often the pragmatic choice for ERP alignment. The election must be made formally, mentioned on invoices, and note that collections-basis stays relevant for advances received before invoicing.

Our VAT return is prepared outside NetSuite. Does the ERP config still matter?

Yes, because the return must reconcile to the ledger and the FEC. An outside preparer working from correct exports beats one reverse-engineering wrong postings every month.

Does SuiteTax solve French VAT by itself?

SuiteTax and the France localization provide the machinery: codes, boxes, reports. The French-specific decisions, chargeability basis, reverse-charge legs, account structure, still have to be made and configured deliberately.

Do we need a French bank account to pay VAT?

Payment runs by direct debit under the professional online account, on SEPA rails. In practice a French or SEPA-zone euro account is what makes filings, refunds and the e-invoicing platform era that began in September 2026 run smoothly, and most subsidiaries have one anyway for payroll and suppliers.

Who should actually sign and file the CA3 each month?

Whoever can stand behind the reconciliation to the ledger, in practice the statutory accountant, in-house or the firm, filing through the professional account or an EDI channel. What matters is that the signer sees the 445 reconciliation before filing, not after; a return signed by someone reading only the report is how small configuration drifts become declared numbers.