When a fraud case closes but the ledger never hears about it

The most common failure is a split between the case file and the books. Investigators resolve a disputed or fraudulent payment and mark the case closed, but nobody posts the matching entries. The loss, recovery or reversal sits unrecorded, and reconciliations quietly stop agreeing.

How it starts

Fraud and dispute work usually lives with a different team from the one that posts to the general ledger. A bank flags a suspicious debit, or a supplier claims a payment never arrived, and someone opens a case in a tracking tool, a shared mailbox or a spreadsheet. The case owner contacts the bank, freezes the account and requests a recall. All of that is operational. None of it moves a balance.

The accounting consequences arrive later. A recall succeeds and cash returns to the bank account with a reference the cash application team does not recognise. A recall fails, and the payment becomes a loss that should be written off or held as a receivable against the payee. A dispute settles with a partial credit. Each outcome needs a journal, and each journal needs someone who knows the case exists.

The handoff breaks when closure in the case tool is treated as the end of the job. The investigator considers the matter finished. Finance assumes the investigator will send something over. Nobody owns the gap.

How it gets noticed

Rarely by the case team.

The first symptom tends to appear in bank reconciliation. An unidentified receipt lands in suspense, or an outgoing payment that the bank reversed still shows as cleared in the payment system. Reconcilers park these items with a note and move on, and the notes accumulate.

A second route is the payment audit. When disbursement detail is compared with ledger balances, an invoice shows as settled even though the supplier never received the money and a replacement payment has since gone out. On paper, the same obligation has now been paid twice.

Auditors find whatever is left. When they request the population of fraud cases and trace each one to the ledger, they expose cases with no entry at all, entries with no case behind them, and receivables from fraudsters carried at full value with no allowance against them. Improper payment reports also come out wrong. The payment system records what was sent, the case log records what was lost, and the two are never compared.

Fixing the open cases

Start with a reconciliation between the case list and the ledger, one case at a time. Pull every case closed since the last point where the books were known to be clean. Tag each one with its financial outcome: recovered in full, recovered in part, lost, or reissued to the genuine payee. Then look for the posting that should match it.

For recovered funds, find the receipt sitting in suspense and clear it against the original payment or the receivable. For losses, decide whether a claim against the payee or the bank is realistic. If it is, book a receivable and record an allowance for the portion unlikely to return. If it is not, write it off through an approved manual journal that cites the case reference. Where a replacement went to the real supplier, check that the original invoice no longer shows as paid by the fraudulent transfer.

Some cases will have no usable evidence. Escalate those to the controller for a judgement before anything is posted, and document the reasoning, because auditors will ask for it.

Stopping it coming back

The durable fix is a rule that a case cannot close until its financial outcome is recorded and a ledger reference is attached. Build that field into the case tool and make it mandatory. Assign the posting to a named role in finance, not to whoever happens to read the email.

Carry the case reference through every journal and payment adjustment. One shared identifier lets a reconciler search suspense, lets an auditor trace the population, and lets reporting teams count losses the same way. A regular session where case owners and reconcilers walk the open items together also pays off. These items are cheap to clear while fresh and painful once nobody remembers them.

Questions to ask the people who run it

• When a case closes, what does the case owner actually send to finance, and to whom?
• Who decides whether a lost payment becomes a receivable or a write off, and is that decision written down anywhere?
• How does cash application recognise money returned through a bank recall?
• Which suspense items carry notes mentioning fraud, disputes or recalls, and why are they still open?
• When a replacement payment goes out, what happens to the original invoice record?
• Does anyone keep a private list of cases alongside the official tool, and do the two match?
• What happens to a case that arrives by phone or while the tracking tool is unavailable?

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.