E-commerce accounting: VAT OSS, tax regime, PSP reconciliation and J+10 monthly close

E-commerce accounting concentrates, in a single file, several problems that other businesses rarely face together: multi-channel sales, multiple payment service providers, high-volume returns, VAT obligations across EU countries, and management reports that become meaningless if reconciliation has not been done. This guide covers the fundamentals — tax regime choice, OSS VAT treatment, PSP reconciliation method — before detailing the J+10 monthly close we deploy in client engagements at Hayot Expertise.

Direct answer. For a goods-selling e-commerce business in France, the micro-BIC regime is available up to €203,100 in revenue (2026–2028 thresholds). Beyond that, or as soon as your EU B2C sales outside France exceed €10,000 cumulated, the standard (réel) regime and the OSS filing portal are mandatory. The three-way reconciliation — order × PSP × bank — is the only method that reliably validates both VAT and channel margin.

This is the first decision to make, and it determines all subsequent obligations.

Micro-BIC thresholds 2026–2028#

Micro-BIC thresholds were revised upward for the 2026–2028 period. For goods-selling e-commerce:

Source: service-public.fr, micro-BIC thresholds revalued for 2026–2028.

When the réel regime makes sense before reaching the threshold#

The 71% flat deduction looks attractive on paper. In practice, a physical-goods e-commerce business typically carries 55–75% in actual costs (cost of goods, shipping, PSP and marketplace commissions, advertising). Once actual costs exceed the flat deduction, the réel regime produces a lower tax bill.

A second reason to switch before the threshold is VAT. Under the micro regime, you benefit from the franchise en base VAT exemption up to approximately €85,000 (verify the current threshold at the time of decision). Once you exceed it, or if your B2B customers need to reclaim input VAT, the exemption becomes a commercial constraint.

Our reading. We consistently recommend the réel regime from around €50,000–€60,000 in revenue, or as soon as EU B2C sales exceed €10,000. The administrative simplicity of the micro regime does not offset the margin distortions and VAT risks it creates at that level.

The e-commerce VAT rules were fundamentally reformed on 1 July 2021 with the introduction of the OSS portal. The mechanism is straightforward to understand; implementation raises several practical issues.

The single EU threshold of €10,000#

Since 1 July 2021, a single threshold of €10,000 excl. VAT applies to all intra-EU distance sales of goods and digital services to B2C customers (all EU countries combined). This threshold is assessed on the current and preceding calendar year.

• Below €10,000: French VAT applies; declare in France via standard CA3.
• Above €10,000: VAT of the customer's country of destination applies; declare and pay quarterly via the OSS portal.

Source: economie.gouv.fr (e-commerce VAT), impots.gouv.fr (OSS portal).

OSS in practice#

The OSS portal is accessible via your professional space on impots.gouv.fr. It lets you declare and pay in one place the VAT owed in all EU member states, without registering for VAT in each country. Declarations are quarterly (deadlines: 30 April, 31 July, 31 October, 31 January).

Key practical points:

1. OSS covers B2C sales only. Intra-EU B2B sales continue to use the standard reverse-charge mechanism.
2. Each line in the OSS declaration identifies the destination country, the applicable VAT rate, and the VAT amount collected.
3. VAT rates vary by member state and product category. A country/product-type matrix is essential if you sell across several EU states.
4. Facilitating marketplaces (Amazon, eBay, Etsy) are liable for the VAT in place of the seller in certain scenarios. You must exclude those sales from your own OSS declaration to avoid double-reporting.

IOSS: imported goods below €150#

The IOSS (Import One-Stop Shop) is a separate regime for goods imported from third countries (outside the EU) with an intrinsic value of €150 or less. If you store products outside the EU and ship directly to EU customers (dropshipping from Asia, for example), IOSS may be the appropriate mechanism.

Source: impots.gouv.fr (IOSS portal).

VAT summary table by scenario#

This is where most errors occur in the e-commerce files we take on. The core cause: people book what the bank receives, not what the customer actually paid.

The PSP transfer problem#

