Spend Analysis

A business can know its total expenses yet still not know how much it spends on packaging across departments, so spend analysis brings purchasing transactions together and groups them in a way managers can use. It answers what was bought, who supplied it, where and when, with the aim of better decisions, not a prettier chart.

NIGP's spend-analysis guidance covers procurement data and its use and SAP explains common analytical approaches and dimensions, but these sources are frameworks, not proof that a specific percentage saving will follow, because the quality of each conclusion depends on coverage, classification and contract facts. Collect data from invoices, purchase orders, card transactions and expense claims, because a single accounts-payable system may miss card purchases or local branches.

Decide the period and which entities are included, and document omissions so a figure labelled "total spend" does not quietly exclude a large category. Clean supplier names too, since "Acme Ltd", "Acme Trading" and a branch name may be one group while similar names can also represent unrelated firms, so match tax identifiers or validated vendor records where possible, because incorrect merging can exaggerate concentration and failing to merge hides it.

Categorise purchases by what was bought, not only the vendor, because one supplier can sell stationery and software, which carry different risk and sourcing opportunities. A single "miscellaneous" bucket makes the analysis less useful, so use a manageable taxonomy and review uncertain classifications with category owners.

Normalise currency and time using a stated method when comparing across countries, and separate tax, freight and rebates consistently, because an increase in nominal spend may reflect exchange rates or inflation rather than greater volume, so explain the basis before declaring a category out of control. Spend by supplier shows concentration, since a business buying 80% of a critical component from one firm may face resilience risk, although spend alone does not reveal whether alternatives are qualified or whether the supplier has several independent factories, so pair numbers with operational context.

Spend by category can reveal fragmented buying, such as five teams purchasing similar packaging at different prices. Consolidation might improve terms, but only if specifications and delivery needs are comparable, because a lower unit price can be offset by higher freight or minimum orders, so test total landed cost.

Contract compliance is another question: compare actual purchases with negotiated suppliers and pricing during each contract's effective dates, and record exceptions separately, because a purchase outside a contract may be an authorised emergency rather than misconduct. A simple coverage metric divides classified spend by captured spend, so if $9 million of $10 million in the data has a valid category, classification coverage is 90%.

That leaves $1 million whose nature is unknown, and it does not tell you whether the captured data includes every channel of purchasing. Validate surprising results before acting, since an apparent 30% price increase could be a change from boxes to individual units, a larger product or tax included in one data source, and a wrong "savings" claim can damage procurement's credibility with operations.

Distinguish negotiated savings from realised savings, because a lower contracted rate only produces a benefit when eligible purchases move to that rate, and a reduction in spend might simply reflect lower production, so finance should verify the baseline and the resulting profit or cash effect. Build an action list from the findings, such as renegotiating a contract, qualifying a backup supplier or repairing the catalogue so staff can use it, with an owner, expected benefit, cost and due date, because the value comes when reliable evidence changes a buying choice or reduces risk.