Drop in any purchase order PDF — issued by your team or received from a customer — and get a clean Excel file with PO number, supplier name, ship-to address, line items (description, quantity, unit price, extended amount), payment terms, and delivery date.
Every ERP issues POs differently — NetSuite POs don't look like SAP POs, which don't look like QuickBooks POs, which don't look like the Word-template POs a small business sends. The line-item structure varies: some put quantity-then-price, some price-then-quantity, some include a separate column for tax or freight. AP teams doing three-way match (PO → receiving → invoice) need clean line-item data from all three documents — but the PO is usually the messiest.
Suppliers often archive issued POs as PDFs in a folder; reconstructing the PO line-item history into a spreadsheet for audit, contract review, or supplier-spend analysis is hours of manual work per audit cycle.
PDFExcel reads any PO format — issued from any ERP, generated from a template, or received from a customer. PO header fields (PO number, supplier, buyer, ship-to, payment terms, expected delivery) extract as one row; line items expand into per-line detail with description, quantity, unit price, extended amount, and any per-line cost codes or part numbers.
Pair the PO export with the matching invoice extraction for three-way match — join on PO number and line description to validate that quantity received and unit price agree before approving the AP bill. Drop both into NetSuite, SAP, Sage Intacct, or your custom three-way match worksheet.
The model knows the difference between a PO header total, a line-item subtotal, and a tax-line total — and that 'Net 30' is payment terms, not a line item. Trained on POs from NetSuite, SAP, Oracle, QuickBooks, Sage, Microsoft D365, plus template-generated POs.
PO extraction is usually an afterthought — most AP automation tools focus on invoice extraction. PDFExcel handles both POs and invoices with the same workflow, making three-way match practical.
One row per PO line item. Header fields (PO #, supplier) repeat per line so you can pivot or filter. Join against invoice line items for 3-way match.
| # | PO # | Supplier | Line | Description | Qty | Unit Price | Extended |
|---|---|---|---|---|---|---|---|
| 1 | PO-1184 | Acme Office Supply | 1 | Letter-size copy paper, case | 20 | $42.50 | $850.00 |
| 2 | PO-1184 | Acme Office Supply | 2 | Black ink toner, HP 26X | 10 | $57.00 | $570.00 |
| 3 | PO-1186 | Northbridge Logistics | 1 | Freight — SF to NYC, palletized | 1 | $2,890.00 | $2,890.00 |
| 4 | PO-1192 | Cascade Print Co. | 1 | Quarterly investor brochure, 4-color | 2,000 | $0.158 | $315.50 |
| 5 | PO-1198 | Helix Software Inc. | 1 | Annual subscription — Helix Pro | 1 | $4,200.00 | $4,200.00 |
Procurement teams reconciling issued POs against contract pricing, AP teams doing three-way match, controllers auditing supplier spend, sales-side ops capturing customer-issued POs.
Each invoice gets joined against its PO and receiving document. Convert PO line items + invoice line items, join on description and unit price, flag mismatches automatically.
Pulls a year of issued POs to a major supplier to verify pricing matches the contract. Convert all PO PDFs as one batch, pivot by line description and date to spot price drift.
Customer emails a PO PDF. Convert to extract PO number, ship-to, line items, and payment terms — drop into the order management system without manual entry.
Yes — NetSuite, SAP, Oracle, QuickBooks, Sage, Microsoft Dynamics 365, plus template-generated POs from Word/Excel. The model reads PO structure rather than relying on per-ERP templates.
Yes. Each line item expands into description, quantity, unit price, extended amount, and any per-line metadata (part number, cost center, project code). Critical for three-way match accuracy.
Yes. Multi-page POs stitch into a single line-item table — page headers and 'continued on next page' rows skip automatically. Header totals reconcile to the sum of line extended amounts.
10 documents per month, free, forever. Plans from $69/month for 50 documents — most small AP/procurement teams fit Starter or Pro.
Yes. Convert PO + invoice + receiving document with the same workflow, then join on PO number and line description in your downstream worksheet to validate quantity and unit price before approving the bill.