Your Collections Process Is Probably Breaking at the Handoffs

A customer disputes a $36,000 invoice because the agreed discount is missing.

Accounts receivable emails sales. Sales forwards the message to the account manager. The account manager asks finance whether the discount was approved. Finance asks who can authorize a credit. Three days later, six people have seen the issue and nobody owns the correction.

The customer still sees an incorrect invoice. The aging report still sees an open balance. The company sees a collaboration problem.

It is really an ownership problem.

Collections stalls at handoffs because visibility is mistaken for accountability. Copying more people can make the issue easier to observe while making the next action harder to assign.

Collaboration is not ownership

Receivables work naturally crosses teams. Sales knows the commercial agreement. Delivery knows whether work was completed. Billing knows how the invoice was created. Finance controls accounting treatment. AR keeps the open balance moving toward resolution.

No single team can answer every question. That does not mean every issue should have several owners.

A handoff needs one current owner: the person accountable for producing the next piece of evidence, decision or correction. Other people can collaborate, approve or provide context. The owner remains singular until the return condition is met.

Without that distinction, “Sales is handling it” can mean five different things. Someone was copied. Someone acknowledged the message. Someone plans to ask a manager. Someone believes finance already fixed it. None tells AR when the invoice should return to the queue.

A shared inbox can show everyone the problem. It cannot decide who must make the next state change.

Six handoffs where collections commonly stalls

1. AR to sales: commercial disagreement. The customer claims the price, discount, term or scope differs from the agreement. Sales or an authorized commercial owner must confirm the deal. AR should request a specific decision and retain ownership of the receivable outcome.

2. AR to delivery or operations: proof of completion. The customer needs a signed timesheet, delivery evidence, service report, milestone approval or completion certificate. The operating team owns producing the evidence. AR owns sending it through the accepted channel and confirming the invoice can proceed.

3. AR to billing: invoice correction. A purchase order, legal entity, tax field, address or format is wrong. Billing owns the authorized correction. The handoff must state the exact mismatch; “customer rejected invoice” is not enough.

4. AR to finance leadership: exception decision. A customer requests a payment plan, credit, write-off or other treatment outside routine policy. The decision-maker owns approval or rejection. AR should not imply that a concession exists before the decision is recorded.

5. AR to cash application: payment claim. The customer says payment was sent or a candidate receipt appears. Cash application owns identifying payer, finding remittance and matching the receipt. External collection should pause when credible evidence warrants investigation.

6. AR to the account owner: relationship-sensitive escalation. A strategic customer stops responding, breaks commitments or raises a broader relationship issue. The account owner may choose the channel and join the conversation. The open balance, history and required outcome should remain explicit.

Each handoff changes the current blocker without changing the accounting truth. The invoice remains open until it is correctly resolved in the ledger.

Use a four-field handoff

Long notes are not required. Four fields are enough to turn a mention into a controlled transfer.

For the discount example, the record might read:

• Owner: Maya, account executive
• Requested action: Confirm whether the 7% implementation discount was approved for Invoice #8841
• Due or wake condition: Decision by Wednesday 2 p.m.; return to AR Thursday morning if absent
• Return evidence: Link to approved order form or written rejection from sales leadership

That handoff is small, but it eliminates ambiguity. Maya knows what decision is needed. AR knows when to resume. Finance knows what evidence can support an authorized correction.

A simple collections swimlane

A swimlane clarifies how ownership moves without pretending every invoice follows the same sequence.

AR lane: diagnose the blocker, assemble customer and invoice context, create the handoff, pause inappropriate customer contact, and verify the return evidence.

Resolver lane: accept the specific request, produce the decision, correction or evidence, and return it by the due condition.

Accounting lane: record authorized invoice, credit or payment treatment in QuickBooks. The operating record can request and track work, but it should not bypass accounting controls.

Account lane: coordinate relationship-sensitive communication when needed, without becoming an undocumented alternate collections system.

The lanes intersect at state changes. A dispute becomes decision pending. A decision becomes correction required. A corrected invoice becomes customer confirmation pending. A payment claim becomes matching in progress. Each transition should have an owner and evidence.

