Why the most expensive sentence in finance operations is "that's just how we've always done it" — and the three kinds of hidden waste it protects.

By Vaibhav Rane, Founder, Cresolv One

There's a sentence I've heard in almost every finance team I've ever worked with. It comes up halfway through a process review, usually with a shrug, usually about a step that makes no sense:

"That's just how we've always done it."

It sounds harmless. It's one of the most expensive sentences in business.

In over 20 years across technology risk, revenue assurance and consulting, I've learned that the costliest problems in finance operations are rarely dramatic. There's no fraud, no system crash, no headline. The cost is quiet — a little bit of wasted effort, repeated thousands of times, by people too busy to question why the step exists at all.

The workaround becomes the process. The process becomes the habit. And the habit becomes invisible.

Why "always done it this way" survives

Manual steps don't survive because they're useful. They survive because they're invisible.

When something is done the same way every day, it stops being a decision and becomes background noise. Nobody re-evaluates it, because nobody sees it anymore. It's just part of the furniture.

And there's usually a reasonable origin story. The double data entry started because two systems didn't talk to each other — five years and one ERP upgrade ago. The extra approval was added after one bad incident — by a manager who left long ago. The spreadsheet reconciliation was a clever fix at the time. None of it was stupid. It was just never revisited.

That's the trap. Every manual step was once a sensible response to a real problem. The problem is that the step outlives the problem.

The three kinds of waste hiding in plain sight

When I review a finance operation, the same three patterns show up almost every time.

1. Re-entry. The same data, keyed more than once. An invoice typed into one system, then re-typed into the ERP. A figure copied from an email into a spreadsheet, then into a report. Every re-entry is pure cost — no judgment is added, only time spent and a fresh chance to make an error. If your best people are retyping data a machine already captured, you're paying salary for a job a robot should do.

2. Redundant approvals. Sign-offs that add a signature but no decision. Ask honestly: when was the last time this approver actually said no? If the answer is "never," the approval isn't a control — it's a delay wearing a control's uniform. Real controls catch something. Ceremonial ones just slow the work and give a false sense of safety.

3. Reconciliation that exists only because systems don't talk. This is the big one. A huge amount of finance effort is spent making two systems agree — manually bridging a gap that only exists because the systems were never connected. That reconciliation feels like real work. It produces no value. It's a tax you pay for a missing integration.

None of these show up as a line item. There's no "manual workaround" account in your P&L. The cost is buried in headcount, in slow cycle times, in errors caught late, in month-ends that run long. Invisible — which is exactly why it persists.

How to find your own

You don't need a consultant to start. You need one honest question, asked about one process this week:

Which steps here add value, and which are just habit?

Walk a single process end to end — say, how an invoice goes from arrival to payment. For each step, ask:

• Does this add judgment, or just movement? Moving data from A to B isn't value. Deciding something is.
• What would break if we stopped doing this? If the honest answer is "nothing," you've found waste.
• Why does this step exist? If the answer is "because the system can't…" you've found an integration gap, not a necessary task.

Most teams are surprised. A process they assumed was lean turns out to be half habit.

Remove first. Then automate.

Here's the part most automation projects get wrong, and it's worth saying plainly: the goal isn't to automate the manual work. It's to question whether the work should exist at all — and automate only what's left.

Automating a useless step just makes you do something pointless faster. The order matters:

1. Remove the steps that add nothing.
2. Connect the systems that should have been talking all along, so the reconciliation disappears instead of getting automated.
3. Automate what genuinely remains — the routine, high-volume work that does need to happen but doesn't need a human.

What's left for your people is the part that actually needs judgment: the exceptions, the decisions, the relationships. That's not a smaller job. It's a better one.

The real shift

Everything I've built Cresolv One to do comes back to a single idea: visibility beats effort.

Almost every operational problem I've seen wasn't caused by a team not working hard enough. It was caused by work, money and risk moving through gaps no one could see. "We've always done it this way" is what those invisible gaps sound like out loud.

When you make the work visible — when you can finally see every invoice's status, every approval's purpose, every place two numbers should match — the waste stops being background noise. It becomes a list you can fix.

So this week, pick one process. Ask the uncomfortable question. You'll find a step that's there for no reason anyone can remember.

That's not a failure. That's the opportunity.

Cresolv One helps enterprises remove manual work from finance, audit, documents and supply chain — automation that connects to your existing ERP, built by people who've run these functions. If you'd like to see where your own processes are leaking effort, start with our Readiness Assessment — six questions, a maturity score, and a free playbook matched to your biggest gap.