A multi-location dispensary — three stores, each operating as a separate legal entity — had a vendor showing roughly $14,000 in open invoices. The vendor's AP team sent over the balance sheet. Everything looked routine. Invoices dated, amounts listed, payment terms noted. The kind of email that usually gets a quick "send the wire" response.
But we manage this retailer's accounts payable. So before any payment goes out, we check.
What We Caught
One invoice on the vendor's balance — $4,873 — didn't belong there. The vendor had it listed under Location A. Our system showed it as a Location B invoice. Different legal entity, different bank account, different payment schedule.
We pulled up the records. Location B had already paid that invoice six weeks earlier. The payment cleared their bank account. The vendor's own system should have shown it as settled — but because the invoice crossed entity lines, it showed up as open under Location A.
If we'd paid the balance as presented, the retailer would have paid $4,873 twice. The vendor wouldn't have flagged it. Their system showed an open balance, so from their side, the request looked correct. The error was invisible to anyone who wasn't cross-checking entities.
How We Caught It
This is what managed accounts payable looks like in practice. Not software sending alerts. Not a dashboard with red flags. A team that checks every number before money moves.
Here's what happened, step by step:
- Invoice verification — Every invoice gets cross-referenced against our records before payment. We don't pay what a vendor says is owed — we verify what's actually owed. When this vendor's balance sheet came in, we matched each line item against our AP records rather than taking the numbers at face value.
- Multi-location entity tracking — When a retailer has multiple stores operating as separate entities, invoices can drift between them. We track which invoices belong to which entity, so a Location B payment never shows up as an open balance under Location A. That's exactly what caught this one — the invoice was tagged to the wrong entity in the vendor's system, but our records showed the correct assignment.
- Payment reconciliation — We confirmed with the bank that the original payment had already cleared. This closed the loop — not just "our system says paid" but "the bank confirms the money left the account." There was no ambiguity.
- Vendor communication — We handled the back-and-forth with the vendor's AP team and the controller, so the retailer never had to get involved. We sent over the proof of payment, the vendor corrected their records, and the balance was adjusted.
The whole thing took about 15 minutes. Check the system, spot the mismatch, pull the bank confirmation, reply to the vendor. Fifteen minutes and $4,873 stays where it belongs.
Why This Gets Missed
This kind of error is more common than most operators realize, especially for multi-location dispensaries. Here's why it slips through:
- Multi-location retailers use the same vendors across stores. When three entities are buying from the same distributor, invoices and payments can easily get crossed between locations. The vendor sees one customer. You see three separate businesses.
- Vendors don't always track which entity paid what. A vendor's AP system might show a single account for your entire operation — or it might have separate accounts that aren't properly synced. Either way, a payment from Location B doesn't always clear the right invoice on the vendor's side.
- Without a system cross-referencing entities, the balance looks legitimate. The invoice existed. The amount was real. The vendor's balance sheet added up — it just included $4,873 that had already been paid by a different entity. If you're reviewing the balance at face value, there's nothing that looks wrong.
- AP staff without multi-entity visibility would just pay it. If your AP person only sees Location A's records, they have no way to know that Location B already covered this invoice. The vendor says you owe it. Your records don't show a payment. So you pay it again.
The Result
$4,873 saved. One morning. No drama. The vendor corrected their records. The retailer never knew it happened until the weekly report.
Here's the broader point: this kind of catch happens regularly. Not every one is $4,873 — some are $200, some are $8,000. But they add up. For multi-location dispensaries, cross-entity billing errors are one of the most common sources of overpayment. Every time a vendor sends a balance sheet, there's a chance something on it has already been paid by a different entity. Without someone cross-referencing every line item across every location, those duplicates become real payments.
This is what happens when vendors self-report what you owe. You need someone checking the math.
If you're running multiple locations and paying vendors based on their balance sheets, this is already happening to you. The only question is how much. Talk to us — we'll run a free evaluation on your vendor payments and show you exactly what's slipping through.