Running-Bill Errors That Quietly Lead to Recovery
Most bill recoveries are not fraud; they are arithmetic and sequence errors repeated across bills until an auditor adds them up. They are also entirely avoidable.
The order-of-deduction trap
A running bill must compute the cumulative value of work first, deduct previous payments to isolate this bill’s value, and only then apply statutory deductions. Engineers who apply deductions in the wrong order, or to the wrong base, create a small error that repeats on every subsequent bill and compounds into a visible recovery.
Writing the sequence on the bill — gross cumulative, less previous payments, less deductions, net payable — makes the error impossible to hide and easy to avoid.
Quantities and rates that drift from sanction
The other recurring cause is paying for a quantity that has crept beyond the sanctioned estimate without a revised sanction, or a rate that does not match the agreement. Each looks minor on one bill but is exactly what an auditor reconstructs across the whole work.
Checking every bill back to the measurement book, the agreement and the sanctioned quantities — the same three documents an auditor uses — is what keeps a file clean from the start.
What is the right order of deductions on a running bill?
Cumulative gross value first, then deduct previous payments to get this bill’s value, then apply statutory deductions to that. Applying deductions to the wrong base repeats across bills and compounds into a recovery.
How do you avoid quantity-related recoveries?
Keep quantities within the sanctioned estimate or obtain a revised sanction, and match every rate to the agreement. Check each bill back to the measurement book, agreement and sanction — the same documents an auditor uses.

G