How to use the Invoice to Purchase Order Matcher.
Match each invoice line to the order and receipt, not just the document totals. Separate price differences from unreceived quantities and leave uncertain matches for review.
Make the workflow fit your task.
Match supplier, currency and item identifiers, then compare ordered quantities, received quantities and invoiced rates line by line. Classify price, quantity and receipt exceptions separately. Keep ambiguous matches unresolved instead of approving based on equal document totals.
- What you provide
- Invoice and matching PO records.
- What you get
- Quantity, price and reference discrepancies.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
PO: 10 chairs at USD 40 each. Receipt: 8 chairs. Invoice: 10 chairs at USD 42 each.
Completed example
Price exception: USD 2 per chair above the order. Receipt exception: 2 invoiced chairs not yet recorded as received. Flag for review; do not approve payment automatically.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Can matching invoice and purchase-order totals prove the invoice is correct?
No. Different line errors can offset each other, and goods may not have been received. Check the underlying lines and receipts.
Why does a partial delivery appear as an overbilling exception?
The invoice may cover units not yet received. Review timing and the agreed billing terms before resolving the difference.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