Who Knows What in Accounts Receivable, and Where the Gaps Bite

Each role in accounts receivable holds only part of the picture. Billing knows what was promised. Cash application knows what arrived. Collectors know why customers are not paying. The ledger team knows what was posted. Trouble starts wherever one role acts on another's incomplete view.

Billing knows the deal behind the invoice

The people who set up receivables and issue invoices know the terms. They know which customer is on an instalment plan and which invoice carries an administrative fee. They also know which charge was keyed in late because the request came through an email and not the proper form.

None of that travels well. An invoice shows an amount and a due date. It rarely shows that the customer negotiated a partial credit by phone, or that a recurring bill was generated from a stale cost figure. When the payment later arrives short, the person matching it has no way to tell a dispute from a mistake.

Cash application reads what the money says

The clerk applying remittances sees the raw evidence. A payment comes with a scrawled reference, or none at all. A cheque bounces. A customer pays three invoices in one lump and leaves the clerk to guess the split.

This role knows which customers never send remittance detail and which bank feeds drop the payer name. It also knows how often items land in unapplied cash or get booked as miscellaneous receipts because nobody could tie them to an agreement. That knowledge is mostly tacit. It lives in habits and personal spreadsheets.

The sharpest problem here is allocation order. Where policy says a payment goes first to penalties, then fees, then interest, and only then to principal, the clerk applies it that way. The customer often believes the whole amount cleared the bill. Collectors then chase a balance the customer insists is paid, and both sides are partly right.

Collectors carry the reasons

Collections staff talk to debtors. They learn that a payment is held because a delivery was wrong, or that the contact who approved the purchase has left. They hear about disputes long before anyone raises a credit memo.

That context seldom reaches the system in a usable form. Notes sit in free text. A promise to pay is logged, but the underlying dispute is not coded. When a receivable ages past the point where policy says it should be referred for delinquent debt collection or written off, the decision gets made on age alone. The collector who knew it was a pricing argument may never be asked.

The ledger team sees totals without stories

General ledger accountants receive summarised activity from the subledger and post it. They reconcile the control account at period end. They know when the subledger and ledger disagree, and they know which manual journals were needed to force them to agree.

What they lack is the cause. A variance might come from a returned cheque reversed in one system and not the other, or from an adjustment posted after the period closed. The accountant can see the gap. Tracing it back means interrupting cash application or billing during their busiest days, so the fix is often a plug entry and a note for later.

Policy owners write rules for work they rarely see

Whoever sets credit terms, interest rules and write‑off thresholds usually sits furthest from daily handling. Their policies assume clean data: every payment identified, every dispute logged, every customer on standard terms.

So exceptions pile up quietly. Staff develop workarounds that keep the process moving and make the official policy look like it works. Reports built on that policy then describe an ageing profile that is partly fiction, and leadership makes provisioning and collection calls from it.

Where the splits do the most damage

Most trouble clusters at handoffs. Short payments bounce between cash application and collections because neither can see the other's evidence. Credit memos are agreed by collectors but entered by billing, sometimes much later, so the customer's statement stays wrong. Intercompany or intragovernmental balances drift because each side records performance and settlement on its own timing, and reconciliation only surfaces the mismatch at close.

Reporting suffers last and worst. External receivable reports and credit bureau submissions draw on the subledger as it stands. If disputes are not coded and unapplied cash is not cleared, those reports can label a customer delinquent who has, in substance, paid.

Questions to ask the people who run it

The documented process and the lived one usually differ. These questions tend to expose the gap:

• When a payment arrives with no usable reference, what happens to it, and who eventually decides where it goes?
• Which customers or payment channels cause the most manual matching work?
• How does a collector find out that a credit was agreed, and how long before billing records it?
• Where are dispute reasons kept, and could anyone report on them today?
• When a cheque is returned, which systems get updated, and in what order?
• What manual journals does the ledger team post every close to make the receivables control account agree?
• Which policy rules get bent most often, and who approves the exception?
• Do customers understand how their payments are allocated across fees, interest and principal?
• Before a receivable is referred for collection or written off, who reviews the account history?
• What does each person keep outside the system because the system cannot hold it?

The answers to that final question usually mark exactly where a redesign should start.

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.