QuickBooks Online Cash Application Exception Review

August 23, 2026

Bottom line: every customer payment should be reviewed for correct application to invoices, and any unapplied, overpaid, or questionable allocation should remain a visible exception until an authorized reviewer directs the next step.

Sidebar: Cash received is not cash applied. The review closes that gap.

Why cash application deserves a dedicated exception review

Cash application is where bookkeeping meets client experience. A customer sends a payment, but the payment may not reference the invoice correctly, may cover two invoices partially, may include a fee deduction, or may arrive as a lump that the bookkeeper must split. QuickBooks Online can suggest an application automatically, and a bookkeeper can accept that suggestion quickly. When the suggestion is wrong, the customer's open balance looks incorrect, the aging is distorted, and the next collection call starts from the wrong number.

For a QBOAssistant client, the virtual assistant often prepares daily AR queues: payments received, deposits recorded, and applications proposed. The owner or AR lead retains authority over sensitive decisions such as writing off a balance, moving a payment between customers, or releasing disputed amounts. A cash application exception review preserves that separation. The VA records what was received and what was applied. The reviewer decides whether an open balance is a true receivable, a short pay that needs follow up, or an amount that should be applied differently.

Without a dedicated exception check, unapplied payments accumulate quietly. One customer has a 1,200 credit that should have cleared two invoices. Another has a payment applied to the oldest invoice when the remittance said to apply to the newest. These details matter when the owner decides collection priorities and when the accountant reviews receivables near close.

Build the population before reviewing

Start with a report set that defines the cash universe for the review date. Use the Payment and Customer Credit reports together with the Accounts Receivable Aging Summary and Detail for the cutoff, plus a Deposits listing for the same period from the bank or merchant processor. Export or save the population before changing any application. Record the preparation date, the filters used, the preparer name, and whether the pull is at the customer level alone or includes sub-customer and job levels. If class or location is used to partition AR, state whether those dimensions are included. That scope note prevents a later assumption that the entire AR was tested.

Group payments by customer and then chronologically. The useful grouping shows one customer and all payments received from that customer in the period, with each payment's received date, method, and reference number beside it. If a payment was split across invoices, keep the split visible rather than collapsing it to a single line. Collapse hides the very decision the reviewer needs to see.

State what is excluded and where it is reviewed elsewhere. For example, merchant fee netting or intercompany transfers may be handled in a separate packet, and direct deposits that did not yet clear the bank feed may be covered in the deposit tie-out. Naming the exclusion keeps the cash application review complete for its defined scope.

Capture the evidence for each payment

For each payment in the scope, capture internal and external support side by side. Internal support is the QuickBooks record: payment transaction ID, payment number, received date, customer and job, method, amount, amount applied, amount unapplied or credited, the specific invoices or credit memos it was applied to, the application date, and the user or process that recorded it. Where history is available, note whether the payment was manually applied or matched by an automatic suggestion.

External support is the remittance or collection source the VA used: check stub, locked box file, merchant settlement detail, lock notice, bank statement line, email remittance, or client portal export. If the customer communicated payment instructions, link the email or portal note that dictated the intended allocation. If the payment was adjusted for a fee or deduction, link the fee statement or deduction notice.

Add the evidence location to the queue so the reviewer can open the payment and the remittance together. Keep internal and external facts in one row so the reviewer does not hunt across tabs.

Check three elements for every payment. First, the payment amount should equal the sum of its applications plus any remaining unapplied amount, with no rounding hidden. Second, the applied invoices should be those the remittance intended, or the reason for a difference should be a documented question rather than a silent change. Third, the application date should be consistent with the payment receipt and period cutoff, especially at month end. Each check gets its own status so a reviewer can see at a glance whether the amount tied but the allocation still needs a decision.

Name the exception patterns plainly

Unapplied payment beyond the normal hold period is the most common exception. A payment shows 900 unapplied for ten days when the customer's invoices total 900. Record the payment reference, received date, unapplied amount, the open invoices available at receipt, and whether any invoice was already credited or disputed. Hold the payment in the queue as unapplied pending instruction rather than applying it to the oldest invoice by default. The reviewer may recognize a context the report cannot, such as a pending credit memo that will absorb the payment after approval.

Partial application with a small residual is another pattern. A payment of 2,000 is applied 1,870 to two invoices, leaving 130 unapplied. Look for a discount taken without approval, a fee deducted by a payment processor, or a short pay that the sales team already discussed. If a discount appears on the remittance, mark the exception as discount taken with a question about approval. If no reason is shown, mark it as short pay pending follow up. Do not absorb the residual silently.

