Mandatory POS Software in France 2026: NF525 & ISCA

A tax inspector walks into your shop on a Tuesday morning, sits down at the end of the counter and asks to see three years of sales. Not the folder of receipt copies: the detail, line by line, in a file he can open on his laptop. There are two ways that morning can go. Either you open your till, generate the export, hand it over, and he is gone before the lunch rush. Or you spend the week piecing figures back together, and he leaves with questions.

The whole regulation lives in that difference. Since January 1, 2018, every VAT-registered merchant in France must take payments on POS software that guarantees four things: a validated sale can no longer be modified, it is secured, it is kept, and it can be handed to the tax administration in a usable format. Those four requirements are what publishers call the ISCA criteria: immutability, security, conservation, archiving. The obligation comes from France's anti-VAT-fraud law and covers shops, restaurants, salons, practices, every business that records payments. If you are not VAT-registered, it does not apply to you.

The cost of ignoring it is written in plain figures: a fine of 7,500 euros per non-compliant piece of software. One till at the counter and a second one on the terrace makes two. And the fine is not the worst part. A till whose sales can be quietly deleted casts doubt on your entire bookkeeping, which gives the administration a good reason to widen the audit and go back several fiscal years. At that point you are no longer arguing about software, you are arguing about a reassessment.

Notice where the obligation actually sits: on your tool, not on your honesty. You can run the cleanest till on the street, but if the software technically allows a validated sale to be erased, it is not compliant, and you are the one who pays. Hence the only question worth asking before you compare any feature list. The software I use today, is it in order or not? You cannot guess the answer. You read it on a document your publisher should be able to send you the same day.

Immutability. A validated sale does not get erased. The waiter rang up the wrong table, the customer sends back a dish, you charged 32 euros instead of 23: the correction is still possible, but it goes through an additional entry (void, credit note, discount) that stays visible in the history. Nothing disappears, everything adds up. This is the pillar that drove the law. Before 2018, some software quietly shipped a feature to tidy up the day before closing, and the tax authority eventually noticed.

Security. Every transaction is signed and chained to the previous one through a cryptographic hash. If someone edits a sale from six months ago straight in the database, the link no longer matches the next one and the break shows. This machinery asks nothing of you: it runs on its own, in the background, and it turns your history into a sequence nobody can touch up without leaving a mark.

Conservation. POS data must be kept for at least 6 years in France. Not just receipts: voids, discounts, payment methods, daily closings. Over six years, a shop doing a hundred receipts a day piles up more than two hundred thousand lines. That is exactly the kind of archive a backup drive eventually loses, and the kind a cloud-based system keeps without you ever thinking about it.

Archiving. On audit day, the inspector does not want to look at your screens, he wants a file. The expected format is the FEC (Fichier des Ecritures Comptables), sometimes a standardized CSV export depending on who you are dealing with. This point sounds minor and is not: software can tick the first three pillars and still leave you without an export button, which forces you to go through the publisher's support, wait, and sometimes pay. digabloPos generates the FEC in one click from the dashboard, for any period you choose.

Keep the underlying logic in mind. These four pillars are not there to watch you, they are there to make your history impossible to contest. The day a customer disputes an amount, an employee swears he never gave that discount, or your accountant cannot find Saturday night's missing 40 euros, the same machinery settles it. Compliance protects you first.

Two documents prove a till is in order, and they carry exactly the same weight with the tax administration: the publisher's attestation, or the NF525 certification issued by an accredited body (the LNE in France). Plenty of merchants believe only the second one counts, and get sold a pricier subscription because of it. That belief is wrong, and it costs money every month.

The attestation is a sworn declaration from the software publisher. It commits their liability, names the product and its version, and spells out how it meets each of the four criteria. It is the usual route for SaaS platforms and independent publishers, and it is fully accepted by the tax administration. What matters is that you have it to hand, current, with the right version number on it. An attestation sleeping in your business partner's inbox does not exist on audit day: print it, file it with your lease and your incorporation papers.

NF525 certification rests on a full third-party audit of the software and of the publisher's procedures. The level of assurance is higher, so are the cost and the lead time, and that spend always ends up somewhere in the price of your subscription. For a publisher selling to chains and large retail, the investment makes sense. For you as a merchant, it changes nothing about your legal position: both documents cover you the same way.

So the right question for your supplier is not "are you NF525 certified?" but "can you send me your compliance attestation today, in my name, for the version I am running?". A serious publisher sends it the same day, or better, lets you download it yourself without asking anyone. That is how digabloPos works: the attestation sits in your account settings. If your current publisher stalls or routes you to a salesperson, you already have your answer.

This is the number-one confusion of the year, and it sells a lot of subscriptions nobody needs. Two reforms, two subjects, two timelines.

NF525 / ISCA compliance is about your POS software: how you record payments at the counter. It has been mandatory since 2018 for every VAT-registered business, and it is the subject of this guide. It is also the only thing you are already late on if you still ring up sales in a spreadsheet or on a cash drawer with no audit trail.

The e-invoicing reform is about business-to-business (B2B) invoices, sent through approved platforms (PDP). Its timeline:

