QuickBooks Online Intercompany Loan Reconciliation Review

August 23, 2026

Bottom line: every intercompany loan balance should be supported by a note summary or approved memo, matched transfer records in both entities, an interest schedule where applicable, and a reviewer approved exception for any non-mirrored entry.

Sidebar: Intercompany loans affect two books at once. The review keeps both sides honest.

Why intercompany loans need a mirrored review

Intercompany loans look simple when they are created and complex when they are not maintained. One entity sends cash to another, a due to or due from is recorded, and operations continue. Later, a repayment is recorded in one entity as a bank transfer while the other entity shows it as an expense, or interest is calculated in a spreadsheet that never reaches QuickBooks. At period end the owner asks why entity A shows a 40,000 receivable from entity B while entity B shows 28,000 payable to A, and no one can point to the note or the transfer trail that explains the difference.

For QBOAssistant clients that operate multiple related entities, the virtual assistant often handles the data assembly: pulling due to and due from balances for each intercompany pairing, listing transfers between entities, checking that each transfer was recorded in both entities with consistent amounts and dates, and organizing the queue where mismatches are visible. The assistant does not decide loan terms, impute interest, or forgive balances. A mirrored reconciliation preserves that boundary while giving the reviewer the combined view required to approve corrections.

Without a dedicated loan packet, intercompany activity drifts into ambiguous transactions. A bank transfer between entities is categorized as an owner distribution, a vendor payment, or an uncategorized expense. Those choices hide the loan. A reconciliation that demands a note, matched entries, and a trail for each movement prevents that drift from becoming a period end surprise.

Define the loan population

Start with a definition of which entities and accounts are intercompany loan accounts. In QuickBooks Online this usually includes the chart of accounts detail for due to and due from accounts by counterparty, plus the related bank detail for transfers tagged to the other entity and any loan payable or receivable account that was created for a formal note. Save the population before proposing entries. Record the included entities, the accounts, the cutoff date, preparer, and reviewer. If loans are tracked by project, class, or custom field in addition to account, state which lens the review uses.

Group activity by counterparty loan rather than by bank account. The useful grouping shows one loan relationship, for example Entity A to Entity B, with its beginning balance, approved advances during the period, repayments, accrued interest if the loan bears interest, and ending balance, shown for both sides. The two sides should mirror. When the business also has trade payables or receivables between entities, separate those routine trade balances from loan balances so a trade invoice is not mistaken for a loan advance.

State exclusions. For example, equity contributions, distributions accounted for as equity, and shared expense allocations that are not part of a lending arrangement should be handled in their own packets. A brief exclusion note keeps the loan review focused on principal, interest, and approved adjustments.

Gather the evidence package for each loan

For each loan pairing in scope, collect the internal and external support side by side. Internal support starts in QuickBooks: loan balance by entity as of the cutoff, GL detail for due to and due from accounts, the bank transfer or bill that created each advance or repayment, the counterpart entry in the other entity, the amount, date, and memo, and any journal that recorded interest. Add the loan note summary, the stated principal, interest rate if any, term, and repayment terms as they appear in the controlled document, plus the last date the note was reviewed.

External support is the trail the reviewer needs to approve a movement: bank transfer confirmations for each advance and repayment, loan notes or board memos where the loan was authorized, interest calculations with source dates, and any written communication that modified terms such as extending maturity or pausing payments. Link the document locations under controlled access rather than copying sensitive transfer detail into the working file.

Add a transfer match summary that lists each movement once but shows both entities. That table should carry movement date, amount, originating bank, receiving bank, due to and due from transaction IDs for each entity, and whether the entries mirror. An unmatched transfer is immediately visible as an exception because one side has a recorded entry and the other shows nothing.

Check three items for every loan. First, the beginning balance plus advances minus repayments plus accrued interest recognized should equal the ending balance for each side. Second, every advance and repayment should have a matched pair in the other entity with the same amount and consistent timing. Third, any interest recorded should trace to a schedule that uses the rate and period documented in the note.

Flag mismatch patterns consistently

Non-mirrored entry is the most frequent exception. Entity A shows a 12,000 transfer to Entity B, but Entity B has no corresponding due from entry for the same date and amount. Record the transfer ID from the originating entity, the bank evidence, and the search performed in the receiving entity. Hold the movement as exception pending entry rather than assuming the other side will be found later.

