Guides

How to find what's wrong in finance data — by hand first, then with the detection rules that run the same checks continuously. One detection rule explained properly each week.

• Rule of the week: Cross-Method Duplicate

  You're reconciling the credit card statement, and a payment to a supplier catches your eye because you're almost certain you already paid them that exact a

• Rule of the week: Invoice Number Reuse

  You're reconciling payables for the month and you notice invoice INV-2041 sitting in the ledger twice. Same number, same amount pattern roughly, but one is

• Rule of the week: Same Amount + Similar Vendor

  You're reconciling the payments run and something in the amount column repeats: $2,340.00, twice, twelve days apart. The vendor names don't quite match — o

• Rule of the week: Exact Invoice Match

  You're doing the monthly supplier reconciliation and a payment run from six weeks ago catches your eye. Same vendor, same amount, sitting two lines apart i

• Rule of the week: Same Amount + Vendor Within Window

  The duplicate payment that invoice-number matching misses by design: same vendor, same amount, different reference — how to find it by hand, and how DUP-002 flags it.

• What is duplicate payment detection?

  How duplicate payments happen, how to find them by hand in any ledger, and where automated detection genuinely helps.

• Finanomaly vs manual audit sampling: what each actually catches

  An honest comparison of full-population anomaly detection against traditional audit sampling — and why auditors will keep sampling regardless.

• What is segregation of duties in bookkeeping?

  What segregation of duties means in a finance function, what it looks like in a small team where full separation is impossible, and how to detect breakdowns.