Tellius for Procurement

Everything you negotiated,
actually realised.

Your ERP flags that the invoice and the contract disagree. Tellius decides which one is wrong and prepares the correction. Then it reads the same contracts for what you were owed and never claimed. Every night, under your rules. Your team approves what moves.

read-only to start

you approve what moves

every line · every night

The problem

The contract changed. The price master did not. Every line matched, and the price was still wrong.

Not fraud, mostly. A unit nobody converted, an amendment nobody loaded, a rebate nobody claimed. Each with its own page.

Hands off, with the evidence attached
Procurement operations

the queue, already decided

Accounts payable

the line, held with the reason

Category management

the amendment, quoted

Contract owner

the clause, cited

Internal audit

the evidence pack

04

04 · Rebates never claimed

What were we owed and never asked for?

Tiered rebates, volume commitments and price protections that expire unclaimed, because nobody reads the clause against what was actually bought.

8.6%

of a contract’s value erodes between signature and delivery, on average

WCC / Deloitte contract value erosion research

Value Recovery

quarterly

See the App →

05

05 · What the audit found a year later

A recovery firm bills a share of what you already lost.

Billing discrepancies, contract ambiguities, conflicting pricing data and missed rebates, all found after the money left.

See the App →

Two years

a cost-plus supplier billed at a 10% margin instead of a 10% markup, before an audit caught it

WCC / Deloitte contract value erosion research

Value Recovery

quarterly

Tellius decides which record is wrong.
Your team approves what moves.

Four jobs, in the order a week happens. Open one to see the screen it lands on.

01

Finds the term that actually governs the line.

Contract, amendment, purchase order, receipt, price master and invoice, pulled for one line before anything is compared. Not the number sitting in your contract system. The term that was actually in force on the day you were invoiced.

Nothing is contacted and nothing is changed.
02

Clears the exceptions that were never real.

A unit nobody converted. An FX date nobody checked. Freight bundled into a unit price. Last night 412 of 2,847 lines were never variances at all, and every one was released with the reason written down. This step is pure arithmetic, so it answers the same way every time.

Below your materiality band, it releases and files the reason.
03

Names which record is wrong. The invoice, the contract, or neither.

Every line resolves to exactly one cause out of twelve, never two, which is what makes a night reviewable a year later. Sometimes the answer is that nothing was wrong at all. A ruling with the evidence attached, not an alert with a score.

The cause and the record are named on every case.
04

Hands it to the person who can fix it.

The master update or the dispute packet is already written when your team opens the case. Every held line sits with a person or a supplier, never with Tellius, and the source is read again after approval to prove the record actually changed.

You approve. Tellius verifies, then closes the case.
01 · What gets pulled
Spend Leakage Control · Assembling one line
Assembling one lineSL-4471990 · Norwell Industrial · line 1 · before anything is compared
ContractCTR-0928 · frame agreement · in force 1 Janpulled
AmendmentA-491 · approved 14 Feb · effective 1 Marpulled
Purchase orderPO 482 · revision 6 · changed 3 Marpulled
ReceiptGR-77120 · quantity and unit as receivedpulled
Price master$13.60 per EACH · last touched 1 Janread, not trusted
InvoiceINV-4471990 · dated 22 Mar · $14.20 per EACHpulled
Six records, one line.Nothing contacted, nothing changed.assembled
02 · Never real
Spend Leakage Control · Unit, currency, date, tolerance
Unit, currency, date, tolerancearithmetic, before anything is judged
2,847lines checked
412never a variance
0records changed
Unit of measure1 CASE = 10 EACH · material master · convertedNot a variance
CurrencyUSD invoice, EUR contract · FX at invoice date · within clauseNot a variance
Tolerance$18.40 over on $22,900 · below your materiality bandReleased
Freightbundled into unit price · split out and re-checkedNot a variance
arithmetic only · no judgment applied at this step
03 · The ruling
Spend Leakage Control · Which record is wrong
Which record is wrong187 held · one of twelve causes · the record named
106the contract was wrong
49the invoice was wrong
19the PO was wrong
Contract is wrongSL-4471990-1 · Norwell Industrial · invoice $14.20 / EACHApprove
GoverningAmendment A-491 · $14.20 / EACH · effective 1 MarCited
Preparedupdate the master to A-491, release the lineWaiting on you
Evidence checked · 9 of 91 failing · contract price: $14.20 against a master that still says $13.60
04 · In play
Spend Leakage Control · In play
187 lines held, $2.15M of payment on holdevery one has a determined cause and a correction already written
CauseLinesHeldBall withPrepared
Contract master stale106$1.24Myour buyermaster update staged
Supplier overcharge38$612Kthe supplierdebit note transmitted
Unauthorised PO change19$148Kthe buyer’s managerPO correction staged
Index miscalculated11$67Kthe supplierpartial dispute sent
No governing contract9$41Ksourcingrouted as maverick spend
Evidence insufficient4$38Kyoublocked on data, not on judgment
Nothing here is waiting on Tellius.Each line is with a named person or a supplier, with a clock on it.0 with us

