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.
- E-procurement Portal
- Features
- Ordering and receipt
Ordering and receipt
Ordering and receipt for the procurement team and its reviewers.
OverviewOrders Awaiting Receipt×
E-procurement Portal · Ordering and receipt
New
Orders Awaiting Receipt
Receipt waits for the buyer
| Record number | Subject | Order reference | Required by | Counterparty | |
|---|---|---|---|---|---|
| PR-25258 | Ordered pr-113 | OR-928 | 10 Oct | SPP-8022 | |
| PR-34251 | Ordered pr-204 | OR-252 | 10 Oct | SPP-1672 | |
| PR-21049 | Ordered pr-719 | OR-716 | 06 Oct | SPP-3117 | |
| PR-74693 | Ordered pr-626 | OR-381 | 21 Oct | SPP-6773 | |
| PR-30780 | Ordered pr-542 | OR-172 | 11 Oct | SPP-1077 |
6 of 6 records
Ordered pr-113Purchase requests · PR-25258
Order referenceOR-928
Required by10 Oct
CounterpartySPP-8022
What you can do
Ordering and receipt
An approved request can carry an order reference and move to Ordered. Its lines retain requested quantity, accepted quantity, acceptance time and invoice reference. The Buyer compares what was asked for with what was accepted before moving the request to Received. The supplier and amount remain visible with the original demand.
How the work is organized
- Order. Buyer records the order reference on the approved request before marking it Ordered.
- Acceptance. Each purchase line holds requested quantity, accepted quantity and acceptance time.
- Evidence. Attachments and the earlier decision remain linked to the parent request.
The order reference identifies the downstream purchase, but accepted quantities explain what arrived. Compare each line with its requested quantity before marking the request Received. If only part arrived, keep the request in Ordered while the Buyer checks the remaining work. The Auditor can later trace the final request state to its lines, supplier and earlier review decision.
What to agree during setup
Agree who enters the order reference, who confirms accepted quantities and when a request is ready for Received. Decide how partial acceptance is reviewed before the remaining quantity is recorded.
Choose one buying organization for the first cycle. Identify the person who can correct the record when the case fails a check. Write down the expected decision and evidence for the pilot before people begin using the queue. This makes it possible to distinguish a record awaiting action from a record that is ready to close.
Check the handoff on an actual case
Order a pilot request with two lines. Accept only one line and compare accepted with requested quantities. Confirm it remains on the order queue while the other line is open. Complete the second line and inspect the received record with its order reference.
Ask the next person to open the same parent request and explain the next action from the record itself. They should point to the responsible owner, current status and supporting decision or receipt. If those disagree, return the case to the person who owns the correction and record the reason. Rehearse the failure route as well as the successful one.
What your team sees
- Orders Awaiting Receipt — Find ordered requests and compare their line acceptance with what was requested.
- Received Requests — Open the completed request to check its order reference and accepted lines.
Follow the work through
Follow demand and review, tender evaluation and award, then receipt and evidence.
What it keeps track of
Data model- Purchase requests
- Demand records raised by buyers, carrying lifecycle, budget and supplier context.
- Purchase lines
- Line items belonging to a purchase request, with requested and accepted quantities.
- Suppliers
- Registered suppliers eligible to receive tender invitations and orders.
- Operation receipts
- Idempotent receipts for every guarded operation executed against a purchase request.
Who uses it
PermissionsSet up E-procurement Portal your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.