Trace a receipt through the invoice and purchase order.

Choose the operation you need

Receipt text or an extraction to check

analyze_receipt extracts structured expense fields from caller-supplied receipt text or checks a supported structured extraction. Use it when those fields still need extraction or validation. Price: 0.25 USDC per accepted paid request. It does not read images or allocate invoice quantities.

How much of this purchase order does the invoice bill?

match_invoice accepts one structured invoice and one purchase order. It aggregates invoice lines allocated to each PO line and reports partial, full, uninvoiced or overbilled quantities, including the remaining quantity. It uses explicit PO line IDs or unique exact product codes; it does not match by description or accept a receipt. Price: 0.50 USDC per accepted paid request.

Where do the receipt, invoice and PO disagree?

reconcile_purchase_documents checks a structured receipt against an invoice and that invoice against a PO, using conservative one-to-one links. It flags reference, item, quantity, price and arithmetic differences. It does not allocate quantities or calculate remaining PO quantities; split links are ambiguous and partial quantities are reported as differences. This comparison is free. Call it directly when these checks suffice; neither paid analysis is a prerequisite.

Supply each tool's fields explicitly using its schema. The free comparison accepts missing documents as incomplete review cases; it does not turn them into a completed two-document allocation result. Both operations are limited to the supplied records, without prior-invoice history, delivery events or inferred documents.

A concrete difference

In a synthetic example with 5 units ordered and 2 units invoiced, match_invoice reports partial invoicing and 3 units remaining on that PO line. The free comparison instead flags the unequal quantities. If two invoice lines bill 2 and 3 units against one PO line, the paid tool aggregates 5 units; the free tool reports the many-to-one link as ambiguous. These examples demonstrate different checks, not customer outcomes.

Inspect before calling

get_document_example with {"service":"invoice"} shows the fixed allocation example; {"service":"reconciliation"} shows the fixed three-document comparison. Neither example processes your documents or requires a wallet.

get_document_service_status accepts receipt, invoice or reconciliation in its service field. It reports the selected service's readiness and terms. A free example is not a test of your document.