Skip to content
Procurement & supply chainFor every industry

Check framework agreements against ERP prices

Prices, tiers, escalation clauses and notice periods from framework agreements, checked against the ERP, with warnings in time.

Today

What was negotiated in a framework agreement often never fully reaches the ERP. Escalation clauses are calculated one way this time and another way the next, and price increases outside the agreed windows go unnoticed. Notice periods pass because the contract sits in a folder.

An example

Talwerk Antriebstechnik buys rolling bearings for the TG 80 gearbox under a framework agreement. The agent finds in § 6.3 that prices may only be adjusted once a year, on 1 January, and flags two increases from April and September. It also reminds the head of purchasing that the agreement can be terminated until 30 June.
Fictional company, typical workflow.

Your data, wherever it lives

Today framework agreements and amendments sit as PDFs or scans in the DMS or in folders, the negotiations in e-mails, and conditions, purchase orders and invoices in the ERP. demi reads, understands and links them per supplier, article and clause, with your rights. The AI checks prices, price breaks and escalation clauses against the ERP in minutes instead of an hour per agreement and flags deadlines in time, and purchasing decides whether to claim, renegotiate or terminate.

Where the data lives today

  • PDFs
  • Scans & paper
  • DMS & archive
  • Folders & drives
  • E-mails
  • ERP
Data LayerOne view of everything, with your rights

How demi solves it

Three layers in this order: connect the data first, then the rights, then the AI.

  1. 1 · ConnectData Layer

    The case needs data from the DMS, e-mail and ERP. demi replaces nothing and ties framework agreements and amendments to suppliers, articles and conditions. demi writes back only after approval.

  2. 2 · PermitPermission Layer

    Purchasing and legal see the contracts. demi changes conditions only after the responsible buyer has approved the change, and every change is recorded.

  3. 3 · ActIntelligence Layer

    The agent reads prices, tiers, escalation clauses and deadlines, each with a reference to its clause, and calculates price adjustments deterministically from the formula and index in the contract. It reports differences to the ERP and upcoming deadlines to the owner.

How it runs

  1. 1

    demi reads framework agreements and amendments and links them to suppliers and articles.

  2. 2

    The agent extracts conditions and deadlines with clause references.

  3. 3

    It compares them with the ERP conditions and with the prices on purchase orders and invoices.

  4. 4

    Differences and upcoming deadlines go to the responsible buyer.

  5. 5

    demi writes back only after approval and records every change.

What changes

  • Agreed prices actually applied

  • Notice periods on the table in time

  • Escalations always calculated the same way

What does it bring you?

Check it with your own numbers

Every starting value is an assumption you can change. The calculation sits right below, step by step.

Assumption, editable

Your numbers

Result

+96 hfreed per year

Assumptions and calculation

demi checks contract prices, tiers and deadlines against the ERP and warns in time; you act.

60 min → 36 min per case

How does it run today?

What is already digital saves less: the factor lowers the share demi brings.

How we calculate

20 framework contracts × 60 min × 40% × 1.0 (manual) × 12 months = 5,760 min = 96 h

Value per year, before demi costs

Freed per year+96 h

Assumption: labour cost of €49.50 per hour in German manufacturing in 2025 (Destatis), plus workplace, IT and overheads.

= Value per year, before demi costs

+€6,240

gained per year

96 h ÷ 1,760 h per role = 0.1 full-time roles

An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.

Combine with more cases and get the package

Questions about this use case

Can the agent read scanned contracts and amendments?

Yes, it reads scanned contracts with text recognition. It links amendments to the main contract, so the version of a clause that is currently valid always counts. It marks unclear passages, and the buyer confirms them against the original.

How does demi calculate index-based price changes?

With the formula from the contract, using the agreed index, base value and reference date. The calculation is deterministic and traceable step by step; the AI does not estimate anything here. If an index value is missing, the agent reports it instead of calculating.

Who maintains the conditions in the ERP?

Your purchasing team, as before. The agent prepares the change with a clause reference, the responsible buyer approves it, and only then does demi write it to the ERP. Every change is recorded.

Does demi also check orders and invoices against the contract?

Yes. The agent compares the prices on purchase orders and incoming invoices with the valid contract conditions. When a price differs, the buyer sees contract, clause and document side by side.

See this case with your data

In the demo we show you the workflow on your own systems.

Your configurator

No use cases yet

Your configurator is still empty

Add a use case from any card or case page and see what it brings per year, with the calculation. Free, no sign-up, no commitment: try it out and change any number.

Browse use cases