Start intercompany balance confirmation by writing what the support role prepares and what the business decides. The bookkeeper can gather records, follow the documented process, update the accounting system, and explain an exception. The owner, controller, or CPA should retain approval, payment release, accounting judgment, and policy exceptions.
An intercompany balance confirmation process
A repeatable intercompany balance confirmation process makes counterparties, timing differences, and unresolved balances visible.
Published · 8 minute read
The short answer
- Define the preparation and approval boundary for intercompany balance confirmation.
- Keep source evidence, system work, review notes, and exceptions together.
- Expand the handoff only after representative cycles are complete and traceable.
Set the decision boundary
Define the recurring input
List the source records, expected timing, format, account or period reference, and the evidence needed for intercompany balance confirmation. If an item arrives through an unusual channel, record it and move it to a hold queue. Clear intake rules expose missing information before it becomes rework.
Use a repeatable sequence
Break intercompany balance confirmation into receive, check, record, compare, document, and hand off. Each step needs one expected output and one stop condition. Do not silently resolve an unfamiliar exception. Record what was checked, what is missing, and which named owner must decide.
Keep evidence with the work
Pair each entity's ledger extract with invoice or recharge support, currency, transaction date, settlement record, and counterparty confirmation. Each group should set retention requirements under its own policy, consulting IRS recordkeeping guidance where applicable.
Separate preparation from approval
Give the bookkeeper enough access to complete intercompany balance confirmation without giving the same person authority to approve their own work. Define the reviewer, deadline, review questions, and close event. Use named accounts and multifactor authentication for system access.
Create an exception path
Log one-sided entries, invoice timing gaps, currency differences, disputed recharges, and settlements posted to the wrong entity pair. Preparers on both sides attach evidence; entity controllers approve corrections, allocations, and foreign-exchange treatment.
Review representative cycles
Confirm one high-volume entity pair and one cross-currency pair before rolling out the protocol. Require both ledgers to agree on document identity and period, not merely net balance, so offsetting errors remain visible.
Make the handoff explicit
Produce a bilateral confirmation showing due-to and due-from balances, currency, matched items, reconciling items, settlement plan, and sign-off from each entity. See the operations support service and reporting and QA service for adjacent workflow design.
Questions owners ask
Can an offshore bookkeeper own intercompany balance confirmation?
The bookkeeper can prepare the documented work, maintain evidence, and explain exceptions. An authorized business owner, controller, or CPA should retain approvals and accounting judgments.
What should a reviewer check?
The reviewer should check source completeness, the recorded result, open exceptions, required approvals, and whether the process was followed.