QuickBooks Online Retainer Billing Reconciliation Review

August 24, 2026

Bottom line: reconcile every retainer balance in QuickBooks Online by tying the advance deposit to applied invoices and to the remaining liability or asset with an owner checkpoint for each unapplied amount.

Sidebar: Billing preparation can be delegated. Retainer application and refund authority stay with the owner.

Why retainer reconciliation needs a dedicated routine

Retainer billing creates a timing gap between receiving money and earning it. In QuickBooks Online that gap is often represented as a liability such as Customer Deposits or Retainer Liability, or as a credit on the customer account, depending on how the business configured its workflow. The balance is meaningful. An overstated liability suggests the business owes more future work than it does. An understated liability hides an obligation to perform. An unreconciled retainer also affects collections because the business may send an invoice for work already covered by the retainer.

QBOAssistant review work for retainers is about traceability. A virtual assistant can assemble the deposit list, map each deposit to the invoices that drew it down, verify the remaining balance, and flag items where the retainer was applied without an approved invoice or where an invoice was sent without considering the retainer. The VA should not decide that a retainer is forfeited, refundable, or reclassified to income without owner approval.

Define the retainer population

Start with a report that shows the retainer-related balances as of the review date. Common sources include the Balance Sheet detail for Customer Deposits, the Customer Balance Detail filtered to deposit-type transactions, and the Open Invoices or Sales reports grouped by customer for retainer customers. Save the population before making notes. Record the preparation date, the reviewer, and the retainer accounts or items in scope.

List every customer with a retainer arrangement. For each, record the agreement reference, the retainer type where the business distinguishes refundable and nonrefundable, the last activity date, the advance deposit total during the period, the invoices applied during the period, and the closing remaining balance in QuickBooks. If the business tracks retainers per matter, project, or engagement, list the matter level rather than just the customer level.

Set the billing policy for the review. Some retainers are evergreen and replenished. Some are one time and applied sequentially. Some convert to income on a schedule independent of invoices. State the policy in effect for each group. Without that label, the reviewer cannot tell whether an unapplied balance is expected or exceptional.

Reconcile deposit to invoice to remaining balance

Create a working file with one row per retainer deposit and its applications. A practical row includes customer and matter, deposit date, deposit transaction ID, deposit amount, application date, applied invoice ID, invoice amount applied from retainer, and remaining retainer balance after application. The file should show that each application links a specific invoice to a specific deposit. A retainer balance that moved without an applied invoice reference is not supported.

Check three balances. First, the sum of deposits minus the sum of applications should equal the remaining retainer balance in QuickBooks for the same customer and matter. Second, the invoice total applied from the retainer should match the credit applied on the invoice itself. Third, the bank deposit for the advance should tie to the original retainer receipt when the business received a bank transfer. A difference may indicate a deposit recorded to income instead of to the retainer liability, a fee withheld by a payment processor that reduced the net deposit, or a timing gap where the invoice was created before the deposit was recorded.

Keep facts and decisions separate. The fact field carries the deposit and invoice linkage. The decision field stays blank until the owner confirms whether any unapplied amount should remain as liability, be applied in the next cycle, be refunded, or be reclassified with accountant guidance.

Exception patterns to protect

Unapplied but earned retainer is the first sensitive pattern. Work has been performed and an invoice exists, but no retainer was applied. The customer may be double paying when the retainer is available. Record the invoice, the available balance, and the billing question. Do not apply the retainer silently when the invoice itself may still be in draft.

Applied without invoice is the opposite. A retainer was reduced through a journal or credit memo without a dated sales document that supports the draw. That entry looks like earned income without evidence of delivery. Keep the entry visible as unsupported until a dated invoice supports it.

Aging retainer without activity is third. A balance has sat for months with no invoice application or refund. That balance may be stale data, a completed engagement that was not closed, or a customer credit that should have been refunded. Assign an owner and a due date. Do not reclassify a stale balance to income to clear the queue without approval.

Partial application not fully recorded appears when a payment processor reports a net retainer deposit after deducting a fee. QuickBooks shows the gross retainer amount. The bank shows the net. The working file should separate the fee from the retainer so the balance is correct and the fee route for review is preserved.

Customer level versus matter level confusion is common. A customer with two matters may send one retainer that belongs to Matter A, but the application posts to Matter B. The customer balance may look correct while the matter balances are wrong. The review should keep the matter identifier on every row and flag any row where the deposit matter and the application matter do not match.

Packet and handoff

The packet includes a cover sheet, a customer and matter retainer table, the deposit to invoice mapping, the balance tie-out by customer, and an exception table. The exception table carries customer, matter, balance, exception type, supporting references, impact on bank and revenue reporting, and the next owner. Impact helps the owner prioritize. An overapplied retainer that affects revenue is more immediate than a small aging balance that needs a closure decision.

Add an application control statement that says who may apply a retainer to an invoice and what approval is recorded. That one paragraph often clarifies whether a VA may draft an application for owner approval or whether an application may be posted directly.

Close with a period statement that lists retainers received, retainers applied, retainers refunded, and closing balances. When the period statement agrees with the QuickBooks deposit and invoice activity, the packet is close ready.

Cadence

A weekly pass works when retainers fund ongoing service. A monthly tie-out is the minimum for most professional service groups. Before sending invoices, run the retainer balance check so customers are invoiced net of available retainer only when the agreement calls for it. Archive the packet with the customer retainer reports and the invoice exports. Limit access to the billing lead and the owner. Avoid copying customer banking details into the review notes.

What good looks like

Good looks like a reviewer seeing which retainers were received, which invoices applied them, which balances remain and under what policy, and which exceptions need approval before invoicing continues. The VA supplies a linked trail. The owner keeps the decision about application, forfeiture, refund, and revenue treatment. That pairing keeps retainer billing both operational and reviewable.

Next step

Select one retainer customer and the current month. Build the deposit to invoice mapping, verify that the remaining balance ties, and list any unapplied or unsupported application for owner decision. Review the first packet for matter accuracy and for whether the balance tie-out stands. Reuse what works for the next billing cycle.