Nordlet

← Blog

Real-Time EU VAT for Developers Building in France

A grounded comparison of accounting and tax platforms that handle French and EU VAT through APIs, SDKs and webhooks, with clear notes on what each one actually covers.

Nordlet Team · · 13 min read

France is about to change what "VAT integration" means. From September 2026 every business has to be able to receive an electronic invoice, large and mid-sized companies have to issue them, and transaction data has to be reported alongside. Any platform selling you "French VAT support" today should be asked which of those it covers, because most of them cover the easy part — computing 20% at checkout — and none of the hard part.

This piece compares the developer-facing platforms that handle EU and French VAT in real time, separates calculation from bookkeeping from filing, and says where each option actually fits.

What "real-time EU VAT management" has to include

The phrase gets stretched to cover very different products. To mean anything, a platform has to do most of the following while a transaction, invoice, settlement or ledger entry is being created:

  • Work out the VAT treatment from the transaction data.
  • Apply the current country and product rules.
  • Cover France and the wider EU, including B2B reverse charge and B2C destination taxation.
  • Expose all of that through an API, SDK or webhook.
  • Keep the data for VAT, OSS, audit and accounting reporting.

Three different capabilities hide inside the words "real time":

  • Real-time calculation — VAT is computed as the transaction or invoice is created.
  • Real-time accounting — the transaction, the ledger entry and the VAT data land in the books immediately.
  • Real-time reporting — the data is transmitted to a tax authority shortly after the transaction.

Most products do the first. Very few do all three. France is one of the countries where the third capability stops being optional: the 2026 reform pairs mandatory e-invoicing through accredited platforms with e-reporting of transaction data to the tax administration.

The French and EU rules that shape the comparison

France applies a 20% standard rate, with reduced rates of 10%, 5.5% and 2.1% and 0% for exports and intra-EU supplies. The franchise en base thresholds are €37,500 for services and €85,000 for goods, with tolerance limits of €41,250 and €93,500 — below them a business charges no VAT at all, which is a state your invoicing code has to represent rather than assume away. The rules and the current thresholds are published by Service-Public / DGFiP.

For qualifying intra-EU B2C distance sales and cross-border digital services, the EU-wide threshold is €10,000, set out on the European Commission's One Stop Shop portal. Above it, VAT generally follows the customer's Member State. The One Stop Shop lets a business register in one Member State and declare cross-border B2C VAT for the whole EU, but it does not remove the need for transaction-level logic.

There is also a marketplace rule that is stricter than most teams expect. Under Article 14a an electronic interface becomes the deemed supplier for distance sales of imported goods in consignments not exceeding €150, and separately for goods supplied to EU customers at any value when the underlying seller is not established in the EU. The Commission's Explanatory Notes on the VAT e-commerce rules set out both limbs. If you are building a marketplace, this changes the architecture rather than adding a field.

The shortlist at a glance

Platform Best fit Real-time VAT capability Accounting, OSS and filing scope Main caveat
Stripe Tax Products and marketplaces already on Stripe Calculates VAT as the transaction is created, France included EU exports and OSS data; no French ledger, and it does not file EU returns itself Only worth it when Stripe is already the payment rail
Paddle SaaS and downloadable digital products Calculates VAT at checkout from the customer location Registers, files and remits as Merchant of Record Takes over the seller-of-record role and the invoice with it
Quaderno Smaller SaaS and digital commerce Calculates at checkout, validates VAT numbers Tax reports and records; automatic filing is not documented for every plan A tax and invoicing layer, not a ledger
Avalara AvaTax Enterprise ERP and billing stacks Real-time determination with maintained tax content VAT Reporting is a separate product in the Returns range Scoped and priced for enterprise rollouts
Fonoa Tax Engine Large platforms and marketplaces Real-time determination across 190+ jurisdictions Returns, e-invoicing and reporting; tax-number validation is a separate product No published pricing
Nordlet Embedded accounting inside marketplaces and platforms Resolves the scheme and the rates per transaction, posted together with the ledger entry Immutable double-entry ledger, payouts, OSS and IOSS figures, exportable audit trail No CA3 return pack and no PDP integration; produces the underlying figures and Peppol invoices

Stripe Tax: the quick path when Stripe is already there

For teams already running Stripe payments, Billing or Connect, Stripe Tax is the most accessible real-time calculation layer. The documentation covers calculating VAT worldwide, the Tax API with PaymentIntents, collecting tax on invoices, and using Tax with Connect as a platform or marketplace.

Where Stripe stops is stated plainly by Stripe. Its filing documentation says: "You must file and remit the tax you collect for every location where you're registered." Automated filing is offered in the United States; elsewhere Stripe works with filing partners, so an EU VAT return is filed by you or by a partner, not by Stripe Tax. It is a calculation and export layer, not a set of books.