The Procurement AI Worker

Two jobs. One before you pay, one after.

Spend Leakage Control stops the wrong price before the money leaves. Value Recovery finds what you were owed and never claimed. Same ERP, same contracts, same price masters. Your team approves what moves.

Agent

Spend Leakage Controlevery night
last run 02:052,847 lines read2,656 released4 need you
this quarter$4.9M

of incorrect payment prevented

1,204 cases closed

What happened

A supplier billed $14.20 per each against a master that still says $13.60.

Decided

The invoice is right. Amendment A-491 took effect 1 March and was never loaded.

Evidence

The amendment, dated · the master it supersedes · the purchase order · the receipt

Response

The master correction, written · the line released on approval

Owner

The contract owner approves the master change · accounts payable releases the line

Every invoice line against the term that governs it, before payment. The cause named, the record named, the fix prepared.

Hands youthe held line, with the correction written · the release, with the reason

Accounts payable releases · the contract owner approves the master change

Agent

Value Recoveryquarterly
quarter closed · 31 Marone supplier bookfiled 12 May
this quarter$1.6M

recovered on disputes

measured on the credit note

What happened

A tiered rebate moved to band 3 in February. The credit was never claimed.

Decided

Owed under §4.1. Volume passed the band threshold on 14 February.

Evidence

Clause §4.1 · the purchase history · the credit notes received · three comparable quarters

Response

The claim packet, filed with the clause and the volume evidence on one page

Outcome

Measured on the credit note, not on submission

What you were owed and never asked for. Rebates, volume commitments and price protections, read against what was actually bought.

Hands youthe filed claim, with the clause · the recovery, on a date

Procurement finance approves before anything is filed

Measured on the record, not the ruling.

All of it runs under the rules your team wrote: what counts, who approves, what was corrected.

“Nothing was wrong” is an outcome.

Those get counted. A system that never reaches it only makes more work.

See your rules ↓

2,847 exception lines.
Only 4 needed a person.

One night, one supplier book. The 412 are the ones to notice — nothing was wrong with them at all. Software that simply makes two records agree would have “fixed” every one of them by editing a contract that was already correct.

2,244released. Nothing was wrong.
412false variances — a unit or a currency, never a variance at all.
187held, with the correction prepared.
4needed your decision.

Reads every source you already run.

Records and documents, as one body of evidence.

The numbers you license and the documents that govern access, read together. Nothing is written back without your team's approval.

Your rules decide what matters.

Written once. Applied the same way on every supplier.

What counts as material, who approves, and what your team has already ruled on: in your words, kept, and applied everywhere.

Twelve things can be wrong.

Each one has exactly one fix.

All twelve, grouped by the answer. Every line resolves to exactly one of them, never two — which is what makes a night reviewable a year later.

The rule, in your words

A regional plan under 50,000 lives doesn't need a person. File it with the reason.
set by the access leadMarch

Applied this quarter

Cardeza210
Velitra118
Omryn62
390 times. Same rule, same reason, no analyst deciding it differently on a Friday.

Corrected once, kept

Patients already past a preferred agent are grandfathered.

given by access strategyMarch
541sizings since March
0overturned
Change it onceEvery brand follows tomorrow.Move a threshold and it applies everywhere.
AlwaysNothing moves without the approver you named.A person approves before anything leaves the team.
Also in placeMateriality bandsRole requirementsReplay on closed quartersEvidence pack archiveCorrections kept

The replay

How much of last year's queue

was never real?Twelve months, read-only, thirty days.

Never real

14% of the queue

Lines your ERP raised that were never variances at all — a unit, a currency — released with the reason written down.

Wrong before payment

$41,200 on one line

Overcharges decided before the money left, so there is nothing to chase back a year later.

Never claimed

$1.6M recovered

Tiered rebates, volume commitments and price protections that expired unclaimed, claimed back inside the lookback.

Of the variances you paid last year, this is what would have been caught before payment, how far it agrees with your own validators, and none of it touches your financial systems.

A recovery firm takes a share of what you already lost. This is a fixed fee, and the record that caused it is corrected, so it does not come back.

Priced by the supplier spend it manages, not per line, per seat or per recovery. The replay comes first, at a fixed price. Nothing is written back without your approval.

Close