PrestaShop, French chartered accountant, VAT and 2026 e-invoicing: the operational guide

Running a PrestaShop store involves far more than processing orders. Behind every sale lies a per-country VAT rule, an OSS or IOSS filing obligation, mandatory invoice mentions, and — from September 2026 onwards — an automatic transmission of transaction data to the French tax authority. For most merchants we work with, these obligations were never properly set up, creating a silent tax liability that only surfaces at an audit or year-end close.

This guide sets out the method we apply in our Paris firm to bring a PrestaShop installation into compliance: VAT configuration audit, OSS threshold management, IOSS, B2C e-reporting, PDP connection, and accounting architecture. It is aimed at French e-commerce merchants and at foreign companies selling into France or across the EU via PrestaShop.

In short: any PrestaShop seller making more than €10,000 of B2C sales to other EU member states must collect the destination country's VAT and file it via the OSS (One Stop Shop) portal. For imported goods valued at ≤ €150 sold to EU consumers from non-EU stock, the IOSS (Import One Stop Shop) applies. From 1 September 2026, B2C e-reporting becomes mandatory: PrestaShop must be configured to produce structured transaction data broken down by country, by VAT rate and by filing regime.

PrestaShop is not an accounting platform. It generates orders, PDF invoices and CSV exports — but that data needs to be reprocessed before it can feed into a compliant French general ledger. Three levels of integration are available.

The first is a direct API connection between PrestaShop and an accounting platform such as Pennylane. Orders automatically create entries in account 707 (sales) and 411 (trade receivables); PSP payments feed account 512 after bank reconciliation. This is the cleanest solution for moderate order volumes.

The second level adds an e-commerce analytics layer — typically Sqalie — between PrestaShop and the accounting platform. Sqalie splits sales by channel, by country and by VAT regime (France, OSS, IOSS), and pushes pre-structured journal entries into Pennylane. This architecture becomes essential as soon as you sell across multiple EU countries.

The third level is manual: a monthly CSV export from PrestaShop, reprocessing in Excel, and a manual accounting import. This is the most common approach and also the most risky — per-country VAT mapping errors only appear at year-end close or during an OSS audit.

The accounts to monitor every month#

For a PrestaShop e-commerce business, the most sensitive ledger accounts are:

• 411 (trade receivables): must be cleared by PSP settlements; any gap signals an incomplete bank reconciliation
• 4457 (output VAT): must be broken down by rate (20%, 10%, 5.5%) and by regime (France / OSS / IOSS)
• 707 (product sales): must exclude credit notes and returns
• 627 or 622 (PSP fees): Stripe, PayPal, Mollie commissions — frequently omitted
• 4452 (intra-EU VAT): for B2B intra-EU reverse-charged purchases (Meta and Google ad spend)

A specialist e-commerce chartered accountant structures this chart of accounts from day one. See also our article on common e-commerce accounting errors 2026.

The principle is straightforward in theory: once your B2C sales to other EU member states exceed €10,000 (the threshold is calculated across all intra-EU B2C sales, regardless of destination), you must apply the destination country's VAT rate and remit it via the OSS portal. Below that threshold, French VAT applies to all EU B2C sales.

In practice, PrestaShop must be configured to:

1. Track the cumulative intra-EU B2C sales total in real time
2. Switch automatically to destination-country VAT once the threshold is crossed
3. Apply the correct rate per country and per product category (reduced rates vary across member states)
4. Generate invoices or receipts with the OSS reference
5. Produce a per-country, per-rate export to prepare the quarterly OSS filing

The OSS declaration is filed quarterly via the impots.gouv.fr portal. A single payment is made to the DGFiP (Direction générale des Finances publiques), which then redistributes to the relevant member states.

The most common trap: the threshold crossed without the switch#

On the majority of PrestaShop files we take over, the €10,000 threshold had been exceeded without the OSS switch ever being activated in the module. The result: all intra-EU sales continued to be invoiced at the French VAT rate, when the destination country's VAT should have been collected. A corrective OSS filing must then be reconstructed country by country, using the rates applicable at the date of each sale.

It is not enough to tick a box in the PrestaShop back-office. You also need to verify that the per-country tax rules are up to date, that product categories are correctly mapped to local reduced rates, and that the OSS module generates the right invoice mentions.

If your PrestaShop store sells products imported from third countries (China, post-Brexit UK, USA) to EU customers for amounts ≤ €150, the IOSS applies. The seller collects VAT at the point of sale, declares it via the IOSS return, and the parcel enters the EU free of import VAT at the border.

Concretely, PrestaShop must:

• Identify eligible orders (non-EU origin, amount ≤ €150, EU customer)
• Apply the destination country's VAT rate at checkout
• Include the IOSS number in the customs data for each parcel
• Produce a monthly IOSS export for the filing

If your carrier uses your IOSS number without PrestaShop being configured to collect the corresponding VAT, you face either double taxation or a customs assessment.

France's e-invoicing reform draws a clear line between two obligations depending on the nature of the sale.

