Deutsch (Deutschland) 
Polski (PL) 
Independent IFS Cloud practice · Procurement
The price you negotiated, and the order that ignored it
There is an active blanket agreement on the part. Someone still raises a purchase order at a different price: a manual override, a price line that lapsed while the agreement stayed active, or an agreement that was never linked to the line. Depending on your setup, nothing stops the order, so it approves, the goods arrive, and receiving does its job. The gap between what you agreed and what you ordered shows up on the invoice, or it does not surface at all, and the negotiated difference is spent one line at a time.
Key takeaways
- An active blanket agreement sets the price you are entitled to. Depending on your setup, IFS Cloud may not stop a purchase order priced differently, so the line can be raised, approved, and received at a rate the agreement never authorised.
- The agreement behind the gap is live and valid; the order did not use it. An expired agreement is a different case.
- The price is decided when the order is raised, days or weeks before the invoice posts, so a comparison at order time is the earliest point to catch it.
- A monitor cannot know which off-contract orders were intended, so it lists candidates for the buyer to check. The SCM Automation Pack runs no such rule today; it would be an additional rule built to order.
- The agreement price and the order price are recorded in IFS Cloud (worth confirming the exact projections in your environment), so a read-only monitor can compare them on the first scan after an order exists, not at month end.
1.Why an agreement can be live and still be ignored
A blanket agreement is a promise about price and terms, and it applies when the purchase line picks it up. Exceptions break that: a part ordered against the wrong supplier site, a manual price typed over the default, an agreement whose validity was set up out of line with how the part is bought. In each case the system holds a valid agreement and a valid order, and the two never meet.
Allowing this is legitimate. Buyers place off-contract orders for a one-off supplier, an urgent substitution, or a volume the agreement does not cover, and the price override exists for that. Whether your setup distinguishes a deliberate exception from an order that missed the agreement by accident is worth checking.
Where it does not, nothing compares the price on the order with the price you were entitled to and asks whether anyone meant to leave money on the table.
2.Which off-contract prices nobody decided
An order placed off contract for a good reason is normal buying. The review separates the deliberate exceptions from the ones nobody decided.
| What you see | What it can point to |
|---|---|
| An order priced above the active agreement for the same part and supplier | A manual override or an agreement the line never picked up: money agreed away, then spent anyway. |
| A part with a valid agreement, ordered on a line with no agreement reference | A setup gap, so the entitled price never applied even though it was available. |
| Repeat off-contract orders to one supplier for covered parts | A buying process that routes around the agreement, beyond a one-off exception. |
| An order at the old rate just after a new agreement price took effect | A timing gap between the agreement and the order that overpays the difference. |
An order raised on the previous rate looks ordinary while the agreement is current. Only a line-by-line comparison of order price with entitled price shows it, and a list of one week of purchasing shows the pattern that a buyer approving orders one at a time does not see.
3.Comparing order price to entitled price, before the invoice
The agreement price and the order price are recorded in IFS Cloud and can be read through OData projections without touching a record (the exact projections are worth confirming in your environment). Detection runs on a schedule, with the first scan after you have set the tolerance, reads open and recent purchase orders for parts that have an active agreement, and checks two things:
- Order price against entitled price - where an order sits above the rate a live agreement would have given, listed while the order still exists rather than after the invoice posts.
- Covered part, no agreement applied - an order line for a part with a valid agreement that carries no reference to it, so a setup gap is listed before it repeats.
Because it is a read-only monitoring pattern, it runs beside purchasing and writes nothing back to IFS. It adds no object inside the client system, so a release update leaves nothing of ours in your IFS to retest. Before each release I check that the standard projections it reads still match, as part of the subscription. It gives the buyer a list of orders to check against contract, and the call on whether each exception was intended stays with the buyer.
4.Rolling it out without noise
- Start with your biggest agreements - watch the parts where an off-contract price costs the most first.
- Dry-run first - in the first week the rule only logs what it would have listed, and nothing reaches a buyer.
- Set a price tolerance - a rounding difference is not a listing, so only orders above a margin you set are shown to the buyer.
- Read only, no footprint - standard OData reads, nothing written back, no new object inside IFS Cloud.
Related reading
5.Frequently asked questions
Does IFS Cloud enforce the blanket agreement price?
Whether IFS Cloud enforces the blanket agreement price depends on your setup, which is worth checking. It applies the agreement price when the line picks the agreement up, and manual overrides and off-contract buying can still produce a purchase order at a different price. Whether a given off-contract price was intended or accidental is a judgement that needs a second look by a person.
Why compare the price at order time instead of at invoice?
The price is decided when the order is raised, so a comparison at that point lets the buyer and the supplier talk before the goods arrive. A difference found only after the invoice posts is found when the money has already moved, during a reconciliation rather than during buying.
Are you saying buyers should never order off contract?
No. Off-contract orders are legitimate for one-off suppliers, urgent substitutions, and volumes an agreement does not cover. The aim is to separate those deliberate decisions from the orders that missed a live agreement by accident, so the accidental overpayments get seen.
Does this monitoring write anything to IFS Cloud?
No. The agreement price and the order price are read through OData projections and compared outside IFS. Nothing is written back, so there is no upgrade footprint and no new object inside the client system.
6.About the author
Dariusz Myśliwiec brings 18 years hands-on with IFS (Apps 7.5–10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Based in Kraków, delivering remotely across Europe and globally as an independent practice, so you talk to the consultant who builds it.
Selected clients: Fugro · LGC · BVI Medical · Betafence (PRÆSIDIAD) · Barlinek · NGK Ceramics · Newag · Oleofarm.
IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
Stop paying past your own agreements
Tell me which agreements matter most and where off-contract orders slip through. On a 30-minute fit call we check whether a rule that compares agreement prices with order prices fits your data. The SCM Automation Pack runs three rules today (unconfirmed purchase orders, late deliveries, stock below minimum), so this would be an additional rule built to order, with a dry-run week before anything reaches a buyer.
