Lessons · Accounting · amounts that stop just short of needing approval
Amounts that stop just short of needing approval
Where a threshold triggers approval, a second signature or a competitive process, amounts cluster just below it far more often than chance allows. The clustering is the signal, and it is counted rather than sensed.
Hone is a place to practise a career, one idea a day. This is one of its lessons, written out in full and free to read without an account.
In beta. This lesson was written for Hone and has not yet been checked by a qualified accountant. Practice material, not professional advice. What that means.
What it is for
It is one of the few tests that is both simple and hard to explain away, because the threshold is arbitrary from the transaction's point of view. Genuine spending does not know where the limit is. It is also not automatically dishonest -- somebody may be avoiding paperwork rather than scrutiny -- which is exactly why it is a question rather than an accusation.
How to think about it
Take the threshold. Count the transactions in a band just below it, and compare that with what the rest of the distribution would predict. Investigate the excess, and ask what the approval was avoiding before assuming it was avoiding anybody.
Worked example
A threshold that triggers approvalArbitrary, from a transaction's point of view.
Count what sits just below itA band, not a single value.
Compare with what the distribution predictsThe excess is the signal.
Avoiding paperwork is a real explanationAnd it is still worth knowing about.
Your turn
Name what is compared against the count just below a threshold.
Compare the count with what the rest of the predicts
Solve one, graded on the server
The trap
Treating every just-under amount as suspicious individually. Any one of them is nothing. The finding is the count against the expectation, and picking on a single invoice is both weak evidence and a good way to lose the cooperation you need.