QuickBooks Online Intercompany Transaction Support Pack

August 24, 2026

Bottom line: make every intercompany entry traceable between entities with balanced due to and due from, linked source evidence, and one clear reviewer question where the path is incomplete.

Sidebar: Organization supports preparation. Authorization remains with the owner or accountant.

Why intercompany records need a support pack

Small business groups that operate two or more legal entities often share a bank account, a vendor, a card, or an owner transaction that touches both books. QuickBooks Online records that shared activity through an entry in one entity and a mirroring entry in the other, commonly using Due To and Due From accounts. When the entries are complete, a reviewer can follow the flow from the paying entity to the receiving entity and back to the elimination or management report. When the entries are incomplete, the trail breaks. One entity shows a due balance with no counterpart. A payment is recorded as an expense in the wrong company. An elimination is attempted without evidence that the two sides balance.

QBOAssistant work often sits at that boundary. A virtual assistant can organize the entry population, verify that each transaction has a counterpart, link the source invoice or bank record, and flag mismatches. The group owner or accountant decides whether an entry is a loan, a management fee, a capital movement, or an operating expense, and whether an elimination is appropriate. A disciplined support pack prevents a VA from making that classification while still giving the reviewer a complete factual file.

Define scope and evidence standard

Start with a scope sheet that names the entities in the group, the review period, and the shared accounts being tested. Common in-scope accounts are Due To, Due From, Intercompany Payable, Intercompany Receivable, and Owner Equity transfer accounts where the business routes shared activity. Record which general ledger and bank sources were used, the preparation date, and the reviewer name.

Set the evidence standard before work begins. Each intercompany transaction should have a source reference in at least one entity, such as an invoice, bill, bank transfer detail, loan agreement, management agreement, or owner instruction documented in an approved system. A journal entry that moves a balance without a dated source is not sufficient evidence. If the source is an email or chat, store the relevant excerpt in the approved document location and link the location rather than pasting the full thread.

Build a traceable queue

Extract the population for the period from each entity. A practical export is the General Ledger detail for each intercompany account filtered by date, with transaction ID, date, account, class, other account, amount, memo, and attachment indicator. Add the bank activity for the same date range to catch transfers that should have created an intercompany entry but did not.

Create a working table with one row per shared event, not one row per QuickBooks line. A shared event might be a vendor bill paid by Entity A on behalf of Entity B. That event should produce two linked rows: Entity A records a Due From entry and Entity B records a Due To entry, both referencing the same vendor bill. In the support pack, group those two rows under one event ID and show the link explicitly. If the business uses three entities, a triangular settlement may need three linked rows. The point is that the reviewer sees the whole movement, not two disconnected ledgers.

For each event, record the paying entity, receiving entity, transaction type, QuickBooks IDs in both entities, amount, entry date, source location, and balance status. The status field should say whether the two sides balance, whether one side is missing, or whether amounts differ. Use a simple match code such as balanced, missing counterpart, amount difference, date gap, or unclassified nature. Keep the memo field factual. A memo that says per owner instruction needs a dated instruction reference. A memo that guesses the purpose creates more uncertainty than a blank memo with a clear question.

Work the exception patterns

Missing counterpart is the most common gap. Entity A shows a Due From 12,000 dated the 9th with a bill attachment. Entity B shows no Due To entry for that date or vendor. Preserve the single-side entry, note the attempted search in Entity B, and route it to the owner. Do not invent the missing entry to make the control appear balanced. The missing side often reveals that a payment was recorded as a direct expense in Entity B instead of as an intercompany liability.

Amount difference is next. Entity A records Due From 8,400. Entity B records Due To 7,900. The difference may be a fee withheld, an exchange adjustment, a partial application, or a data entry difference. Record both amounts, the variance, and the source that explains the fee or adjustment if known. If no source explains the variance, keep the two amounts visible rather than adjusting one to match the other.

Date gap appears at period ends. Entity A posts the Due From in one period. Entity B posts the Due To in the next. That creates a temporary imbalance in a point-in-time report even when the transaction is ultimately paired. Record the date on both sides, flag the item as a timing entry with an expected clearing date, and keep it open until the paired period is reviewed. This treatment avoids presenting a reconciliation adjustment when only timing is involved.

Unclassified nature is subtler. The entry exists and balances, but no one knows whether it is a loan repayment, a management fee, an advance, or an owner distribution. The pack should keep the entry as supported as to existence but open as to nature, with a question directed to the owner. The VA should not select a nature label when the evidence supports more than one interpretation.

Elimination pressure is another edge case. At reporting time, someone may want to eliminate the due balances for a consolidated view. The support pack should distinguish the legal entity view where the balances remain from the management view where they are eliminated. Keep both trails with a clear label so a later reviewer understands which presentation was sent to which audience.

Review table and handoff

The exception table should contain event ID, transaction type, entities, QuickBooks IDs, amount, balance status, source location, impact statement, and reviewer. The impact statement answers why the mismatch matters: it may overstate an asset, understate a liability, misplace an expense between entities, or delay a consolidated report. That context helps an owner prioritize.

The handoff section summarizes the number of events reviewed, the number balanced, the number missing a counterpart, the number with amount differences, timing gaps awaiting next period evidence, and unclassified nature items awaiting owner decision. Add a statement of what was not tested, such as prior period opening balances or a third entity that was out of scope for this review date.

Add approval blocks for the owner or accountant to confirm the treatment for each open item. Approval should be a dated decision attached to the event, not a hallway conversation. The VA can update the queue after approval but should not change history without a linked correction entry.

Cadence and retention

For active groups, a monthly pack works well alongside the bank reconciliation. For groups with daily shared payments, a weekly sample keeps the queue current while the monthly pack closes the period. Before a loan or tax handoff, run the full period pack so the advisor receives a balanced trail rather than two disconnected ledgers. Store the pack with the period close file and the source exports. Access should be limited to the approved reviewers. Avoid placing entity identification numbers or full banking credentials in the pack when a transaction ID suffices.

What good looks like

Good looks like a reviewer answering whether every shared payment has a linked counterpart, whether every due balance can be traced to a source, whether variances have an explicit owner, and whether no elimination was presented as a legal entity correction. The VA delivers a factual trail. The owner preserves the authority to classify and to decide on adjustments. That pairing keeps QuickBooks Online intercompany records both operational and reviewable.

Next step

Select one shared vendor and one recent period. Pull the intercompany detail from each entity, group the events, link the source in each row, and assign one reviewer for open items. Review the first pack for link reliability and for whether the exception table drives a decision. Keep what helps, remove what adds noise, and reuse the approved template for the next period.