For a French build, Stripe Tax answers the rate question and none of the 2026 reform questions. Neither the CA3 nor the e-reporting flow comes out of it.

Paddle: hand the whole tax role to someone else

Paddle is a different category of product. It acts as Merchant of Record and takes responsibility for "calculating, filing, and remitting" tax where your customers are, so it computes VAT at checkout, issues the invoice, and files and remits for you. Its developer documentation covers Paddle.js, the catalog APIs, checkout and webhooks such as transaction.completed, which fires once a transaction reaches completed status and is the usual hook for granting access after payment.

The trade-off is structural rather than technical. Paddle becomes the seller of record, so you no longer hold the merchant, invoice and accounting model you would keep with your own checkout.

For digital products sold to French consumers this removes the filing problem entirely. It does not remove the e-invoicing obligation on invoices your own French entity issues to French businesses.

Quaderno: a tax layer for smaller digital businesses

Quaderno is one of the clearer developer-first options for smaller digital businesses that want a tax service independent of a single payment processor. Its API documents a /tax_rates/calculate endpoint that computes the applicable rate from the customer's address and the transaction type, a /tax_ids/validate endpoint that covers EU VAT numbers, and invoice, receipt and credit-note endpoints. A documented Connect section with account resources is the part a marketplace would build on.

The limit is scope. Quaderno is a tax and invoicing layer, not an accounting system with an immutable double-entry ledger, and its public material does not establish automatic filing on every plan in every country. Treat filing responsibility as something to confirm in writing.

It covers checkout calculation and VAT-number validation well. It does not produce a CA3, and it is not an accredited platform in the French reform.

Avalara and Fonoa: the enterprise tax engines

Avalara's AvaTax performs real-time tax determination during checkout, invoicing or order processing, through REST APIs and SDKs. Note the product split: VAT Reporting sits separately under Returns, so an EU VAT compliance workflow is not simply "AvaTax" — scope the modules you actually need. Avalara documents a signup path with a 90-day free trial, while the production commercial model is enterprise-shaped.

Fonoa's Tax Engine states that it "calculates the correct indirect tax treatment for every transaction in real time" through a versioned API across more than 190 jurisdictions. One architectural detail matters: tax-number validation is a separate Fonoa product (Validate), not part of Tax Engine, so if VIES evidence matters to you, scope it explicitly instead of assuming the engine covers it.

Both are credible choices for a large French platform, and both are the sort of purchase that comes with a scoping exercise rather than a signup form.

Where Nordlet fits: the VAT answer and the ledger entry are the same record

Nordlet is an accounting API for marketplaces and platforms that need ledgers, payouts, EU tax and an exportable audit trail inside their own product, rather than an invoicing app attached to a checkout.

The architectural difference is that VAT determination and the accounting entry belong to one system. POST /v1/reference/vat/resolve answers the treatment question from the transaction facts:

{
  "customerCountryCode": "FR",
  "customerIsBusiness": false,
  "supplyType": "digital"
}

{
  "scheme": "oss_union",
  "vatCountryCode": "FR",
  "reverseCharge": false,
  "deemedSupplier": false,
  "zeroRated": false,
  "rates": [
    { "category": "standard", "ratePercent": "20.00" },
    { "category": "reduced", "ratePercent": "10.00" },
    { "category": "reduced", "ratePercent": "5.50" },
    { "category": "super_reduced", "ratePercent": "2.10" }
  ],
  "legalBasis": "Directive 2006/112/EC art. 58 — taxable where the consumer resides; report via the Union OSS"
}

Change the customer to a business with a valid French VAT number and the same call returns reverse_charge with Directive 2006/112/EC art. 44, 196 — VAT due by the customer (reverse charge). Set actingAsMarketplace with a seller established outside the EU and it returns deemedSupplier: true under art. 14a(2). The legal basis travels with the answer, which is the part an auditor asks about years later.

Nine schemes are modelled: domestic, intra_eu_b2b, reverse_charge, oss_union, ioss, marketplace_deemed, export, out_of_scope and sme_exempt. The €10,000 distance-selling threshold is tracked rather than assumed — /v1/declarations/eu/distance-sales-threshold/get reports where a company stands against it, and /v1/declarations/eu/oss/compute and /v1/declarations/eu/ioss/compute produce the period figures, including a corrections section for earlier periods. Rates come from the European Commission's TEDB feed with effective dates, and a company can override them per country.

The determination then posts into an immutable double-entry ledger with the VAT metadata attached to the entry, so there is no second reconciliation between a tax engine and a separate system of record. Monetary amounts are decimal strings, never floating-point numbers. Around that: typed SDKs, webhooks such as sale_invoice.paid, Idempotency-Key support for safe retries, sandbox companies, VIES validation frozen against the invoice, multi-company support, and period locking so a closed month cannot be quietly edited.

