Research brief · Published
Payroll vendor invoice reconciliation evidence review
A review design for testing whether payroll vendor invoices match the contracted rate, the approved work, and the payroll records that justify the charge.

Research finding
Compare each invoice to the current rate card and the approved service scope.
Methodology
This brief triangulates the headline measure against official Philippine government, regulatory, development, and labor sources. It translates evidence into an operating control and separates context from recommendations.
| Measure | Interpretation |
|---|---|
| 4 evidence layers compared for every payroll vendor invoice. | Context signal for planning, not a promise about an individual worker or provider. |
| 4 source records | Primary source links are listed and numbered below for review. |
Key takeaways
- Compare each invoice to the current rate card and the approved service scope.
- Tie per-employee or per-pay-run charges to the payroll record that supports them.
- Check duplicate charges, credits, and minimum fees as separate review steps.
- Keep approval evidence for the work and for the payment in one file.
- Record findings by dollar impact and by the control that failed.
Question and scope
This review asks whether a payroll vendor invoice is supported by the contract, the approved work, and the payroll records. The scope covers payroll processing fees, per-employee charges, off-cycle run fees, tax filing fees, and related support charges for one employer. The unit is one invoice line for one billing period. The design measures evidence coverage and reconciliation quality, not whether the vendor is competitively priced. Results describe one employer review.
Invoice population
Build the population from the vendor invoices for the review period, not from a sample chosen by the vendor. Include recurring invoices, one-time project charges, and credits. Record the invoice number, period, amount, and service line. Check that the accounting system shows the same invoice and payment status. A missing invoice is a population gap and should stay visible in the review.
Rate card comparison
Compare each line to the current rate card and the contract terms. Record the rate that should apply, the rate charged, and the difference. Check minimum fees, tier thresholds, and any discount that depends on volume. A rate that changed mid-year needs a note showing the effective date. The comparison should show the arithmetic, not only a pass or fail.
Hours and headcount tie-out
Tie per-employee and per-run charges to the payroll register or headcount report for the same period. Explain a difference caused by a mid-period hire, a termination, or a separate pay group. Check whether off-cycle runs were approved and billed once. A charge that cannot be tied to a payroll event needs a vendor explanation. Keep the tie-out with the invoice so the next reviewer can repeat it.
Approval evidence
Confirm that the work was approved before it was performed. A project invoice without an approved scope or a change request is hard to challenge after delivery. Match the approver to the authority limit and the service owner. Record the purchase order or approval reference on the invoice line. Payment approval and work approval are separate decisions and both belong in the file.
Duplicate and credit review
Check for duplicate charges across invoices, especially when a service line is billed by both a platform fee and a per-run fee. Look for credits that were promised but never applied. Compare the invoice total with the prior period and ask about an unexplained jump. A credit that appears only after a dispute is a sign the review should happen earlier. Record every duplicate and credit with the resolution date.
Timing and accrual
Confirm that the invoice period matches the payroll period it supports. A charge for December work billed in January still belongs to the December accrual. Check cut-off entries and any prepaid amount carried into the next period. Record the accounting period and the payroll period separately. A timing difference is not an error, but an unexplained one weakens the reconciliation.
Evidence gates
Score each invoice line against four gates: a contract or rate reference, a payroll record tie-out, an approval, and a payment record. A line that passes three gates and fails one should be reported as a partial finding rather than a clean item. Keep the gates separate so a strong contract does not hide a missing approval. The score is a review aid, not a substitute for the reviewer's explanation.
Findings and severity
Classify each finding by dollar impact, recurrence, and the control that failed. A small recurring overcharge matters more than a one-time rounding difference because it repeats every period. Record the vendor contact, the requested correction, and the date of the response. Separate a billing error from a contract interpretation question. The finding should be specific enough for the vendor to correct or dispute.
Limitations
The review depends on the invoices and payroll records the employer can access. A vendor may combine services in a bundle that cannot be split cleanly. Contract terms can be ambiguous, and a rate comparison may not capture service quality. The design does not audit the vendor's internal records. State these limits and route contract disputes to the owner or legal adviser.
Decision and retest
Name the decision the review supports, such as disputing a charge, changing a billing code, or adding a pre-approval step. Record who accepted the finding and the expected correction date. Retest the next invoice to confirm the fix. If the same error repeats, escalate to the contract owner rather than reopening the same ticket. A review that only produces a credit does not fix the cause.
Vendor alignment
Share the reconciliation method with the vendor so future invoices arrive with the supporting detail. Ask for the payroll period, the employee count, and the service line on each invoice. Confirm who to contact when a line cannot be tied out. A vendor that understands the evidence standard sends fewer incomplete invoices. Put the expectation in the contract or the service schedule.
Sources
Prepare a vendor invoice reconciliation file
A Philippines-based payroll support specialist can collect invoices, tie charges to the register, and prepare the exception list for owner review. The specialist can also log duplicate charges and credits and request missing billing detail. Your finance or payroll owner still approves payment and disputes the vendor. Keep the reconciliation with the invoice so the next review starts from the same numbers.
Review payroll reporting supportFAQs
Should every invoice line be tied to an employee?
Per-employee charges should tie to the register or headcount report. Flat platform fees may tie only to the service period, so record the basis that applies to each line.
Who should approve off-cycle run fees?
The payroll owner who authorized the off-cycle run should approve the related fee. Keep the run approval and the invoice line linked so the charge can be checked later.
What if the vendor will not provide billing detail?
Ask for the minimum detail named in the contract or service schedule. If it is still unavailable, record the limitation and escalate to the contract owner.
For adjacent operating context, see Payroll Preparation and the payroll operations guide library.