Blanket releases
Order within an approved agreement while keeping its term, pricing, remaining capacity and delivery obligations reconciled.
6 stages · 2 approvals
Roles and responsibilities
-
Step 1Agreement
Step NumberDocument TypeRequisitionPurchase OrderPurchase Order
-
Step 2Release
Release NumberMaster AgreementSupplierRelease Date
-
Step 3Order
PONumberSupplierOrder DateTotal Amount
-
Step 4Receive
POLine NumberItemItem Description
-
Step 5Burndown
Release NumberMaster AgreementSupplierRelease Date
-
Step 6Renew or let lapse
Step NumberDocument TypeRequisitionPurchase OrderPurchase Order
Process steps
Follow the process from start to finish. Select a step to see who acts and what changes.
Approval required
Agreement
Approver, Controller and Procurement Manager decide their assigned matrix tiers for the agreement scope and ceiling. Procurement Manager separately signs the commercial terms and renewal notice. Buyer can prepare draft rates; a Procurement Manager other than their preparer activates the reviewed rates. A signed document without the required recorded authority does not permit release.
Release
Requester or Buyer prepares covered items, quantities and delivery dates. Every line uses an effective rate belonging to the agreement. Release validates scope, supplier eligibility and remaining approved capacity and reserves it once. A request beyond the ceiling stays held until separately authorised scope exists; retry or concurrent release cannot consume the same capacity twice.
Order
Buyer reviews the generated order and its link to the release. Reused agreement approval applies only while the line scope, rates and reserved authority remain valid. Pricing and supplier holds still apply. Buyer sends the approved revision through the configured supplier channel, and Supplier acknowledges the revision it will fulfil.
Receive
Receiving Clerk confirms accepted dock deliveries; Requester confirms assigned desk receipts. A configured warehouse connection can supply dock evidence. Partial acceptance leaves the remaining obligation open. Rejections and returns preserve their quantity treatment; returning already-rejected goods does not reduce accepted fulfilment again. Release completion follows its generated order's applicable fulfilment and close conditions.
Burndown
Controller reviews agreement consumption against budget. The agreement uses posted commitment allocations, including amendments and fulfilled value. A release retains its initial value and the current commitment of its generated order. Approved cancellation releases only unfulfilled capacity. The projection uses observed consumption and should be reviewed with timing and scope assumptions.
Approval required
Renew or let lapse
Approver, Controller and Procurement Manager decide the assigned matrix tiers for changed scope or ceiling. Procurement Manager signs the renewal or records expiry using Buyer's sourcing review. Additional capacity requires its own approved version. An agreement entering its notice window can remain usable while still valid; expiry or termination blocks new releases without erasing existing order obligations.
Approvals and exception handling
2 approvals required in this process
-
Agreement
Approver or Controller or Procurement Manager signs · release waits
MasterAgreements, ContractRates, SpendApprovals, SpendApprovalLines, ApprovalSteps -
Renew or let lapse
Approver or Controller or Procurement Manager signs · closes the process
MasterAgreements, SpendApprovals, SpendApprovalLines, ApprovalSteps - Keep authority specificDepartment, category, item, rate, term and remaining capacity all constrain release. An agreement reference alone is insufficient.
- Reconcile changesThe initial release value does not conceal an amended order. Commitment allocations record approved increases and reductions with their source events.
- Retain fulfilled consumptionReceipt and invoice closure do not restore the agreement capacity already used. Only supported unfulfilled cancellation releases it.
- Respect supplier holdsSuspended suppliers can finish issued orders but receive no new commitments; blocked arrivals stay disputed and cannot post fulfilment.
- Plan renewal from evidenceMaster Agreement Burndown supports the review; its projection is not a guaranteed exhaustion date or an automatic ceiling increase.
When the process needs attention
-
hold
Order
Pricing and supplier holds still apply.
-
reject
Receive
Rejections and returns preserve their quantity treatment; returning already-rejected goods does not reduce accepted fulfilment again.
Records and postings
| Stage | Records | Effect |
|---|---|---|
| 1 Agreement | MasterAgreementsContractRatesSpendApprovalsSpendApprovalLinesApprovalSteps | reviewed term, scope and ceiling authorised |
| 2 Release | BlanketReleasesBlanketReleaseLinesCommitmentAllocations | scope validated and available capacity reserved once |
| 3 Order | PurchaseOrdersPOLineItemsBlanketReleases | approved generated order issued and acknowledged |
| 4 Receive | ReceiptsReceiptLineItemsPOLineItemsBlanketReleases | accepted fulfilment updates remaining delivery |
| 5 Burndown | MasterAgreementsBlanketReleasesCommitmentAllocations | current and fulfilled commitments reconcile to ceiling |
| 6 Renew or let lapse | MasterAgreementsSpendApprovalsSpendApprovalLinesApprovalSteps | renewal or ceiling change approved; lapse blocks new releases |
Process reports
All reportsOpen Commitment
Outstanding delivery value QtyOpen × UnitPrice on issued POLineItems, by Department, CostCenter, Category and Supplier. This is distinct from full retained CurrentCommitment and agreement Spent, which include fulfilled portions; reconcile both measures to the labelled budgeting feed.
Master Agreement Burndown
TotalCommit against Spent per MasterAgreements with monthly burn rate, projected exhaust date and the renewal notice window.
Maverick Spend
POLineItems with OffContract set, and lines that needed PriceOverrideApproved, grouped by Supplier, Buyer and the recorded OffContractReason or PriceOverrideReason; where the policy is being routed around and why.
Spend by Category
Committed and received spend rolled up the Categories tree by Department and period, drilling to Supplier and PO, with OffContract lines flagged per category.
Spend by Supplier
Spend per Suppliers by Category and period with share of total, year-on-year change and the share tied to a ContractRates or MasterAgreements row.
Run by an agent
Agent support
Required approvals, supplier awards, price exceptions and supplier-status decisions stay with their designated people. An agent cannot expand a spend approval, bypass a matrix step or turn an RFQ award into authority to order. Configure any permitted automated transition explicitly and retain the policy and source revision that justified it. Acting through an agent never removes a conflict of duties or a pricing restriction.
# Example after configuration
$ curl -fsSL https://www.erp.ai/skill.md | paste into your agent
› blanket releases · agreement on MasterAgreements, ContractRates, SpendApprovals, SpendApprovalLines, ApprovalSteps
⏸ approval · waiting for the approver or controller or procurement manager
# 5 more stages after approval: release, order, receive, burndown, renew or let lapse
Other processes
4 moreRequisition to receipt
Connect purchase requests, recorded spending authority and accepted deliveries through to the invoice-matching handoff.
6 stages · 2 approvals
Competitive sourcing
Compare eligible suppliers on a frozen scope and carry the chosen offer into an independently authorised purchase order.
6 stages · 2 approvals
Change orders
Review the full effect of order changes, preserve cumulative spending authority and keep suppliers on the approved revision.
6 stages · 1 approval
Supplier onboarding
Verify supplier identity, terms and qualifications before purchasing, then apply clear controls when status changes.
6 stages · 2 approvals