Field note
Cut-off testing without chaos
Most close apps will happily mark cut-off as complete once invoice dates and shipment timestamps sit inside the period. That is necessary, not sufficient. Chaos starts when warehouse docs, carrier confirmations, and billing batches arrive out of order and the team “clears” whatever the UI lights up first.
Order the evidence, then the UI
We coach teams to freeze a cut-off packet in this sequence: goods movement extracts, carrier proofs for late-day shipments, billing batch IDs, then GR/IR aging. Only after those four land do we run the app’s cut-off diagnostic. If the diagnostic is green while a carrier proof is missing, the green is a hypothesis — not a conclusion.
Sample with intent
Pick the last business day and the first two days of the next period. Pull a stratified sample across high-value SKUs and rush orders. Document why an item was waived. Monthly Close Audit Mastery Module 3 walks this live with manufacturing-shaped data; SaaS teams should swap in deferred schedules but keep the same discipline.
What to refuse
Refuse verbal “we always bill next week” as evidence. If policy allows post-period billing for period shipments, write the policy ID into the waive reason so next month’s reviewer is not reinventing folklore.