SAP Concur and Corporate Food Delivery: How to Automate Employee Meal Expenses
Ordit exchanges coded meal data with SAP Concur by daily SFTP file: expense codes in, order records out, one monthly invoice for finance.

SAP Concur is the enterprise expense management platform used by thousands of large organisations globally. It's designed to eliminate manual expense processing — to automate the flow of expense data from the point of transaction to the general ledger without requiring human intervention at each step.
The irony is that for most companies running employee meal programmes, food expenses are precisely the category that breaks this automation. They come in through consumer delivery apps, personal cards, or manual reimbursement flows. They generate individual expense claims that have to be submitted, reviewed, approved, and coded — each one a unit of manual work that Concur was built to eliminate but that the food programme keeps creating.
Ordit closes that gap by integrating with SAP Concur via daily SFTP, so meal orders arrive in Concur already coded, with no claim for the employee to submit. It is included as standard on every corporate account.

How the integration works
The Ordit-SAP Concur integration operates in three layers:
Layer 1: Expense code sync (SFTP to Ordit)
Ordit's Admin Portal connects to your SAP Concur or Workday instance via a daily SFTP feed. Each night, Ordit pulls the current expense code structure — cost centres, project codes, PO numbers, event descriptions, or any custom code scheme your firm uses — and loads them into employee accounts.
The result: when an employee opens the Ordit app to place an order, the expense codes that apply to them are already loaded at checkout. They pick from the list rather than recalling a code. No guessing cost centres. No errors from employees entering codes they've half-remembered.
Codes can be configured as mandatory — no order completes without a confirmed expense code — making compliance automatic rather than a matter of enforcement.
Layer 2: Order data push (Ordit to SAP Concur via SFTP)
Each order placed on Ordit generates a transaction record: employee name, order date, restaurant, itemised receipt, amount, expense code, and location. Each morning, Ordit pushes the previous day's transaction data to your SAP Concur instance via SFTP, in the exact format your Concur configuration requires.
This data arrives in Concur already coded — because the expense code was captured at checkout, not after the fact. It's ready for the approval workflow your finance team has configured. It doesn't need to be re-keyed, because the code was validated at the point of entry against the list your Concur configuration supplies.
Two illustrative records show the shape, with fictional cost-centre labels and no prices. In the first, an employee orders lunch from atis and the record carries the cost centre "Lunch Operations" with the restaurant name. In the second, a colleague orders an evening meal from Coqfighter Soho and the record carries the code "Project Dinner"; the overtime guide shows how such evening rules work. How corrections, refunds and duplicate files are handled is something to agree with the integration team during setup.
From restaurant order to expense record
Ordit's own riders deliver the order that the expense record describes, so the company that codes the meal for finance is also the one that carries it. Meals arrive accurate, and finance can match the restaurant and code to the order if a colleague queries a delivery. Each Ordit delivery is covered by its on-time delivery guarantee. On the same coded account, employees can order meals delivered in around 30 minutes. Explore integrations or book a demo.
Layer 3: Consolidated invoicing
All Ordit transactions across all employees, teams, and locations are consolidated into a single monthly invoice, issued on the 1st of the following month with 30-day payment terms. The invoice is formatted to your accounts payable requirements — or can be delivered directly into a Coupa P2P workflow if that's how your procurement team operates.
What this eliminates
The manual process that Ordit replaces typically looks like this in organisations without integration:
- Employee orders food using a personal card or a corporate card without an expense workflow
- Employee submits an expense claim at the end of the week or month
- Employee selects an expense category, enters a cost centre, and attaches a receipt (if they still have it)
- Manager reviews and approves
- Finance team audits the coding, queries any mismatches, and re-codes where needed
- Transaction posts to the general ledger
- At month-end, someone reconciles food expenses against budgets by team and location
Take a company with 100 employees who each order 15 meals a month: 1,500 orders. In the separate-report scenario, every order becomes its own claim, so 1,500 expense claims a month pass through the employee, a manager and finance. At an illustrative £15 per claim (the GBTA/HRS benchmark, a historical US figure, puts a single expense report at $58 and 20 minutes of staff time), that is £22,500 a month in admin overhead, or £270,000 a year. In the batched scenario, each employee puts a month of receipts into one report: 100 reports a month at the same £15 cost £1,500 a month, or £18,000 a year, before the per-receipt checking inside each report. Coded orders remove the claims in either scenario, while finance still handles the exceptions, such as a disputed order or a wrong cost centre. The full cost model is here.
With Ordit's SAP Concur integration, step 1 still happens (employee orders food). Steps 2 through 7 do not. The record is in Concur the next morning, already coded, and the monthly invoice follows. Finance still reconciles the two, but nobody submitted a claim.
What the setup looks like
Integrating Ordit with SAP Concur does not require a significant IT project. The setup process for the SFTP integration typically takes one to two weeks, including configuration, testing, and validation.
The Ordit technical team handles the integration setup directly. The information required from your IT or Finance team:
- SFTP server credentials and file path
- The expense code file format (CSV structure, field names, encoding)
- Concur instance details for the receiving end
- Confirmation of which employee fields should drive code assignments (team, location, job level, or custom)
Ordit's team configures the connection, runs test transfers with sample data, validates the received records in your Concur test environment, and confirms accuracy across the whole chain before going live. Most clients see their first live SFTP transfer within five working days of providing credentials.
There are no setup fees, no integration consulting charges, and no minimum volume requirements to access the SAP Concur integration. It is included as standard for all corporate accounts.

The Workday variation
The same integration architecture applies to Workday. Ordit supports Workday both as a source of employee and expense code data (pulling the current organisational structure nightly via SFTP) and as a destination for expense data (pushing transaction records into Workday's expense module daily).
For companies that use Workday as their HR system and SAP Concur as their expense platform, a common combination in financial services and professional services (the guide for London banks and fintechs covers cost and deal codes at City firms), Ordit can connect to both simultaneously: pulling from Workday for employee data and expense codes, and pushing to Concur for expense recording.
What good looks like at month-end
For a Finance Director using SAP Concur, the ideal month-end state for food expenses is:
- All transactions coded correctly at the point of ordering
- No individual expense claims to review or approve
- One invoice in AP covering all food spend for the month
- Concur records ready to reconcile against the invoice
- Budget vs. actual visible in the Admin Portal by team and location, updated in real time (see finance operations)
This is what Ordit delivers. It's not a theoretical state — it's the current experience for financial services, technology, and professional services clients in London who have the SFTP integration live.
Starting the technical conversation
Ordit's enterprise team works with Finance, IT, and Procurement to scope and deliver the SAP Concur integration. The setup conversation typically takes 30 minutes and results in a clear integration plan with a confirmed go-live date.
Ready to feed your team properly?
Join hundreds of London offices already using Ordit for individual meals, group orders, and catering.



