Where collections breaks down: handoffs, exceptions and workarounds

Collections usually breaks where work passes between cash application, the collector, the teams who own the customer relationship and whoever approves write-offs. Unapplied receipts, disputes nobody owns and informal payment deals cause most of the rework. Each one leaves a trace in the ledger, the aging report or the correspondence file.

Cash that arrives but never lands on the account

The collector works from the receivables balance. That balance is only as good as cash application. When a payment arrives without a clear reference, it goes to suspense. Until someone researches it, the customer still looks delinquent.

Partial payments create a quieter problem. Policy may say receipts go first to penalties, then administrative charges, then interest, and only then to principal. If cash application staff apply everything to the oldest invoice instead, the account history stops matching what the customer was told. Returned checks add another loop. A bounced payment that is reversed late lets an account drop off the delinquency list, then reappear with no explanation.

How to tell: the unapplied cash balance keeps growing between closes. Collectors report calling customers who have already paid. Customers dispute interest figures more often than they dispute the underlying invoice.

Disputes that sit between teams

A collector often learns first that an invoice is wrong. The fix belongs to billing, sales or service. That conversation is where accounts go to wait. The collector cannot resolve it alone, and the other team has no target tied to it.

How to tell: the same accounts show up on every delinquency review with a note such as "awaiting credit" or "with sales." Credit memos arrive in large batches near period end. Dispute reasons are recorded as free text, so nobody can report on them.

Policy that exists only on paper

Most organisations have a written delinquency policy with escalation stages. In practice, collectors use judgment. Key accounts get exceptions granted by phone or in a hallway. Over time the documented process describes almost nothing.

How to tell: dunning letters are suppressed by hand. Accounts are held out of escalation with no approval on file. Two collectors treat similar accounts very differently.

Payment plans agreed off the system

Negotiated arrangements are often captured in an email or a personal spreadsheet. The receivables system knows nothing about them. It keeps sending reminders and accruing interest. The customer, who believes a deal was struck, complains or stops paying.

How to tell: a private tracker exists that only one person updates. Complaints mention a promise the system does not reflect. Plan payments land as unexplained partial receipts.

Adjustments and write-offs waiting for approval

Small residual balances pile up because nobody wants to sign off on them. Larger write-offs stall because the approver needs a history the collector never assembled. When adjustments do post, they are sometimes coded as revenue reductions when they belong in bad debt, or the reverse.

How to tell: the aging report carries a long tail of tiny balances. Write-offs cluster at year end. Reconciliation finds adjustments in the wrong account and reclassifies them after the fact.

The handoff to recovery and default

When an account goes to an outside agency or to legal, the file is often incomplete. Recovery staff then rebuild the history from scratch. Money recovered later may come back net of fees and sit unmatched, because nobody set up how to record it.

How to tell: defaulted accounts still accrue interest or still receive standard letters. Recovered amounts appear in suspense. The gross balance referred out never ties to what the agency reports.

Balances owed by related entities

Amounts due from other divisions or other government bodies behave differently. Delinquency is usually a disagreement about whether the order was delivered, not an inability to pay. Treating these like external debt wastes effort and strains relationships.

How to tell: intercompany or intragovernmental reconciliations show the same differences repeatedly. Settlements arrive that match no open receivable. Collectors chase internal buyers with external dunning letters.

Questions to ask the people who run it

The written procedure rarely matches daily practice. These questions tend to surface the gap:

• When a payment arrives and the account is unclear, what happens to it next, and who decides?
• Which accounts never go through normal escalation, and who told staff to treat them that way?
• Where are payment plans recorded? Could someone else find one if the person who agreed it were away?
• When a dispute needs another team, how is it handed over, and how does the collector know it was fixed?
• What balances does nobody want to write off, and why?
• What does the recovery agency receive when an account is referred, and what comes back?
• Which reports are rebuilt by hand before every review meeting?
• What would break first if the most experienced collector left?

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.