Financial controls for a gateway cutover weekend
A checklist finance can own when a payment gateway application or processor path switches — before volume makes surprises expensive.
Technology teams rehearse deployments. Finance needs a parallel rehearsal for money movement. A financial audit mindset before go-live is less about perfection and more about knowing who acts when a batch fails at 02:00.
Name the authoritative file
On day one, which artifact wins if the gateway console and the bank disagree? Write it down. Ambiguity here creates duplicate postings or silent omissions.
Assign the first five settlement closes
Do not leave the first week to “whoever is on shift.” Name primary and backup owners for each close, including a holiday cover plan for Bangkok calendars.
Rehearse a failed batch
In UAT, force a settlement file delay and practice the communication path to customer support and seller management if payouts slip. The rehearsal often reveals that finance was not on the incident list.
Plan day-thirty, not only day-one
Chargebacks and delayed intercepts arrive after the celebration email. Your pre–go-live control check should include how those reverse into the new gateway path and who reconciles them.
If your cutover date is fixed, a short Pre–Go-Live Control Check can pressure-test this checklist against your actual files.