Home · Solutions · Procurement
Solution · ProcurementWhat the clause entitles, what the supplier charged, and a decision before the window shuts
Indexation clauses that get applied, and renewals decided
Robots recalculate each contract's entitled uplift from the published index, compare it with what was invoiced, and put the renew, renegotiate or terminate decision in Teams before notice expires.
Executive summary
Your suppliers calculate your annual price increase. Nobody on your side checks their arithmetic.
Each price clause first becomes parameters a machine can apply: the index it names, the base period, the lag, any floor or cap.
Every anniversary is recalculated, not the handful somebody had time for.
the SAP claim log; the SharePoint recalculation record; the Power BI renewal and exposure model
Business problem
Contract economics
Price clauses are negotiated with care, then applied by the only party with an interest in the answer. Each names an index, a base period, a lag, often a floor or a cap, sometimes a formula weighting consumer prices against labour costs. Turning that into a number takes ten minutes when the clause is at hand. In practice it is done once, by the supplier, who never shows the working.
The notice date is the other half. Every agreement has a window, and the company either uses it or the contract runs another term. Using it means arriving with a position: what the term actually cost, how the price moved against the index, what the market now offers. That takes days to assemble, so it starts late, and letting the contract roll is the safe answer.
None of this feels like a crisis, which is why it survives. A category manager sees one increase at a time and each looks small; the controller books the variance and blames inflation; the finance director sees the aggregate at the next budget round, when the increases already sit inside the base. At 480 contracts nobody holds the whole picture, and a register that lists them does not do arithmetic.
How it works today
- SystemThe supplier sends a new rate card, a price letter, or an invoice at a higher rate citing the clause
- PersonSomeone in procurement or property finds the contract, reads the clause and forms a view on the number
- WaitingChecking waits on the published index, on whoever knows the base date, or on month end; the invoice is paid first
- Risk of errorThe uplift is accepted as charged, nothing is compared with the entitled figure, and the new price becomes next year's base
- PersonThe renewal surfaces from a calendar reminder with weeks left in the window; spend history, complaints and the clause wording are then requested from three departments
- Risk of errorThe notice date passes, the agreement renews on the incumbent's terms, and the decision is deferred a full term
Why the current process costs more than it appears
The budget shows headcount, not what it is spent on.
- Overcharges compound. A third of a point above entitlement does not end with that invoice; it becomes the base for the next indexation and every one after it, and recovering it later means a credit-note negotiation most teams abandon.
- Checking is skipped where the money is. Small contracts get verified because they are easy; the lease and the facilities framework, where a point is worth five figures, are the ones nobody has time to reconstruct.
- Budget variance is explained rather than investigated, because proving a supplier wrong needs the clause, the index value for the right period and three years of charges in one place.
- Renewal by default is still a decision, taken by nobody, and a closed window commits the company for another term at a price it never tested.
Cost of inaction
Indexation errors behave like annuities: an uplift accepted this spring is charged again next spring on a base that already contains it, which is why the third row is not a worst case but two years of one mechanism. The middle row is one line of arithmetic on stated assumptions, about €32m of this illustrative group's spend and rent under an indexation clause, and a third of a point of unchecked drift on it.
Beside that runs the renewal nobody decides: another term at a price never tested, competing offers never requested. Evidence erodes at the same pace, because a difference raised inside the period is arithmetic the supplier has to answer, while the same difference a year later is a favour to ask for.
A plausible organisation with realistic proportions. The figures are there to be recalculated on your data; they are not a client result.
A retail and property group, 130 stores in Poland and Czechia plus a small commercial portfolio, 2,600 employees, SAP and Microsoft 365; four category managers, one lease administrator and two lawyers cover the whole base.
480 active supplier and lease contracts worth about €48m a year, roughly €32m of it under an indexation clause; 140 indexation or renewal events a year, about 12 a month, across leases, facilities, security, waste, energy and IT.
Contracts are registered and their dates tracked, but the price clauses live as scanned text. Increases arrive already calculated by the supplier, are checked against the budget rather than the clause, and renewals are prepared in the last three weeks.
About three hours per event, most of it reconstruction rather than judgement: locating the clause, establishing the base period, finding the index vintage, pulling the charges applied since the last anniversary.
Each clause is held as parameters; robots retrieve published index values, recalculate the entitled price, compare it with what was invoiced, and open a renew, renegotiate or terminate task in Microsoft Teams with the numbers and the deadline attached.
In the modelled case every anniversary is recalculated instead of a chosen few, differences are raised inside the period rather than a year later, and no window closes without a recorded decision. The figures are a model, not a measurement.
Proposed solution
Each price clause first becomes parameters a machine can apply: the index it names, the base period, the lag, any floor or cap, the weights where a formula mixes indices, the effective date and the notice window with its owner. They live in a versioned workbook procurement edits in Excel Online, beside the contract record on SharePoint. Clauses that resist parametrisation go to a lawyer, and their count is reported.
On each publication date a robot fetches the index values the clauses name, from Eurostat and the national statistical offices, storing each with its vintage so a calculation can be reproduced as it stood. At the indexation date it applies the clause, writes the entitled price with its arithmetic, then reads what was actually charged since the last anniversary from SAP conditions, invoices and rent charges. At or below entitlement the event closes; above it, a claim pack is assembled from the clause text, the index vintage and the invoice lines. Entitled but never invoiced goes to finance, because a supplier can still back-bill it.
Ninety days before a window closes the owner gets a task in Microsoft Teams carrying the price trajectory, the entitled-against-charged history, total spend and the days left, with three answers that each need a reason: renew, renegotiate, terminate. This is deliberately not the contract register, which reads agreements into a living record and raises alerts before a date arrives; without that, this has nothing to stand on. What begins here is the entitled price as arithmetic, the comparison with what was billed, and a decision the calendar cannot take for you.
UiPath Orchestrator triggers, queues, credential store and audit log; UiPath Integration Service connectors for Microsoft OneDrive & SharePoint (including Excel Online) and Microsoft Teams; UiPath Action Center tasks completed as actionable notifications in Microsoft Teams, with due dates and reassignment; Power BI scheduled refresh
The clause parameter model, the index store with vintages, the entitlement calculation, the comparison and claim pack, the decision task and its escalation ladder, the renewal calendar and the exposure report
Index retrieval from the Eurostat statistics API and national statistical office publications; SAP conditions, invoice and rent-charge history through UiPath SAP activities (BAPI/OData); the property system by scheduled export
How the automated process works
- AutomationOn each publication date the robot retrieves the index values the clauses name and stores them with their vintage
- AutomationAt each indexation date the clause is applied, index ratio, weights, lag, floor and cap, and the entitled price is written with its arithmetic
- SystemConditions, invoices and rent charges since the last anniversary are read from SAP and the property system, and the difference is computed in euros
- AutomationDifferences inside tolerance are closed; anything above becomes a claim pack with clause text, index vintage and invoice lines attached
- PersonNinety days before the window closes the owner answers in Microsoft Teams: renew, renegotiate or terminate, with the price history and the days remaining in front of them
- AutomationThe answer is written back, unanswered tasks escalate to the category lead then the procurement director, and Power BI shows every open window and accepted uplift against the index
Human-in-the-loop model
Automation handles
- Retrieving published index values on their publication dates and keeping every vintage
- Computing the entitled price for each clause type, with lag, weights, floors and caps, and comparing it with what was invoiced
- Watching every notice window, reminding the owner and escalating what nobody answers
People decide
- Whether a contract is renewed, renegotiated or ended, and on what commercial grounds
- Whether a difference is claimed or traded inside a wider negotiation, with the reason recorded
- How an ambiguous clause is read, and what the tolerances, escalation levels and category ownership are
Before and after
Systems and integrations
We do not add technology to make an architecture look serious. Every element below has a specific job in this process.
Inputs
- the contract register on SharePoint (index code, base period, notice window, owner)
- the clause parameter workbook in Excel Online
- index values from Eurostat and national statistical offices
- SAP conditions and invoice history
- rent-charge schedules from the property system
Automation layer
- UiPath Orchestrator
- UiPath Robots
- UiPath Integration Service
- UiPath Action Center
Target systems
- the SAP claim log
- the SharePoint recalculation record
- the Power BI renewal and exposure model
Human touchpoints: the decision task in Microsoft Teams; the weekly window digest in the category channel; escalation to the procurement director
Technologies used
run the indexation and notice calendar, queue each event, retry, hold credentials, log every calculation
Areads clause parameters from Excel Online, writes each recalculation to the register, posts the weekly digest
Athe renew, renegotiate or terminate task with a due date and escalation
Arenewal calendar, indexation exposure by category, recovered against conceded amounts
Acontract conditions, info records, invoice and rent-charge history
Athe official index values a clause names, stored with their vintage
BIllustrative economic model
What it is worth, with the arithmetic shown.
Three hours per event is the honest middle of a wide range: a single-index clause on a small supply contract takes twenty minutes when the register is good, while a weighted lease formula with a cap, a contested base date and three years of charges to rebuild takes most of a day. €36 an hour is a fully loaded cost for a category manager or lease administrator in Central Europe. Only preparation is priced here; the money the decisions move sits below.
Run the numbers on your data
An illustrative estimate from your own inputs. It models released capacity; it is not a promise of savings.
Business benefits
- Every anniversary is recalculated, not the handful somebody had time for, so the entitled price is a number the company owns rather than one it receives
- Differences are raised inside the period, when they are arithmetic on a signed clause, not eighteen months later as a request for goodwill
- Wrong uplifts stop compounding, because each new calculation starts from a base that was verified rather than inherited
- Renewal conversations open with the term's price history on the table, and no window closes without a recorded decision and a reason
The management view
- Indexation exposure becomes a figure the board can ask for on any day, by category and entity, instead of a surprise inside a budget round
- Every price change carries its own evidence, so a supplier dispute is settled by opening the record rather than rebuilding it
- The renewal pipeline is a calendar with owners that survives a category manager leaving, and it does not shrink as the contract base grows
Board-level KPIs
Security and governance
The automation holds exactly the rights it needs, and not one more.
- The robot reads SAP and the property system through a dedicated retrieval-only account; nothing changes a price or issues a document until a person has answered the task
- Contracts, recalculations and evidence stay in your Microsoft 365 tenant and the UiPath Automation Cloud EU region, with connection secrets in the Orchestrator credential store backed by your own key vault
- Each calculation is reproducible and cannot be edited afterwards: clause version, parameters, index value and vintage, charges compared, and the person who answered; who may accept an uplift or serve notice is a value matrix owned by finance and legal
Why now
Today's base prices were set through a period of unusual index movement and almost none were checked at the time; each anniversary that passes without a recalculation carries those uplifts into the next one, on top of the modelled €1,296 a month the checking would consume
Renewal decisions are being taken by the calendar rather than the category manager, and every default commits a full term at whatever price the incumbent indexed to
None of this needs a new platform: Eurostat publishes its series through a documented public API with no authentication, the clause parameters sit in a workbook procurement already owns, and a Teams task with a due date is a standard Action Center pattern
Relevant executive roles
Indexation becomes a number with arithmetic behind it, per category and per entity
Every renewal reaches negotiation with the term's price history attached, and no window closes by accident
Rent and service-charge increases are verified against the lease before payment, caps included
Clauses nobody can apply without interpretation surface as a list, which is the drafting agenda for the next round
Common questions and objections
Then the hard part is done and this sits on top of it. A register says a date is approaching; it does not say whether last year's increase was owed, or what this renewal is worth. What is added is the clause as a calculation, the index values behind it, and a task that has to be answered.
They are, which is why they are parameters rather than code. Most reduce to an index, a base period, a lag, a weighting and an optional floor and cap; the rest go to a lawyer instead of being forced into a formula, and their number is a useful output in itself.
The claim is arithmetic on a clause both parties signed, raised inside the period rather than as an ambush a year later, and most suppliers correct it without argument. The larger value is arriving at the renewal able to describe the price history.
When this is not the right solution
- Fewer than about fifty contracts carry a price formula, or prices are fixed for the term and renegotiated by conversation, where a calendar and a spreadsheet cost less than the integration
- The contract base is not digitised and the price and notice clauses have never been extracted; the register is the first project and this one follows it
- Charges cannot be traced to a contract because invoices post to a cost centre with no reference; that reconciliation comes first and is often a project of its own
A question for the next management meeting
How many euro separate the indexation this company owed last year from the indexation it actually paid, and if nobody can say, why is that number nobody's job?
Implementation approach
What we deliver, and what we need from you to start.
We deliver
- A read of your base: which agreements carry a price clause, which indices they name, how many parametrise and how many need a lawyer
- The clause parameter model and the versioned workbook procurement owns, with every field documented
- Index retrieval for the sources your clauses name, with vintage storage and a published-value check before any calculation runs
- The entitlement calculation, the comparison against SAP and property charges, the tolerances, the claim pack and the Power BI exposure report
- The decision task in Microsoft Teams with its escalation ladder, a pilot on one category, then rollout with hypercare and a runbook
We need from you
- The contract base with price and notice clauses accessible, plus a year of invoice and rent-charge history
- A named owner for the clause model, one lawyer for the clauses that resist parametrisation, and a service account for SAP and the property system
- Your escalation policy: who decides at what value, and what happens a fortnight before a window closes
Stages
Discovery
Clause inventory, index sources named in the base, availability of the charges applied
Design
Parameter model, tolerances, the decision task and its escalation, the reporting model
Build
Index retrieval, entitlement calculation, comparison against SAP, Teams tasks, Power BI
Back-test and go-live
Last year's events recalculated on real data, then one category live under supervision and the rest with hypercare
Departmental. Effort follows how many distinct clause shapes exist, whether charges can be read per contract rather than per cost centre, and how many index sources publish something other than an API.
Last year's price increases became this year's base, and nobody checked the arithmetic.
Send us twenty indexed contracts and one year of the invoices behind them. We recalculate the entitled uplift, show you where it differs from what was charged, and hand back the clauses we could not parametrise.
Recalculate twenty of your clausesThe neighbouring process usually has the same problem
The numbers in your supplier review were exported by hand last week, and nobody can show the lines behind them.
View solution Finance & accountingThree-way match exceptions resolved before the payment runStop chasing price and quantity differences by email while supplier payments wait for weeks.
View solution Legal & complianceStandard contracts generated, approved and e‑signed in a dayA two-page NDA takes ten days because it is copied, proofread, printed, scanned and filed by hand.
View solution Supply chainFreight invoice audit against rate cards and shipmentsCarrier invoices are checked on a sample and paid in full; the overbilled lines are the ones nobody opened.
View solution Case studyThe intelligent contract registerEvery new contract and amendment passes through IXP: parties, amounts, dates and clauses land in a living register.
View case study Case studyAutomated P2P query handlingInvoice copies, statuses and statements delivered instantly — around the clock.
View case studyIndustries we deliver this in most oftenManufacturing & industryTransport & logisticsRetail & e‑commerceServices & IT