A factory consumes sheet steel all year round. Procurement negotiated a price in January, but every week a buyer rekeys an order, looks up the rate in an Excel file, and hopes nobody has changed the grid in the meantime. In November, finance notices that three orders were placed at last year’s price, and that the annual volume promised to the supplier, the basis for the discount, was never tracked.
The framework agreement, or blanket order, exists to prevent exactly this. The ERP holds the negotiated deal (price, ceiling, duration) and every real requirement becomes a call-off that draws down that ceiling. The principle is simple. The configuration decides what you actually control: the price, the commitment, or nothing at all.
This guide is aimed at procurement managers, supply chain managers and IT leads in charge of the purchasing module. It follows the order of a configuration project. The figures used are illustrative: they are there to help you reason, not to set a market benchmark.
Framework Agreement, Blanket Order, Call-Off: Definitions and Use Cases
Three terms circulate, sometimes for the same thing. It is worth separating them before you configure anything.
- The framework agreement is the deal negotiated with the supplier: item scope, price or price formula, ceiling, duration, delivery and payment terms. It triggers no delivery by itself.
- The blanket order (blanket purchase order) is its counterpart in the ERP: a purchasing document with no single delivery, authorizing orders up to a ceiling.
- The call-off (release) is the individual order placed under the agreement. It triggers delivery, receipt and invoice, and it consumes the ceiling.
When a Framework Agreement Makes Sense
It fits when three conditions combine: a recurring need, an identified supplier, and a price negotiated on overall volume rather than per order. Typical cases are raw materials (steel, plastics, packaging), industrial consumables, spare parts, maintenance, and some services (transport, cleaning, temporary staffing).
Conversely, a one-off purchase or a highly volatile item with no indexation formula is better handled as a standard purchase order. For the long tail of scattered purchases the logic is different: our guide on indirect procurement and tail spend explains why catalogs and approved suppliers are preferred there.
Vocabulary by Vendor
Each vendor names these objects differently, and exact functionality varies by version and module. A few landmarks, to confirm in your edition’s documentation:
| Concept | Terms you will encounter |
|---|---|
| Negotiated agreement with a ceiling | Outline agreement, quantity or value contract (SAP); purchase agreement (Dynamics 365); blanket order (Odoo); blanket purchase order (Business Central) |
| Call-off | Release order, scheduling agreement release, order linked to the contract |
| Ceiling | Target value, commitment, maximum amount or quantity |
Above all, remember one fundamental distinction: some objects set a ceiling in value or quantity (a framework agreement in the strict sense), while others schedule staggered deliveries with dates (a scheduling agreement). Both are useful, but they are not managed in the same way.
Modeling the Agreement in the ERP
The quality of your configuration is decided on the agreement itself. A poorly modeled agreement produces useless alerts or, worse, none at all.
Value and Quantity Ceilings
The first choice: cap by value, by quantity, or both.
- Quantity ceiling: suited to a single item with a stable unit price (for example 500 tonnes of steel coil over the year).
- Value ceiling: suited to a multi-item agreement (consumables, parts) where quantity per reference is meaningless. The ERP accumulates the amounts of the call-offs.
- Dual ceiling: useful when the price is indexed. Quantity secures the commitment to the supplier, value protects the budget when the price rises.
Also plan for an alert threshold (for example 80% consumed), a hard or soft ceiling (block or simple warning when exceeded), and the agreement currency. On a foreign-currency agreement, decide whether the ceiling is expressed in the agreement currency or the company currency: the exchange rate will change apparent consumption.
Duration
A start date and an end date are mandatory. An agreement with no end date is one of the most frequent traps: it keeps serving as a price reference long after the commercial deal has ended. Configure:
- a validity date after which no call-off is possible;
- an expiry alert (for example 90 days ahead) to the responsible buyer;
- an explicit renewal rule: “tacit renewal” in the legal contract must not mean “automatic” in the ERP without human validation.
Price Grid
The grid is the heart of the mechanism: it is what secures the negotiated price. It can take several forms.
- Fixed price per item, valid for the whole term.
- Quantity-tier pricing: the price drops with the cumulative quantity consumed or the size of the call-off. Check whether the tier is assessed per call-off or on the agreement’s cumulative total; the ERP does not always handle both.
- Indexed price: a formula tied to an index (materials, energy, labor). The agreement holds the formula, and price updates follow a revision procedure. We cover the topic from the vendor side in our guide on price revision and indexation clauses, whose contractual logic carries over to supplier agreements.
- Year-end rebate on cumulative volume: treat it as a supplier receivable tracked separately, not as a price reduction.
The key point: the agreement price must be enforced on the call-off. If the buyer can freely change it at data entry, the grid no longer has any control value.
Example: Steel Framework Agreement
Take an illustrative agreement with a steel producer.
| Parameter | Value |
|---|---|
| Scope | 3 coil references |
| Ceiling | 600 tonnes and €450,000 |
| Duration | 12 months, 1 January to 31 December |
| Price | Tier above 300 cumulative tonnes, quarterly indexation |
| Alert | 80% consumed, 90 days before expiry |
| Overrun | Block above 100% of value, purchasing manager approval |
This configuration fits on one page. If it takes ten, the legal contract is probably too complex to be carried as is by the ERP, and it is better to simplify the structure than to multiply exceptions.
Call-Offs and Ceiling Consumption
Once the agreement is active, the daily flow is made of call-offs.
- The need appears (MRP replenishment, purchase requisition, warehouse entry).
- The ERP detects the applicable agreement for the item and supplier, and proposes the linked call-off.
- The grid price is applied, with the matching tier.
- The call-off is approved under the usual rules, then sent to the supplier.
- Receipt and invoice attach to the call-off, and therefore to the agreement.
What the ERP Must Handle
- Which agreement wins? If two agreements cover the same item (duplicate, old and new), the priority rule must be explicit: the most recent, the cheapest, the preferred one. Without a rule, the outcome depends on entry order.
- When is the ceiling consumed? At call-off approval (committed), at receipt (delivered) or at invoice (billed)? The choice changes every indicator. To manage commitment, consumption at call-off is the most useful; for delivery tracking, receipt.
- What happens to a cancelled or modified call-off? The undelivered quantity must be released back to the ceiling, otherwise the agreement looks consumed when it is not.
- Partial receipts and staggered deliveries: the balance stays open on the call-off, and billing control happens at matching. The invoice is then checked against the call-off and the agreement, as described in our guide on three-way matching.
Alerts, Overruns and Approval Workflow
A framework agreement without alerts is just a more expensive spreadsheet. Three families of events deserve a notification.
Consumption Alerts
The alert threshold (80% in the example) warns the responsible buyer before the ceiling blocks production. It should trigger a decision: raise the ceiling by amendment, renegotiate, or switch to another supplier. An alert that arrives at 100% is an incident, not an alert.
Calendar Alerts
Agreement expiry, end of a price list’s validity, an index revision to apply. They prevent you from discovering on the day of the call-off that the agreement has expired and that the ERP has fallen back on a higher standard price.
Overruns and Their Workflow
When a call-off exceeds the ceiling, three behaviors are possible: outright refusal, warning, or overrun subject to approval. The last is the most common in practice, because production cannot always wait for an amendment. Define:
- a tolerance threshold (for example a 5% overrun) handled by the purchasing manager;
- above it, a higher-level approval (procurement director, CFO);
- an audit trail: reason, approver, date, regularizing amendment.
Access Control and Delegation
Separate the rights: who creates and edits an agreement (lead buyer), who changes grid prices (purchasing manager, with dual validation), who places call-offs (buyers, authorized requesters), who approves overruns. Temporary delegations (leave, absences) must be time-bound and logged: a delegation with no end date is a permanent bypass of control. Segregation of duties between whoever negotiates the price and whoever receives the goods remains the best safeguard against fraud.
Link to Budget and Accounting Commitment
The framework agreement is also a budgeting tool, provided you know what it actually commits.
- The agreement itself is generally an off-balance-sheet commitment of a legal nature: the supplier can count on a volume, but the company has not yet ordered. Many ERPs do not record it, or track it as an informational commitment.
- The call-off creates the budget commitment in the budget control sense: available budget decreases at approval.
- The receipt creates the payable (goods received not invoiced account), and the invoice clears it.
Two questions to settle with finance:
- Is budget reserved at agreement level or call-off level? Reserving the full ceiling at signature locks up budget that may end up half consumed. Reserving at call-off is truer to consumption, but reveals budget overruns later.
- What about an agreement that spans two fiscal years? The agreement’s annual ceiling does not always match the fiscal year. An agreement running July to June is spread over two budgets, and the ERP must be able to split the commitment or, failing that, track it in a supplementary table.
The accounting rules applying to these commitments depend on your framework (local GAAP, IFRS) and the nature of the agreement: have the treatment validated by your auditor rather than relying on a default configuration.
Reporting: Consumption Rate and Realized Savings
Reporting turns the agreement into a management tool. Five indicators are enough to start.
| Indicator | What it measures | How to read it |
|---|---|---|
| Consumption rate | Value or quantity called off / ceiling | Too low: oversized ceiling or off-contract leakage. Too high too early: underestimate |
| Compliance rate (spend under contract) | Share of category purchases made through an agreement | Measures maverick spend outside contract |
| Applied price variance | Call-off price vs. grid price | Detects prices changed at entry |
| Realized savings | (Reference price − contract price) × quantity | Handle with care: depends on the chosen reference |
| Expiring agreements | Agreements expiring within 90 days | Feeds the renegotiation calendar |
A word on savings: the figure depends entirely on the comparison baseline (last price paid, list price, average price). Fix the method once, document it, and have finance validate it. A savings figure without a method is not credible in front of a CFO.
Finally, link these indicators to supplier evaluation: an agreement honored on price but delivered late does not keep its promises. Our guide on the supplier scorecard shows how to cross OTIF, quality and price before a renegotiation.
Common Pitfalls and Checklist
The Five Pitfalls
- Outdated prices. The grid was not updated after an index revision or an amendment, and the ERP applies the old rate. Plan a revision procedure with an effective date, and a price variance check at invoicing.
- Agreements without an end. No validity date, or unmonitored automatic renewal. The agreement outlives the commercial deal.
- Duplicates. Two active agreements for the same item and supplier, left over from data migrations or unclosed renegotiations. The ERP picks at random, and consumption gets scattered.
- Wrong ceiling. Too wide, it protects nothing. Too tight, it blocks production and pushes people to work around it with off-contract orders.
- Workarounds. If creating a call-off is heavier than placing a free-form order, teams place free-form orders. Control only works if the normal path is also the easiest.
Implementation Checklist
- List recurring purchasing categories and the suppliers involved, starting with the largest volumes.
- Choose the ceiling type (quantity, value, dual) and its overrun rule.
- Set start, end and renewal dates and expiry alerts.
- Load the price grid and decide whether the agreement price can be edited at call-off.
- Define at which event the ceiling is consumed (approval, receipt, invoice).
- Configure alert thresholds and the overrun approval workflow.
- Separate the rights to create, change prices, call off and approve.
- Validate with finance the budget and accounting treatment of the commitment.
- Deduplicate existing agreements and clean up those past their end date.
- Publish the five indicators and set a quarterly agreement review.
Start with one supplier and one item family, measure price variance and compliance rate for a quarter, then extend. A well-configured framework agreement does not save time in the first month: it prevents quiet pricing errors in the months that follow, and makes commitment visible before it becomes a problem.
To link this agreement tracking to your suppliers’ service quality, read our guide on the supplier scorecard, and complete it with three-way matching to secure the invoicing of call-offs.