In short
- Each entity's ERP or ledger checks only its own bills, so a cross-entity duplicate is invisible to both.
- Suppliers that serve several entities may address invoices loosely.
- Combining paid-bill histories across entities and comparing by supplier, invoice number and amount finds them.
- The invoice's bill-to entity should decide which company pays.
- Recovery is the same as any duplicate, but the request should come from the entity that paid in error.
How it happens
The setup usually looks ordinary. A packaging supplier serves several companies in the group and sends the invoice to the plant company, while a copy goes to the holding company because the buyer there placed the order. Each accounts payable team sees a valid bill for its own entity. The plant pays from its bank account. The holding company pays from the shared service center. Neither ledger flags the other payment, because each ledger checks only its own bills. The duplicate is invisible to both until someone combines the histories.
Shared service centers make the gap wider. The center may process for the parent, while a local office keeps its own bank account and pays small suppliers directly. A logistics supplier emails the invoice to the center and also posts a copy to the local office. The center pays against a purchase order. The local office pays against the statement. Both entries carry the same supplier invoice number, but the supplier names are spelled differently, so a quick search in either place misses the match.
Suppliers that serve several entities often address invoices loosely. The bill-to line may name the group, a trading name, or a division that is not a legal entity. The remit-to address may point to a lockbox used by another company. A clerk picks the entity that seems right. A second clerk in another entity does the same. Add a month-end rush, a new supplier master record, and an approval limit that sends the invoice to a different office, and the same bill can be paid from more than one bank account without anyone seeing it.
Finding it in your payment history
Start with paid bills, not open invoices. Pull the paid-bill history from every entity in the group and from any shared service center or local office that pays its own suppliers. Put the records in one working file with a column for the paying entity. Keep the original supplier name, invoice number, invoice date, payment date, amount and bank reference. This is the only way to see a payment made by one company against a payment made by another.
Then compare on the fields that matter: supplier, invoice number and amount. Clean the supplier names first. A packaging supplier may appear as a legal name in one entity and a trading name in another. An invoice number may have spaces, hyphens or a prefix added by the local office. Match the same amount and the same invoice number even when the supplier record is different. Look at credits too. A duplicate payment can sit as an unapplied credit on an entity's vendor record while the other entity still shows the bill as paid.
A simple worked situation: a logistics supplier sends the same invoice to the shared service center and to a local office. The center pays it under a central vendor record. The local office pays it under a local record. The supplier names differ by a word, and the invoice numbers differ by a prefix. The invoice number at the center carries an extra prefix, but the base number and amount match. When both histories sit side by side, the pair stands out. On its own, each payment looks normal. Also compare bank references and remittance advice, because a supplier may deposit a payment against the wrong account.
Getting the money back
The request should come from the entity that paid in error. That sounds obvious, but groups often send a group-level email that tells the supplier to refund the parent. The supplier then credits the parent, and the entity that actually paid still has a receivable to clear. Put the paying entity's name, bank reference and remittance advice in the request. Attach the invoice copy and the payment proof. Ask for a refund to the same bank account, or a credit on the paying entity's vendor record.
If the supplier offers a credit instead of cash, make sure it lands in the right place. A credit posted to another entity can become an unapplied credit that nobody owns. Ask the supplier to confirm the credit in writing and state which legal entity it belongs to. Apply it to open bills from that same entity. Do not let the supplier net it across the group unless the entities have agreed to that in writing and the accounting treatment is clear. Where tax or legal treatment matters, check the contract and local rules with an adviser. This is not a tax or legal call for AP.
Keep the valid bill in view. If the invoice was correctly billed to the holding company, the duplicate payment by the plant company is the excess. The holding company may still owe the supplier. Recovery focuses on the duplicate, not on cancelling a real liability. Update the vendor record with the refund or credit, close the duplicate payment, and keep the supplier's written confirmation with the payment file. If the supplier is slow, escalate through the account manager and keep the request factual: invoice, amount, paying entity, payment date and bank reference.
Stopping the next one
Decide the bill-to entity before the invoice reaches payment. The invoice's bill-to entity should decide which company pays. If the supplier is not sure, AP should not guess. Ask for a corrected invoice that names the legal entity and the purchase order. Shared service centers and local offices should use the same rule. A local office may pay a small supplier directly, but it still needs to check the group's paid-bill history before it releases the payment.
Add a cross-entity check to the payment run. For any supplier that serves more than one company in the group, compare the invoice number and amount against paid bills in the other entities. This can be a manual report at first. The check should cover the shared service center, the parent, the subsidiaries and any local office with its own bank account. When the check finds a possible match, hold the payment and ask the bill-to entity to confirm. Do not release it just because the local approval is complete.
Tighten supplier onboarding across the group. Use the legal entity name and a clear bill-to instruction on every vendor record. Tell suppliers to send invoices to a single address for the entity that is buying, with the purchase order and the legal entity on the face of the invoice. Train AP clerks to question invoices that name the group rather than a company. Review vendor statements by entity and at group level. Keep a log of refunds and credits so an unapplied credit does not sit unnoticed. These steps cost time, but they catch the duplicate before it becomes a recovery task.
Questions
What is a cross-entity duplicate payment?
It is the same supplier invoice paid by more than one company in a group, or by both a shared service center and a local office. Each payment looks valid in its own ledger, so neither team sees the duplicate without a combined view.
How do I find duplicate invoices paid by different subsidiaries?
Combine paid-bill histories from every entity and compare supplier, invoice number and amount. Clean supplier names and invoice prefixes first, because the same supplier can appear under different records. Include credits as well as payments.
Who should ask the supplier for the refund?
The entity that paid in error should make the request and receive the refund or credit. A group-level request can send the money to the wrong company and leave the paying entity with a receivable. Include the payment proof and remittance advice so the supplier can trace the payment.
Can we apply a supplier credit to another entity's open invoice?
Not as a default. A credit belongs to the entity that paid, and moving it across entities can create an unapplied credit or an intercompany balance that nobody clears. Get written agreement and clear accounting treatment first, and check with an adviser where tax or legal treatment matters.
Updated Nov 9, 2026. Figures on this page are calculated by ERPSav from the definitions shown. The explanatory text is drafted with AI from those figures and checked automatically before it is published. General information only, not legal, tax or financial advice.