Cutover weekend: five receivables checks before go-live
A short list for controllers pressure-testing a new receivables tracking application before cutover weekend.
Implementation teams track tickets. Controllers track cash. Before a receivables tracking application goes live, these five checks belong on the controller’s list — not buried in a technical runbook.
1. Opening balances that still age
Confirm open items land with original invoice dates, not the cutover date. Otherwise every balance looks “current” on Monday morning.
2. Credit holds that survive the move
Release a test customer from hold in the old system and verify the new application does not silently clear the block during migration.
3. Write-off paths with named approvers
Post a dummy adjustment in a non-production company and confirm the approval chain matches policy after role migration.
4. Collector lists on day one
Generate the same list collectors will use Monday. If it requires a manual filter nobody documented, fix the report before cutover — not after the first angry call.
5. A rollback sentence
Write one paragraph: if batch posting fails Saturday night, who decides to roll back, and which balances are authoritative. Ambiguity here costs more than a delayed go-live.
A readiness check from an outside reviewer is useful when the project team is too close to the build to see these gaps. It is not a substitute for user acceptance testing; it is a second set of eyes on the controls that protect receivables.