A Stripe transfer received on the 15th does not correspond to the sales of that month. It corresponds to orders placed between J−7 and J−2 (depending on your Stripe plan), net of all deductions Stripe has applied: commissions (~1.4% + €0.25 per transaction, indicative figure for Stripe Europe), refunds, chargebacks, dispute fees, and any rolling reserve.

Booking that transfer directly to account 707 (goods sales) means ignoring the fees, mixing periods, and making VAT verification impossible.

The three-way reconciliation method#

The reliable method is to reconcile three sources for each PSP and each period:

The expected gap between back-office and bank is the sum of PSP fees, refunds, chargebacks, dispute costs and payout lag. Any unexplained variance above 0.5% of revenue warrants investigation and documentation.

Marketplace accounting#

For Amazon, Cdiscount or Etsy, the same logic applies but statements are more complex and must be split into six distinct accounting lines:

• Gross revenue by channel and VAT rate;
• Referral commissions (8–15% by category);
• FBA fees (preparation, shipping, return);
• Storage fees (monthly + long-term);
• Amazon Ads (with reverse charge if billed from Ireland);
• Refunds and seller-charged indemnities.

Each line has a distinct accounting treatment. Commissions go to an expense account (6xx), not as a reduction of revenue. Amazon Ads invoiced from Ireland require a French reverse-charge VAT entry.

Reconciliation is less a tool question than a timing and discipline question. The starting point is always the same: never start from the bank statement.

The four systematic sources of divergence#

1. Payout lag: Stripe, PayPal and marketplaces do not transfer in real time. Delays range from J+2 to J+7 depending on your plan and history. End-of-month orders arrive in the following month's bank statement.
2. PSP fees: deducted before the transfer, they do not appear as line items on the bank statement. They must be posted as separate expense entries.
3. Refunds and chargebacks: a refund triggers a partial VAT reversal. A chargeback also involves a dispute fee. Both reduce the transfer but in different ways.
4. Reserves: Stripe may hold a reserve on your balance during active disputes or with a higher-risk profile. This reserve is neither a charge nor income until released.

The underestimated risk#

Without monthly reconciliation, gaps accumulate across periods. When the annual accounts are prepared, it becomes very difficult to reconstruct payout timing month by month. The OSS VAT filed quarterly becomes an estimate rather than a calculation. In a tax audit, the absence of documented monthly reconciliation is a negative signal.

This 5-step checklist, anchored on a J+1 to J+10 working day calendar, is tenable for a store of up to approximately 5,000 orders/month with 1 to 3 PSPs. Beyond that volume, plan for J+12 to J+15.

Step 1 — J+1: extract gross sales by channel#

On the first working day of the following month, extract sales reports from each channel (Shopify Orders export, Amazon Date Range Report, marketplace equivalents). The goal is to lock in a reference baseline — not yet to reconcile.

Step 2 — J+3: three-way reconciliation order × PSP × bank#

For each PSP, reconcile the three sources described above. Document any variance above 0.5% of revenue.

Step 3 — J+5: marketplace commissions, returns, credits#

Split marketplace statements into six accounting lines. Post returns with their associated VAT correction.

Step 4 — J+7: OSS VAT computed, FEC, stock cut-off#

With reconciled net revenue by channel and country, compute French VAT on French B2C sales, OSS VAT country by country above the €10,000 threshold (art. 259 D French Tax Code), IOSS where applicable, and reverse charge on Irish-billed ad invoices. Export the FEC and run the stock cut-off.

Step 5 — J+10: channel net margin, KPI dashboard, validation#

Publish the monthly dashboard, have your accountant review the entries, validate the VAT position, and flag threshold alerts (€10,000 OSS, €203,100 micro-BIC, VAT exemption threshold).

J+10 calendar summary#

Updated 2026-05-26. This article is for information purposes and does not replace personalised advice. For your specific situation, consult a chartered accountant registered with the Ordre des experts-comptables.

