01
Name the run
Which application proposes vendor payments, which legal entity, and which completed batch you want reconstructed. We confirm read-only access and a named AP owner before sampling starts.
Payment runs
Four steps from a completed batch to a pack a sitting can read
A working method we use on vendor payment applications in Malaysia—not a generic process poster.
The run
What we reconstruct
A payment run is the batch your application proposed, approved, and released to the bank. We sample invoices inside that batch and write the path each one took. The method frames the sample; it does not replace your application data.
02
Pull the batch
We select invoices across amount bands, new vendors, and rush payments. Each item is followed from match status through proposal, approval, bank file, and confirmation.
03
Write the pack
Working papers name the document, the user, the timestamp, and the next status. Screenshots illustrate the path; they do not replace the sample.
04
Walk it through
AP, treasury, and internal audit sit with the pack. We mark keep, split, or reconfigure items someone can put on a change window before the next payment calendar.
Where teams usually start
Displayed memo, live path
The help screen shows two approvers. Sampled proposals follow acting roles. A reconstruction starts with the completed batch, not the policy PDF.
On-screen total, different file
Proposal totals match the AP listing. The generated bank file is the instruction. Integrity reviews sit beside the reconstruction when treasury needs both.
Match warning, still paid
Three-way match that only prints a message is a suggestion. Match-control testing asks whether the application blocked, parked, or let a clerk continue.