Supplier spend is scattered across hundreds of purchase orders, each in a different layout and each spelling the vendor a little differently.
PDF, JPG, PNG, BMP, HEIC, TIFF
Submit your purchase orders
Drop documents here, or choose a file
Up to 50 files per batch
Uploading...
Supplier spend is scattered across hundreds of purchase orders, each in a different layout and each spelling the vendor a little differently. This guide shows how to turn that pile into one clean table you can pivot by supplier and category, starting with the extraction step below.
Purchase orders hold the most detailed record of what you committed to buy, from whom, at what unit price. The trouble is that the record lives in documents, not in a table, so the question of how much you spend with each supplier goes unanswered until someone rebuilds the data by hand.
Most supplier and buyer purchase orders exist as PDFs, scans, or email attachments. A spend review cannot start until every order is turned into rows, and keying them is the step that usually stalls the whole exercise.
The same vendor shows up as Acme Supplies Ltd, ACME SUPPLIES LIMITED, and Acme Supplies. Summed as written, one supplier looks like three smaller ones and your largest relationships are understated.
A spend report built from PO totals tells you how much went to a supplier, not what you bought. Without line items you cannot see categories, compare unit prices, or find the same SKU bought from two vendors.
Line descriptions are written by suppliers, not by your finance team. Without a mapping step, office supplies, MRO parts, and software licenses end up mixed together and category totals mean very little.
Consolidation works when every purchase order ends up in the same shape: one row per line item, a clean supplier name on every row, a category, and a unit price you can compare. PurchaseOrders handles the capture and supplier grouping, and the analysis happens in the spreadsheet or BI tool you already use.
Each order comes back with its header fields (PO number, supplier, order date, currency, totals) and a line-item table with SKU, description, quantity, unit of measure where printed, unit price, and line amount.
The vendor is read from the document itself, so a mixed batch does not need to be sorted or renamed first. Batch results are grouped by supplier, and documents where no vendor can be read are kept in their own group rather than dropped.
On the Plus plan and above, supplier name variants are folded onto one canonical name and line items can be filed under procurement categories such as raw materials, MRO, services, and software.
Every export uses the same column set regardless of supplier layout, so a batch from this month stacks directly under last month and a single pivot table covers the whole period.
The consolidation only works if every line comes through, which is why accurate purchase order line item extraction is the foundation: a missed row is spend that disappears from the report. The supplier column comes from automatic supplier detection, which reads the vendor from each document so mixed batches group correctly without tagging. For a larger stack of orders, bulk purchase order upload takes a whole folder at a time, and the purchase order PDF to Excel converter gives you the file you pivot.
Once the table exists, the analysis itself is covered in depth in our guide to procurement spend analysis, which walks through cleansing, classification, and what to look for in the results. The long list of small suppliers that appears at the bottom of every consolidated view is the subject of tail spend management, and purchases made outside agreed suppliers are explained in maverick spend.
These are the purchase order fields that make a consolidated spend table useful. Extract all of them, even the ones you do not plan to report on yet.
| PO field | What it holds | Why it matters for spend |
|---|---|---|
| Supplier name | The vendor as printed on the order | The pivot key. Normalize variants before grouping. |
| PO number | The buyer reference for the order | Finds duplicates and ties spend back to the source document. |
| Order date | When the commitment was made | Sets the period for monthly, quarterly, or annual views. |
| SKU and description | What was bought on each line | Drives category mapping and like-for-like price comparison. |
| Quantity and UOM | How much, in which unit | Needed to compare unit prices when suppliers sell by box, case, or each. |
| Unit price | Agreed price per unit | Reveals price differences for the same item across suppliers. |
| Line amount | Quantity times unit price | The value you sum by supplier and category. |
| Currency | The currency the order is priced in | Prevents mixed-currency totals in a consolidated view. |
Purchase orders show committed spend. Actual spend comes from invoices and payments, so reconcile the two before using the figures for budgeting or supplier negotiations.
The same workflow works for a quarterly review of fifty orders or an annual review of several thousand.
Pull every PO for the period from email, shared drives, your ERP document store, and supplier portals. Include scans and photos, since they often cover the smaller suppliers that are easiest to miss.
Tip: Agree the date range first and filter by order date, not by the date the file was saved.
Upload the orders and extract the PO number, supplier, order date, currency, and the full line-item table with SKU, description, quantity, unit price, and line amount. Review the rows on screen and export to Excel or CSV.
Tip: Keep one row per line item. Rolling up to PO totals at this stage throws away the detail you need later.
Fold every spelling of a vendor onto one canonical name by removing case differences, punctuation, and legal suffixes such as Inc, LLC, and Ltd. Where you have a vendor master, map each name to its vendor ID so the result matches your ERP.
Assign each line to a spend category, for example raw materials, MRO, packaging, IT, professional services, or freight. Use your own chart of accounts or taxonomy so the result lines up with the general ledger.
Tip: Map by SKU first, then by keywords in the description for lines that carry no SKU.
Build a pivot table with supplier and category as rows and the sum of line amount as values, with order month as a column if you want a trend. Sort by total to see your largest suppliers and categories at the top.
For items bought from more than one supplier, compare unit prices after converting to the same unit of measure. Differences point to consolidation opportunities, contract gaps, or orders placed outside preferred vendors.
It means bringing every purchase from every supplier into one table so you can see total spend per supplier and per category. In procurement it also refers to the follow-on action: moving volume onto fewer suppliers to negotiate better prices and terms. The table comes first, because you cannot consolidate what you cannot measure.
Use both if you can. Purchase orders show what you committed to buy, often before the goods arrive, and they carry the agreed unit price. Invoices show what you were billed. Starting from POs gives an earlier view of spend and a clean baseline for comparing billed prices against agreed prices.
Normalize the names before you group them. Convert to one case, remove punctuation and legal suffixes such as Inc, LLC, Ltd, and GmbH, and map the result to a single canonical name or vendor ID. On the Plus plan and above, PurchaseOrders folds common name variants onto one supplier automatically.
Totals tell you how much went to each supplier. Line items tell you what you bought. Category analysis, unit price comparison, and finding the same product bought from several vendors all need line-level data, so extract the full line-item table even if the first report only uses totals.
Match lines that describe the same item, convert quantities to a common unit of measure, then divide line amount by the converted quantity. Compare within one currency. Differences between suppliers for the same item are the most direct evidence for a consolidation or renegotiation decision.
Keep the original currency and amount on every row and add a converted amount in your reporting currency. Summing mixed currencies as if they were one produces meaningless totals. PurchaseOrders keeps the printed figures unchanged and adds converted columns where a rate for the order date is available.
Excel or Google Sheets handle most consolidations with a standard pivot table. For larger volumes or recurring reporting, load the CSV or JSON into a BI tool or your data warehouse. The extraction output uses the same columns every time, so the pivot or model only has to be built once.
Choose your plan