This English section is written for international readers who need to apply the French guidance to a real management decision. The key point for accounting for a French e-commerce site in 2026 is not to memorise every technical rule, but to connect the rule to documents, deadlines, cash impact and governance. For online merchants, marketplaces and SaaS-led brands selling from France, the right approach is to identify the decision to be made, collect reliable evidence, and only then choose the accounting, tax, payroll or legal treatment.

The practical decision is which VAT, payment-reconciliation and inventory workflow to set up so the accounts mirror real cash flows. That decision should be documented before the year-end close, financing discussion, payroll run, transaction signing or tax filing concerned by the topic. When the matter is material, the file should include who decided, which assumptions were used, and which professional advice was obtained.

Evidence to keep#

• payment-platform statements;
• monthly VAT reconciliation file;
• marketplace settlement report;
• inventory close procedure;
• refund and chargeback log;

Mismatches between payment-platform reports and accounting entries are the top source of margin distortion for French e-commerce operators. A clean file also helps the company answer questions from banks, investors, auditors, tax authorities, employees or buyers. It is usually cheaper to prepare that evidence during the process than to reconstruct it after a dispute, audit or urgent financing request.

Management checklist#

Before acting, management should run a short checklist. First, confirm that the entity, period and perimeter are correct. Second, compare the accounting treatment with the tax, payroll or legal consequence. Third, quantify the cash effect, because a technically valid option may still be unsuitable if it creates a short-term liquidity issue. Fourth, make sure the decision can be explained in plain English to a shareholder, lender, employee or buyer who is not familiar with French terminology.

For French subsidiaries of foreign groups, translation is also a control topic. A term that sounds familiar in English may not have the same legal meaning in France. The safer method is to keep the French source wording in the working file, then add a short English management note explaining the decision, the financial effect and the residual risk.

How Hayot Expertise would frame the work#

In a professional review, the starting point is the business objective. Is the company trying to reduce risk, close the accounts, prepare a filing, obtain financing, retain employees, sell a business or improve reporting? Once the objective is clear, the technical analysis becomes more useful because it is attached to a concrete decision. Hayot Expertise would generally separate the work into three layers: compliance, numbers and management judgement.

The compliance layer answers whether a rule applies and which documents are required. The numbers layer measures the effect on profit, tax, payroll, cash, equity, valuation or working capital. The management layer decides whether the option is consistent with the company's strategy and risk appetite. This separation avoids a common mistake: treating a French technical rule as if it were only an administrative formality.

A fuller decision framework#

For a director who does not work daily with French accounting and tax rules, the safest framework is sequential. Start with the legal form and tax regime of the business. Then identify the income stream, expense, asset, employee benefit, transaction or reporting obligation concerned. Then test the accounting treatment, the tax treatment and the cash effect separately. Only after those three views are consistent should the company automate the process in accounting software or payroll.

This matters because French compliance is document-heavy. A bank feed, invoice, contract, payroll notice or tax form may each be correct on its own, while the overall file remains inconsistent. For example, the accounting entry may not match the tax return, the VAT position may not match the invoice wording, or the management report may not match the board minutes. English-speaking directors should therefore ask for a short reconciliation note whenever the amount is significant.

Questions to ask before closing the file#

• What is the exact French rule or accounting principle being applied?
• Which document proves the amount, date, counterparty and business purpose?
• Does the treatment affect VAT, corporate tax, income tax, payroll or social contributions?
• Is the cash impact immediate, deferred or only visible at sale, audit or financing?
• Who inside the company owns the update next year?

Why this improves SEO and real usefulness#

For an English reader, the value of this article is not a literal translation of the French version. It is the bridge between French terminology and management action. The content should help the reader understand what to verify, what to ask the accountant, and where the risk may sit in the financial statements or cash forecast. That is also the reason the English version keeps the French concepts visible while explaining them in operational language.

When to ask for help#

Professional input is useful when the topic changes the tax result, payroll cost, legal position, financing capacity, valuation or shareholder relationship. It is also useful when the company is growing quickly and the same decision will repeat every month. A small error in a one-off file is inconvenient; the same error embedded in a recurring workflow becomes expensive.