
Write a payment run checklist with a second reviewer
How to approach: Write a payment run checklist with a second reviewer
A payment run checklist should make the release decision visible. Cover the batch, the approvals, the bank file, and the confirmation. A run that depends on one person's memory is a single point of failure. Update the template when the same question appears twice.
Keep the checklist short enough to complete before the bank cutoff. The reviewer should be able to verify the key controls in minutes. A long checklist that is signed without reading is worse than no checklist. Keep the boundary visible in the place where the work is assigned.
Confirm the batch and the approvals
Compare the payment batch with the approved invoice list. Check the vendor, the amount, and the currency. A batch that includes an unapproved invoice should stop. Keep the original note beside the corrected version.
Confirm that the required approvers have signed. Record the names and the dates. A verbal approval is not enough for a payment run. Review the first few notes together before the process expands.
Check the bank file
Compare the bank file total with the batch total. Check the account, the currency, and the payment date. A file that is sent to the wrong account is hard to reverse. Separate what was observed from what was assumed.
Confirm that the file format matches the bank's requirement. A format error can delay the run or create a manual repair. The reviewer should see the file before it is released. A short note with four fields is easier to use than a long narrative.
Release and confirm
Record the time the file was released and the person who released it. Confirm that the bank received the file. A release without a confirmation is not complete. Keep the original note beside the corrected version.
Keep the bank acknowledgement with the run record. If a payment fails, the acknowledgement shows what was sent. The record should support a same-day repair. Use the same format for every handover so the next reader can scan it.
Review the exceptions
List the payments that failed or were held. Record the reason and the next step. A failed payment should not disappear from the run record. Separate what was observed from what was assumed.
Assign the follow-up to a named person. A failed payment that is not owned will become a vendor complaint. The review should happen before the next run. Update the template when the same question appears twice.
Review the checklist after the run
Ask the preparer and the reviewer what was unclear. Update the checklist based on the answer. A checklist that improves after each run is more useful than a perfect template. Name the owner in the same line as the action.
Keep the completed checklist with the run. A later audit may need to see who checked what. The record is the evidence that the run was controlled. If the source is unclear, route the question instead of guessing.
This note is operational guidance, not accounting, tax, legal, or security advice. Use the back office support service and read the GAO Green Book before turning the routine into policy.