These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Purchase Order System
- Features
- Approval control
Approval control
Keep each purchasing decision attached to its scope, revision and eligible reviewer.
OverviewApproval inbox×
Purchase Order System · Approval control
New
Approval inbox
Approval conditions
| Step number | Document type | Tier | Approver | Due at | Source revision | |
|---|---|---|---|---|---|---|
| AS-39081 | Requisition | 110 | USR-7222 | 19 Oct | 290 | |
| AS-25149 | Purchase order | 180 | USR-6702 | 26 Oct | 800 | |
| AS-12497 | Amendment | 470 | USR-4651 | 20 Oct | 620 | |
| AS-31478 | Master agreement | 280 | USR-1897 | 24 Oct | 450 | |
| AS-26240 | Requisition | 510 | USR-6644 | 19 Oct | 760 |
6 of 6 records
USR-7222Approval steps · AS-39081
RequisitionTier110
Due at19 Oct
Source revision290
Rule version160
StatusPending
What you can do
Give the reviewer the complete decision
An approval is tied to a specific purchasing document and its revision. The Approver needs to see the requested amount, department, cost center and category before deciding. The approval rule records the applicable amount band and tier, along with the named reviewer and effective dates. This makes the route understandable when a request crosses a spending threshold.
The decision retains the approved amount and its scope. A later order or amendment can be compared with that authority rather than relying on a general statement that a purchase was approved. The approval inbox brings pending decisions together with their due dates and assigned owners.
How the work is organized
- Effective rules. The Procurement Manager and Controller review the routing policy before use. Amount bands, departmental scope and named reviewers determine who must consider a request. Effective dates and rule versions preserve which policy applied at the time.
- Individual decisions. Each approval step records its tier, status and assigned Approver. Comments and action details explain a rejection or an approval. The decision also retains the source revision so a revised request can be distinguished from the content already reviewed.
- Controlled delegation. A delegation identifies the principal reviewer, eligible delegate, date window and approval limit. Its approved scope matters when a person is covering leave. Assignment history and the acting identity keep the resulting decision attributable.
What to agree during setup
Map department heads, budget owners and senior signers to people who hold the Approver role. Confirm the amount bands and category rules with finance. Decide how a committee decision is represented and who is permitted to record it. A job title alone should not establish a person’s authority over every purchasing request.
Agree how to handle a requester who would otherwise become their own reviewer. Name an independent eligible reviewer and rehearse that route. Set target response days and the person who follows overdue steps. Review delegation dates before a planned absence so urgent purchasing does not depend on an informal forwarding chain.
Check the handoff on an actual case
A facilities request includes equipment and installation charged to the same cost center. The Approver reviews the complete amount at the applicable tier. Check that the pending step names an eligible person and shows the correct source revision. Record the decision and inspect the retained approved scope.
Next, increase the installation amount before the order is issued. Compare the changed scope with the earlier authority and route the new decision as required. The earlier approval should remain understandable as a decision on its original content.
Finally, rehearse the same case while the principal reviewer is away. Use an approved delegation within its effective window and limit. Confirm that the recorded actor and the principal they represented can both be identified after the decision. A delegate outside the permitted window needs a new valid route.
What your team sees
- Approval inbox — Pending decisions with assigned reviewers, tiers, due dates and the revision under review.
- Orders awaiting approval — Purchase orders awaiting an independent decision on supplier, funding and amount.
Follow the work through
Follow request approval and controlled order changes.
What it keeps track of
Data model- Approval matrix
- Effective-dated approval rules for Department x Cost Center x Category x amount x tier.
- Approval steps
- One row per approval tier a requisition, purchase order or amendment passes through.
- Approval delegations
- Effective-dated, approved delegation of a principal approver to a named eligible delegate.
- Spend approvals
- Versioned authority request and frozen decision for a complete source revision.
- Spend approval lines
- Immutable scope and approved allowance within a Spend Approvals decision.
- Users 2
- Internal user directory for everyone who requests, approves, buys or receives.
- Departments
- Organisational units that raise requisitions and own approval rows.
- Cost centers
- Budget units within a department.
- Categories
- Purchasing taxonomy aligned to UNSPSC.
Who uses it
Permissions- Approver
- , Procurement Manager, Controller, Buyer.
- Approval authority follows the applicable rule; access to a queue does not itself authorize a decision.
Set up Purchase Order System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.