Most PE operating CFOs and portfolio financial leaders are working with a 30-day lag.
The month-end AP report arrives, the team reviews it, and decisions get made based on what happened three weeks ago. Duplicates, missed payments, and wrong-entity billings surface in the report after the fact, when the damage is already done.
This is not a technology failure. It is a structural one. Standard accounts payable processes were built for single-entity operators with one location and one inbox. When a PE firm executes a roll-up strategy—acquiring five operators, consolidating twelve entities, and running invoices from 80 locations through the same function—the architecture breaks. The month-end report is the best a broken system can produce.
There is a better baseline.
Why the month-end report fails multi-entity operators
A monthly AP report is a historical document. It tells you what was paid, to whom, from which entity, against which GL. That information is useful for reconciliation and audit. It is not useful for running a multi-location business in real time.
The problems that cost PE-backed roll-ups the most—duplicate invoices, missed payments, wrong-entity billings, unapproved vendor relationships—are invisible in a monthly report until they have already compounded. By the time the CFO sees the line item, the vendor has already been paid twice, the late fee has already accrued, and the controller is already rebuilding the journal entry.
Operating CFOs at multi-entity operators need a different view: what is coming in right now, where it is going, and whether it looks right. Not last month. This week.
The AP coding problem is upstream of the visibility problem
Before you can have real-time AP visibility, you need invoices that are structured well enough to be tracked instantly. That is harder than it sounds.
Most invoices arrive as unstructured PDFs with no location tag, no entity assignment, no GL code, and no cost center. Someone on the AP team decides all of that manually. Until those decisions are made, the invoice is invisible to any reporting layer. It is just a PDF in an inbox.
This is why multi-entity AP software and visibility tools have historically been limited to post-close reporting. The data does not exist in a structured form until a human creates it, and that human works on a monthly cadence.
Automated invoice pre-coding changes the sequence. When every invoice is automatically assigned to the right location, entity, GL, and cost center before it reaches AP review, the structured data exists from the moment the invoice arrives. The visibility layer has something to work with immediately.
What real-time AP visibility looks like for a roll-up portfolio
When invoices arrive pre-coded, a PE operating CFO can see the full picture across the portfolio in real time.
- Which vendors are active across which locations.
- Which entities are running above or below expected spend.
- Whether a new vendor has appeared on an entity that should not have that relationship.
- Whether the same invoice has come in twice from the same vendor in the same period.
These are not questions that require a month-end report to answer. They are questions that can be answered immediately if the underlying portfolio data is structured correctly.
For a PE operator running multiple entities across dozens of locations, this changes the operating cadence. Instead of a reactive review at month-end, the CFO has a live view that surfaces anomalies as they happen. The close becomes a confirmation of what is already known, not a discovery process.
Accelerating the month-end close for portfolio companies
The standard month-end close for a multi-entity operator involves significant time spent on AP coding and reconciliation. Invoices get matched to purchase orders, assigned to entities, and manually coded to GL accounts—work that was done by the AP team during the month, now being verified and corrected.
When invoices are pre-coded on arrival, that work is already done. The close becomes a review, not a reconstruction. Teams that were closing on day 10 or 12 move to day 5 or 6. Not because the team worked faster, but because the automated GL coding ensured the data was ready.
More importantly, the quality improves. Pre-coded invoices are consistent. The same vendor gets the same GL treatment every time, across every entity, regardless of who is on the AP team that week. Audit trails are clean. Journal entries are straightforward.
The multi-location pilot that changed how we think
We ran a pilot with a PE-backed franchise operator running 86 locations. The goal was to fix the coding problem: invoices arriving uncoded into a shared inbox, bouncing between six different tools, creating duplicates and missed payments across multiple entities.
We fixed that. But the thing that surprised the operating CFO was not the time saved. It was the visibility.
For the first time, she had a live view across all 86 locations. Not a spreadsheet someone compiled at month-end. Not a report that arrived three weeks after the fact. A real-time picture of what was coming in, where it was going, and whether it looked right.
She stopped asking what happened last month. She started asking what was happening this week.
That is a different job. A more useful one.