UAE · ENBook a demo
Procure AIFinanceInvestigator

Savings Realisation Agent

Checks claimed procurement savings against invoiced spend and contract terms.

Savings Realisation AgentProcurement Spend Agent · Planning and Compliance
Industry
Procure AI
Department
Finance
Team
Planning and Compliance
Kind
Investigator
Approver
Procurement Director
Code
FIN-16

It validates the savings procurement teams claim for clients and for the company itself, comparing the negotiated contract price and baseline with what was actually invoiced and paid, and explains where savings leak: off-contract buying, invoiced prices above the contracted rate, missed volume tiers, volumes below forecast, or a baseline that does not hold. It marks each savings line validated, partly realised or not realised with its evidence, which gain-share billing and bonuses then rely on. **The problem it solves:** Why realised savings differ from what was claimed: which suppliers, invoiced prices, volumes, off-contract buying or baselines drive the gap, and since when.

How it works

6 steps, and a person signs off before step 6.

  1. 01Looks it up

    Finds the record the request is about in the spend analytics warehouse: invoiced and paid spend, unit prices and volumes by supplier, category and client, alongside the contracted rates, volume tiers and baselines from the contract lifecycle management system..

  2. 02Reads the request

    Works out what is being asked and what a complete answer needs.

  3. 03Checks the facts

    Checks figures, dates and rules against the source records, not from memory.

  4. 04Works it through

    Weighs competing explanations against the evidence and shows which one holds up.

  5. 05Asks a person

    Hands the work to Procurement Director with its reasoning before anything goes out.

  6. 06Acts

    Once approved, it acts in the spend analytics warehouse: it records each savings line's validation status and evidence, and creates recovery tasks for the category managers. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The savings methodology agreed with finance and in each client contract: baseline rules, hard savings versus cost avoidance, realisation periods, contract rates and volume tiers, and the evidence needed for finance validation.

Reads from

the spend analytics warehouse: invoiced and paid spend, unit prices and volumes by supplier, category and client, alongside the contracted rates, volume tiers and baselines from the contract lifecycle management system.

Acts in

the spend analytics warehouse: it records each savings line's validation status and evidence, and creates recovery tasks for the category managers.

Hands back

An object with realisation_period, total_claimed, total_validated, lines (a list, each with initiative_id, client, supplier, savings_type, claimed, validated, status (validated, partly_realised, not_realised or too_early) and evidence), leakage (a list, each with leak_type (price_above_contract, volume_shortfall, off_contract, baseline_failed or missed_tier), supplier, value, evidence and likely_cause) and recovery_actions (a list, each with action, owner, amount and deadline).

Asks a person when

It marks a savings line that a gain-share invoice or bonus depends on as not or partly realised, proposes recovering an overcharge from a supplier, or the client disputes the baseline.

ApproverProcurement Director

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Invoiced price above contract that counts as leakage (%)2An invoiced unit price this far above the contracted rate is leakage.
Volume below forecast that cuts the saving (%)15Volume this far below forecast reduces hard savings pro rata and is explained.
Flag a category off contract by more than (%)10A category with more than this share of spend outside the new contract is flagged as leakage.
Months of invoices before validating3A hard saving is validated only after this many months of invoiced spend at the new price.
Smallest leakage to report (USD)2000Leakage below this is summarised, not itemised.

Limits are settings, not code: a manager changes them without a developer.

Rules it always follows

  • Validate a hard saving only from invoiced and paid spend at the new contract price over at least 3 months, against the baseline the methodology or client contract sets.
  • Never count cost avoidance as hard savings, and never validate a saving whose baseline is undocumented.
  • An invoiced price more than 2 percent above contract is leakage; report its value and the invoices behind it.
  • Volume more than 15 percent below forecast cuts the saving pro rata, with the cause named.
  • Flag a category with more than 10 percent of spend outside the new contract as contract leakage.
  • Itemise leakage of at least 2000; recovering an overcharge from a supplier or changing a gain-share basis needs the Procurement Director.

See the Savings Realisation Agent agent on your own work.

We’ll run it on a sample of your work and show you what your approver would see.

Savings Realisation Agent · Procure AI | Basinwright Industries