E-reporting: the case of POS and cash register software
60 POS software, almost none concerned by e-reporting. Why cash register editors are at the heart of the 2026 French fiscal reform, not on the periphery ?
E-reporting: the case of POS and cash register software
In October and November 2024, Philip Schneider from Chift was working daily with 60 cash register software companies. Almost none of them felt concerned by e-reporting.
A few months later, the questions are flooding in.
This is no coincidence. It signals that awareness is accelerating. But between knowing the topic exists and being ready by September 1st, 2026, there is a gap that many POS editors have not yet measured.
The figure that puts things in perspective
Everyone talks about e-invoicing. The reform, the formats, the Approved Platforms. Rightly so: 2 billion B2B invoices per year are affected.
But e-reporting covers 20 billion B2C transactions. Ten times more.
Cash register software, POS systems, payment solutions: you are the ones who will process this volume. You are the ones who will need to ensure that this data is transmitted to the DGFiP on time. Not your client. Not their accountant.
The concrete case
Take a craftsman. His accountant has been handling everything for years: he receives his B2B invoices, general expenses, suppliers. On the e-invoicing side, it's sorted.
But his cash register lives its own life. B2C tickets, card payments, cash: none of these flows are transmitted automatically. From September 2026, this merchant will be 50% compliant. Half of his tax obligations will not be covered.
The problem does not come from him. The issue will potentially come from the cash register software that has not made the necessary integrations to push at minimum the mandatory data.
The mistake everyone makes
"We're looking for an Approved Platform to become compliant."
This is the phrase we hear most often. And it reveals a fundamental confusion: the Approved Platform expects structured data. If the cash register software does not provide this data in the right format, the entire chain breaks down. Delegating compliance to an Approved Platform does not exempt the editor from doing their work upstream.
What the editor must do upstream
Three fundamental principles, sourced from the reform specifications:
1. Collect each transaction individually. Each sale and each payment must be captured separately. Do not group too early: you will lose the granularity needed to produce clean corrective flows.
2. Qualify regulatorily. Identify the type of operation, the declarant's role, and the VAT regime of the end client. This parameter determines the transmission frequency.
3. Aggregate at the right time. Only at the point of transmission, not before. Premature aggregation is the leading cause of PPF rejections.
What Chift and Iopole solve
Once the data is correctly structured by the cash register software, Chift connects to the cash register and processes the data into the right format. Iopole transmits the flows to the DGFiP and manages all regulatory complexity: VAT periods, aggregation, corrective flows, PPF declaration.
As Philip Schneider puts it:
"Don't worry about the whole reform. You're already out of your certification. Trust us, we'll guide you through it."
Go further
📖 Our complete e-reporting guide
🔗 A question about your integration? Contact us!
