Extract purchase orders to structured JSON
Purchase orders document what a buyer is ordering: line items, quantities, prices, delivery terms, and payment conditions. Every company formats POs differently. Sensible extracts PO data into validated JSON for order management, invoice matching, and procurement analytics.
Quick links:
Why purchase orders defeat one-size-fits-all extraction
Every company formats POs differently. Line items, shipping terms, and conditions appear anywhere.
No two companies format purchase orders alike. Sensible's hybrid engine adapts to each layout while enforcing consistent output.
PO line items include SKUs, unit prices, quantities, discounts, and delivery dates. Sensible extracts all detail levels per line.
POs embed payment terms, shipping terms, and compliance clauses in varied formats. Sensible extracts terms regardless of location.
Fields we extract
Extract any data you need from purchase orders into your desired output schema
Buyer name/address, vendor name/address, PO number, PO date, ship-to address, bill-to address, payment terms, shipping method
Line number, SKU/part number, description, quantity, unit price, unit of measure, discount, tax, extended amount, requested delivery date
Subtotal, tax total, shipping cost, total amount, FOB point, freight terms, special instructions, approval signatures
Federal or state government procurement order with FAR/DFAR compliance fields.
Long-term PO covering recurring purchases with periodic releases.
Buyer-issued PO with line items, quantities, unit prices, and delivery terms.
Supported PO formats
Sensible processes purchase orders from any company or procurement system. New PO formats can be configured quickly, with common layouts available as starting templates.
SAP, Oracle, NetSuite, Coupa, Ariba, Jaggaer, QuickBooks, manual/handwritten POs
Standard POs, blanket/standing POs, contract POs, planned POs, drop-ship POs, government POs (SF-1449)
Common Questions
Details on purchase order extraction across formats.
Yes. Validation rules verify that line item extended prices sum to the subtotal and that tax and shipping charges produce the correct grand total. Discrepancies are flagged automatically.
Yes. Sensible captures requested delivery dates, ship dates, partial shipment allowances, and delivery location details for each line item when specified on the PO.
Sensible extracts payment terms, delivery terms (Incoterms), ship-to and bill-to addresses, required delivery date, FOB point, and any special instructions.
Sensible extracts each line item with item number, description, quantity, unit price, unit of measure, and extended price. Multi-page PO tables are stitched into a single array.
Yes. Sensible sends extraction results to your webhook endpoint when processing completes. You can also poll the API for status.
Yes. Sensible flags extractions with low confidence for human review. You can configure review thresholds and workflows.
Sensible is SOC 2 Type II certified and HIPAA compliant. Data is encrypted in transit and at rest.
Documents are deleted after 30 days by default. You can configure shorter retention periods or request immediate deletion via API.
Yes. Sensible offers a free tier with 50 documents per month. No credit card required to start.
Sensible uses per-document pricing for predictable costs. No token-based billing or usage surprises. Volume discounts are available for higher throughput.
Sensible provides REST APIs and SDKs for Python and Node.js. Most integrations take a few hours. Webhooks, Zapier, and direct API calls are all supported.
Sensible processes PDF, PNG, JPG, and TIFF files. PDFs can be native or scanned.
Accuracy depends on document quality and configuration. Most production deployments achieve 95%+ accuracy with proper validation rules and confidence scoring.
Most documents process in 2 to 10 seconds depending on complexity and page count.