Reconcile the last payroll card batch by state of payment, not just by total dollars. A file containing a rejected credit and a duplicated credit of identical size can still balance as a dollar total. If you only compare the bank debit with the upload total, you may miss both errors.

Keep the three evidence layers separate

Expected
The approved payroll register, including credits deliberately moved to another route.
Accepted
The outgoing route’s accepted payment records, with separate rejected and unresolved entries where reported.
Confirmed
Posting or another verified final status plus documented exceptions and replacement actions.

Use the employer’s minimum necessary identifiers inside approved systems. A shared dashboard can show status counts and exception deadlines without displaying employee names, account numbers or exact wage amounts to people who do not need them. The Department of Labor’s FLSA recordkeeping fact sheet is a useful starting point for distinguishing a payroll register from evidence created solely for the transition.

Worked example: the totals agree and two cases remain

Suppose two synthetic workers are due USD 280 each. Worker A’s credit is posted twice and worker B’s is rejected. The amount debited can still equal USD 560. A per-record reconciliation identifies a duplicate and an unpaid worker rather than recording a clean batch. Escalate both items through approved recovery and wage-correction procedures rather than deducting a value from another worker’s pay or attempting an unverified reversal.

Record the last verified status and the owner of each exception. If an item is still open after contract access ends, test how the authorized employee will obtain the next update. Do not mark the case resolved just because it moved to a different vendor queue.

The output is a short handover record: approved control totals, treatment of unresolved entries, and who can verify remaining evidence. Pair it with the evidence export and final-pay route.