Finance has never been more automated. And yet, in many businesses, it still feels strangely manual.

Invoices arrive, approvals happen, data is entered, reports are produced—and somewhere along the way, the same work is repeated, the same information is handled twice, and the same mistakes creep in again and again.

Automation promised to simplify this. In reality, it often formalised inefficiency.

Thinking like a CFO means understanding why.

Start With Something Basic: How Invoices Actually Enter the System

Let’s take a simple, old-fashioned example: a restaurant.

Invoices arrive with deliveries—on paper.
The manager looks at them to check the stock, prices etc,
They approve them manually. Or he may have a dedicated Restaurant Management System separate from the accounting system

Then, somehow, those same invoices need to get into the accounting system.

So the process is duplicated:

• Once for running the business (checking stock, approving spend)
• Once for accounting (entering, coding, reconciling)

Automation often starts after this duplication already exists. It speeds up data entry, but it doesn’t remove the double handling.

The core question is never asked:

Why are there two processes instead of one?

Digital Didn’t Eliminate Duplication — It Just Hid It

Now fast-forward to a more “modern” version of the same restaurant.

Invoices arrive by email or PDF.
The manager opens them on their phone or email
They click “approve”.

That feels automated.

But then:

• Someone still has to make sure the invoice is in the accounting system
• The same invoice is reviewed again for coding
• The same approval logic is implicitly repeated

The interface changed.
The duplication didn’t.

Automation made the process look cleaner—but it didn’t make it coherent.

Again, the core question is never asked:

Why are there two processes instead of one?

Disparate Systems: Where Automation Really Breaks Down

As businesses grow, the problem compounds.

More advanced organisations often have:

• An operating system for the business (procurement, inventory, operations)
• A separate accounting system
• Sometimes a third tool for approvals
• Sometimes a fourth tool for invoices “on the go”
• Another process or solution for Payments

Invoices flow into:

• The operating system (to run the business)
• Then have to be pushed or pulled into accounting
• Then spread across AP, reporting, and cash flow

Each handoff introduces:

• Delay
• Duplication
• Assumptions
• Gaps

Automation doesn’t remove these handoffs. It just moves them faster.

I will address in a separate post the challenges and costs of payment tools – solutions like Bill.com , Bill com , Melio, Corpay or Tiplatti for enterprises

Incoming, Outgoing, and Everything In Between

Now add complexity:

• Incoming supplier invoices
• Outgoing customer invoices
• Credit notes
• Recharges
• Expense claims

Each has its own “tool”:

• AP platforms
• Expense apps
• Invoice portals
• Payment tools

Each tool claims to automate finance.

But the real question is:

Is this actually linked to the accounting system—or just adjacent to it?

If approvals happen in one place, invoices live in another, and accounting happens somewhere else, automation becomes a collection of fast silos.

And Then There’s Excel

Despite everything, Excel is still everywhere.

Why?

Because Excel is where:

• Gaps are patched
• Exceptions are tracked
• Reality is reconciled
• “Just this once” becomes permanent

Excel is not the problem.
It’s the symptom.

It exists because automated systems don’t talk to each other in a way that matches how the business actually operates.

Why Automation Alone Was Never Enough

Automation assumes that if you:

• Speed up data capture
• Standardise workflows
• Enforce steps

…you will naturally get better outcomes.

But finance doesn’t fail because it’s slow.
It fails because workflows don’t reflect real daily behaviour.

If:

• Managers approve in one system
• Finance posts in another
• Exceptions live in spreadsheets
• Memory lives in people’s heads

Then automation simply locks in fragmentation.

Discipline Is the Missing Layer

This is where thinking like a CFO matters.

CFOs don’t ask:

• “Is this automated?”

They ask:

• “Is this the same process, end to end?”
• “Does approval actually mean accounting is done?”
• “Do we touch this once—or twice?”
• “If this breaks, will we know tomorrow—or next month?”

Automation without disciplined daily workflows just creates faster noise.

Why This Keeps Resetting Every Month

At month-end:

• Finance pulls everything together
• Fixes gaps
• Explains variances
• Chases missing documents

Then the month closes.

And the system forgets.

The same invoice paths.
The same duplications.
The same manual patches.

Automation helped finance survive month-end.
It didn’t help finance learn from it.

What Actually Needs to Change

The fix is not “more tools”.

It is:

• One coherent workflow from approval to accounting
• Clear ownership of how invoices enter the system
• Daily discipline, not monthly heroics
• Automation that supports how the business runs, not how software is sold

AI and automation only work when they sit on top of clean, intentional workflows.

Otherwise, they just accelerate bad habits.

A CFO Reframe

Automation didn’t fix finance because it tried to optimise steps instead of joining them.

It made finance faster, but not simpler.
More digital, but not more coherent.
More impressive, but not more reliable.

Thinking like a CFO means designing finance as one continuous process—not a collection of tools that reconcile with each other once a month.

How This Works in Your Business

If you want to understand where duplication, handoffs, and fragmented workflows are quietly undermining your finance function—and how AI accounting automation can support one disciplined, end-to-end process—schedule a strategy call with Persofi.

Visit www.persofi.com to start the conversation.

Further reading – SME vs. Mid-Market Reality

How This Shows Up in SMEs

In small and owner-managed businesses, the problem is not lack of automation—it’s overlapping roles.

• The same person:
  • Approves invoices
  • Checks stock
  • Enters data
  • Reviews cash
• Invoices arrive by:
  • Email
  • WhatsApp
  • Paper
  • Supplier portals

Automation often adds:

• An invoice capture tool
• An expense app
• A payment platform

But the workflow remains fragmented:

• Approval happens informally
• Accounting happens later
• Exceptions are remembered, not recorded

The result:

The business feels “on top of things” daily,
but finance resets every month.

How This Shows Up in Mid-Market Businesses

In larger, more sophisticated businesses, the problem flips.

There are:

• Procurement systems
• Operational platforms
• Approval workflows
• Accounting systems
• Reporting layers

Invoices:

• Enter the operating system first
• Then need to be pushed into accounting
• Then reconciled across entities, departments, and periods

Each system works well in isolation.
The failure happens between systems.

Automation speeds up:

• Handoffs
• Interfaces
• Reconciliations

But it does not remove:

• Duplication of review
• Re-approval
• Re-interpretation
• Re-explanation

Month-end becomes the point where all systems finally meet—and argue.