Sunday, November 1, 2026

What is spend analysis? How to see where your company’s money actually goes

Procapy Team

Procurement went into the courier contract renewal with the number finance had sent that morning: Rp 610 million last year, the total on the courier’s vendor account. They asked for the rate the courier gives customers who spend more than Rp 1 billion a year, and were turned down politely. At Rp 610 million, the account manager said, the current rate was already a good one.

Three weeks later, an analyst building next year’s budget found the rest. The courier had two more vendor records, created by different AP staff under slightly different names. A sister company in the group used the same courier without a contract, at list prices. And branch staff sent parcels from the courier’s counters and claimed them back on expense reports and corporate cards, coded to “Postage” or “Miscellaneous”. In total, the company had spent Rp 1.2 billion with the courier. The courier knew. Procurement didn’t.

Spend analysis is how you find the Rp 1.2 billion before the meeting rather than after it. This guide explains what spend analysis is, how it works, a worked example of the courier, why spend analysis goes wrong and how to start one that stays up to date.

What is spend analysis?

Spend analysis is the work of collecting everything the company spends, from every source and every entity, cleaning and classifying it, and looking at it by vendor, by category and by who bought it. The point is to act on what you find: consolidate vendors, negotiate prices, move spend onto contracts and see purchases that went around the process.

The result is often called a spend cube: every line of spend tagged with who supplied it (the vendor), what it was (the category) and who bought it (the cost centre, entity or project). Any question about spend is a slice of the cube.

It’s easy to confuse with three reports finance already produces:

Budget against actual: shows whether each cost centre spent more or less than planned. It doesn’t show who they bought from or at what price.
Expenses by GL account: classifies spend the way the accounts need it, not the way the company buys. One “Office expenses” account can hold paper, printer leases, cleaning and the coffee machine.
The AP ageing report: what you owe suppliers today. Spend analysis looks at what you paid them over a year, including spend that never went through AP.

How spend analysis works

Gather every source. Supplier invoices and purchase orders (POs), but also employee claims, corporate cards, petty cash and every entity in the group. Twelve months is a common starting window.
Clean the vendors. Merge records that are the same company under different names or codes, so each vendor appears once, with one total.
Classify by category. Give every line a category from a short list that matches how the company buys (courier, IT hardware, cleaning, travel), separate from the GL account.
Add who bought it. Cost centre, entity and project, plus whether the purchase was under a contract or a PO.
Slice it by the question. One vendor across every entity, one category across every vendor or one cost centre across every category.

The questions most teams start with:

Who are our top vendors, and how much of total spend do the top 20 account for?
How many vendors do we use per category? Ten courier companies is usually nine too many.
How much spend is under a contract or on a PO? Purchases made outside agreed contracts and processes are often called maverick spend, and they’re where list prices get paid.
Do we pay different prices for the same thing? The same item at different prices on different POs, or the same service at different rates in different entities.
What is our tail spend? Tail spend is the long list of small vendors that together make up a small share of spend, each too small to manage on its own.

A worked example: one courier, five places

After the renewal meeting, the analyst pulls a year of spend from every source and searches for the courier by name, NPWP and bank account. The amounts are only illustrative:

Where the courier spend was (Rp million)	Amount
Main vendor record, head office	610
Two more vendor records, head office	185
Sister company, no contract	240
Employee claims, branches	95
Corporate cards, branches	70
Total	1,200

The analyst then compares what each part of the group paid per kilogram for the same parcel service:

Buyer	Spend (Rp million)	Rate per kg (Rp)
Head office, on contract	795	10,000
Sister company, list rate	240	12,500
Branches, at the counter	165	15,000
Total	1,200

What the analysis tells procurement:

The company is a Rp 1.2 billion customer, not a Rp 610 million one. That is above the Rp 1 billion threshold for the rate procurement asked for.
Rp 103 million was paid above the contract rate. At Rp 10,000 per kg, the sister company’s 19,200 kg would have cost Rp 192 million instead of Rp 240 million, and the branches’ 11,000 kg Rp 110 million instead of Rp 165 million. That’s before any better rate for the bigger volume.
Most of the fix is process, not negotiation. Merge the three vendor records, extend the contract to the sister company and give the branches an account under it, so a parcel sent from a counter goes on the company’s rate instead of an expense claim.

Procurement reopened the renewal with the full number, and with a plan to move Rp 405 million of spend onto the contract.

Why spend analysis goes wrong

