← All posts

2026-09-29 · 7 min read

Fraud Indicator Weighting: Why Math Outranks Metadata

How bank-statement fraud indicators should be weighted: balance-chain errors first, metadata flags second. A practical scoring model.

Not all fraud signals weigh the same. Math proves tampering. Metadata only suggests it.

Weight balance-chain errors highest. A broken running total means numbers changed. No innocent export causes that. One break outweighs three metadata quirks.

Weight payer and sequence anomalies next. Missing pages, date gaps, duplicate rows. These alter totals indirectly. They deserve half the weight of math.

Weight metadata lowest. Editor names, stripped fields, odd dates. Useful context. Weak alone, since banks re-export through odd software too.

A sound model: 60 math, 25 sequence, 15 metadata. Score 0-100. Route clean straight through. Review the middle. Reject math breaks fast.

FAQ

Why should number-totaling errors outrank metadata flags?
Balance breaks prove altered amounts. Metadata flags only prove odd software, which also happens on legitimate re-exports.
How should fraud indicators be weighted?
Roughly 60 percent balance math, 25 percent sequence and payer anomalies, 15 percent metadata. Every trigger should cite its rows.

Now try it on a real statement

Deleted after 24 hours.

Fraud Indicator Weighting: Why Math Outranks Metadata — Bank Statement Analyser