Your Food Programme Has a Hidden Cost. It's Not the Food.
GBTA puts a single expense report at $58 and 20 minutes of staff time. A 100-person meal programme can generate thousands of them a year. There's a better way.

When companies calculate the cost of an employee meal programme, they typically add up the obvious figures: the food spend, the delivery fees, and the service charge. These numbers appear on the invoice. They're easy to track.
What rarely appears on any invoice is the cost of processing the expense reports that result from a meal programme that doesn't integrate with your finance system. And in a company running a manual or semi-manual food benefit, that cost is not trivial.

What a manual expense claim actually costs to process
The most-cited benchmark comes from a US study by the GBTA Foundation with HRS, which put the average cost of processing a single expense report at $58 and 20 minutes of staff time, with the 19% of reports containing errors costing a further $52 and 18 minutes to correct. It is a historical US travel-expense benchmark, not a UK meal-claim figure, so the modelling below uses an illustrative £15 per report instead. The cost is made up of:
- The employee's time submitting the claim (form completion, receipt upload, category selection)
- The manager's time reviewing and approving it
- The finance team's time auditing, reconciling, and posting it to the general ledger
- Any exceptions, queries, or resubmissions when the claim is coded incorrectly
For most companies, that cost sits quietly in the background, absorbed by the finance and HR teams as part of their normal workload. It's rarely attributed to the meal programme itself. It should be.
What the numbers look like at scale
Consider a London company with 100 employees on a meal benefit, each ordering an average of 15 meals per month. That's 1,500 meal orders per month.
If each order generates a separate expense claim — which is the default in any food programme that lacks direct finance system integration — that's 1,500 expense claims per month, every month.
At an illustrative £15 per claim to process:
1,500 claims x £15 = £22,500 per month in expense processing costs Annualised: £270,000 per year
Many employees batch a month of receipts into a single report, and that is the like-for-like comparison. On the same £15 per report, 100 batched reports cost £1,500 a month, or £18,000 a year, against £22,500 a month for 1,500 separate reports. How much of the gap a company sees depends on how its employees claim, and a batched report still carries per-receipt checking that this simple model leaves out.
Either way, the cost is invisible on the finance P&L, because it is buried in salary lines rather than attributed to the meal programme that generates it.
On the same basis at an illustrative £8 per report, 1,500 separate reports cost £12,000 a month (£144,000 a year) and 100 batched reports cost £800 a month (£9,600 a year). Either way the cost is real, and either way it is invisible.
Why most meal programmes generate this problem
Many of the food delivery platforms used by London companies were built for consumers, not for corporate finance workflows. They offer a corporate account with a central payment method, but the expense coding, cost centre allocation, and finance system synchronisation are manual — left to the employee to do at checkout (if they remember) and to the finance team to reconcile (if they have time).
When evaluating any platform, ask three things: whether the code is chosen at checkout from a list the employer supplies, whether the order data reaches the finance system as a file or has to be re-keyed, and whether the monthly invoice can be traced to individual orders. Where the answer to any of them is no, the work moves back to employees and the finance team.
The problem compounds when organisations have multiple teams, locations, and cost centres — each with different expense coding requirements. At that point, the reconciliation burden becomes a regular source of friction between the finance team, HR, and the employees they're both trying to serve.

What integration actually eliminates
Ordit is built with enterprise finance workflows as a first-class requirement, not an afterthought. The integration stack is live today:
- Daily SFTP feed syncs expense codes — cost centres, project codes, PO numbers, event descriptions — from Workday or any compatible HR system into Ordit overnight. Employee accounts are automatically updated.
- SAP Concur integration (see the SAP Concur integration guide) pushes itemised order data directly into Concur in the format your finance team has configured. No manual upload. No re-keying. Ready for month-end without any intervention from the employee or the finance team.
- Expense codes at checkout are auto-filled from the SFTP feed. Employees see the correct code pre-selected when they order. Codes can be set as mandatory — no order completes without one.
- One monthly invoice covers all individual orders, group deliveries, and catering events across every team and location, in the format your accounts payable team requires.
Take two employees on the same account in the same month. One orders lunch from Farmer J and picks the project code at checkout; the other orders from itsu and picks a different cost centre. Each order is a separate coded record under the employee who placed it, and both sit on the one employer invoice.
One meal, from kitchen to reconciliation
Ordit's own riders carry each order from the restaurant to the desk, so the company that records the meal for finance is also the one that delivers it. Orders arrive accurate, and the expense code travels with the order record. Every delivery on the account carries Ordit's on-time delivery guarantee. Through the finance-controlled account, employees can order meals delivered in around 30 minutes. See finance operations or book a demo.
The result is that a 100-person meal programme on Ordit generates not 1,500 expense claims per month for employees to submit but a coded order record for each meal. The data flows from Ordit to SAP Concur by daily file, so finance sees the spend already coded and can trace it, step by step, to the monthly invoice when an exception needs review. Nobody submits a receipt.
The broader budget conversation
This matters particularly in the current environment, where HR and Workplace teams are under pressure to demonstrate ROI on employee benefit spending.
The conventional framing of a meal programme ROI is: cost of food programme vs. value of employee retention, attendance, and productivity. That framing is correct, but it's incomplete if it ignores the hidden processing cost embedded in the programme.
When the full cost is calculated — food + delivery + admin processing — a manual meal programme can cost significantly more than it appears on the surface. When the admin cost is removed through integration, the ROI calculation changes materially.
Take an illustrative London company spending £20,000 per month on food for 100 employees. At £15 per report, 1,500 separate reports add £22,500 a month in processing, more than the food bill, while 100 batched reports add £1,500. The size of the hidden cost depends on how claims are made, which is why it is worth measuring before a platform review. The ROI measurement guide shows where this admin baseline fits.
The conversation finance teams aren't having (yet)
Most conversations about employee meal programmes happen in HR or Workplace. Finance is often brought in late, to review the invoice and sign off the spend.
The more useful conversation is one where Finance is at the table from the beginning — not just to approve the budget, but to shape which platform is selected based on how it handles expense coding, finance system integration, and audit trail requirements.
A meal programme that generates 1,500 monthly expense claims is not just an admin burden. It's a compliance risk. Any expense claim that is miscoded, submitted late, or rejected by the approver becomes a reconciliation problem. At volume, these problems compound.
A meal programme with a coded SAP Concur or Workday feed removes much of that risk at the source. The expense code is correct because it came from the HR system, not from an employee guessing their cost centre. The data is in the finance system the next morning, not three weeks later at month-end.
The question worth asking your finance team
Before your next meal programme renewal or platform review, it's worth asking a specific question: how much time does your finance team spend each month reconciling food-related expenses, and what would it cost to eliminate that time entirely?
If the answer involves any manual process — spreadsheet reconciliation, expense report review, Concur upload, or anything that requires a person to touch a food expense claim — the hidden cost is real, and it's quantifiable.
Ordit ships SAP Concur, Workday and SFTP integration as standard on every corporate account, not as an enterprise upgrade. Setup takes one to two weeks including integration testing, and there are no setup fees.
Want to see what a low-admin food programme looks like for your team?
Ordit's team works with Finance, HR, and Procurement to configure integrations, set up expense code automation, and demonstrate the admin cost reduction before any commitment is made.
Ready to feed your team properly?
Join hundreds of London offices already using Ordit for individual meals, group orders, and catering.