The vendor master is full of duplicates. With or without “PT”, with or without “Indonesia”, with a branch name added: one vendor becomes three, and none of them looks big. Duplicate records also cause duplicate payments.
Categories that are really GL accounts. Accounts describe a cost for the books, not what was bought. And a large “Miscellaneous” or “Other” hides exactly the spend you’re looking for.
Only AP counts. Employee claims, cards and petty cash are left out because they live in another system, though at branches they can be most of what you spend with some vendors.
One entity at a time. Each PT analyses its own spend, so nobody sees that three of them buy from the same supplier at three prices.
Coding in a hurry at month-end. When AP codes hundreds of lines in the last week, the category is whatever fits fastest. The person who made the purchase knows what it was, so code it when they request or claim it.
A once-a-year project. A consultant cleans the data, the report is impressive, and by the next quarter new duplicates and new “Miscellaneous” lines have crept back.
Findings without an owner. “Too many courier vendors” isn’t an action until someone is named to consolidate them by a date.

Spend analysis in Indonesia

Match vendors on NPWP and bank account. Names are written many ways, while the tax ID (NPWP) and the bank account rarely change. One company’s branches can share an NPWP, so check the address before you merge two records.
Compare amounts before VAT and withholding. Input VAT you can credit (PPN masukan) isn’t a cost to the company, and PPh 23 withheld on a service is still part of the vendor’s price. Compare every vendor on the same basis, usually excluding VAT and before withholding, or service vendors look smaller than they are.
Faktur pajak as a cross-check. The faktur pajak you receive show each VAT-registered vendor’s NPWP and the amounts invoiced, which makes them a useful check that the analysis hasn’t missed a large vendor.
Petty cash and cash advances. At branches, warehouses and project sites, much of the spend goes through petty cash (kas kecil) and cash advances. Include them, and settle advances with receipts that name the vendor, or that spend stays invisible.
A group of PTs. Many Indonesian groups run several PTs, each with its own books. Spend analysis has to sit above them, with one vendor list for the group and each line still tagged with the entity that paid.

Signs your spend analysis needs work

Your spend analysis probably needs work if any of these sound familiar:

Nobody can say this morning how much you spent with your largest vendor last year.
Procurement asks finance for vendor totals before a negotiation, and waits days.
The same vendor appears under more than one vendor code.
“Miscellaneous” is one of your biggest categories.
Employee claims, cards and petty cash aren’t in the numbers.
Each entity reports its spend in its own spreadsheet.
The last spend review was a project, not a monthly report.

The vendor always knows how much you spend with them. Spend analysis is how you find out too.

How to start a spend analysis

Start with one question. Your top 20 vendors, or the category with the next contract renewal. A useful first answer earns the time for the next question.
Pull 12 months from every source. AP invoices, POs, claims, cards and petty cash, from every entity, with the vendor name, NPWP, bank account, amount, date, GL account and cost centre.
Clean the vendors first. Merge duplicates on NPWP and bank account, and stop new ones at the door with a vendor onboarding checklist that flags an NPWP or bank account already on file.
Write a short category list. For example, 15 to 30 categories in the words buyers use, each mapped to a GL account, and a rule that “Other” stays small.
Code at the source. The requester or claimant chooses the category and cost centre when they ask, not AP at month-end, and the approver checks it.
Track four numbers. Spend with the top 20 vendors, the share of spend under a contract or on a PO, vendors per category and price differences on items you buy often. A PO policy raises the second number over time.
Give every finding an owner and a date. Consolidating courier vendors by the end of the quarter is procurement’s job, not a line on a slide.
Make it a monthly report. The same cut, refreshed every month and reviewed in the same meeting, so drift shows up within a month rather than at next year’s renewal.

How Procapy helps

In Procapy, spend is classified when it happens rather than cleaned up a year later. In Proca to Pay, spend starts from approved vendors, and requests are checked against policy and budget before they become commitments, with the cost centre, project and expense category filled in automatically. In Capy Expense, ProcAI proposes the category, cost centre and project from each receipt and the employee’s history, and card spend is coded and approved like any other expense. Procapy suggests the GL account and cost centre from the vendor, category and history, learns from your team’s corrections, and lets finance lock the mapping for specific vendors or categories.

Spend by cost centre, vendor, project, category and entity is then available the moment a transaction is approved, without a spreadsheet being assembled first. Total spend with each vendor is shown across departments, cost centres and entities, with price variance on the same item across purchase orders, so procurement walks into a renewal knowing the whole number. Groups see spend by country, category, vendor and cost centre side by side, translated to the reporting currency at the rates you specify.

With Proca Agents, the recurring report doesn’t need building either. An agent assembles reports such as spend by cost centre and the month-end pack on schedule, and ad hoc ones on request, and drafts summaries for management from the transactions themselves. Your team reviews the numbers instead of building the spreadsheet, and every run is logged in the same audit trail as the team’s own work. The finance team resources page has more. Book a 30-minute walkthrough, bring your chart of accounts and the spend report your CFO asks for, and we’ll map where each number would come from in Procapy.

Back to blog