Direct answer

What this role should do

A price variance review compares the invoiced unit price with the current purchase order and the approved change history. It separates price from quantity and freight, documents the buyer decision, and updates the order only through the authorized owner.

Set the tolerance before the invoice

A variance is only meaningful against a stated tolerance. Record whether the company allows a percentage, an absolute amount, or no tolerance for the supplier or category. The rule should be written before the invoice arrives so the reviewer is not negotiating with themselves.

Apply the tolerance to the unit price, not only to the total. A large quantity can make a small unit price difference look material, while a freight change can push the total over the line without any price issue. State which field the tolerance covers.

Different categories may need different tolerances, but the rule should be written per category and approved by the owner who is accountable for the spend.

Compare the right price fields

Match the invoice line to the PO line by line number, description, unit of measure, and quantity. Compare unit price, extended price, tax, freight, and any discount. Record the currency and the price basis, such as per unit or per case.

Do not compare a total invoice amount to a total PO amount and call the difference a price variance. That method hides line-level errors and makes it impossible to tell whether the buyer approved a change or the supplier billed the wrong item.

If the unit of measure differs, convert before comparing and record the conversion. A case price compared to an each price can look like a large variance when the commercial price has not changed. Attach the PO line and the invoice line to the case so the reviewer can see the exact fields rather than a summary.

Separate price, quantity, and freight variance

Price variance is the difference between the invoiced unit price and the PO unit price at the invoiced quantity. Quantity variance is the difference between invoiced and received or ordered quantity. Freight and surcharge variance are separate again.

Classify each difference once. A quantity variance may be a receiving issue rather than a purchasing issue. A freight variance may belong to the carrier agreement. The class determines the owner and the evidence required to clear the item.

Report each variance type with its own amount and owner. A combined total makes the buyer responsible for a freight problem and the receiver responsible for a price problem.

Check the change history

Review PO revisions, approved change orders, supplier price notices, and contract amendments. A variance may be valid because the buyer approved a new price after the order was issued. Record the revision number and effective date.

Confirm that the invoice date falls within the approved price period. A new price approved for future shipments should not apply to an earlier delivery unless the change says so. The effective date is often the missing fact in a disputed variance.

If the buyer approved a change verbally, ask for the written confirmation before clearing the variance. A verbal approval is not a revision, and the next invoice will raise the same question.

Route the decision to the buyer

The buyer or category owner decides whether to accept the new price, dispute it, or amend the order. AP can calculate the difference and assemble the evidence, but it should not approve a price change on the buyer's behalf.

Send one question with the line details, the PO revision, the invoice reference, and the amount at issue. Name the response date and the payment impact. A vague request to check the price produces a vague answer and another cycle.

Include the PO remaining quantity and the receipt status so the buyer can see whether the price applies to future deliveries or only to the invoice in hand. Set a response date that reflects the payment due date, and escalate when the buyer does not answer before the run.

Document the acceptance or dispute

If the buyer accepts the variance, record the approval, the reason, and the revised PO or contract reference. If the buyer disputes it, record the supplier response, the credit requested, and the payment hold. Keep both the invoice and the PO versions.

Do not change the PO to match the invoice without the buyer's approval. That reverses the control and leaves no evidence that anyone agreed to the new price. The order should reflect the commercial decision, not the supplier's bill.

If the supplier issues a credit for the difference, link it to the invoice and keep the variance open until the credit is applied. A credit in transit is not a resolved variance.

Update the PO only through the owner

When an update is approved, use the system's change process and record the reason code, effective date, and approver. Recalculate the tolerance against the revised order. A manual note outside the system is not a substitute for the revision.

Check downstream effects: commitments, budget, receipt matching, and accruals. A price change can affect the remaining open quantity and the forecast. The buyer owns the commercial change; AP should surface the downstream impact rather than silently absorbing it.

Record the effective date and whether the change applies retroactively. A revision that applies only to future receipts should not be used to clear an earlier invoice.

Review variance patterns monthly

Report variance count, amount, supplier, category, buyer, and disposition. Separate accepted, disputed, and pending items. Look for suppliers with repeated unexplained differences and categories where the tolerance is consistently too tight.

Sample a few accepted variances and confirm the approval is present and the PO was updated. A high acceptance rate without evidence may mean the team is clearing items to keep the queue moving rather than applying the rule.

Compare the variance trend with the category plan and with supplier price notices. A jump after a contract renewal may be expected, while a jump without a notice needs a buyer explanation.

Close with a matched record

Close when the invoice line, PO line, receipt, and variance disposition agree, or when the item is explicitly held or disputed with an owner. The record should show the tolerance applied and the approver for any exception.

If a credit is expected, link it to the invoice and keep the case open until the credit is applied. A verbal promise to credit the difference is not a closed variance, because the payable is still overstated.

If the PO cannot be amended because the period is closed, record the compensating entry, the amount, and the owner who approved it. Link that entry to the invoice so a later reviewer can see why the order and the bill differ.

Continue with purchase order reconciliation support and the three-way match support.

Check the price variance review

  • The tolerance and the field it covers are stated
  • Invoice and PO lines match by item, unit, and quantity
  • Price, quantity, and freight variances are separated
  • PO revisions and effective dates are checked
  • The buyer or category owner makes the decision
  • The PO is updated only through the approved change process
  • Accepted variances have an approver and a reason

Common questions

Accounts payable virtual assistant FAQs

Can AP approve a small price variance?

Only within a written delegation that names the limit and the evidence required. The buyer usually owns the commercial price decision.

What counts as the price variance?

The difference between the invoiced unit price and the PO unit price at the invoiced quantity. Freight and quantity differences belong in their own categories.

What if the PO was revised after the invoice date?

Check the effective date. A later revision does not automatically apply to an earlier delivery unless the approved change says it does.

How should a disputed variance be closed?

Close on an approved PO change, an applied supplier credit, or a documented payment decision. A promise to review is still open.

Factual checks

Sources

These sources support the tax-form, access-control, and phishing guidance in this article. The planning numbers above are labeled examples and do not come from these sources.

  1. SBA: Manage your businessSmall-business management guidance used as general context for purchasing and payable routines.
  2. NIST SP 800-53 Rev. 5Control context for authorization, change control, and audit records over purchase order revisions.
  3. NARA: Records management policyRecords policy supporting retention of PO versions and variance dispositions.
  4. SBA: Stay legally compliantCompliance guidance used as general context for documented commercial records.

International Labour Organization guidance on remote work arrangements reinforces why remote role briefs should document expectations, communication rhythms, and accountable handoffs.

Contact Us to turn this article into a scoped Philippines-based staffing brief.