For B2B sales (to VAT-registered businesses in France), the obligation is to issue invoices in a structured format (Factur-X, UBL, CII) via a DGFiP-approved PDP (Plateforme de Dématérialisation Partenaire — Partner Dematerialisation Platform). The deadline for SMEs and micro-businesses is 1 September 2027 for issuance, but reception of B2B e-invoices is mandatory from 1 September 2026 for every company, without exception.

For B2C sales (to end consumers) and international sales (outside the EU, or to non-VAT-registered EU buyers), the law does not require the issuance of a structured e-invoice to the customer. Instead, it mandates e-reporting: the periodic transmission to the DGFiP of aggregated transaction data — revenue, output VAT by rate, number of transactions, OSS sales, IOSS sales.

For a predominantly B2C PrestaShop store, e-reporting is therefore the central obligation for 2026-2027. The exact periodicity and transmission format should be confirmed with your PDP or chartered accountant against the regulations in force at your go-live date.

What PrestaShop must produce for e-reporting#

B2C e-reporting cannot be produced from a simple monthly CSV export. The data must be structured and accurate:

If your PrestaShop exports do not cleanly separate these categories, e-reporting becomes impractical. The per-country, per-rate breakdown must be built upstream, at the moment the VAT module is first configured.

A PrestaShop store that also issues B2B invoices (sales to VAT-registered professionals) must connect to a DGFiP-approved PDP. Several accounting software vendors are positioning themselves as candidate PDPs; check your solution’s actual status on the official register of accredited PDPs. Other solutions exist depending on the complexity of your transaction flows.

The connection can be established in several ways:

• Via the Pennylane API: B2B orders in PrestaShop automatically generate invoices in Pennylane, which forwards them to the PDP
• Via a middleware layer (Sqalie, Make, Zapier): PrestaShop flows are transformed into Factur-X format before transmission to the PDP
• Via a native PrestaShop PDP module: some approved PDPs offer modules to install directly in the back-office

The right choice depends on B2B volume, budget, and the existing technical architecture. For a purely B2C PrestaShop, the priority is e-reporting rather than a B2B PDP connection. To compare options, see our guide on choosing a PDP in 2026.

A general-practice accountant can handle a PrestaShop bookkeeping file. But the specific challenges of e-commerce — multi-country OSS VAT, IOSS, B2C e-reporting, PSP reconciliation, per-channel margin tracking — justify a specialist profile.

In our firm, we regularly take over PrestaShop files where:

• OSS returns were never filed despite the €10,000 threshold having been exceeded for 18 months
• Reduced VAT rates (books, food) were applied at 20% across all EU countries
• PSP fees (Stripe, PayPal) were never posted, distorting the actual margin
• The trade receivables account (411) had not been cleared for 6 months, masking outstanding PSP settlements

A specialist engagement covers: the initial configuration audit, monthly VAT export review, quarterly OSS filing, annual year-end close with the liasse fiscale, and e-reporting scoping ahead of the 2026-2027 deadlines. For tariffs and methodology, see our e-commerce practice page or our article on the cost of accounting for an e-commerce site.

Anonymised real file. 2025 revenue: €720,000 — 600 orders/month across France, Spain, Italy and Belgium. OSS had never been correctly filed. Findings from the configuration audit:

• €18,000 of VAT misallocated between France and Italy (Spanish rate applied instead of Italian rate over 8 months)
• Shipping fees charged at 20% on 320 book orders (should have been 5.5%)
• 14 test orders never deleted, creating gaps in the invoice numbering sequence
• No Pennylane connection: account 707 (sales) and 411 (receivables) rebuilt manually from CSV exports every month
• OSS threshold of €10,000 crossed in March 2024, switch never activated

6-week action plan: module audit, per-country tax rule overhaul, Pennylane API integration, Sqalie deployment for per-channel margin tracking, e-reporting configuration for 2026. Outcome: 3 days per month saved for the business owner, zero corrective filing on the first quarterly OSS return after the scoping exercise.

The e-invoicing reform is generating a lot of noise. In e-commerce files, three points deserve immediate attention.

First: the OSS audit comes first. The €10,000 threshold is easy to cross in the first year of cross-border growth. A corrective OSS assessment covers all undeclared intra-EU sales, using the rates applicable in each country at the date of each sale. This is the most immediate and most under-estimated risk in PrestaShop files.

Second: structure your data before e-reporting. B2C e-reporting cannot be set up in a week. If PrestaShop exports do not distinguish VAT rates by country and by product category, bringing the data into compliance requires a heavy retrospective reprocessing exercise. Fixing the configuration now is far cheaper.

Third: the technical architecture matters. PrestaShop alone is not enough. The combination of PrestaShop + analytics layer (Sqalie) + accounting platform (Pennylane) + specialist chartered accountant is the only architecture that reliably handles bookkeeping, OSS/IOSS filings, e-reporting preparation and audit readiness.

Updated 2026-06-14. This article provides general information and does not replace personalised advice. For your specific situation, consult a chartered accountant (expert-comptable) registered with the Ordre des Experts-Comptables.