invoice-3way-match

Reconciles blocked supplier invoices against POs, goods receipts, and contract prices.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai --skill invoice-3way-match-metafloor-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: invoice-3way-match
Source: https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai/tree/main/skills/business-workflows/invoice-3way-match
Command: npx skills add https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai --skill invoice-3way-match-metafloor-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a supplier invoice fails the automated three-way match on a price or quantity variance, it lands in an AP exception queue ahead of the payment run, forcing a fast decision: pay, short-pay, or dispute. Handled ad hoc, this either delays payment or pays out overbills that are hard to claw back. This Skill decomposes the gap into named variance terms, classifies the cause, and prices each disposition so the approval gate is a real decision. ## Core Features & Use Cases - Variance Decomposition: Splits the invoice gap into unit-price variance, quantity variance, and receipt-timing terms using the contract price, PO, and goods receipt as authoritative sources. - Cause Classification & Disposition: Distinguishes price overbill, short-ship, receiving error, and legitimate price changes, then recommends short-pay, hold-and-dispute, or pay-in-full with a recovery number attached. - Gated Execution: Stages dispositions in SAP (MIRO, GR/IR), SAP FI, or Coupa only after human approval, with a hold-not-release default when the payment-run clock beats the gate. - Use Case: An invoice for $14,300 blocks against a $13,200 PO at 5:10pm with a 6pm payment run. The Skill identifies a $1,100 unit-price overbill against the contract price and recommends short-paying to $13,200, recovering the full gap. ## Quick Start Ask the assistant to reconcile the blocked supplier invoice against its PO, goods receipt, and contract price and recommend whether to pay, short-pay, or dispute before the payment run.

Frequently Asked Questions about invoice-3way-match

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve a blocked invoice that failed the 3-way match?

Reconcile the invoice line by line against the PO and goods receipt, splitting the gap into unit-price variance, quantity variance, and receipt-timing. Classify the cause (price overbill, short-ship, receiving error, or legitimate price change), then short-pay, dispute, or pay in full based on the priced options.

What is the difference between price variance and quantity variance in invoice matching?

Unit-price variance is (invoice price minus contract price) times matched quantity, recoverable by short-pay since the contract governs price. Quantity variance is (invoiced minus received quantity) times contract price, since unreceived units are never payable.

When should I short-pay versus dispute a supplier invoice?

Short-pay unilaterally when the variance is below the dispute threshold and the cause is clean, such as a confirmed price overbill. Hold and dispute when the variance exceeds the threshold, the cause is ambiguous, or the quantity itself is in dispute.

Should I release a mismatched invoice to make the payment run deadline?

No. A held invoice can always be released later, but a paid overbill requires a supplier credit chase to recover. Block the invoice and escalate to the AP manager once the approval SLA lapses rather than auto-releasing to beat the clock.

Which system is authoritative for price versus quantity in a 3-way match?

The contract or CLM system is authoritative for price, and an amendment supersedes a stale PO price. The goods receipt in the WMS is authoritative for quantity received. The invoice is only the supplier's claim and is never authoritative.

How are edge cases like UoM mismatches or credit memos handled in invoice matching?

UoM mismatches and multi-currency invoices must be normalized before pricing, or they appear as phantom price variances. Supplier credit memos run with inverted signs, verified against the original overbilled invoice they correct.