Support Intercompany Payable Confirmations

What an intercompany confirmation is testing

An intercompany payable confirmation compares what one entity owes with what another entity records as receivable. The purpose is to identify differences in amount, period, entity, or transaction before consolidation. It is not a payment approval and it does not replace the accounting close.

Payables support can prepare the confirmation package, match identifiers, collect counterparty responses, and document differences. The accounting owner decides how a difference should be treated. Keeping that boundary clear prevents an administrative match from being mistaken for an accounting conclusion.

Use a shared transaction reference

The most common cause of a false difference is that the two entities use different identifiers. A vendor invoice number may not be the same as the intercompany billing reference, and a payment may be applied to a different period. Use a shared reference, such as an intercompany agreement number or a transfer identifier, and record it on both sides.

If a shared reference is not available, build a mapping table with the entity, counterparty, invoice or billing number, amount, currency, service period, and status. The mapping should be reviewed before the confirmation is sent so the counterparty is not asked to reconcile against the wrong population.

Use the related specialist service role as a starting point for defining scope and evidence.

Document differences by cause

Classify differences as timing, amount, entity, currency, duplicate, missing record, or disputed charge. Timing differences may resolve in the next period, while amount differences require evidence. A generic unreconciled label makes it impossible to see whether the process is improving.

Attach the source records for each difference: the invoice, the billing statement, the payment advice, the general ledger extract, and the counterparty response. The record should show what was compared, not only the final difference. A reviewer should be able to reproduce the comparison without asking for a new spreadsheet.

Keep netting and settlement separate

Some organizations settle intercompany balances through netting or a periodic transfer. The confirmation should show the gross payable and receivable before any netting, then the approved netting arrangement. If the netting is recorded in a separate system, link the record rather than replacing the gross balance.

Do not let a netting entry hide an unresolved difference. A difference that is netted away may reappear in a later period or distort the confirmation. The accounting owner should approve the netting treatment and the payables record should retain the evidence.

GAO Standards for Internal Control in the Federal Government provides public guidance that can help your team test relevant workflow assumptions.

Route disputes to the right owner

When the counterparty disagrees, record the disputed amount, the reason, the evidence provided, and the owner responsible for resolution. Set a response date and a next checkpoint. If the dispute involves a service issue, involve the business owner rather than trying to resolve it through the confirmation process alone.

Escalate when a difference remains open past the close calendar or when the same counterparty repeatedly provides incomplete responses. The escalation should include the facts and the decision needed, not a demand to clear the item. The goal is a reliable confirmation, not a clean-looking spreadsheet.

Compare this approach with our guide to the next related workflow.

Close the confirmation cycle

At the end of the cycle, summarize the population, responses received, differences resolved, differences remaining, and the owner for each open item. Retain the summary with the supporting records. The next cycle should start from the prior open items rather than rebuilding the list from memory.

Review the process for recurring causes such as late billing, inconsistent references, or unclear ownership. A confirmation that always finds the same difference is telling you something about the upstream workflow. Fixing that cause is more valuable than adding another round of follow-up.

Common questions answered

Ready to create a clearer support role?

Bring the workflow that consumes the most attention. We will help you shape the role, handoff, decision boundaries, and review points.