Case 04 · Finance

Month-end close went from a week and a half to a couple of days.

A growing software company whose finance team was maturing fast.

Outcome · days, not weeks
  • Invoices
  • Approvals
  • Audit-ready
  • Always on
Scroll

The issue

Where it hurt.

Their accounts team was three people, none of whom had been hired to type invoices all day. More than a thousand invoices a month came through a shared inbox, got keyed in by hand, and a meaningful share had a mistake in them. Closing the books took a week and a half. Audit prep dragged on for months. The finance chief told us he'd hired a controller specifically to fix this, and after six months in the role she was straight with him: the way it was set up wasn't sustainable, and they needed a different way of working — not another hire. That's where we came in.

Discovery

What five days of looking found.

  1. 01

    Six months of invoices, every supplier type, sorted by who they were from, how they got paid, how reliably they matched a purchase order, and how many approvals they needed.

  2. 02

    Mapping the approvals showed where reality had drifted from the written policy — which suppliers really triggered which approvers, not which ones were supposed to.

  3. 03

    Early on we sat down with their outside auditor and agreed up front on exactly what evidence would keep the audit clean.

How we worked

Side by side, not over tickets.

  1. 01

    The controller was in the room every week while we wrote the rules — she signed off on each one before it went live.

  2. 02

    Each person on the accounts team took the review queue for a day during the first stretch so they all understood the exceptions.

  3. 03

    We checked in with the outside auditor each quarter to keep the evidence lined up with what they'd actually want to see.

The build

What runs now.

  1. 01

    An invoice lands in the inbox, the system reads it, checks it against the matching purchase order and receipt, and posts it to their accounting software.

  2. 02

    Anything that looks off is flagged with the context to decide quickly — similar past invoices, the supplier's history, a suggested category — and parked for an approver, who sees a single screen, not a PDF to dig through.

  3. 03

    The repeating month-end entries get prepared and queued; the controller reviews and posts them.

  4. 04

    At any point, the full trail behind any entry can be exported, so the auditor reviews the export instead of sampling people's email.

Outcome

What it's worth.

days, not weeks
  • The controller is still there and got promoted.
  • "The close is automated" has shown up in a few board updates now.
Saving
Auditor fees came down noticeably with cleaner evidence, and the accounts team got freed up for the supplier work they'd always wanted to do.
Speed
Closing the books went from a week and a half to a couple of days. The large majority of invoices now post correctly on the first pass.
Reliability
The error rate on entries dropped from roughly one in eight to almost none. The last audit had no material corrections.

Where it is now

Most days it just runs, and we're still involved. On the revenue side we're scoping the next piece — matching usage-based billing against what the product actually recorded.

Your next step

Your version of this story.

Thirty-minute call. We'll find three flows worth automating before we hang up. No deck. No "discovery proposal." Just the work.