Philippines staffing guide · 10 min read · Published November 10, 2026

Set a Purchase Order Matching Rule for Offshore Finance Support

Define the three-way match, set tolerances before invoices arrive, and route mismatches by cause so the offshore desk can prepare clean approvals.

On this page

The short answer

A purchase order matching rule tells an offshore finance desk how to compare the purchase order, the receipt, and the invoice before an invoice is approved for payment. Set tolerances for price, quantity, tax, and freight before the first invoice arrives, and route each mismatch by cause rather than by amount alone. The rule should separate data entry from approval and give every mismatch a named owner. Use offshore staffing services and the research library to connect the rule to the role's authority boundary. Review the mismatch log monthly so the same vendor or process does not generate the same exception.

Match the purchase order, receipt, and invoice before preparing payment.
Set tolerances for price, quantity, tax, and freight in advance.
Route mismatches by cause and keep approval with an authorized role.
Review vendor master changes and repeated mismatches every month.

Define the three records that must agree

The standard match compares the approved purchase order, the evidence that goods or services were received, and the vendor invoice. Each record must refer to the same vendor, the same items, the same quantities, and the same commercial terms. Write down which system is authoritative for each field so the team does not compare a draft with a posted record. If the organization uses a two-way match for services, state that exception and the evidence that replaces the receipt. The rule should also say what happens when a record is missing, because an absent receipt is not the same as an accepted delivery. A clean match requires a shared definition before it requires software.

Set tolerances before the invoice arrives

A tolerance is the difference the team may accept without escalation, and it should be agreed with finance and the budget owner before the invoice cycle starts. Set separate tolerances for unit price, quantity, tax, freight, and rounding rather than one blanket percentage. A small freight difference may be acceptable, while a quantity difference may indicate a short delivery that should be recorded. State the tolerance in the rule and show it on the matching worksheet so the preparer does not invent a judgment. Review the tolerances when a contract, tax rate, or shipping term changes. A tolerance that nobody can explain is not a control.

Route mismatches by cause, not by amount

A mismatch can come from a price change, a short shipment, a duplicate invoice, a tax error, a missing receipt, or a vendor master problem. Each cause has a different owner and a different fix. Route price mismatches to the buyer or contract owner, quantity mismatches to receiving, tax mismatches to the tax or accounts payable lead, and missing receipts to the requester. Do not send every mismatch to the same approver, because that person cannot fix a receiving error or a vendor record. Record the cause at the moment the mismatch is found. The cause code should be short enough to use consistently and specific enough to drive a repair.

Separate data entry from approval

The offshore desk can key invoice details, compare records, request missing receipts, and prepare a clean approval packet. It should not approve a payment or change a vendor master without the authority to do so. Mark the approval field with the role that owns the budget or the payment, and keep the preparer's name separate. If the same person both enters and approves, record the exception and treat it as a design issue. The approval packet should show the match result, the tolerance applied, the cause of any mismatch, and the evidence link. An approver should be able to accept or return the item without reopening the vendor file.

Handle partial receipts and backorders

A partial receipt is not a mismatch if the purchase order allows it. Record the quantity received, the quantity outstanding, and the expected date for the balance. Match the invoice only to the quantity that was actually received, unless the contract requires progress billing. For a backorder, show the open quantity and the next delivery date so the approver can see what remains. Do not pay the full invoice because the vendor sent it early. If the vendor bills the full amount, route the difference as a timing item with a named owner. Review open receipts at month-end so a partial delivery does not disappear from the match queue.

Keep a mismatch log with a named owner

Every mismatch should leave a short record: the invoice, the purchase order, the receipt, the field that differed, the cause, the owner, the action, and the date closed. Do not store the entire invoice in the log when a link is enough. Use the log to see which vendors, buyers, or receiving locations generate the most exceptions. A repeated price mismatch may mean the contract was not updated, while a repeated missing receipt may mean the receiving process is not followed. Review the oldest open mismatch each week and escalate when the owner does not respond. The log is useful only if it closes items rather than accumulating notes.

Review vendor master changes

Many payment errors start with a change to the vendor master rather than with the invoice. Require a second review for changes to bank details, tax identifiers, remittance addresses, and payment terms. Compare the request with the vendor's existing record and with an independent confirmation where the risk is high. Record who requested the change, who verified it, and when it took effect. The offshore desk may prepare the change but should not approve its own update. Review the month's changes in a short report and look for urgent requests, new contacts, or altered bank details. These are common fraud signals and deserve a separate check from routine invoice matching.

Test the rule on a sample each month

Select a sample of paid invoices each month and re-perform the match from the source records. Include a normal invoice, a partial receipt, a tolerance case, a mismatch that was resolved, and a vendor with a recent master change. Check that the approval was recorded, the evidence was available, and the cause code matched the actual issue. Ask the preparer and the approver to explain one case each without looking at the other's notes. Record the exceptions and fix the rule, the training, or the source process. A sample that only confirms clean invoices will not tell you whether the control works under pressure.

Sources and further reading

COSO Internal Control - Integrated FrameworkControl framework used to separate preparation, matching, and approval.
APQC Process Classification FrameworkProcess framework used to structure procure-to-pay tasks.
Association of Certified Fraud Examiners, Fraud resourcesPublic fraud guidance used to frame vendor master review.
U.S. Small Business Administration, Manage your businessPublic guidance used to frame payment controls.

Questions managers ask

Can the offshore desk approve an invoice below a small threshold?

Only if the organization explicitly grants that authority and records it. Most designs keep approval with the budget owner and let the offshore desk prepare the match and evidence.

What if the purchase order was never created?

Route the invoice as a no-PO exception to the budget owner. Do not create a retroactive purchase order without the required approval, because that defeats the control.

A practical decision framework

Define the task, evidence, authority boundary, reviewer, and stop condition before assigning live work. Test a normal case and an exception, then expand access or volume only after the evidence is consistently reviewable.

Compare offshore staffing services, review the research library, or request a role plan grounded in your systems and approval boundaries.