What a gap in the receipt sequence does—and does not—prove

Receipt sequence completeness is a useful control because every issued number should have a status. A missing number, however, is the start of a question rather than proof that cash was taken.

Establish what generates the number

Some systems reserve a receipt number when payment begins and leave it unused after a failed transaction. Others assign a number only after confirmation. Manual books have a different risk: physical leaves can be removed or spoiled. Document the generation rule before interpreting the gap.

Account for every status

Build a sequence schedule that distinguishes issued, voided, failed, unused and duplicate numbers. For voids, inspect the original record, reason, user, timestamp and approval. A high void count may indicate poor application-category setup even where every amount reached the bank.

Join sequence testing to money testing

Trace surrounding receipts to settlement and compare daily control totals. Search application records for the absent reference and inspect user activity for that time. If cash collections are involved, include cash-up, custody and deposit evidence.

Report the supported conclusion

Possible outcomes include a documented system reservation, an authorised correction, a missing control record, or an unexplained gap requiring further investigation. Those outcomes are not interchangeable. State the financial effect separately from the control weakness.

A well-kept sequence register saves later effort. It should be reviewed daily by someone independent of receipt issue, with old unresolved statuses carried to a visible exception list.