- September 1, 2026: every VAT-registered business must be able to receive electronic invoices; large enterprises and mid-caps (ETI) must also issue them. - September 1, 2027: it is the turn of small and medium businesses (TPE/PME) to issue their invoices electronically through an approved platform.

Translate that for a restaurant, a salon or a corner shop. The September 2026 deadline mostly asks you to be able to receive your supplier invoices electronically. Issuing yours waits until 2027 if you are a small or medium business. The salesperson who calls waving "the September 2026 law" to sell you a sixty-euro-a-month platform is mixing the two subjects, deliberately or out of ignorance. Ask him straight: are you talking about my till or about my supplier invoices?

The two obligations are complementary, not interchangeable. Your ISCA-compliant till records counter sales, receipt by receipt. Your B2B invoices will travel through an e-invoicing platform, typically billed between 5 and 50 euros a month depending on volume and services. digabloPos covers the first part, the till, and leaves you a clean sales base that makes the second one far easier. The e-invoicing module switches on at 10 euros a month the day you actually need it, not before.

With digabloPos, ISCA compliance sits in the engine. There is nothing to switch on, nothing to tick, nothing to configure. Every sale is timestamped, signed and chained to the previous one the moment you validate the payment. You see none of it happen, and that is the point: an obligation handled properly is an obligation you forget. Data goes to the cloud with redundant backups, which also settles the six-year question. Your history no longer depends on the tablet at the counter, which will eventually be dropped, stolen or replaced.

The daily Z report is generated automatically at closing, with the totals the administration expects: revenue by VAT rate, breakdown by payment method, ticket count, voids, discounts. On its own it is a two-minute formality. Over a year, it is the accounting record that saves you from rebuilding twelve months of figures by hand, and the one your accountant will ask for anyway.

The FEC export takes one click, for any period you pick. Send it to your accountant in January, or to the inspector who asks for it on a Tuesday morning in February. As for the compliance attestation, it downloads from your account settings: print it once, file it, forget it.

One honest caveat. Compliance lives in the software, not in your habits. The tool guarantees an unassailable history and exports in the right format; it will never stop you from taking cash for a table without ringing it up. No publisher can promise that on your behalf, and any publisher who does is lying to you.

Here is the number missing from most articles on the subject: being in order does not necessarily cost you a cent in subscription fees.

The French market spreads across a wide range. At the entry level, certified products around 10 euros a month. In the middle, general-purpose French tills between 25 and 50 euros a month. At the top, full restaurant systems from 75 to 100 euros a month, with kitchen display, reservations and detailed analytics. And at the bottom of the scale, a handful of free products that still hand you the attestation, digabloPos among them.

So the real question is not "what does compliance cost?" but "what am I paying for on top of compliance?". A sixty-cover restaurant running two services a night has good reasons to pay for a kitchen screen and a floor plan. A wine shop, a hair salon or a food truck has none. They end up paying 40 euros a month to tick a box a free product ticks just as well, and over three years that is more than 1,400 euros gone.

Three cost lines hide behind the advertised subscription, and they are the ones that make up the real bill:

- Hardware. A generic thermal printer runs about 100 euros, a decent Android tablet between 200 and 300. Be wary of publishers who impose their proprietary terminal on a monthly rental: you are renting, year after year, a box less capable than the tablet already sitting on your shelf. - Payment commissions. "Free" software that takes 2% of your card takings costs you 4,000 euros a year on 200,000 euros of revenue. The same shop on a 30-euro-a-month subscription pays 360. - Add-on modules. E-invoicing, loyalty, notifications, customer display: turn them on when the need shows up, not on the day you sign.

Count over three years, never over one month. It is the only way to see that a 30-euro-a-month subscription adds up to more than a thousand euros, and to decide with your eyes open whether that thousand euros earns anything back at the counter.

The most common mistake is not running non-compliant software. It is believing you are covered without ever having seen the document. Ask for your attestation today, before you even finish this article. If your publisher takes three weeks to answer, you have learned something useful.

The second: ringing up sales in a spreadsheet or a notes app on the assumption that small volume goes unnoticed. There is no threshold. The text mentions neither revenue nor receipt count, it talks about payment-recording software.

The third: running two tools side by side, the old till at the counter and a new one on the terrace, and leaving the non-compliant one plugged in. Remember that the fine is counted per software.

The fourth: mistaking the September 2026 deadline for a till deadline when it concerns business-to-business invoices. The risk is paying for a platform you have no use for yet while keeping a till that has been outside the law since 2018.

Where to start, concretely. Open your publisher's website and search for the word attestation; if you cannot find it in five minutes, email them. Check that the version installed on your till matches the one on the document. Test the FEC export once, on a random month, to see whether it really comes out and whether your accountant can open it. Print the Z report for a typical day and check that the totals by VAT rate are there. Keep those three pieces of paper together, in the same folder.

If one of the tests fails, switch software, and do it in a quiet week rather than on December 20. Migrating a till fits in one evening: enter the catalogue, set the VAT rates, create the staff codes, print a test receipt. digabloPos is free to start, the attestation is available the moment you open the account, and you can test the FEC export before you ring up your first customer.