You Didn't Automate Your Expense Process. You Gave Your Chaos a Company Car.

The boldest thing a business can do, apparently, is take a process that has never once worked correctly, and make it run at the speed of light. No fixing. No honest conversation. Just velocity. Congratulations — you now have a very fast disaster with a dashboard.

This is the quiet religion of enterprise technology: the belief that software, applied with sufficient budget and a vendor who maintains eye contact during the demo, will impose order on human messiness. Expense reporting has become its most devoted congregation.

The Process Is Not the Problem

Here is what actually happens. A company has a manual expense process that nobody would defend under oath. Receipts arrive in formats that suggest the submitter was raised by wolves. Approvals are applied with the consistency of a weather forecast. One manager waves through a four-hundred-pound team dinner because she trusts her people. Another treats a twelve-pound taxi receipt like evidence in a parliamentary inquiry, because he once read something about fraud risk and never fully recovered.

Nobody can articulate the actual policy. The actual policy lives in the institutional memory of three people who joined the company when the building still had a fax machine, and they are, statistically speaking, eighteen months from a leaving card and a supermarket cake.

Then someone goes to a conference, or a new CFO arrives with a mandate, or procurement gets that particular look in their eye. The conclusion is unanimous: we must automate.

And so they do. They automate every single broken thing, faithfully, efficiently, and at remarkable scale.

The Self-Checkout Problem

Picture this. You are standing at a supermarket self-checkout with a leaking bottle of fabric softener you need to return. The machine was built to handle a clean, linear transaction — scan, pay, leave. It was not built for your situation. You press "need assistance." The machine announces your need for assistance to the entire store. You wait. A staff member arrives, sighs with the weight of someone who has had this exact conversation forty times today, overrides the system with a code only she knows, and processes the return manually — the same way it would have been done before the machine existed, just slower, more formally, and with considerably more dignity stripped from everyone involved.

This is enterprise expense automation without standardised approval rules. The machine was built to process what was already agreed. When agreement was never actually reached — when the rules were reconstructed from interviews with three people who gave three incompatible accounts — the machine is simply enforcing confident fiction at scale. The exception queue fills immediately. The finance team, who were promised liberation, are now triaging tickets with the hollow eyes of people who understood the brochure differently.

Automation did not remove the need for human judgment. It just made human judgment slower, more formal, and considerably more exhausting to access.

The Category Error Nobody Puts in the Vendor Deck

I have, with genuine enthusiasm and negligible wisdom, pressed the shiny button before understanding what it was connected to. There is something seductive about the idea that a problem which has irritated an entire organisation for three years can be resolved by a workflow engine with a go-live date. It feels like progress. It has a slide. It can go in the board report.

What cannot go in the board report, in the months that follow, is the quiet erosion of trust from the people who use the system every day and are now engineering workarounds with the creativity of people who have simply given up expecting things to make sense. They learn which category codes sail past the bot. They discover that mileage submitted under a different label moves cleanly through the system. The automation has not reduced human ingenuity. It has redirected it entirely toward gaming a machine rather than doing actual work.

The root problem is a category error. Leaders treat expense reporting as a process efficiency problem. It is not. It is a trust and judgment problem wearing a process costume. The inconsistency in approvals — the thing that makes the manual process so maddening — is not a technical failure. It is the visible symptom of an organisation that has never had an honest conversation about what it actually values. Does it trust its managers to exercise discretion? Does it trust its employees not to abuse flexibility? If the answers are yes, you need a clear, human-readable policy and managers who understand it. If the answer to either is no, you have a culture problem, and no workflow engine in the world fixes a culture problem. It will merely automate the distrust, quantify it in a weekly digest, and send you a formatted report on how systematically you are failing to believe in your own people.

The Offensively Obvious Sequence

The companies that genuinely solve this follow a sequence that feels almost embarrassingly straightforward in retrospect. Before touching a single piece of software, they have the argument. The real one. About what is actually allowed. About why some managers approve everything and some approve nothing, and which of those behaviours the organisation wants to endorse going forward. They write a policy that can be explained to a new joiner in four minutes. They test it against real, recent, chaotic expense submissions. They find where it breaks, and they fix the policy, not the submission. They get commitment from the people who will be held accountable for enforcing it.

Then — only then — they automate.

At that point, the automation is almost incidental. Because what has been built is clarity. The software is the mechanism for applying that clarity consistently at scale. The hard work was the conversation nobody wanted to have.

There is no go-live date for "we finally agreed on our expense policy." It does not get applause at the all-hands. But it is the single thing that makes everything else worth having.

Without it, the expense problem has not been solved. It has been given a faster internet connection and told to get on with it.