Skip to content

Procurement analytics

Analytics dashboards for procurement: real spend, prices paid and gaps, every figure sourced

Zylio’s procurement analytics dashboards analyse spend as it was invoiced, not as it was budgeted: by supplier, site, category and period, with prices paid against prices negotiated, evolution over time and gaps between entities. Every figure opens on the lines that make it up, and every line on the document it came from.

The problem

The reliability of a dashboard depends on that of its data

There is no shortage of visualisation tools. What is missing is the material: consolidated procurement spend, line by line, with the price actually paid, the quantity actually delivered and the contract that applied. The ERP has the order amount; the scanning tool has the invoice total; the contract is in a PDF. None of the three knows what the other two say.

So procurement dashboards rest on aggregates: spend per supplier from payments, category from the allocation typed at order time, reference price from the rate negotiated at signature. They are right on average and wrong in the detail, and the detail is precisely where the gaps are.

A useful analytics dashboard therefore starts before visualisation: with reading the documents. That is what Zylio does, and it is what makes every displayed figure openable down to its proof.

Analyses

Three analyses, on the same lines

The same data extracted from the documents serves three complementary readings, with no new collection.

  • Price analysis

    The invoiced price against the price of the contract, rate card or price list in force, line by line. Gaps quantified, non-compliances listed, compliance rate by supplier and by site.

  • Historical analysis

    How the price paid for a reference has moved over time, at one supplier and across suppliers. The same item bought by several sites at different prices becomes visible.

  • Gap analysis

    Budget against invoiced, ordered against delivered, accepted quote against received invoice. An increase is broken down: price effect, volume effect, mix effect. Missing data is declared, never estimated.

Price-volume-mix analysis, in detail

Knowing whether an increase comes from price, quantities or what you buy.

Mechanism

From the question to the figure, and from the figure to the proof

  1. 01

    The documents are read

    Contracts, rate cards, orders, receipts, invoices, credit notes: read line by line by the Capture agent, in every format.

  2. 02

    The lines are linked

    Graph, the knowledge graph layer, attaches each invoiced line to its supplier, its item, its order and the price clause that applies. The same supplier under three legal names becomes one.

  3. 03

    The question is asked

    In plain language, in the dashboard or outside it: “spend on this category by site over twelve months”, “references whose price went up at this supplier”.

  4. 04

    Insight calculates

    Insight, the procurement intelligence layer, translates the question into a query of the graph and the procurement base, calculates, and returns the useful form: a figure, a table, a curve, a dashboard view.

  5. 05

    Every value opens

    An amount opens on the lines that make it up; a line, on the invoice, the page and the clause. The path from figure to proof is always the same.

  6. 06

    Nothing is written

    Zylio reads; it does not write. It changes neither the ERP, nor the documents, nor the data. What it displays is reproducible and traceable.

By role

Three readings of the same dashboard

An analytics dashboard does not serve the same questions depending on who looks at it. The data is the same; the scope and the angle change. Each role opens the dashboard on its own perimeter and asks its own questions, without a separate data collection for each one.

  • Procurement director

    Where spend goes across the group, what share runs under contract, which suppliers concentrate the gaps. The material for a renegotiation strategy.

  • Management controller

    Why a cost line exceeds its budget: price, volume or mix. What needs accruing, and what is explained by one specific invoice.

  • Site manager

    Their suppliers, their prices compared with other sites, their off-contract purchases. The actions within their reach, without the noise of the rest of the group.

Zylio for management control

Real cost per item, budget-to-actual gaps explained by the invoices.

Outcome

What changes for your decisions

The delay between question and answer disappears. A buyer preparing a renegotiation no longer waits for a slot with the data team: they ask the question, get the table, open it down to the invoices. The meeting is held with the facts, not with last week’s extract.

The figures presented are defensible. A price gap shown in a meeting points to the clause and the invoiced line; off-contract spend points to the invoices concerned. What used to be debated, the reliability of the figure, is no longer debated; what remains to be debated is the decision.

