How to Reconcile Intercompany Due To and Due From Balances in QuickBooks Online
October 6, 2026
Bottom line: One entity’s due-from balance should have a supported counterpart in the other entity’s due-to balance, but matching totals alone are not enough. Reconcile transaction by transaction, preserve each legal entity’s books, identify timing and currency differences, and route settlement, allocation, and elimination decisions to the authorized accountant.
Define the entity map
List every legal entity, its QuickBooks company, functional currency, fiscal year, bank accounts, tax registrations, and responsible owner. Assign a stable entity code and counterparty code. Similar company names are a common source of miscoding, especially when one operating team pays bills for several entities.
Document why intercompany activity occurs. Typical flows include shared vendor costs, central payroll, cash transfers, management fees, inventory movement, loans, and expenses paid on behalf of another entity. Each flow needs an approved source, account pair, allocation basis, posting frequency, and settlement method. A due-to account is not permission to move any unexplained difference off the income statement.
Keep agreements for loans, services, cost sharing, interest, and repayment terms. Note whether the relationship is short-term operating activity or formal financing. Tax, legal, and transfer-pricing consequences require professional review; the assistant’s role is to make the facts and entries complete and consistent.
Create a bilateral transaction matrix
Export the due-to and due-from general ledgers from every entity for the same cutoff. Include transaction ID, effective date, posting date, counterparty, document number, description, source currency, functional-currency amount, class or location, and attached evidence. Normalize signs in a separate reconciliation column instead of changing the source exports.
Assign one intercompany reference to both sides. For a shared invoice, that reference can connect the vendor bill, allocation schedule, receivable entry in the paying entity, payable entry in the benefiting entity, and later settlement. Never rely only on equal amounts: recurring transfers can produce false matches.
Group rows as matched, timing difference, currency difference, amount difference, account mismatch, wrong counterparty, one-sided entry, disputed, or unsupported. Record the owner and expected clearing date. This classification explains the gap and prevents a reviewer from treating every difference as a posting error.
Reconstruct a shared-cost example
Assume Entity A pays a 9,000 software invoice covering A, B, and C. An approved usage schedule assigns 4,500 to A, 3,000 to B, and 1,500 to C. Entity A’s books should retain its own supported cost and the approved intercompany amounts; B and C need their corresponding costs and obligations under the company’s policy. The matrix connects all sides to the invoice and allocation version.
If B records 3,000 but C records nothing, the consolidated net may still appear plausible when other transfers exist. Counterparty detail reveals the one-sided 1,500. Creating a plug in Entity A would hide the missing C entry and could misstate each entity even if a consolidated worksheet later eliminates intercompany totals.
The allocation driver must be documented. Headcount, users, revenue, floor area, direct identification, or another measure may be reasonable for different costs. Preserve the measurement date and source. Do not reuse last month’s percentages without confirming that the approved driver remains current.
Resolve timing and currency correctly
A payment late on the final day of the month may clear one entity’s bank before the other records receipt. Identify the bank traces and both posting dates. A genuine cutoff difference can remain on the reconciliation with a subsequent-clearing reference; it should not automatically be backdated.
For multiple currencies, retain source amount, transaction-date rate, each entity’s functional amount, settlement-date amount, and approved foreign-exchange treatment. Two functional-currency balances may differ even when the source-currency obligation agrees. Separate that explainable currency component from missing or duplicated principal.
Do not force one entity’s books to equal the other by copying a translated balance. The accountant should determine remeasurement, translation, and exchange-gain treatment. The schedule provides the dates, currencies, rates, and calculations needed to make that decision.
Control corrections and settlements
For each proposed correction, show the original transaction, root cause, affected entity, proposed date, accounts, amount, source support, and approver. Post in the entity where the error occurred. A correction in the wrong company can make the bilateral difference larger while appearing to fix one report.
Use stable settlement references for actual cash transfers. Confirm payer, recipient, bank ownership, amount, currency, and authorization. Match the transfer against the approved open items rather than recording new income or expense from the bank feed. Partial settlements should leave a visible remaining balance by intercompany reference.
Elimination entries belong in the approved consolidation process, not automatically in an entity’s operating ledger. Preserve a distinction among local-book entries, reconciliation adjustments, and consolidation eliminations. Otherwise a later reviewer cannot tell whether the legal entity still owes cash or whether a reporting-only entry removed the balance.
Complete the month-end proof
Roll forward each entity-counterparty pair from opening balance through new charges, repayments, credits, currency adjustments, and ending balance. Confirm that reciprocal source-currency balances agree after identified timing items. Tie every entity’s ending total to its QuickBooks general ledger and the consolidated intercompany matrix.
Review aging, unusual direct journals, dormant balances, round-dollar transfers, missing agreements, and items repeatedly carried as timing. A timing item that never clears is not a timing item. Escalate old disputes and potential loan balances to finance, tax, and legal owners.
Keep final exports, the matched matrix, source packets, correction approvals, settlement evidence, and reviewer signoff. The IRS offers general recordkeeping guidance, but entity, tax, and consolidation treatment should come from qualified advisers familiar with the organization.
QBOAssistant can maintain entity-coded registers, assemble bilateral exports, match references, and prepare exception schedules without making tax or legal conclusions. If due-to and due-from accounts are accumulating as unexplained totals, contact QBOAssistant to create a counterparty-level reconciliation handoff.
QuickBooks VA workflow table
| Workflow area | What the VA prepares |
|---|---|
| Daily queue | Invoices, receipts, bank feeds, and open QuickBooks questions |
| Weekly review | Owner approvals, exception list, and unresolved transaction notes |
| Monthly packet | Reports, missing documents, and accountant-ready source material |
Related resources
Compare the service fit on the QuickBooks VA services page, then use the free consultation form to map the first handoff. For platform context, review QuickBooks Online.