Build a Customer Retainer Application Register for QuickBooks Online

October 2, 2026

Bottom line: A customer retainer register connects money received to the agreement that explains it, the QuickBooks record that holds it, each approved application to an invoice, and the balance still available. It prevents deposits from disappearing into income, sitting unidentified in a bank feed, or being applied twice. A virtual assistant can maintain the register and prepare application evidence; the owner or accountant decides classification, revenue timing, refunds, and corrections.

Why retainers become hard to follow

Service businesses often receive money before all contracted work is performed. A law firm may receive a client retainer, an agency may collect a project deposit, or a consultant may require an advance against future invoices. The words customers use are not reliable accounting instructions. “Deposit,” “advance,” “prepayment,” and “retainer” can describe different contractual arrangements.

Problems arise when the receipt, agreement, invoice, and ledger are maintained in different places. A bank-feed deposit may be added to sales without a customer assignment. Another user may create a credit for the same amount. Later, an invoice is reduced manually even though the retainer balance was never relieved. The customer statement can look settled while the general-ledger liability remains unchanged.

The register provides continuity. It does not impose an accounting conclusion. It records what was received, why the payer says it was sent, how QuickBooks recorded it under the approved workflow, and what later event supports an application.

Define the population from more than one source

Begin with the reviewer-approved retainer or customer deposit accounts in QuickBooks. Export their general-ledger detail for the review period and include an opening balance supported by the previous reconciliation. Then obtain the customer-level retainer report or supporting schedule, open customer credits, unapplied cash reports where used, bank deposits, and the contract or engagement repository.

Search bank receipts for descriptions associated with advances, but do not treat the search as complete. Some retainers may arrive through a merchant processor, be transferred from a trust or clearing account under an approved process, or be carried forward from an earlier system. Conversely, a receipt containing “deposit” may be payment of a completed invoice. Cross-reference sources and state the scope searched.

Record the cutoff and the file's configured time zone. Keep receipt date, bank settlement date, QuickBooks transaction date, agreement date, and application date separate. A single date column hides cutoff questions and makes later review difficult.

Design one row per receipt with a movement history

Assign a stable register ID to each receipt. Capture customer legal or account name, project or matter, agreement reference, amount, currency, payment source, bank reference, QuickBooks transaction type and number, holding account, restrictions stated in the agreement, and evidence links. Mask bank and customer information that the review does not require.

Under each receipt, record movements rather than overwriting the original amount. Useful movement types are approved invoice application, refund, transfer under an approved workflow, correction, and other reviewer-authorized adjustment. Each movement needs its own date, amount, target transaction, approval, and remaining balance.

For example, a design studio receives a 6,000 project retainer on September 4. The agreement references discovery, concept, and delivery milestones. Invoice 1048 for 2,200 is issued after discovery and the owner approves applying 2,200. Invoice 1071 later bills 3,000, but only 2,500 is approved for application because part of the work remains disputed. The register should show the original 6,000, applications of 2,200 and 2,500, and 1,300 remaining. It should not automatically clear the remaining amount merely because the second invoice exceeds it.

This movement structure also prevents double application. If both an invoice credit and a journal reduce the liability for the same milestone, the register reveals two movements tied to one approval.

Test every application against four facts

First, identify the source receipt and verify its remaining unallocated balance immediately before the application. Second, locate the invoice or other target transaction. Third, locate the agreement milestone, customer authorization, or internal approval required by the company's process. Fourth, trace how the approved application changed both the customer record and the relevant general-ledger account.

A match is incomplete if only the invoice total agrees. The application date, amount, customer, project, and ledger effect must also align. If QuickBooks uses a product or service item to move an approved deposit onto an invoice, preserve the configured item and account mapping. If the business uses another accountant-approved method, document that workflow rather than substituting a generic one.

QuickBooks publishes product guidance on recording upfront deposits or retainers. Consult the current QuickBooks retainer and upfront deposit guidance for mechanics, then follow the business's authorized setup. Product steps do not determine when the amount is earned under a specific agreement.

Reconcile customer detail to the general ledger

Roll the register forward from the prior supported total: opening unapplied retainers plus new receipts, less approved applications and refunds, plus or minus separately authorized corrections. Sum the remaining balances by customer and compare the result with the QuickBooks liability or designated holding account.

Investigate differences in both directions. A ledger amount with no register row may be an unidentified receipt or an old conversion balance. A register balance absent from the ledger may have been posted to income, applied without relieving the holding account, or omitted during migration. Do not add a plug row. List the amount, first known date, sources searched, and next owner.

Also compare the register with customer-facing records. A customer statement may show a credit that does not agree with the liability schedule. Preserve the discrepancy and confirm what the customer was told before any cleanup. Customer communication should be approved when it changes a balance or promise.

Separate refunds and disputes from routine applications

A refund request is not a completed refund. Record request date, requested amount, reason, approval status, payment reference when issued, bank settlement, and ledger effect as separate events. The person preparing the register should not release funds or promise a customer outcome without authorization.

For disputed work, freeze the relevant portion in an exception status such as “application disputed, owner review” rather than treating it as earned or refundable. Keep the underlying invoice and communication linked. Legal, contractual, tax, and revenue-recognition questions belong with qualified reviewers.

The IRS recordkeeping overview supports retaining documents for receipts and business transactions. For this process, the agreement, payment evidence, invoice, approval, and refund evidence form one chain. That chain supports review but does not itself settle the accounting policy.

Produce an owner-ready control packet

Summarize opening retainers, new receipts, approved applications, refunds, other changes, expected closing balance, QuickBooks balance, and unresolved difference. Add balances by customer and age, movements during the period, exceptions, source index, and evidence request list. Highlight negative customer balances, applications exceeding available retainers, dormant amounts, and unidentified receipts.

Each exception should ask a concrete question: Which agreement supports this receipt? Was invoice 1071 approved for a 2,500 application? Did refund confirmation 88 settle? Which customer owns this processor deposit? Specific questions reduce the risk that a reviewer approves a total without seeing the underlying issue.

After decisions are posted, re-run the customer and general-ledger reports and attach the approval. Carry unresolved rows forward with their original receipt date and history. A monthly cadence can measure unidentified receipts, applications awaiting approval, customer-to-ledger differences, dormant balances, and oldest evidence request.

QBOAssistant can organize the register, attach source records, trace approved movements, and maintain the exception queue without taking the owner's accounting decisions. Review virtual assistant services for QuickBooks workflows and the QuickBooks bookkeeping VA task guide, or request a consultation to define a retainer control that fits the business's existing approval process.

Sources

• QuickBooks: Record a retainer or upfront deposit
• IRS: Recordkeeping
• SBA: Manage your finances