DocPro · Agent
PTAS DocPro Purchase Order Agent
Header, lines, dates and terms extracted and shaped for two- and three-way match, with quantity and price variances flagged early.
What the agent does
Read, Then Shaped for the Match
An order extracted into fields is only half the job. It has to line up with an invoice that describes the same goods differently.
Read
Order header
Order number, dates, buyer entity, delivery address, currency and payment terms, taken from wherever the form puts them.
Read
Line detail
Item code, description, quantity, unit, unit price and line total, held in the order they were issued.
Normalise
Unit conversion
Cases ordered against units invoiced are converted to a common basis before anything is compared.
Normalise
Item cross-reference
The supplier part number is resolved to your item master, so a match does not depend on both sides using the same code.
Track
Amendments
Revisions are tracked against the original line, so a changed quantity or price does not quietly break the match.
Track
Receipt position
Received quantities accumulate per line, so a partial delivery leaves the balance open rather than closing the line.
Normalisation
Where Matching Usually Fails
Rarely on the numbers. Almost always on two documents describing the same thing in different words and different units.
One line, three documents · Illustrative example
Four cases against forty units is the same quantity once the pack size is known. That conversion is where most manual matching stalls.
Unit conversion
Cases, packs and singles reconciled to one basis.
Part numbers
Supplier codes cross-referenced to your item master.
Amendment tracking
Revisions carried so the three-way match still holds.
The difference
Six Reasons a Match Breaks
FAQ
Questions Teams Ask
Do you need the order and the invoice at the same time?
No. Orders are read and stored as structured data when they are issued, and the match runs when the invoice arrives, which can be weeks later. The same applies to goods received notes, so all three parts of a three-way match can turn up in any order.
What if our suppliers use different part numbers to us?
That is the normal case, and it is why cross-referencing sits in the middle of this. Supplier codes are resolved against your item master, so a match works on the item rather than on both sides happening to use the same string.
How are over-deliveries and short deliveries handled?
Received quantities accumulate against the order line, so a short delivery leaves the balance open and an over-delivery is flagged against your tolerance rather than silently accepted. Neither closes the line on its own.
Does this work with orders raised in our ERP?
Yes. Orders can be read from documents or taken directly from your ERP. Either way the output is the same structured order used for matching. Your ERP stays the system of record for the order itself.
Keep reading
Related Capabilities
Invoice Extraction
The other side of the match, read the same way.
Read more →Procure-to-Pay
The full commitment cycle these orders sit inside.
Read more →AP Automation
Where the finished three-way match gets acted on.
Read more →DocPro
Every other document type the same engine reads.
Read more →Next step
Bring Us a Match That Keeps Failing
An order, its invoice and the receipt. The interesting part is always why the three do not agree.