.svg)
Managing accounts payable for one company means making a coding decision once: this vendor goes to this account, coded this way, every time. Managing it for five companies at once means that same decision either gets made five separate times, or it doesn't get made consistently at all. Either way, the financial picture for each entity gets murkier.
Charly Green, Controller and CPA at Provignage, inherited exactly that problem when she took over AP for the company's portfolio of wineries nearly two years ago.
The problem: one account, five companies, no breakdown
Vendor bills across Provignage's entities were landing in one account with no breakdown by line item. "Our vendors all went into one account, so we lost sight of detailed costs," Charly noted.
Data entry compounded it. Bills arrived by email, and the same vendor's details got typed in again and again, often with small variations depending on who entered them and when. "We were entering the same information repeatedly," Charly explained. "And many entries were prone to errors."
On top of that, Provignage processed payments through Melio, where even ACH transfers took three to four days. That held up vendor relationships that depend on wineries paying reliably and on time. A personnel turnover expanded Charly's responsibilities right as she was trying to solve this. "I found myself constantly fixing errors," she shared.
Why multi-entity AP breaks most single-company tools
Most AP tools are built around one set of coding rules for one company. That's reasonable if the buyer only has one entity to manage. It becomes a liability the moment a controller is responsible for several. Every incoming bill gets treated identically regardless of which entity it belongs to, so the entity-level judgment still has to happen in the controller's head, every time.
What MakersHub's Integration Mapping changed
MakersHub's Integration Mapping lets Charly map exactly where a vendor's bill should route, once, and the system remembers and applies that mapping automatically every time that vendor's bill comes in again, for whichever entity it belongs to. "I could map exactly where each invoice should go, and the system remembered it for the next time," she explained.
That mapping is what makes the rest of the automation usable across a portfolio, rather than for a single company.
Extraction accuracy and QuickBooks sync
Bill data now extracts at close to 90% accuracy, including invoice numbers, line items, terms, and due dates. "I'd never seen anything like it," Charly shared. "It extracts everything, invoice numbers, line items, terms, and due dates, all without me lifting a finger."
QuickBooks sync happens in real time through a two-way integration, rather than the multi-minute lag she'd seen with other platforms.
Faster payments
Payments that used to take three to four days through Melio now process the next day. "Now, I don't have to log into the bank and manually initiate payments," Charly said. "Everything happens through MakersHub, and it's fast."
The results
The combined effect: Charly manages AP across five or more entities without adding staff to do it. "MakersHub has given me the tools to manage AP for multiple companies without the stress," she said.
The complexity ceiling multi-entity operators hit
The pattern underneath Provignage's story shows up anywhere one person owns accounts payable across more than one legal entity: a bookkeeping firm serving several clients, a controller overseeing a group of related companies, a multi-location hospitality group running several properties. In every version, the constraint is complexity, not volume. Most AP software can process more bills without falling over. The real test is whether it can hold five, ten, or twenty separate sets of vendor logic at once and apply the right one automatically, instead of that judgment quietly falling back on the person running the process.
What to look for in multi-entity AP tools
Does a coding rule persist per vendor, or reset with every new bill?
If a mapping has to be reconfirmed each time, the tool is making repetition faster, not solving it.
Does line-item detail reach the books, or just a vendor total?
Without it, cost visibility across a portfolio collapses into one undifferentiated account.
Does the payment process add its own delay?
Faster bill capture doesn't help if payments still sit for days on the back end.
Does the tool distinguish between entities automatically, or does the controller have to?
The value of automation across a portfolio depends on the software carrying that distinction, not the person running it.