Being precise about the boundary, because it decides whether this fits a French build. Nordlet does not ship a French return pack: /v1/declarations/eu/vat-return/compute with countryCode: "FR" returns a 422 naming the packs that do exist — Lithuania, Germany and Poland — so there is no CA3 or CA12 generation and no FEC audit file. There is no integration with an accredited platform (PDP) for the 2026 reform. What is there for France is the VAT determination, the ledger the numbers come from, OSS and IOSS figures, and structured invoices over Peppol BIS 3.0 through your own access point or the platform one. Rate determination is per country and rate category, not per product classification, so anything that turns on a CN or CPA code still needs deciding upstream.

The honest summary: if you need live calculation in as many countries as possible and someone else to file, the enterprise tax engines and the Merchant of Record services are further ahead. If your central requirement is real books — a marketplace-aware double-entry ledger where settlements and VAT sit in one place — that is the gap Nordlet is built for, and none of the calculation layers fills it. The API reference shows the full surface before you commit.

What France makes you file

The French picture has one steady obligation and one large change in progress.

  • CA3 VAT return — filed monthly through impots.gouv.fr, or quarterly when annual VAT due is under €4,000. Smaller businesses may instead use the simplified annual regime (CA12).
  • FEC audit file — the fichier des écritures comptables, produced on demand during an audit rather than filed on a schedule. It is a reason to care whether your ledger is exportable in a structured form.
  • E-invoicing and e-reporting from September 2026 — every business must be able to receive electronic invoices, and large and mid-sized companies must issue them; small and micro businesses follow in September 2027. Invoices travel through accredited platforms (PDP) in Factur-X, UBL or CII, and transaction data is reported alongside.

The reform is the part worth planning around. It changes the invoice from a document you render to a message you route, and a platform that issues invoices on behalf of French sellers inherits that change.

The full picture for the country — corporate tax, payroll, filing calendar and the authorities behind each form — is on the France tax page.

Selection criteria worth running before you commit

Before treating any "VAT-ready" product as equivalent to another, check it against these:

  • Calculation or bookkeeping — does it determine the VAT treatment, or only store a code you pass in?
  • French coverage — 20%, 10%, 5.5%, 2.1%, 0%, reverse charge, and the franchise en base state?
  • EU destination logic — can it tell French VAT from another Member State's for a B2C sale?
  • B2B VAT-number validation — does it check VIES and keep the evidence?
  • OSS and IOSS — does it aggregate, prepare, submit, or only export?
  • Marketplace liability — can it model seller, platform and deemed-supplier roles?
  • Accounting integrity — does each calculation produce a matching ledger entry?
  • Developer ergonomics — REST API, SDKs, webhooks, sandbox, idempotency, versioning?
  • Audit trail — rate, rule, location evidence, VAT number, timestamp, revision history?
  • Readiness for the 2026 reform — can it produce Factur-X, UBL or CII, and does it have a route to an accredited platform (PDP) before September 2026?
  • Filing responsibility — exactly which step does the vendor accept?

FAQ

Which platform offers complete real-time EU VAT management in France?

None should be described as offering all three real-time capabilities for every business model, and the 2026 reform widens the gap: calculation vendors are not accredited platforms. Verify calculation, bookkeeping and transmission separately for your own case.

Is Stripe Tax enough for a French marketplace?

For calculation and exports, often yes. For a double-entry ledger tracking payouts across many sellers, no. It also does not produce the CA3 or connect to an accredited platform, so the 2026 reform still needs a separate answer.

Does Nordlet file French VAT returns automatically?

No, and it does not compute the CA3 either. Country-specific return packs ship for Lithuania, Germany and Poland; for France the API returns a 422 that names them. For France it produces the VAT determination, the ledger, OSS and IOSS figures, and the audit trail.

What does the September 2026 French e-invoicing deadline require?

From September 2026 all businesses must be able to receive electronic invoices, and large and mid-sized companies must issue them; small and micro businesses follow in September 2027. Invoices go through accredited platforms in Factur-X, UBL or CII, with transaction data reported alongside.

What to do first

Decide which of the three real-time capabilities you actually need, then decide who handles the 2026 reform for you. If you need live calculation on a Stripe stack, start with Stripe Tax. If you sell digital products and want filing off your plate, test Paddle. If you are building a marketplace where the books, the settlements and the VAT belong inside your product, get started with the sandbox and confirm what is and is not covered for France before you build around it. Pricing is published rather than quote-only.

Sources

Every vendor claim above links to that vendor's own documentation. The rules themselves come from:

Vendor capabilities and national mandates both change. Everything here was checked against public documentation on 8 September 2026; verify anything you are about to build on.