A consumer-services platform buying six to eight independent operators a year — each arriving on its own bookkeeping system. We built a touchless AP pipeline that absorbs every acquisition's chart of accounts, so invoice volume can triple while the payables team stays exactly the same size.
Every deal added invoice volume, a new entity, and another chart of accounts — and AP headcount was scaling in lockstep with the deal count. Eleven days from invoice to posted. GL coding by hand. Approvals chased over email across mismatched systems. Early-payment discounts routinely missed because nothing moved fast enough to earn them. Each integration meant onboarding temp AP staff just to keep up.
One Pipeline, Every Entity
Posts untouched. No inbox, no approval chase, no human in the loop — matched, coded, routed, and on the ledger.
A human decides — with the match, the proposed coding, and the reasoning already on screen. One decision, not twenty minutes of digging.
Every invoice runs the same path regardless of which acquisition it came from, what system sent it, or what format it arrived in.
What We Built
Each acquired operator arrives with its own bookkeeping system, its own vendors, its own way of naming the same expense. Underneath the pipeline sits a semantic layer that maps every entity’s chart of accounts into one shared language — so the platform reads a new acquisition’s invoices the same way it reads its own.
That’s what makes the rest possible. The pipeline doesn’t care where an invoice came from, because by the time it’s in the flow, every invoice speaks the same language.
PDFs, emailed scans, portal downloads, whatever a two-location operator was using before the deal closed — the pipeline captures all of it and runs the three-way match against purchase orders and receipts automatically.
Mismatches surface immediately with the discrepancy spelled out, not three weeks later when a statement doesn’t reconcile. Duplicate invoices die at the door.
GL coding is proposed from years of the company’s own historical codings — not a generic rulebook — with a confidence score on every line. Above the threshold, it posts untouched. Below it, a human decides, with the reasoning already laid out.
Every correction feeds back in. The threshold doesn’t move; the share of invoices clearing it does.
Approvals route by policy — amount, category, entity — instead of by email thread. The AP team works one exception queue across 250+ locations, and the controller sees every invoice in flight, every discount window closing, every exception aging, in one place.
The eleven-day cycle collapsed to three. Which is why early-payment discounts stopped being theoretical: $1.2M a year, captured because invoices now clear inside the window.
The Whole Argument, In One Chart
Every marker is an acquisition landing on the platform. Each one used to mean temp AP staff and months of catch-up. Now it means one more entity on the same pipeline.
Integration Speed
A new acquisition plugs into the pipeline in about a week.
What used to be a months-long back-office integration — temp staff, duplicate processes, two ways of paying the same vendor — is now a mapping exercise. The acquired operator's chart of accounts gets absorbed into the layer, and their invoices start flowing through the same pipeline as everyone else's.
of invoices are fully touchless.
Captured, matched, coded, approved, and posted without a person touching them. The AP team's inbox isn't the invoice flow anymore — it's the exceptions worth a decision.
100 invoices · the 22 grey ones are the queue humans actually see
If finance headcount scales with your deal count, the platform doesn't actually scale.
The Impact
The payables function stopped being a line item that grows with every acquisition. Seven deals in, the team is the same size it was before the first one — and the work in front of them is exceptions and judgment, not keying and chasing.
Vendors get paid inside the discount window, which turned early-pay terms from an aspiration into $1.2M a year of captured margin. The controller has one view of payables across every entity instead of a spreadsheet stitched together from mismatched systems.
And the deal team’s integration math changed. Back-office absorption is no longer a cost, a delay, or a risk in the model — it’s a week.
We design and deploy AI-native systems for companies moving fast in competitive markets.
Talk to LightCI