The scope analysed grows with no extra effort. The platform reads over 10,000 supplier documents per week; opening a new category or a new entity to analysis requires no retyping. From 5% to 100% of your spend verified: the dashboard follows the scope you decide.

The question is never “how much did we spend”. It is “how much, with whom, under which contract, and since when has it been drifting”.

Your tools

In Zylio, or in your BI tool

The dashboards live in Zylio, but the data is not captive. If your analyses are already built in Power BI or another BI tool, the extracted and linked lines go there in a stable model: same supplier, item, contract and period keys, same units, link preserved to the original document. You keep your reports and the habits of the people who read them; they now rest on real spend, line by line, rather than on aggregates copied from three systems.

Export to Power BI

Data model, refresh, join keys.

Procurement intelligence · Insight

Ask the question. It builds the analysis, and shows where every figure comes from.

Translates a question asked in plain language into a query over the graph and the procurement database, computes, and returns the useful form: a figure, a table, a curve, a dashboard. It reads, it does not write. Every value opens onto the lines that make it up, and every line onto its source document.

The delay between the question and the answer. A buyer preparing a renegotiation no longer waits for a slot with the data team.

What Insight detects

  • A category whose price has been drifting for months
  • A contract coverage rate falling, by category and by entity
  • Credit notes outstanding, with whom and for how long
  • A single-source reference with no alternative on record
  • A gap between the budget for a cost line and what was actually invoiced
  • An increase driven by mix or volume rather than price
  • A missing figure: declared as missing, never estimated

Nothing is lost. Everything can be checked, everything can be proven.

  • The contract clause and the invoice line, highlighted side by side.
  • Every extracted value stays linked to the exact place in the document where it was read.
  • The same case produces the same decision, today as in six months: the rules are applied deterministically.
  • No discrepancy is set aside in silence. Anything that matches no rule is raised, with its reason.
  • The agent records what it did, in the order it did it: who, what, how much, when.

Frequently asked questions

How is this different from a dashboard built on the ERP?

The ERP knows the order and the payment; it knows neither the invoice detail nor the contract. Zylio dashboards rest on documents read line by line, which makes it possible to compare the price paid with the price negotiated and to open every figure down to the invoice. The two complement each other: Zylio reads the ERP, it does not replace it.

Are the analyses predictive?

Zylio shows what the documents say: a price drifting for several months, an increase driven by volume rather than price, a coverage rate falling. It does not estimate what is missing and does not predict what is not written. Anticipating remains your decision, taken on dated, sourced facts.

Do I need a data team to use the dashboards?

No. Questions are asked in plain language and the answer comes in the useful form: figure, table, curve. A data team remains valuable for integrating the data into your warehouse or existing reports, which the export in a stable model makes easier.

Can several entities or sites be compared?

Yes, it is one of the most frequent uses: the same reference bought by several sites at different prices, the same supplier under several legal names, a framework contract applied at headquarters and ignored elsewhere. The comparison is made on invoiced lines, with the documents as proof.

Measurable impact in every environment

More than 5 million procurement documents analysed

Between 1 and 7% of margin recovered

on the scope analysed

From 15 to 45% of time given back to teams, per FTE

depending on the scope and on data maturity

Zylio fits into your existing ecosystem.

The ERP runs the process. Zylio handles the exception and recovers the value that escapes it: invoices without a purchase order, line-by-line price discrepancies, duplicates and overbilling, off-contract spend.

  • SAP
  • Sage
  • Oracle
  • NetSuite
  • Microsoft Dynamics 365
  • Pennylane
All integrations

Your data under high security.

Zylio meets the most demanding standards, and nothing is committed without your approval.

Certifications
SOC 2 Type II · ISO 27001
Hosting
Hosted in France
Encryption
End-to-end AES-256 encryption
Access
Enterprise SSO · multi-factor authentication · Zero Trust approach
Security and compliance

See what this looks like on your own data

Twenty minutes, on a spend category of your choosing. We show you what the agents detect, with the evidence behind it.

  • No commitment, on your own data
  • Result in 3 weeks
  • 20 minutes, no sales pitch
  • Your data stays hosted in France
  • No change of tool or process