Allocation to the wrong invoice is subtle but important. A customer paid invoice 2045 according to the remittance, but QuickBooks shows the payment applied to invoice 2048. Preserve the correct invoice number from the source, the invoice currently credited, and the aging impact of the error. A simple move requires reviewer confirmation when the invoices differ in age, dispute status, or terms, because moving the application changes collection priority and follow up ownership.

Overpayment and duplicate application form another exception class. The payment exceeds open invoices by more than the approved tolerance, or the same payment appears twice because a manual entry and a bank feed both created a receipt. Keep both payment IDs visible, total the customer balance across both, and escalate the duplicate question rather than deleting one transaction to trim the list.

Credit memo and refund interaction is a fifth pattern. A payment arrives after a credit memo was issued, or a credit is available but no payment has been linked to it. Review both together. Record the credit memo number, the reason it was issued if documented, and whether the payment should be linked to that credit or handled as a refund decision. Refund decisions require approval. The VA documents the options. The reviewer selects one.

Assemble the owner review packet

An effective packet fits on one working table with supporting links. Include a cover sheet with business name, period, cutoff, preparer, and reviewer. Add the population summary: total payments received, total applied, total unapplied, total overpayments, total partial residual amounts, and the aging balance before and after the proposed corrections. That header tells the reviewer how large the issue is before the row detail consumes attention.

The exception table itself should use one row per payment that is unapplied, partially residual, misallocated, overpaid or duplicate suspected, or entangled with a credit memo. Each row carries the payment reference, customer, received date, amount, amount applied, remaining unapplied, intended invoice or remittance instruction, actual invoices credited, evidence location, exception type, impact note, and owner. An impact note can be short and honest: leaves 1,200 credit on report, understates past due 45 days, risks duplicate follow up with customer, or blocks close until applied.

Include a cutoff note that defines whether payments received after the accounting cutoff belong to this period or the next. That sentence prevents a late-arriving check from being misread as a new exception when it is really a timing item.

Add a handoff section that separates handled items from waiting items. Use statuses such as correctly applied, unapplied awaiting instruction, partial residual pending discount approval, allocation correction awaiting approval, overpayment review pending, duplicate suspected, or linked to credit memo. Close an exception only when the corrected application is visible or the approved hold or refund instruction is documented.

Decide cadence and keep the review tight

For active AR clients, run this review weekly, before collection calls and before any management report that will be shared outside finance. The VA prepares the queue after the daily payment recording, captures remittance evidence, and drafts specific questions for each exception rather than one generic ask. The owner or AR lead reviews the queue on a fixed day, approves applications or moves, and notes any follow up task that the VA then adds to the collection packet.

At month end, rerun the population with the period cutoff. Confirm that every payment received in the period was either correctly applied or remains visible in the exception table, and that every open invoice reflects the correct remaining balance after approved moves. Archive the packet with the aging report export and the payment evidence links so the accountant can repeat the tie-out without rebuilding the population.

Quality checks for the reviewer are simple. Ask whether every unapplied balance was explained by an invoice shortage or a documented decision, whether every partial residual ties to a reason that has been approved or tasked, whether any payment was moved without a remittance link, and whether any write off was recorded without a second set of eyes. Sampling should favor large residuals, duplicate suspects, and payments applied near period end.

The QuickBooks bookkeeping VA service describes how preparation and approval should interact for AR work. For collection follow through, pair this lane with the QuickBooks AR aging review.

What good looks like

Good looks like a reviewer who can, in minutes, see which payments are cleanly applied, which need a simple move, which need a client conversation, and which need a credited decision elsewhere. Unapplied credits stop lingering as mystery balances. Customers stop receiving dunning notices on invoices they already paid because the cash was sitting in unapplied credit. And the close packet does not show receivables that should have been cleared by approved applications.

Next step

Pilot the review on one customer that generates several payments a week and one customer that often pays with remittance notes. Pull the last two weeks of payments for both, record the three checks per payment, and draft a concise question for each exception that would let the owner decide without reworking the file. Review the table for clarity. Keep fields that drove a decision, drop fields that produced noise, and reuse the approved template on the normal weekly cadence. That measured test creates a repeatable control around cash application without altering authorization inside QuickBooks Online.