Pricing Agent
This is the largest of the six leaks, and the most ordinary. The contract says one number, the invoice says another, and nobody opens the contract for a bill this size.
Nothing is paid above the rate that was agreed.Every line is checked against the contract and the PO it belongs to. A variance does not get approved quietly — it stops, and it names the buyer who owns the contract.
What it checks
On every invoice, not a sample.
- Line rate against the contracted rate for that item, that vendor, that period
- Rate against the PO, where a PO exists and the contract does not cover the item
- Price escalations claimed against the escalation clause that permits them
- Freight, handling and surcharges against what the contract actually allows to be added
What it reads, what it writes
Reads
The vendor contract and its rate schedule · The purchase order · Invoice lines, item by item
Writes
A hold on the line, with the variance in both percentage and rupees · The contract clause the line was tested against · A note to the buyer who owns the contract
Where it sits in the team
Agents do not work alone. Each one hands its result to the next, so a finding raised here shows up as context downstream rather than being re-derived.
Hands to it
It triggers
When it isn't sure
Where no contract covers the item, the agent says so rather than passing the line. An uncovered rate is a different finding from an overcharge, and it is reported as its own thing — usually it means a contract expired and nobody renewed it.
Any check that runs on every transaction will meet cases it cannot settle. What makes a control trustworthy is not that it never hesitates — it is that hesitation produces a named question for a person, rather than a silent pass or a silent block.
See what this one finds in your last 90 days.
One export. No connector. We come back within a working day.
$Check your savings→