The goal is not bureaucratic routing. It is to prevent an invoice from disappearing between “I told them” and “I thought it was fixed.”

Make acceptance and return explicit

Many handoffs fail at the beginning because the recipient never accepts them. Email delivery is not acceptance. A shared task with no assignee is not acceptance. A Slack reaction is not necessarily acceptance.

The recipient should acknowledge ownership or reject the assignment with a reason. Rejection can be healthy when the wrong person was selected; silent ambiguity is not.

Return is equally important. “Done” should be accompanied by the evidence specified in the request. If billing corrected the entity, return the new invoice identifier or link. If sales confirmed a discount, return the approval. If delivery found a completion certificate, attach or link it.

AR then validates whether the blocker is actually removed. A document can exist but still be rejected by the portal. A corrected invoice can still use the wrong purchase order. The resolver produces evidence; AR confirms the receivable can move.

A 25-minute weekly handoff meeting

Meetings should not replace the protocol. They should address exceptions the protocol exposes.

A useful weekly agenda has five lists:

1. Handoffs past due without return evidence
2. High-value items with no accepted owner
3. Disputes waiting on commercial decisions
4. Payment claims waiting on matching or application
5. Repeated blockers that indicate a process defect

Do not review every overdue invoice. Start with broken ownership. For each item, decide whether to keep the owner, reassign it, change the requested action or escalate the due condition.

The meeting should end with changes in the record, not a second set of meeting notes. If someone accepts an action, update the owner and due date while the group is present.

Repeated blockers deserve process work. If five invoices wait for completion certificates every month, the answer is not faster internal chasing. The job-to-cash process should produce the certificate before billing or attach it automatically where appropriate.

Measure handoff health

Cash collection outcomes remain important, but handoff metrics reveal why a balance is stuck inside the company.

Track:

• Time from blocker diagnosis to accepted owner
• Share of handoffs with a requested action and due condition
• Time from acceptance to return evidence
• Handoffs returned incomplete
• Items reassigned more than once
• Open value waiting on internal action
• Recurring blocker type by team or process stage

Avoid rewarding teams for closing tasks without validating the receivable state. A sales task marked complete because someone replied “looking into it” has not resolved a commercial dispute.

The most useful measure is often aging caused by internal waiting. It makes visible how much of “customer lateness” is actually seller-side delay.

Use the tools you have, but define the record

A small team can run the protocol with QuickBooks links, a spreadsheet and a task system. Keep balances and accounting status in QuickBooks. Use one shared register for blocker, owner, requested action, due condition and return evidence.

Email and Slack can carry conversation, but the current state should return to the shared register. Otherwise the operating truth follows whichever person was included in the latest thread.

As volume and team size grow, a dedicated receivables workspace can connect account history, invoice context, internal handoffs and wake dates. The benefit is not another chat surface. It is a stateful operating record that survives inbox boundaries while continuing to defer financial truth to the ledger.

Whatever tool is used, preserve the central rule: one current owner, one requested action, one due or wake condition, and evidence that proves the handoff can return.

Document a backup owner for absences, but do not make both people concurrently accountable. The backup rule should activate when the primary owner is unavailable or the due condition is missed. This keeps urgent work moving without recreating the ambiguity the protocol is meant to remove. For recurring handoffs, publish a simple routing map so collectors know which role accepts pricing questions, completion evidence, billing corrections and payment matching before the next exception arrives.

Review that routing map whenever responsibilities or approval limits change; stale ownership guidance creates the same delays as having none.

Return to the discount

With the protocol, the original $36,000 dispute moves differently.

AR records the claimed 7% discount and links the customer email. The account executive accepts ownership of the commercial decision due Wednesday. She returns the signed order form showing the discount. Billing receives a separate request to issue the authorized correction. QuickBooks remains the authority for the revised transaction. AR sends the corrected invoice, confirms customer acceptance and sets the next wake condition.

Several people still collaborate. At every moment, only one person owns the next state change.

That is the difference between a thread and a workflow.