Purchase Analytics

The Purchase Analytics report is the procurement equivalent of the Sales Analytics report. It answers "how much have we bought, from whom, of what, over time?" and lets purchasing managers spot supplier concentration, mix shifts, and trend changes in spend.

Where to find it

Buying > Reports > Purchase Analytics.

Filters

Filter

What it does

Company

Mandatory. Drives the base currency.

From Date / To Date

The reporting window. Defaults to the current fiscal year.

Tree Type

The grouping hierarchy: Supplier Group, Supplier, Item Group, or Item. Drives which dimension forms the row tree.

Based On

Purchase Order, Purchase Receipt, or Purchase Invoice. The choice changes what "purchasing" means: PO is committed spend, PR is received goods, PI is invoiced spend.

Value Quantity

Value shows monetary totals; Quantity shows unit counts.

Range

Weekly, Monthly, Quarterly, Yearly. Adds one column per period.

Project / Cost Centre / Item Group

Scoping filters.

Purchase Analytics filter panel

Purchase Analytics filter panel


What the report shows

Column

What it shows

Tree column (Supplier / Item / Group)

The row hierarchy chosen by Tree Type. Click the chevron to expand a group.

Period columns

One column per Weekly / Monthly / Quarterly / Yearly bucket showing the value or quantity.

Total

Sum across all visible periods.

A chart at the top of the report shows the same trend.

Purchase Analytics by Supplier with one group expanded

Purchase Analytics by Supplier with one group expanded


Reading the numbers

  • Use Based On = Purchase Invoice for finance reconciliation. PI dates and amounts match what's in the General Ledger.

  • Use Based On = Purchase Order for forward-looking commitment review. This shows what you've contracted to buy, regardless of whether goods or invoices have arrived.

  • A single supplier dominating any item line is supply-chain concentration risk. Consider dual-sourcing.

  • A rising trend on one item with flat overall spend = mix shift, not growth. Useful for surfacing changing input patterns.

  • Year-on-year supplier comparison is easiest when you set Range to Yearly and Tree Type to Supplier.

Common pitfalls

  • A supplier is missing from the report. Usually no submitted document of the chosen Based On type exists in the date range. Switch Based On from Purchase Invoice to Purchase Order to check for committed-but-not-yet-received spend.

  • Cancelled documents are excluded. Amended documents show only the latest amendment.

  • Quantity sums across mixed UoMs are nonsense. If items have mixed UoMs (kg vs each), filter to one Item Group or use Value instead of Quantity.

  • Date filter is on the document's posting date. Not the receipt date or payment date. For payment-cycle analysis use a separate AP report.

  • Stock-only purchases miss expense items. This report only includes items linked through a purchase document; one-off journal-entry expenses don't appear.

Related documentation

  • Buying: module overview covering Purchase Order, Purchase Receipt, Purchase Invoice, and supplier management.

  • Run a Payment Run: batch-pay suppliers from purchase invoice balances.