Most expense tools assume the person who spent the money will install an app, photograph the receipt inside it, and choose the GL code. Only one of those three steps genuinely requires the employee. The photograph is the part nobody else can do. The coding is the part finance will redo anyway. Designing the workflow around that reality, rather than around app adoption, is what actually gets receipts in on time.
A finance lead at a wholesale distributor had already shopped expense tools twice and come away with the same result both times: low adoption from field staff, and a coding cleanup job for AP every month. Their story is below. It matters most if your spenders work in warehouses, vehicles or job sites rather than at desks, if receipts routinely arrive weeks after the card transaction, or if finance already corrects most employee coded expenses before posting.
Two failures, in sequence
The distributor’s pattern was consistent across both tools they had tried. Open an app, take the picture inside the app, then sit there and categorise the spend.
Their employees were not going to do that. Many were not especially comfortable with new software and had no interest in becoming so. When someone did make the effort and coded the receipt, the codes came back wrong, and finance corrected them anyway.
So the promise that employees would self serve their expenses turned into a second job for accounts payable: chase the photo, then rewrite the coding.
That is two distinct failures arriving in order. The first is adoption. Field staff, warehouse teams and mixed age workforces will text a photo to someone. They will not maintain another login, another icon on their home screen and another interface they use twice a month.
The second is quality, and it only appears once adoption is solved. Even when the photo arrives, GL and tax decisions made by the person who bought the coffee are frequently wrong. Finance owns the chart of accounts. Pushing coding to the edge of the organisation does not remove that work, it just relocates the cleanup to a later date.
The corporate card version is the same story in a different order. The statement line is already in the system. The receipt is still in somebody’s jacket pocket, and someone in finance is sending the fourth follow up email.
What an expense report actually costs
The most widely cited figure comes from the GBTA Foundation’s study on expense reporting practices, which put the average cost of processing a single expense report at $58 and the time at around 20 minutes. It also found that roughly 19 percent of reports contain errors or missing information, each taking a further 18 minutes and about $52 to correct.
Two caveats worth stating plainly, because most articles quoting these numbers do not. The study is now over a decade old, and the dollar figures are American. Treat them as a sense of proportion rather than a precise benchmark for a Canadian mid market team in 2026.
Even discounted, the shape of the finding holds up. Correction is the expensive half. A company processing 500 reports a month is reworking roughly 95 of them, and that rework is pure overhead created by the original capture design. Whatever the true figure is for your team, the ratio between doing it once and doing it twice is the number that matters.
What we built, and why the coding stays with finance
The company gets a dedicated number. The employee texts a photo of the receipt. That is the entire employee workflow. No app, no login, no category picker.
Finance owns coding. GL, tax, entity and policy checks stay with the people who will post the entry and answer for it later. Email forwarding exists for people who live in their inbox instead. Lost receipt declarations sit beside the same process for when the paper is genuinely gone. When the spend was on a corporate card, the receipt meets the transaction later rather than being chased separately.
The design decision is simply this: using our software should not be the price of getting a receipt into AP. Capture belongs in whatever channel people already use without thinking. Accounting belongs where accounting already happens.
That split only works because expenses run on the same engine as vendor invoices. Finofo brings accounts payable, expense management and purchasing together on one AI native platform, built in Calgary, so a texted restaurant receipt gets the same line level extraction, the same Canadian tax handling and the same approval routing as a supplier bill. Finance codes it in the interface they already use for AP, not in a second system with a second set of rules. It is the only Canadian built platform that works this way, and it is why "text a photo" is a complete workflow rather than a front door to more admin.
This is not the same as supporting SMS
Plenty of tools accept a text message. That is a pipe, and it is not the interesting part.
The question is what happens after the photo arrives. If the text drops the employee into an app to finish categorising, all that changed is which button they press first. If finance still re-keys every category afterwards, none of the rework has gone anywhere. The distinction is whether the workflow expects the spender to touch the chart of accounts at all.
Questions worth asking any expense vendor
It works this way because Finofo was built AI native from the first line of code rather than adapted from older software, and built in Canada for Canadian tax, entities and ERPs. Accounts payable, expense management and purchasing share one engine, so a rule written once holds across every way money leaves the business.
What stays with your team
Finofo is designed so that the people who own the accounting stay in control of it, and so that nothing about the rollout forces a change the business did not choose.
Policy stays with finance. Spend that breaks the rules, alcohol restrictions, and receipts missing merchant detail are surfaced sooner because capture is easier, and they are decided by your team with the lost receipt path and approvals built in. The software gets the document to the right person quickly. The person decides.
The cards stay with you. Finofo works with the corporate cards and bank the business already uses, so receipt capture is never a reason to switch issuers or give up a rebate program. If you want a particular card for banking or credit reasons, keep it.
And accountability stays with managers. The channel is easier, which removes the excuse. Making sure people use it is still a leadership job, and Finofo gives managers the visibility to do it: what is outstanding, from whom, and for how long.
Start from who will actually do the work
If your evaluation checklist asks whether employees can submit from mobile, the more useful next question is who is supposed to code it, and what happens when they get it wrong.
For most Canadian mid market finance teams, the honest answer to the first half is finance. Build the capture path for that reality. Let people text a photo, and keep the accounting with the accountants.
Frequently asked questions
Why do employees avoid expense apps?
Friction and frequency. An app used twice a month never becomes a habit, and it competes with a phone already full of software. Field, warehouse and trade based teams in particular will use a channel they already use daily, which is usually messaging, and will not maintain a separate login for occasional admin. Finofo meets them there: a texted photo is the whole submission.
Should employees code their own expenses?
Usually not. The person who made the purchase rarely knows the chart of accounts, and finance ends up reviewing the coding regardless. Finofo drafts the coding automatically and finance reviews it in the same interface used for vendor invoices, so it is done once by the people who own the ledger.
How much does processing an expense report cost?
The GBTA Foundation study most often quoted puts it at around $58 per report and 20 minutes, with about 19 percent of reports needing correction at a further $52 and 18 minutes each. Those figures are American and over a decade old, so use them for proportion rather than precision, and measure your own rework rate if you want a real number. The lever Finofo pulls is the correction half: capture is one step for the employee, and coding happens once, reviewed by finance.
About Finofo
Finofo is the AI native platform built in Calgary for Canadian finance teams. It brings accounts payable, expense management and purchasing onto one engine, on the cards, bank and ERP a business already uses, with line level extraction, Canadian tax handling and approval workflows designed for multi entity, multi province operations. Finofo does the verification. Finance keeps the judgment.
