Keep the invoice separate from the obligation

An invoice is a vendor's claim. The obligation is what the company agreed to buy, at the agreed price, under the agreed terms. A mismatch review starts by putting those two records side by side rather than treating the invoice as the source of truth. The reviewer should be able to point to the purchase order, contract, statement of work, or approved rate card that supports the amount being billed. A Philippines-based finance administrator can retrieve the obligation, compare the line items, calculate the difference, and prepare the exception. The administrator should not approve payment, release a hold, or tell the vendor that the invoice is correct. Payment approval belongs to the authorized finance owner, and the evidence packet should make that decision easier without making it for them.

Match on the right keys

Use the vendor identifier, the purchase order or contract reference, the period, the currency, and the line-item description. A matching invoice number is not enough if the vendor bills under several entities or contracts. A matching total is not enough if the line-item mix is wrong. Record the key used and the fields that matched so a later reviewer can reproduce the comparison. Watch for common traps: a credit note applied to the wrong period, a currency conversion that uses a stale rate, a quantity that includes a backorder, a tax line that should be reverse-charged, or a service period that overlaps a prior invoice. These are classification questions, not arithmetic errors. The packet should name the trap and route the policy question to the owner who can answer it.

Classify the mismatch before writing to the vendor

A useful classification list includes price mismatch, quantity mismatch, missing receipt, duplicate invoice, wrong entity, wrong period, tax or currency difference, and documentation gap. Each class has a different owner and a different next step. A price mismatch may need procurement; a missing receipt may need the receiving team; a duplicate may need the payment team to confirm whether the first invoice was paid. Do not send a vendor a generic message that says the invoice is wrong. State the specific line, the expected value, the source of the expectation, and the question the vendor needs to answer. Copy only the people who need to see the vendor communication. Keep the internal packet separate from the external message so internal comments and unresolved suspicions are not sent by accident.

Build the evidence packet

The packet should contain the invoice image or approved electronic record, the obligation, the receipt or acceptance evidence, the calculation of the difference, the classification, the prior correspondence, and the proposed next action. It should also show the payment status and any hold already applied. A reviewer who has never seen the vendor should be able to understand the case in a few minutes. Record the observation time and the source system for each item. If a document is missing, say whether it was requested, not received, or unavailable in the system. Do not mark a missing receipt as 'not delivered' unless the receiving record supports that conclusion. The difference between a documentation gap and a delivery dispute is important, and the owner needs to see which one is present.

Work a realistic price mismatch

A staffing vendor invoices 120 hours at a rate of 48 dollars per hour. The approved rate card for the period shows 45 dollars for the role, with a 48 dollar rate only for a different seniority level. The administrator matches the role, the period, and the hours, calculates the difference, and records that the hours and the service period appear correct while the rate does not match the approved card. The packet goes to the procurement owner with the rate card, the invoice line, the time records, and the question of whether an approved exception exists. The administrator does not pay the undisputed portion without confirming the approved process, and does not tell the vendor that the higher rate will be accepted. The owner decides whether to request a credit or approve an exception; the administrator records the decision and the corrected payment instruction.

Close on the ledger, not on the email

An invoice case is not closed because the vendor replied or because the owner sent an email. It is closed when the approved adjustment is reflected in the payable record, the vendor statement, and the payment instruction. Check that the corrected amount matches the approval, that the hold is released only by the authorized person, and that the vendor's next statement does not repeat the same error. Keep the original invoice and the corrected entry linked. If the vendor issues a credit note, record the note number and the period it applies to. If the dispute remains open, set a follow-up date and an owner. A case that disappears from the queue without a ledger change is not resolved; it is only hidden.

Review the mismatch queue monthly

Sample closed and open cases each month. Check the classification, the evidence completeness, the time spent waiting for each owner, and whether the same vendor or the same line item repeats. A pattern of duplicate invoices may point to a vendor process problem; repeated missing receipts may point to an intake problem on the company side. Fix the cause rather than only clearing the queue. Use a simple age bucket and a reason code so the review can see where cases stall. Do not average away a small number of high-value or high-risk cases. Report the count, the value, the age, and the owner for each material item. The finance owner can then decide whether to change the process, the vendor agreement, or the review cadence.

Sources and limits

The AICPA, the U.S. Government Accountability Office, and the Internal Revenue Service publish general guidance on internal control, records, and documentation. These references support good practice but do not determine the accounting treatment, tax treatment, or payment approval for a specific invoice. Sources: https://www.aicpa-cima.com/ https://www.gao.gov/products/gao-14-704g https://www.irs.gov/businesses/small-businesses-self-employed/recordkeeping