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.
- IT Procurement System
- Features
- Purchase requests
Purchase requests
See each IT purchase from request through order and receipt.
OverviewRequests awaiting review×
IT Procurement System · Purchase requests
New
Requests awaiting review
Approval conditions
| Record number | Subject | Revision | Requested amount USD | Counterparty | Required by | |
|---|---|---|---|---|---|---|
| PR-16506 | Submitted pr-692 | 340 | 660 | SPP-6870 | 12 Oct | |
| PR-17767 | Submitted pr-708 | 800 | 880 | SPP-5364 | 22 Oct | |
| PR-22956 | Submitted pr-526 | 510 | 750 | SPP-3020 | 06 Oct | |
| PR-52932 | Submitted pr-820 | 690 | 960 | SPP-8881 | 27 Oct | |
| PR-51892 | Submitted pr-632 | 760 | 250 | SPP-1782 | 09 Oct |
6 of 6 records
Submitted pr-692Purchase requests · PR-16506
SubmittedRevision340
Requested amount USD660
CounterpartySPP-6870
Required by12 Oct
What you can do
Purchase requests in daily work
A Buyer needs replacement laptops before the required date. The request records a subject, owner, supplier and requested USD amount. A budget code identifies the charge path for the team to discuss. Lines retain item descriptions, quantities and unit prices. The request number stays with the work as the status changes.
A request number gives the Buyer and Purchasing Approver a shared case to discuss. The status shows its place in purchasing, while a linked review decision shows the source revision the approver saw. After ordering, the order reference and dated acceptance evidence explain the delivery without replacing the earlier decision.
How the work is organized
- Ownership. Buyer prepares the request. Purchasing Approver decides a submitted revision. Auditor inspects its evidence.
- Record context. Use the parent request and its organization when checking a related record, then confirm the selected supplier and owner where relevant.
- Evidence. Keep the decision, accepted quantities, attachments and operation outcomes with the same purchase context so later review has the facts in order.
What to agree during setup
Agree which organization owns the purchase, who may be its owner and how the supplier is chosen. Decide who records the order reference after approval. Check the requested amount against the lines before submission, because they tell different parts of the same purchasing story.
Rehearse one request that stays on its first revision and another whose supplier or amount changes after review. The Purchasing Approver should identify which decision applies to each revision. Agree who updates the order reference and how the Buyer reports a delivery discrepancy.
Check the handoff on an actual case
Open the submitted request and compare its revision, amount, supplier and required date with the decision. Then follow its order reference into accepted lines and attached evidence. A request marked received should have enough acceptance detail for the team to explain what arrived.
The Purchasing Approver should be able to find the reviewed revision from the request, and the Auditor should locate the same decision and attachment. If the current amount or supplier differs from the reviewed version, obtain a decision for the changed revision before relying on approval.
What your team sees
- Purchase request worklist — Track requests by status, owner, supplier and required date.
- My purchase requests — Find requests assigned to the current owner.
- Requests awaiting review — Open submitted requests with their amount and revision for review.
Follow the work through
Read request preparation, review and order and receipt reconciliation. The data model shows how the records connect.
What it keeps track of
Data model- Purchase requests
- IT purchase requests with lifecycle status, owner, counterparty and requested USD amount.
- Purchase lines
- Requested and accepted line items belonging to exactly one purchase request.
- Organizations
- Legal entities that own procurement records, with time zone and reporting currency.
- Team members
- Authenticated platform identities with an active membership and role in an organization.
- Suppliers
- Eligible supplier parties with contact, address and eligibility evidence.
Who uses it
Permissions- Buyer
- Prepares the request.
- Purchasing Approver
- Decides a submitted revision.
- Auditor
- Inspects its evidence.
- App Administrator
- Maintains organization membership and supplier configuration.
Set up IT Procurement System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.