In short
- Compare the run with the last few runs for repeat vendors and amounts.
- Look for new or changed bank details since the last run.
- Check for open credits that should be applied first.
- Confirm the file total matches the approved run.
- The person releasing the file should not be the one who built the run.
What the check does
The check is the last point before money leaves. A payment run is the batch of vendor payments your team has assembled from invoices due for payment. Once the file goes to the bank, reversing a wrong payment takes phone calls and paperwork. A short review before release is cheaper than the cleanup.
Look at the run in context. Compare it with recent runs for repeat vendors and amounts that look familiar. Scan the vendor record for bank details that are new or changed since the last run. Check for open credits that should be applied before a payment goes out. Confirm the file total matches the approved run. These checks are a quick pass through the same file, not a rebuild.
AP teams get caught by ordinary mistakes. A duplicate invoice gets entered under a new invoice number. A supplier gets paid outside the normal run and then again inside it. A bank detail change sits in the vendor record with no note. A credit memo is open while the invoice is paid at full value. A line is added after approval. The reviewer's job is to spot the pattern before the bank acts.
Setting it up
Set a simple release routine. The builder assembles the run and gets approval. The reviewer receives the approved run and the payment file. The vendor change list comes too. The reviewer should have recent run history so the comparison is possible without chasing people. Keep the approved total visible next to the file total. That comparison catches late edits and file mix-ups.
Time the review close to the bank cutoff. A review done early in the day can miss changes made later. The person who builds the run should not be the person who releases it. Name a backup for the roles so the check does not disappear when someone is out. If your bank or your contract sets a cutoff, work backward from it and leave time for a callback on a bank detail change.
Keep evidence light but useful. Note the exceptions you cleared, who confirmed them and what you saw. A short note on the run is enough. For a bank detail change, call the vendor contact on file, not the phone number in the email that asked for the change. If the callback fails, hold the payment. The release step is a stop point, not a formality.
Where it falls short
The review sees only what is in the run and the records behind it. It won't catch an invoice that never made it into the system. It won't catch a missed credit that was never recorded against the vendor. It won't correct a wrong price on a purchase order. Those problems need checks earlier in the process, at invoice entry and vendor master maintenance.
New vendors are a weak spot. A fraudulent invoice can arrive with correct-looking bank details and clear the run because there is no history to compare. Match the invoice to a purchase order and a receipt where you have them. Require a separate approval for vendor master changes. The release review can confirm that the approval exists, but it cannot make the master data right.
Time pressure turns the check into a formality. A large run and a late approval can push a reviewer to skim, especially with a queue at the bank. Give the reviewer clear authority to stop the file. If the total does not match the approved run, hold it and find the line that moved. If a bank detail change cannot be confirmed, hold that vendor payment and release the rest only after the file is rebuilt and approved again.
Checking that it works
Track what the check stops. Keep a short log of held payments and cleared exceptions. Note near misses too. When a supplier calls about a missing payment, ask whether the review should have caught it. When a duplicate shows up in a later run, trace it back to the build step and the release step. Use those answers to change the checklist, not to blame the clerk.
Test the handoff on a completed run. Can the reviewer get the approved total without asking the builder? Is the vendor change list available before release? Does the payment file match the approved run? If any answer is no, the setup is the problem. Fix the handoff before adding more checks.
Ask the AP clerks where duplicates and wrong bank details come from. They see the messy invoices and the urgent emails. Their answers will tell you which part of the review needs more attention. Keep the routine short enough to survive a busy week. A check that gets skipped under pressure is not a control. A check that gets done every time, even when it is uncomfortable, is worth keeping.
Questions
Who should release a payment run?
The release should sit with someone other than the person who built or edited the run. That person compares the file total with the approved run and clears the exceptions. Name a backup so the check still happens when the usual reviewer is out.
What should I check before releasing a payment run?
Compare the run with recent runs for repeat vendors and familiar amounts. Look for new or changed bank details. Check open credits that should be applied first. Confirm the file total matches the approved run and hold anything you cannot explain.
Can a pre-release review catch duplicate payments?
It catches repeats that show up against recent runs or the vendor record. It will not catch a duplicate where the invoice is new and the vendor history looks clean. That needs invoice-level matching and a clear approval path for urgent payments.
What do I do if a vendor's bank details changed just before release?
Pause that payment and verify the change with a known contact from the vendor record. Do not use the contact details in the email that requested the change. Get the vendor master change approved separately, then rebuild and approve the run again.
Updated Nov 15, 2026. Figures on this page are calculated by ERPSav from the definitions shown. The explanatory text is drafted with AI from those figures and checked automatically before it is published. General information only, not legal, tax or financial advice.