Where cash management breaks down

Cash management usually breaks where information crosses a team boundary. Receipts arrive without remittance detail, payments get released outside the approval path, and forecasts are built from data other teams never send. Each failure leaves traces in suspense accounts, reconciliations and late adjustments, and those traces are worth looking for first.

Receipts that cannot be matched

Money lands in the bank before anyone knows what it is for. A customer pays several invoices in one transfer. A cheque arrives with no stub. A public payer sends a fee with a reference that matches nothing in billing. The cash is real, but receivables cannot apply it, so it sits in an unapplied or miscellaneous account while someone researches it.

The workaround is usually a shared inbox or a spreadsheet of "unknowns" that collections staff work through when they have time. Watch for a suspense balance that never quite clears. Watch also for customers being chased for invoices they already paid. When the allocation rules are unclear, staff guess where money should go. Penalties, interest and principal then get applied in different orders by different people, and the disputes that follow are hard to unwind.

Returned items and reversals

A returned cheque or a recalled transfer has to reverse a receipt that may already have been applied, reported and forecast. The bank notifies treasury. Receivables owns the customer. Accounting owns the entry. Often nobody owns the whole reversal.

The tell is a reconciling item that ages on the bank reconciliation with a note such as "NSF, follow up." A customer account that shows as paid while the bank shows the funds gone is another sign.

The reconciliation that runs behind

Daily cash positioning depends on knowing what cleared yesterday. In practice, matching bank activity to the ledger often happens at month end, by hand, in a workbook that one person understands. The daily position is then an estimate dressed up as a fact.

Symptoms include treasury keeping its own cash balance that differs from the general ledger, and reconciliations signed off with a long tail of "timing differences" that turn out not to be timing at all. If auto-matching rules exist but the exception queue is ignored, the tool is doing little.

Forecasts nobody feeds

A cash forecast is only as good as the inputs from payables, payroll, tax, procurement and the business units planning large purchases. Those teams rarely see the forecast as their job. Treasury ends up projecting from history and phoning around before key dates.

The clearest sign is a large disbursement or deposit that treasury learns about on the day it hits. Forecasts that are rebuilt from scratch each cycle point the same way, as does a variance analysis that nobody performs because the forecast was never trusted. When large requirements are reported informally by email or in a hallway, they get missed when the right person is away.

Payments released around the controls

Electronic transfers have the strictest controls and attract the most pressure to bypass them. Urgent vendor payments, intercompany moves and wires requested late in the day push people toward shortcuts. One approver gets a shared login. A callback to confirm changed bank details is skipped because the request "came from the controller."

Look for templates edited outside the change process, approvals logged after release, and payments sent from a bank portal that bypass the payment system entirely. Each of these turns a fraud risk into a matter of luck.

Bank accounts and fees nobody owns

Accounts get opened for a project, a subsidiary or an acquisition and are never closed. Signatories leave and remain on the mandate. Fee statements arrive in formats that resist comparison, so they are paid without review.

An account with a small idle balance and regular fees is a reliable clue. So is a bank analysis statement that no one can explain line by line, or a pricing agreement nobody can locate. Fee errors are common, and banks rarely correct them unprompted.

Cash entries that reach the ledger late

Interest, sweeps, investment maturities and bank charges all need accounting entries. When treasury records them in its own system and passes a summary to accounting at period end, the ledger is wrong for most of the month. Management reports drawn from it mislead anyone relying on them.

Watch for recurring manual journals labelled "treasury true up," and for cash equivalents valued differently by treasury and accounting.

Questions to ask the people who run it

The written procedure and daily practice often part ways. These questions tend to surface the difference:

• When money arrives that nobody recognises, where does it go first, and who decides what it is?
• What happens on the morning a cheque comes back unpaid? Who hears about it, and who tells the customer?
• Which bank balance do treasury staff actually trust when deciding to invest or borrow?
• Who warned treasury about the last unusually large payment, and how did that warning arrive?
• Has a payment ever gone out before every approval was recorded? What made it necessary?
• How are changes to a supplier's bank details confirmed when the requester is senior or in a hurry?
• Which bank accounts would staff close tomorrow if anyone let them?
• Who reads the bank fee statement, and what do they compare it against?
• What spreadsheet would cause the most trouble if its owner left?
• Which journal entries get made every month that the system should be making on its own?

Answers that begin with "usually" or "it depends who is in" mark the places where the process relies on memory instead of design. Those are the places to fix before anything else changes.

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.