Why does one vendor show two different balances in AP aging?
The vendor almost certainly exists as two separate records in your vendor master file — created under slightly different names (a typo, a rebrand, a merger, a re-onboarding) — so bills and credits are split across both. AP aging reports by vendor record, not by real-world vendor, so it shows two partial balances instead of one true balance.
By Zuny Fester, Head of Operations and MarketingPart of the accounts payable and invoice processing guide.
| Symptom | One real vendor, two vendor records, two partial AP aging balances |
|---|---|
| Root cause | Inconsistent vendor master data — name variants, no dedup on TIN or address |
| Common triggers | Rebrand, merger, re-onboarding after a name change, manual entry without a naming standard |
| Where to check | Search AP aging by TIN or remittance address, not vendor name |
How one vendor becomes two records
Vendor master files rarely enforce a single naming standard, so the same real-world vendor can be entered more than once: "ABC Manufacturing" and "ABC Manufacturing Inc." from two different business units, a supplier that starts invoicing under a new legal name after a rebrand or merger, or a vendor re-onboarded from scratch because the original record was inactive or hard to find. Each record accumulates its own bills, payments, and credits — so a vendor who is current on one record can look overdue on the other, and a credit issued against one record does nothing to offset a balance sitting on the duplicate.
Why AP aging doesn't catch it automatically
An AP aging report groups and sums by vendor record, not by the real-world entity behind it. Two records with different names, even for the identical company, are two separate rows with two separate balances — nothing in a standard aging report flags that they should be one. The split usually surfaces only when someone matches by tax ID (TIN) or remittance address instead of by name, which most day-to-day AP workflows don't do.
How to find and fix it
Search the vendor master file by TIN and by remittance address, not by name — that's what actually identifies a unique real-world vendor. If two records share a TIN or address, they're almost certainly the same vendor. Most accounting systems won't let you merge vendor records with existing transaction history, so the fix is to pick the record to keep active, move any open bills onto it, and inactivate the duplicate (many systems recommend prefixing the inactive record's name with something like "DO NOT USE" as a standing reminder rather than deleting it, since deleting would remove real transaction history).
Next step
Map the finance workflow with the most exposure and prove the automation path.
Bring the invoice, contract, payment reconciliation, or customer finance workflow you have to defend at audit. Loopfour can map the trigger, controls, integrations, and approval loop.
Worked example
One vendor, two records, two balances that don't tell the truth alone
"Ferrera Logistics" was onboarded in January. In August, after a rebrand, the same company started invoicing as "Ferrera Logistics LLC" — a new vendor record was created because AP didn't recognize it as the same supplier. By month-end, the aging report shows "Ferrera Logistics" with a $0 balance (fully current) and "Ferrera Logistics LLC" with $18,400 overdue. Both records share the same TIN and the same remittance address — the giveaway once someone checks. The fix: keep the newer record active (it matches the vendor's current legal name), move the $18,400 in open bills onto it if they were mistakenly entered against the old record, and rename the old record "Ferrera Logistics — DO NOT USE, see [new record ID]" so it can't be selected on a future bill.
Frequently Asked Questions
Sources
Related
Diagnostic
How do I reconcile a phantom AP liability from a broken Bill.com sync?
Compare open bills in your AP aging against actual disbursements on the bank statement. A phantom liability shows up as a bill still open in AP with a matching payment already visible on the bank side, which means the payment posted in Bill.com but its corresponding payment record never synced back to the accounting system, leaving the original bill looking unpaid.
Read moreTopic
AP & Invoice Processing
Accounts payable and invoice processing is the set of steps a vendor bill goes through between arriving at a company and turning into a payment: capturing what the vendor sent, checking it against wha…
Read moreDiagnostic
What causes a three-way match failure between the PO, receipt, and invoice?
A three-way match compares the PO, the receipt (what was actually delivered), and the invoice on quantity, price, and charges. A failure means one of those three disagrees beyond tolerance — usually because the invoice bills a quantity that isn't fully receipted yet, the unit price differs from the PO, or the invoice adds a charge, like freight, the PO never included.
Read moreDiagnostic
Why did we pay the same vendor invoice twice?
Almost always one of two things: the vendor exists as two separate records in your vendor master, so a duplicate-invoice-number check that only compares within one vendor ID never sees the second copy — or the invoice was entered twice by different people, because it arrived through two channels and each assumed they had the only copy.
Read more