Amount mismatch is a second pattern. Both entities recorded the movement but amounts differ by a fee, an exchange effect, or a data entry error. Keep both amounts visible, link bank detail that may explain a fee, and raise a question about whether the books should show the gross, the net, or gross with a separate fee.

Timing mismatch appears near period ends. Entity A recorded a repayment on August 31 that Entity B recorded on September 2 because of bank clearance timing. Flag the movement as cutoff timing. Both entries can be correct in their own books, but the cutoff balance will not mirror. Disclosure of in transit items resolves the apparent gap without posting an adjustment.

Interest missing or double counted is another exception. Interest was calculated but not posted, posted without a supporting schedule, or posted twice because both entities recorded the accrual without designating which side drives the entry and which side mirrors it. Link the schedule, show the calculation for the period, and ask the reviewer to confirm whether an entry is still required.

Loan and equity confusion is a practical risk. A transfer that should be a loan advance was categorized as a contribution or distribution. Flag the entry as classification under review. Include the transfer detail, any approval note that describes the intent, and the impact on equity if left as posted. The reviewer decides whether to reclassify.

Build a packet an owner and accountant can trust

A concise packet fits on one file with links and ownership. Start with a cover sheet that names the entities, loan pairings in scope, cutoff date, preparer, reviewer, total advances, total repayments, total interest accrued, and the ending loan balance per pairing as shown in each entity. Show the mirroring check on the cover: balances mirror, in transit explained, or exception pending.

Follow with the movement table for each loan pairing. Useful columns include date, movement type such as advance, repayment, interest, or adjustment, amount, source bank or account, due to transaction ID in one entity, due from transaction ID in the other, interest schedule link where applicable, and exception status.

Add the exception queue that isolates every loan where transfers do not mirror, amounts differ, timing creates a cutoff gap, interest lacks support, or a transaction may be misclassified as equity. Each row carries the loan pairing, movement date and amount, entry IDs in each entity, evidence location, exception type, impact on reported intercompany balances, and owner.

Include a note summary that lists each active loan's principal, rate, term, last approved review date, and any recent amendment with evidence links. Include an in transit disclosure that names transfers initiated before cutoff but recorded on the other side after cutoff, with amounts and expected clearance.

Use simple statuses such as mirrored and supported, single sided pending entry, amount difference pending review, timing in transit disclosed, interest schedule pending approval, or classification question with reviewer. Close an exception only when the paired entries mirror, the schedule supports the interest, or the reviewer approves a documented reclassification.

Control the cadence and archive discipline

For clients with active intercompany transfers, run the review monthly before intercompany eliminations are considered and before any management report that presents combined results. The VA refreshes balances, lists new movements, matches pairs, drafts specific questions, and presents the packet on a fixed date. The reviewer approves entries, confirms interest, and decides on any reclassification. At quarter or year end, rerun the packet with the formal cutoff and confirm that the set of active loans, note terms, and balances are ready for accountant or tax preparer review.

Archive the packet with due to and due from detail, bank transfer evidence links, note summaries, interest schedules, and the exception queue. Keep the archive location consistent and avoid copying full bank numbers into the working table when a transaction ID and date suffice.

A reviewer should be able to answer five questions after reading the packet: which loans exist between the related entities, what the current balances are in each book, how balances moved during the period, how much of the change is timing versus a missing entry, and who owns each exception.

Quality checks that help include asking whether every advance and repayment has a mirrored partner, whether both sides show the same principal and interest assumptions, whether any transfer was categorized outside due to and due from without approval, whether interest ties to a stated rate and day count, and whether any adjustment was posted without a documented reason.

The QuickBooks bookkeeping VA service describes preparation and review separation for intercompany work. For period packet framing, pair this with the QuickBooks month-end close packet.

What good looks like

Good looks like two books that agree by counterparty, balances that reconcile to notes and schedules, transfers that appear once and mirror in both entities, and interest that is demonstrably based on documented terms. Period explanations are short because the evidence already shows the movement. Accountants spend time on judgment rather than hunting for missing transfers.

Next step

Pilot the review on one loan pairing that had frequent activity last month. Pull due to and due from detail for both entities, list bank transfers between them, match pairs, link note terms, and populate the exception queue. Draft a concise question for each mismatch that would let the reviewer decide without rework. Review the packet for clarity. Keep fields that drove an entry or approval, remove fields that created noise, and reuse the approved packet on the normal monthly rhythm. That focused start turns scattered intercompany bookkeeping into a paired control without changing approval authority in QuickBooks Online.