Back to Browse
Invoice Purchase Order Matcher
x402
Invoice Purchase Order Matcher is a paid API for AI agents from mcp-factory.bowling-anthony.workers.dev, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-15).
Analyzes and matches invoice lines against purchase orders and receipt data, flagging discrepancies and exceptions with three-way reconciliation.
Price / call$0.05
Success—
StatusUnknown
How this service works
Customer-input analysis tools with per-call x402 v2 USDC payments on Base. Discovery and examples are free.
Output
Returns a JSON object with a list of matched invoice lines (each with SKU, quantities, unit price, line total in minor units, and any exceptions), a receipt exceptions array, a purchase order summary per SKU showing ordered/invoiced/received quantities and exceptions, an overall match status boolean, exception count, total invoice amount in minor units, and currency metadata including minor unit digits and tolerance.
Example use cases
AP automation three-way matching
“We received an invoice from our supplier for 50 units of PART-A at $15.00 each. Our purchase order was for 50 units at $15.00 and our warehouse confirmed receipt of 48 units. Run a three-way match and tell me if there are any exceptions.”
Overpayment risk detection
“I have an invoice charging us for 100 units of SKU-XYZ at $5.50 each, but our PO only authorized 80 units at $5.00. Can you compare these and highlight all the discrepancies so I know what to dispute?”
Automated invoice approval workflow
“Before we approve this vendor invoice for order PO-2024-889, match it against the purchase order and goods receipt — the invoice shows 25 units of CABLE-CAT6 at $3.00 each with a tolerance of $0 — and let me know if it's clean to pay.”
Technical details
Endpoint
POSThttps://mcp-factory.bowling-anthony.workers.dev/invoice-purchase-order-matcher/analyzeWhen to prefer
Use this endpoint when you need automated three-way matching of invoices against purchase orders and receipt records, especially in accounts payable workflows where you want structured exception reporting per line item. Prefer this over manual reconciliation or generic document comparison tools when you need SKU-level quantity and price validation with tolerance support and a machine-readable summary.
Side effects
- Mismatched SKUs between invoice and PO result in unmatched line exceptions
- Quantity discrepancies beyond tolerance flagged as exceptions rather than hard errors
- Missing or malformed line data may cause parsing failures or incomplete matching
- Currency or minor-unit mismatches can produce incorrect totals
- Payment failure via x402 returns 402 before analysis is performed
Output
Schema · Response
{
"type": "json",
"example": {
"ok": true,
"lines": [
{
"sku": "WIDGET",
"line_id": "INV1",
"quantity": "10",
"exceptions": [],
"po_line_id": "PO1",
"unit_price": "2.00",
"line_total_minor": "2000"
}
],
"stage": "complete",
"summary": {
"matched": true,
"exception_count": 0,
"invoice_line_count": 1,
"receipt_line_count": 1,
"total_invoice_minor": "2000",
"purchase_order_line_count": 1
},
"currency": "USD",
"tolerance_minor": "0",
"minor_unit_digits": 2,
"receipt_exceptions": [],
"purchase_order_summary": [
{
"sku": "WIDGET",
"exceptions": [],
"po_line_id": "PO1",
"ordered_quantity": "10.000000",
"invoiced_quantity": "10.000000",
"received_quantity": "10.000000"
}
]
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"