Compare supplier confirmations with purchase orders
Check what a supplier accepted against what you ordered. Route changed terms with the original documents attached.
How this works
Check what a supplier accepted against what you ordered. Route changed terms with the original documents attached.
Compare the supplier’s accepted terms line by line with the purchase order. Keep quantity, unit of measure, price basis and delivery date separate so an apparent match does not conceal a commercial change.
Before you start
Defined operating scope
Buyers manually reconcile supplier acknowledgements against placed orders.
Required source material
Obtain Purchase order; Supplier confirmation; Approved commercial terms. If connectors are unavailable, use authorized files with the same fields.
Decision and exception rules
Supplier uses an unknown pack size. Request the conversion rather than comparing incomparable quantities.
Prepare the inputs
- purchase_order
- Required
Header and item lines
Use the effective approved revision.
- confirmation
- Required
Supplier response with references
Match order ID and supplier identity.
- unit_mapping
- Required
SKU and pack conversion table
Conversions require an approved ratio.
- tolerance_rules
- Required
Field-specific permitted differences
Absence of tolerance means review, not automatic acceptance.
Implementation, step by step
Establish the working record
- Confirm the selected records, effective versions and responsible owner.
- Check purchase_order, confirmation, unit_mapping, tolerance_rules before beginning. Record the source version and the selected scope; an unavailable value stays unknown rather than becoming an inferred fact.
Checkpoint: The input record identifies the selected purchase_order and any missing required fields.
Match the confirmation to its purchase order
- Resolve the purchase-order revision and map supplier line references to internal item IDs.
- Recalculate pack conversions and extended amounts independently.
Checkpoint: A saved intermediate result for: Match the confirmation to its purchase order.
Extract item, quantity, price and delivery fields
- Normalize units using approved pack ratios while preserving the supplier’s original quantity and price basis.
- Show every missing or changed line; do not remove unconfirmed quantities from the order.
Checkpoint: A saved intermediate result for: Extract item, quantity, price and delivery fields.
Compare values and flag discrepancies or missing details
- Compare quantities, unit prices, currency and delivery dates; calculate extended amounts deterministically.
- Recalculate pack conversions and extended amounts independently.
Checkpoint: A saved intermediate result for: Compare values and flag discrepancies or missing details.
Send exceptions to procurement before updating the order
- Prepare a discrepancy queue showing ordered, confirmed and difference values; proposed ERP updates remain distinct from accepted terms.
- Show every missing or changed line; do not remove unconfirmed quantities from the order.
Checkpoint: A saved intermediate result for: Send exceptions to procurement before updating the order.
Package the result and unresolved work
- Procurement checks source values and approves changes to agreed terms.
- Procurement decides whether changed terms are acceptable.
Checkpoint: A documented queue of supplier discrepancies. Unresolved items remain visible in the review record.
Decisions along the way
Supplier uses an unknown pack size.
Request the conversion rather than comparing incomparable quantities.
Confirmation accepts only part of a line.
Record partial acceptance and keep the unconfirmed balance open.
Order reference is ambiguous.
Hold matching and request the correct purchase-order reference before any update.
What you will produce
supplier-order-confirmation-review-result.json
JSONA documented queue of supplier discrepancies. Label proposed and completed states separately.
Include: purchase_order_id · line_id · ordered_value · confirmed_value · difference · procurement_decision · status · evidence_reference · review_note
supplier-order-confirmation-review-review.md
MarkdownKeep the evidence and unresolved decisions needed to apply this result, including exceptions involving tolerance_rules.
Include: source_reference · question · owner · next_action
Check the result
- Recalculate pack conversions and extended amounts independently.
- Show every missing or changed line; do not remove unconfirmed quantities from the order.
- Inspect purchase_order and confirmation in both the original and output; confirm that record identity and interpretation survived the transformation.
- Procurement checks source values and approves changes to agreed terms.
When something goes wrong
Supplier uses an unknown pack size.
Request the conversion rather than comparing incomparable quantities. Retain the affected evidence and recovery status.
Confirmation accepts only part of a line.
Record partial acceptance and keep the unconfirmed balance open. Retain the affected evidence and recovery status.
Order reference is ambiguous.
Hold matching and request the correct purchase-order reference before any update. Retain the affected evidence and recovery status.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Compare supplier confirmations with purchase orders for the following bounded example; prepare the result for review.
Inputs
Synthetic example: PO-22 requests 100 units at 8 EUR each by 20 October. Confirmation accepts 8 packs of 10 at 80 EUR per pack by 23 October.
Expected result
Synthetic expected result: Normalize to 80 units and 640 EUR. Flag 20 units unconfirmed and delivery three calendar days later; unit price remains equivalent.
Run a small pilot
Start small
Trial a representative batch containing the ordinary case and the exception demonstrated above.
Record the baseline
Record current preparation time, review effort and correction types for the same records.
Agree success criteria
Agree acceptable review and error limits; measure missed discrepancies; reviewer minutes per confirmation.
Stop or revise
Order reference is ambiguous. Pause affected records and apply this recovery: Hold matching and request the correct purchase-order reference before any update.
Keep the scope clear
- Procurement decides whether changed terms are acceptable.
- Do not amend the purchase order or contact the supplier without the requested authority.
Check before using
Procurement checks source values and approves changes to agreed terms.
Business activities
- Plan inventory and production
- Manage finances and accounting
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Purchase order · Supplier confirmation · Approved commercial terms
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow