Philippines staffing guide
Prepare Vendor Invoice Packets for Three-Way Match Review
An assistant can assemble invoices, receipts, and purchase orders into a reviewable packet while finance keeps approval and payment authority.
Published · 8 minute read
On this page
Three-way matching sounds like a finance ritual until a duplicate invoice slips through. The packet that prevents it is built before anyone opens the accounting system: the purchase order, the receiving evidence, and the vendor invoice, each with a clear source and a person who can explain a difference. An assistant can assemble that packet without becoming the approver.
Define what makes a packet complete
A complete packet has a purchase order or approved request, proof that the goods or services were received, the invoice itself, and a note for any line that does not match. The proof can be a signed delivery note, a service acceptance email, or a timesheet, depending on the contract. Write these options down. Otherwise every vendor becomes a debate about whether a screenshot counts as receiving evidence.
Match line by line, not total by total
A total that matches can still hide a swapped quantity, a substituted item, or a tax line that was never quoted. The assistant compares description, quantity, unit price, tax, freight, and payment terms. Differences go into a variance column with the source that supports each value. Do not overwrite the invoice amount to make the packet balance; preserve what the vendor sent and show the correction separately.
Flag the patterns that warrant a second look
Duplicate invoice numbers, a new bank account, a changed remit-to address, round-number totals, and a vendor name that is one letter off are all reasons to pause. These are signals, not verdicts. The assistant records the signal and routes the packet to the finance owner rather than emailing the vendor to confirm banking details from an address in the invoice itself. That last step is a common fraud path.
Keep approvals with the budget owner
The assistant may confirm that the packet is complete, that the math is right, and that the contract reference exists. The budget owner approves the spend, and finance releases payment. Do not let a clean packet imply approval. State the separation on the cover note so a busy approver does not treat assembly as a recommendation. When an approver is unavailable, use the documented delegate, not an assumption.
Store evidence where the auditor can reach it
Attach the packet to the accounting record or link to the approved document store. Do not leave the only copy in a personal inbox or a chat attachment. Use consistent file names so a later reviewer can find the invoice by vendor and period. Remove unrelated personal data from the packet; the reviewer needs the transaction, not the vendor representative's home address.
Review exceptions monthly
Count packets that needed a correction, packets that arrived without receiving evidence, and duplicates caught before payment. Sample a few of each and ask whether the cause was a vendor habit, a missing field on the purchase order, or an internal process that lets work start before approval. Fix the earliest step that would have prevented the exception.