Who knows what in a financial fraud or dispute case

Payment staff know what left the account and when. Investigators know why it looks wrong. Accountants know how the loss must be booked. Each holds a piece the others need. Most trouble comes from cases that move between them without context, which leads to late write-offs and recoveries nobody posts.

The payments desk

Treasury and payment operators see the bank side clearly. They hold the payment file, the approval trail and the confirmation from the bank. They know whether a recall request went out and what the receiving bank said. They often spot a changed beneficiary account before anyone else does.

They rarely know whether the underlying invoice was genuine. They also do not see what the investigation has found. So they act on the money alone. A common failure is a quick reissue to the real supplier before anyone has decided who carries the loss. Another is a successful recall that never reaches accounts payable, so the invoice still shows as settled.

Accounts payable and supplier records

The payables team knows the commercial story. They can match the invoice, the order and the receiving report. They know who asked for the bank detail change and how the request arrived. They also know what normal looks like for each supplier.

What they lack is the bank position. When the genuine supplier chases payment, payables sees a paid status and says so. The supplier gets annoyed. Worse, a clerk may pay again to clear the complaint. Supplier record corrections also get made quietly. The original fraudulent change then disappears from view just when the investigator needs it.

The investigator

Whoever runs the fraud or dispute review knows the pattern. They see linked cases, the likely route in and whether police or an insurer are involved. They also know what must stay confidential, and that is where the friction starts.

Confidentiality makes them share less than finance needs. Accountants cannot tell whether a case is fraud, a processing error or a genuine commercial dispute. Each of those is booked differently. Without that signal, a fraud loss can sit for months as a receivable from a supplier who never owed anything.

The ledger and reporting team

General ledger staff know where the money has to sit at each stage. It might go to suspense, to a receivable, to an allowance for uncollectible amounts or straight to loss. They know the close calendar and what a manual journal voucher needs as support.

They seldom know the case itself. Suspense balances grow old with no owner. At close, someone books a provision with no case reference attached. When a recovery finally arrives, it lands as unidentified cash and is cleared to the wrong account. Payee tax reporting can also go wrong. The year end return may show the fraudster as paid and understate what the true supplier received.

Legal, insurers and the bank

These parties know the rules that decide whether money comes back. Insurance policies carry notification conditions and evidence requirements. Banks have their own recall procedures. Legal knows when a claim is worth pursuing and when it is not.

Finance often learns these conditions after they have lapsed. A claim is refused because notice was late or because the payment audit trail was not preserved in the form the insurer wanted.

Where the gaps actually bite

Case status usually lives in one tool and money status in another. Nobody owns the link between them. The most useful single fix is a case reference that travels with every related record. It should appear on the payment adjustment, the journal voucher, the receivable and any recovery receipt. With that in place, the reconciliation between the investigation log and the ledger becomes something a person can actually do.

Ownership of the decision on who bears the loss matters too. When that decision has no named owner, it defaults to whoever closes the period, and they have the least information.

Questions to ask the people who run it

Written procedures tend to describe the tidy path. These questions surface what really happens:

• When a payment is recalled, who tells payables, and how do they find out today?
• Where does a suspected fraud payment sit in the ledger on the day it is found, and who decides that?
• How does an accountant learn whether a case is fraud, error or dispute?
• What happens when the real supplier calls about an unpaid invoice that shows as paid?
• Who can change supplier bank details, and is the old value kept anywhere?
• When money is recovered, how does the person posting the receipt know which case it belongs to?
• Which insurer or bank conditions has the team missed before, and why?
• Who signs off the write-off, and what do they look at before signing?
• How are payee tax reports corrected when a payment went to the wrong party?
• Which suspense or clearing balances does everyone know about but nobody touches?

The answers usually disagree. Where they do, that disagreement marks the place to redesign first.

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.