SAP Concur and 2026 e-invoicing: what stays invisible in your expense reports
September 1 has passed — and the question has changed
Since September 1, 2026, every company established in France must be able to receive a compliant e-invoice. The switch happened without much drama: large companies and mid-caps already issue through their certified platform (Plateforme Agréée), everyone else receives. On paper, the obligation is met.
But for teams running their expense reports on SAP Concur, a quieter question now comes up: what actually changed in expense control, beyond document compliance?
What e-invoicing compliance solves — and what it doesn't
A compliant e-invoice proves a document follows a regulatory format (Factur-X, UBL, CII) and passed through a certified platform. It proves nothing else.
| What e-invoicing compliance solves | What still needs auditing in Concur |
|---|---|
| The document format is valid | The amount actually matches the expense incurred |
| The invoice passed through a certified platform | The same invoice doesn't appear twice on two different reports |
| Legal mentions (SIRET, VAT) are present | The expense is consistent with travel policy |
| The structured data is usable for accounting | The receipt wasn't artificially generated or altered |
The real gap: two flows that don't reconcile on their own
On SAP Concur, the e-invoice received through your certified platform and the expense line entered by the employee remain, by default, two separate flows. One arrives on the accounts-payable side, the other comes up from the field. Nothing connects them automatically.
An employee traveling books a hotel, attaches a photo of the receipt to their Concur report, and gets reimbursed. A few days later, the corresponding e-invoice arrives separately, through the certified platform, tagged with the company's SIRET. Without reconciliation, nobody checks that both documents match the same expense — or that VAT was recovered on the right document.
The special case of SAP DRC
One clarification matters here: companies already running SAP DRC (Document and Reporting Compliance) have a native answer to this invoice/expense reconciliation, built into the SAP ecosystem. CONNECT doesn't replace SAP DRC where it's deployed — it addresses the same need for organizations that don't have it, or that go through a third-party certified platform not natively connected to that ecosystem.
What CONNECT adds to SAP Concur
CONNECT sits between your certified platform (or your SAP DRC) and SAP Concur to automatically reconcile the official e-invoice with the matching expense line.
CONNECT keeps pace, country by country
France switched over on September 1, 2026. Poland has run its KSeF system since February 2026. Italy has its own (SdI). The EU's ViDA directive is reshaping the rules across the continent, on different timelines by country, and the coming years will bring new mandates one after another.
CONNECT is built to track this regulation by regulation, country by country, without your SAP Concur deployment having to change. When a new obligation kicks in or a format evolves, CONNECT adapts — not your teams.
A document that follows the regulatory format is not proof that an expense is legitimate, or that it hasn't already been reimbursed in another form. That's the role of content audit, not document compliance.
Read more: expense over €150: why an electronic invoice becomes mandatory and TEVASOFT and SAP Concur: the intelligent audit your expense management was missing.
Want to see how CONNECT reconciles a real e-invoice with a Concur expense report? Contact us.
See also: to export SAP Concur receipts in bulk or according to your criteria, discover Smart Extract for SAP Concur (SAP Concur receipt export to Excel, CSV, JSON or Power BI).
See also: Connect your approved platform to SAP Concur: reconcile e-invoices and expense reports.