The outcome.
Most receipts match themselves. The few that do not are where the controller’s week goes: the check that is $200 short, the wire with no reference, the payment from a client with nothing open. This capability puts all of them on one list after matching, with the evidence gathered and a proposed next step for each.
The controller spends the review deciding. The billing coordinator leaves with the exact questions to send. Unapplied cash stops drifting into month end. The list never applies a receipt, writes off a difference or issues a credit; people the firm names take those actions.
Who starts the work, and when.
The billing coordinator runs it once provisional matching is done and the clean matches are posted, each week and again before close. The controller reviews the list and decides each item. Account leads join on items that depend on what a client said.
What they supply.
- The receipts log, with remittance details and bank references.
- The provisional match results: matched, short, ambiguous or unmatched.
- The ledger or aging export after posting, plus 30 days of postings for the duplicate check.
- Each account lead’s notes and client correspondence: promises, queries, disputes and agreed discounts.
- The firm’s rules for short payments, disputes and write-offs.
What comes out.
An exception list for the controller. Each item gives the amounts, the evidence, the possible explanations, a proposed next step and who decides. It closes with the checks that found nothing and what could not be assessed.
Illustrative example with invented data. One week at an invented 60-person professional-services firm, after five receipts totalling $16,100.
Receivables exceptions for the controller: 25 September 2026
- Period
- Receipts 21 to 24 September. Ledger as of 25 September. Bank feed to 24 September.
- 1. Short payment
- Invoice 1042, Client A, $1,200. Check for $1,000 on 22 September, memo “Inv 1042”, applied by the billing coordinator under the remittance rule; $200 open. No agreed discount in the notes. Possible: short payment, a discount the client expects, a second payment in transit. Next step: billing coordinator asks Client A which applies; hold any reminder. Decides: controller.
- 2. Ambiguous receipt
- Wire for $5,600 on 23 September, no reference, payer not on file. Candidates: 1044 (Client D) and 1045 (Client F), each $5,600, each due 20 September. Neither account lead’s notes mention a payment. Next step: hold unapplied; billing coordinator asks the bank for originator details; both account leads check with their clients; hold reminders on both. Decides: controller.
- 3. Unmatched receipt
- $350 from Client J on 24 September, reference “retainer top-up”. No open invoice; no retainer terms in the files. Next step: Client J’s account lead confirms whether a retainer was agreed. Decides: controller.
- 4. Disputed invoice
- Invoice 1035, Client E, $3,800, 42 days past due. Note of 2 September: client queries phase-two hours. Not chased. Next step: account lead reports on the dispute. Decides: controller, on any credit.
- Checked, nothing found
- Duplicates: none among the five receipts or against postings from the last 30 days.
- Could not assess
- Whether Client A has a second payment in transit: the bank feed ends 24 September. Who sent the $5,600 wire.
Prepared for the controller to review. No receipt has been applied, written off or credited by this list.
Where it fits.
- Professional services, where retainers and partial payments are routine and the account lead often holds the explanation.
- Law firms, where one payment can cover several matters and billing needs the responsible attorney’s notes.
- Engineering firms, where retainage produces expected short payments that must stay apart from unexpected ones.
- Finance and accounting, which owns cash application and the close.
- Established businesses, where the same awkward items return every month.
- Acquisitions & integration, where two ledgers send more receipts that match neither cleanly.
What has to change for your company.
Your controller sets the rules: how a short payment is applied when the remittance names the invoice, the write-off amount the controller may approve, and how long unapplied cash may sit before it goes to the finance lead. Account leads record promises and disputes in one place the assistant can read. The assistant gets read-only exports and no access to post.
What has been checked.
Fully Powered AI wrote this capability template. It was editorially reviewed on 9 November 2026. It has not yet been tested in a client environment. It has not yet been tested as a packaged version in ChatGPT, Claude, Copilot or Gemini.
Testing in your environment means running it on a past month whose answers your controller already knows, with cases written in advance: a short payment, a receipt that fits two invoices, a disputed invoice, a duplicate and a missing account note. The controller compares each list with what was actually decided before anyone relies on it. Pilot acceptance-test preparation sets those cases up, and what we test before we call an AI workflow ready describes the record we keep.
Next step.
Bring one recent week of receipts and the exceptions your controller had to chase down by hand.
Related capabilities.
- Overdue-invoice follow-up preparation: the follow-ups that wait on these decisions.
- Weekly receivables summary: the page that reports each open exception and its owner.
- SOP exception capture: for the rules your controller applies from memory.
- The worked example: What a fully powered finance team knows before month end.