Extract data from purchase order changes
A purchase order change is the amendment a buyer issues to modify a purchase order that has already been placed. Rather than reissue the whole order, the buyer sends a change that references the original by number and states only what moves: a quantity, a price, a delivery date, or a cancellation. It is not the original purchase order, and it is not a construction change order, which amends a building contract under a form like AIA G701. That transactional amendment to a goods order is exactly what Northwind Retail GmbH issues as change PCR-2026-0451, against its original order PO-2026-0088 dated 2026-05-02, to Baltic Components AB.
Value lives in the deltas, so the original reference and the per-line changes have to travel together. EDI defines this as its own transaction, an ANSI X12 860, an EDIFACT ORDCHG, or a UBL Order revision, precisely because a change is not a fresh order. On line 1, a change_reason of quantity adjustment raises the count from 500 to 700 units, a quantity_change of positive 200, while line 2 drops by 50. Suppliers need the new total quantity and the new line amount, not just the difference. Revising the delivery_date moves the whole order, and the money still has to foot: the line amounts net of tax sum to the line_extension_total, and the tax at 19 percent brings the change to its total_amount.
Given the change, Talonic returns the original_po_number, the original_po_date, the change_reason, the buyer and supplier, the currency, and the revised delivery_date as fields, with the line_items as a table carrying both the quantity_change delta and the new quantity per line. Those figures, a 3,350.00 EUR line-extension total, a 636.50 EUR VAT at 19 percent, and a 3,986.50 EUR total, are typed as numbers and checked to foot. Each line keeps its original_line_number so a buyer can trace a quantity delta to the line it amends, and the document_date and delivery_date parse to ISO 8601. Talonic captures the amendment as issued and does not apply it to the original order or confirm the supplier accepted it.
What gets extracted from purchase order changes
How extraction works for purchase order changes
Purchase order changes arrive as EDI messages (X12 860, EDIFACT ORDCHG) and as PDF amendment forms, and neither the header nor the line grid sits in a fixed place. Talonic classifies the change and aligns it to the order schema in the Field Registry, which follows the OASIS UBL 2.1 Order model, so original_po_number, change_reason, buyer.name, supplier.name, currency, and delivery_date each resolve to a field while line_items return per row. Per line, both the quantity_change delta and the new quantity are captured, plus the original_line_number that ties it to the order being amended, so an increase from 500 to 700 units reads as a positive 200 delta against a specific line. Monetary values are typed as numbers in the document currency, and the line amounts net of tax are checked to foot to line_extension_total, which plus tax_amount equals total_amount. Each value returns with a confidence score and a source-region pointer under DIN SPEC 91491, so a procurement analyst can verify a revised price against the change. Talonic reads the amendment as issued and does not merge it into the original order.
Sample extraction
A PO change adjusting two line quantities and the delivery date
{
"document_number": "PCR-2026-0451",
"document_date": "2026-06-24",
"original_po_number": "PO-2026-0088",
"original_po_date": "2026-05-02",
"document_uuid": "a3f2c9e0-8b71-4d2a-9f11-2c7e5d904418",
"change_reason": "quantity_adjustment",
"change_details": "Increase line 1 by 200 units; reduce line 2 by 50 units; revise delivery date",
"buyer.name": "Northwind Retail GmbH",
"buyer.address": "Hansaallee 12, 40549 Dusseldorf, DE",
"buyer.contact": "procurement@northwind-retail.de",
"supplier.name": "Baltic Components AB",
"supplier.address": "Sveavagen 44, 111 34 Stockholm, SE",
"currency": "EUR",
"line_extension_total": 3350,
"tax_amount": 636.5,
"total_amount": 3986.5,
"payment_terms": "Net 30",
"delivery_date": "2026-07-20",
"delivery_terms": "DAP Dusseldorf (Incoterms 2020)",
"line_count": 2,
"line_items": [
{
"line_number": "1",
"original_line_number": "1",
"item_code": "BC-7720",
"item_description": "M6 stainless fastener, 20mm",
"quantity_change": 200,
"quantity": 700,
"unit_price": 3.5,
"line_amount": 2450,
"line_tax_amount": 465.5,
"line_delivery_date": "2026-07-20"
},
{
"line_number": "2",
"original_line_number": "2",
"item_code": "BC-7815",
"item_description": "M6 washer, zinc",
"quantity_change": -50,
"quantity": 150,
"unit_price": 6,
"line_amount": 900,
"line_tax_amount": 171,
"line_delivery_date": "2026-07-20"
}
]
}Frequently asked
How is a PO change different from the original PO or a construction change order?
The original purchase order places the order. A purchase order change amends it, referencing the original by number and stating only the deltas. A construction change order amends a building contract under a form such as AIA G701. Talonic reads each on its own schema and keeps the change tied to its original_po_number.
Does it capture the quantity deltas and new totals per line?
Yes. Each line carries both quantity_change, the signed delta, and quantity, the new total after the change, so a raise from 500 to 700 units shows as a positive 200 delta against a new total of 700, not just a difference.
Do the line amounts foot to the totals?
Yes. The line amounts net of tax are checked to sum to line_extension_total, and that plus tax_amount is checked against total_amount, so the 3,350.00 EUR net, 636.50 EUR VAT at 19 percent, and 3,986.50 EUR total are verified to reconcile.
Does Talonic apply the change to the original order?
No. It extracts the amendment as issued, including the change_reason and the per-line deltas. Applying the change to the referenced order, or confirming the supplier accepted it, is a downstream step handled by the buyer's system, not the extraction.
What fields are extracted from purchase order changes?
Talonic returns purchase order changes as schema-validated, typed fields. Common fields include Change Number, Original PO Number, Original PO Date, Change Reason, and more, each normalized (dates to ISO 8601, amounts as numbers) and mapped to a stable key so the output shape stays the same across layouts.
How accurate is extraction from purchase order changes, and how is confidence reported?
Every extracted cell carries a confidence score from 0.0 to 1.0 and a provenance pointer back to the source page and region, so low-confidence values can be reviewed against the original before the data is trusted downstream. There is no single accuracy number: confidence is reported per field so you can gate on it.
Can I use purchase order changes extraction in production?
Yes. The same engine behind this guide is available as a production REST API and Node SDK with sync, async, and streaming modes, schema versioning, signed webhooks, and EU-resident processing. Start free with an API key, then scale on usage-based pricing.
What does it cost to extract data from purchase order changes?
There is a free tier for prototyping and agent evaluation with no credit card. Paid usage is credit-based at 1,000 credits per euro: page ingestion is 100 credits per page and registry-resolved queries are free. See talonic.com/pricing for current rates.
Ready to extract from your own purchase order changes?
- GDPR
- HIPAA
- ISO 27001 / 42001 aligned
- DIN SPEC 91491 co-author
- EU-resident infrastructure
Author note
Reviewed by Talonic engineering, logistics schema review · last reviewed 2026-07-08