
E-invoices and SAP Concur expense reports: push mode or pull mode?
Since 1 September 2026, every company established in France must be able to receive its invoices electronically, through an approved platform (plateforme agréée). The first thing that comes to mind is regular supplier invoices, the ones handled by accounts payable. But the reform also covers part of your expense reports.
When an employee books a hotel, a train or a rental car and the invoice is issued in the company's name, that invoice falls under the mandate. It no longer arrives only as a PDF in the employee's inbox or as a receipt tucked into a wallet. It is delivered to the company's approved platform, in a structured electronic format.
For companies that manage expenses in SAP Concur, a practical question comes up quickly: how does that invoice get from the approved platform to the employee's expense report?
Push mode: the invoice reaches Concur before the expense is even entered. Pull mode: Concur fetches the invoice when the employee enters the expense. The two combine very well.
Two worlds to connect
Receives the invoices addressed to the company
Those from regular suppliers, and among them the ones that are business expenses: hotels, trains, car rentals.
Manages employee spend
Expense entry, approval and reimbursement.
Employees keep photographing their receipts, accounting has to find the matching e-invoice by hand to secure VAT recovery, and the company ends up with two versions of the same expense.
There are two ways to connect the two worlds: push mode and pull mode.
Two ways to connect the approved platform to SAP Concur
The invoice comes to the employee
Starting point: the approved platform
- 1Approved platform
An invoice addressed to the company arrives (hotel, train, car rental…).
- 2EVA Connect
Triage: is it an employee expense? If so, whose?
- 3SAP Concur
The expense lands in the employee’s space, with the PDF and the e-invoice file.
- 4Employee
They attach the expense that is already there to their report.
Concur asks for the invoice
Starting point: the expense report
- 1Employee
They enter the expense in SAP Concur, as they do today.
- 2SAP Concur
Concur requests the matching e-invoice.
- 3EVA Connect
Search on the approved platform (supplier, invoice number…).
- 4SAP Concur
The invoice is attached to the expense, or Concur is told there is none.
Push mode: the invoice comes to the employee
In this mode, everything starts on the approved platform. As soon as a new invoice arrives, it is analysed: is it an employee expense, and whose? If so, the invoice is sent straight to SAP Concur, into the employee's space, with the readable PDF and the electronic file that has legal value.
When the employee prepares their expense report, the expense is already there. All they have to do is attach it.
Push mode at a glance
- Employees have almost nothing to type or photograph.
- The e-invoice, which is the legal supporting document, travels with the expense from the start.
- Expenses flow in continuously, without anyone having to ask for them.
- You need to know who each invoice belongs to: the traveller's name, the booking reference or company-specific rules identify the right employee, and some cases will remain ambiguous.
- Not every invoice received is an employee expense: reliable triage is essential so that an accounts-payable invoice never lands in Concur.
Pull mode: Concur asks for the invoice
Here, the starting point is the expense report. The employee enters the expense in SAP Concur exactly as they do today. Concur then requests the matching e-invoice. It is looked up on the approved platform using the expense details, such as the supplier and the invoice number, and sent back to Concur, which attaches it to the expense.
If no invoice matches, Concur is notified and the expense follows the usual rules.
Pull mode at a glance
- Only expenses that were actually entered are processed: no upfront triage, no doubt about the recipient.
- The employee journey does not change, which makes adoption easier.
- Expense and e-invoice are matched when it matters, before approval.
- The invoice must already be on the platform when the employee enters the expense: if the supplier issues it late, it will not be found right away.
- Pull mode relies on a feature that SAP Concur has to enable for your company: plan for it in the project timeline.
How to choose
The two modes are not mutually exclusive, and many companies will use both. Four questions help decide where to start.
Which expenses are involved?
If most of your spend goes through a few large suppliers (travel agency, hotel chains, rail) whose invoices clearly identify the traveller, push will work very well. If spend is more scattered, pull is often the safer choice.
What do you want to change for them?
Push saves them time but changes how they work: the expense waits for them instead of being created by them. Pull keeps their habits.
Who does what?
Push requires defining triage and assignment rules and monitoring them. Pull mainly requires that what employees enter is reliable enough to find the invoice.
Where do they stand?
During the transition, not all of them issue e-invoices yet, especially the smallest ones. You will have to keep handling traditional receipts in parallel anyway.
Every company must be able to receive e-invoices; large and mid-sized companies must also issue them.
SMEs and micro-businesses must issue e-invoices too. Until then, some of your suppliers will still send traditional receipts.
Key takeaways
The French e-invoicing reform changes the nature of the supporting document for many expense reports. For SAP Concur customers, the goal is to get the right e-invoice onto the right expense, without adding work for employees or for accounting.
Push mode bets on upstream automation: the invoice arrives before the expense. Pull mode bets on precision: the invoice is looked up when the expense is entered. The right balance depends on your spend, your suppliers and your organisation.
Decide on the mode (or the mix of both) with finance, IT and your Concur administrator in the room: each of them owns part of the prerequisites.
At Tevasoft, we built EVA Connect to connect approved platforms to SAP Concur in both modes. If you are weighing the question for your company, let's talk.
