Operational case file
Case File: One Real Transaction Was Entered Twice
A duplicate entry can make expected cash or float move twice even though the customer transaction happened only once.
Evidence basisDuplicate transaction recording has appeared during field reconciliation. The important control question is whether there were two real provider movements or one real movement recorded twice.
Why duplicates distort expected balances
Reconciliation calculates expected balances from recorded movements. If one real transaction is entered twice, the expected side can become wrong even when the actual cash and provider statement are correct.
Control lesson
Compare references, amount, provider, time and counterparty evidence before deleting or reversing anything. Preserve an audit trail of the correction so the owner can see what changed and why.
This case publishes the control principle without customer names, transaction references or proprietary app implementation.