Blog · Procurement and supply chain · Procurement
Procurement spend analysis starts with reconciled accounts payable lines and a consistent purchasing scope. Follow the export, mapping, comparison and review steps, with spreadsheet formulas and a worked example.
Procurement spend analysis turns reconciled purchasing lines into comparisons by category, supplier, site and period. Its first job is to prove the spend total; its next job is to identify the purchases worth investigating. A large category or a fast increase is a review priority, not a savings estimate.
Write down the business entities, posting dates, currencies and accounts included. Choose invoice spend, purchase-order commitments or cash payments and label that choice. They answer different questions, and adding them together counts different stages of the same purchase.
For the workflow below, a US distributor analyzes September 2026 AP invoice lines in USD. Amounts are signed purchasing values after credits, with separately identified taxes excluded on the approved analytical basis. The AP owner supplies a control extract on that same basis. Neither payroll nor customer invoices belongs in this file.
Keep a short scope register beside the calculation: included accounts, exclusions, the date field used, and who approved the definition. An exclusion should have a reason and an amount that can be tied back to the original export. Resolve the detailed treatment of credits, tax and currency before comparing categories.
Export the entity, supplier identifier, invoice or credit number, invoice line number, posting date, account, site, currency and signed amount. Keep the original supplier name and description even after mapping them. Those fields let the category owner inspect an unexpected purchase without reconstructing the export.
Build a line key from entity, supplier, document number and line number. An invoice number alone is insufficient when different suppliers reuse numbering sequences. In this small table, the abbreviated keys represent those complete identifiers.
| Line key | Posting period | Supplier | Category | Site | Net spend (USD) |
|---|---|---|---|---|---|
| L01 | September 2026 | Acme Packaging | Packaging | Dallas | 18,000 |
| L02 | September 2026 | Lakeside Packaging | Packaging | Denver | 7,000 |
| L03 | September 2026 | ClearSite Services | Facilities | Dallas | 12,000 |
| L04 | September 2026 | ClearSite Services | Facilities | Denver | 8,000 |
| L05 | September 2026 | Northstar IT | IT | Dallas | 15,000 |
| L06 | September 2026 | Acme Packaging | Packaging | Dallas | -2,000 |
| Total | 58,000 |
The negative line is a credit, not a duplicate to discard. The control extract totals $58,000, so the line sum must equal that amount before any category comparison is accepted.
With this table in A1:F7, calculate the line total and the difference from the AP control in Google Sheets:
=SUM(F2:F7)
=SUM(F2:F7)-58000
The difference is zero. Check repeated line keys in G2 and fill down:
=COUNTIFS($A$2:$A$7,A2)>1
Google documents COUNTIFS as counting rows that meet the specified criteria. Investigate a repeated key before deleting a row: an allocation export may intentionally split a source line and need a more detailed key.
Use supplier identifiers to group spelling variants, and keep the original values available for review. Assign each purchasing line one category for this view. When a line must be split, document allocation amounts that sum back to its original value.
A mapping table should return one applicable result per line. Several matching supplier or contract records can multiply an invoice amount when combined. Compare both the number of purchasing lines and the signed total before and after mapping; a matching grand total alone can hide offsetting mistakes.
Keep unmapped purchases visible in an explicit exception category. A blank category should never disappear from the report. The separate spend-cube workbook guide covers the workbook structure; this workflow concentrates on the controls and decisions around it.
The distributor's approved August category totals are the comparison inputs below. Both months use the same scope and mapping. September follows directly from the invoice lines above.
| Category | August spend (USD) | September spend (USD) | Change (USD) | Change |
|---|---|---|---|---|
| Packaging | 20,000 | 23,000 | 3,000 | 15.0% |
| Facilities | 18,000 | 20,000 | 2,000 | 11.1% |
| IT | 10,000 | 15,000 | 5,000 | 50.0% |
| Total | 48,000 | 58,000 | 10,000 | 20.8% |
For a category label in H2, return September spend with:
=SUMIFS($F$2:$F$7,$D$2:$D$7,H2)
Google's SUMIFS documentation explains how the function sums values meeting multiple criteria. Add site or period criteria when working from an export containing several sites or months.
If August is I2 and September is J2, calculate the change and percentage in K2 and L2:
=J2-I2
=IF(I2=0,"Review baseline",K2/I2)
Percentages are rounded to one decimal place. The total change is $10,000 divided by $48,000, or 20.8%; it is not the average of category percentages. IT contributes $5,000 of that increase, so its invoice detail deserves an early review.
The category sum is $23,000 + $20,000 + $15,000 = $58,000. The site view must agree: Dallas is $43,000 and Denver is $15,000. Supplier totals must also return $58,000, including Acme's credit. A view that does not agree is an incomplete or duplicated population.
Give the IT owner the underlying invoices and ask whether the increase reflects renewals, additional licenses or a changed charge period. Give facilities its site split. Assign each question an owner and a follow-up date rather than labeling the entire increase avoidable cost.
Spend concentration does not establish procurement control. Calculate spend under management separately when contract dates, category scope and buying channels are available. For a proposed purchase, cost and price analysis addresses quote comparisons and disclosed supplier costs rather than this historical spend grouping.
Covirage is not affiliated with Google.
Bring your AP line export and the supplier or category files that support your review. Covirage maps the columns, and its tools compute and check the spend comparisons; the external AI model explains the results with every figure traced to its rows. Create a free Covirage account, then set up your business and bring a sample of your own export.
See Covirage for procurement teams for the purchasing context.
Start with AP invoice lines containing a stable line identifier, posting date, supplier, site, account or category, signed amount and currency. Add the supplier master for consistent names and contract or purchase-order exports when the review also needs purchasing coverage or compliance.
Use a closed accounting period for the recurring review and refresh the mapping exceptions alongside it. Monthly reviews suit changing categories, while sourcing decisions may need a longer comparison window. Keep the same scope and period basis whenever you compare results.
Higher spend can reflect more units, different items, timing, freight or price changes. A category total cannot separate those causes. Investigate the underlying item, quantity and unit-price rows before describing a spend increase as inflation or a purchasing failure.