Flow 01
Purchase requests and approval routing
Staff need things the reorder check does not cover: a pallet jack, a forklift service, stock for a one-off customer order. Without a request record these get agreed in chat, the budget is looked at after the bill arrives, and nobody can say later who approved the spend or why.
- Starts when
- A staff member needs goods or a service, or a confirmed sales order has an item Harbourline does not hold.
- Ends with
- An approved purchase request with its approval log, its value committed on the budget line, and its lines queued for PO drafting or supplier selection.
- 1.Person: Requester
Raises a request with the item or a description, quantity, estimated unit price, need-by date, reason and budget line.
- All six fields are required. A request tied to a sales order or a job carries its reference and takes the need-by date from it.
- For a stock item with a reorder point, the form shows on hand, on order and any open PO, and asks for a reason, because the daily reorder check already covers normal demand.
- 2.System: System
Groups the request with the same requester's requests in the same category over the last 7 days.
- If two or more requests in that window together cross a matrix threshold (S$1,000, S$5,000 or S$20,000), each one is routed at the combined value, so splitting a purchase does not lower the approver.
- 3.System: System
Checks the budget line before anyone is asked to approve.
- Remaining = budget for the period, minus bills posted, minus commitments (approved requests not yet on a PO, plus open PO value not yet billed). All figures before GST.
- Over budget: the approver must enter a reason. An overrun above S$1,000 adds the finance manager to the route.
- 4.System: System
Builds the approval route from the matrix.
- Every request goes to the requester's department head first, who approves the need and the budget line.
- Above S$1,000 it then goes to the approver for that amount: operations manager up to S$5,000, finance manager above S$5,000 and up to S$20,000, director above S$20,000.
- Category rules add a reviewer where the client wants one, for example the finance manager for items that will be recorded as fixed assets.
- 5.System: System
Resolves who holds each approval step on the day.
- A requester never approves their own request. A department head's own request goes to their manager.
- If the approver has set a delegate for the day, the delegate gets the step only when their own approval limit covers the amount. Otherwise it goes one level up.
- When one person holds two steps, one approval covers both and the log records both roles.
- 6.Person: Approver
Approves, rejects with a reason, or sends the request back with a question.
- An approver may lower the quantity or value and approve in the same action. Any increase re-runs the budget check and the route.
- 7.System: System
Sends a reminder after 4 working hours without action, and escalates one level if the step is still waiting.
- Escalation after 1 working day when the need-by date is within 5 working days, after 2 working days otherwise.
- 8.System: System
Marks the request approved, records its value as committed on the budget line and queues it for purchasing.
- Lines with an approved supplier and a valid price go to PO drafting. Everything else goes to supplier selection.
Exceptions
- The approver is on leave and has set no delegate
- The step waits for the escalation time, then moves one level up. The log shows that it was escalated and why.
- The purchase was made before approval, such as an emergency forklift repair arranged by phone
- The requester records it as an after-the-fact request. It goes to the matrix approver for its amount and to the finance manager whatever the amount, and these requests appear on a monthly list for the finance manager.
- The item is already on an open PO
- The request shows the PO number, quantity and expected date. The requester withdraws it or adds a reason, such as a separate customer order, and the approver sees both.
- The request is rejected
- The requester sees the reason and can revise and resubmit. The new version keeps the history of the first.
- The budget line is wrong or closed for the period
- The finance manager moves the request to the right line before approval continues, and the move is logged.
Worked example
PR-0157: pallet jack and stretch film for the Tuas warehouse
- Pallet jack 2.5 t × 1 @ S$1,180.00 = S$1,180.00. Stretch film 500 mm × 24 rolls @ S$9.80 = S$235.20. Request value S$1,415.20 before GST.
- Above S$1,000, so the route is the warehouse manager as department head, then the operations manager (up to S$5,000).
- Budget line Warehouse equipment, FY2026: S$18,000.00 budget, S$14,260.00 billed, S$2,950.00 committed, S$790.00 left. The request is S$625.20 over, below the S$1,000 overrun limit, so the approver must give a reason and nobody is added to the route.
- The operations manager is on leave from 4 to 6 Nov with the finance manager as delegate. The finance manager's limit of S$20,000 covers S$1,415.20, so the step goes there and is logged as approved on behalf of the operations manager.
- If the PO later comes in at or under S$1,415.20, to an approved supplier with no price rule triggered, this approval stands for the PO. Otherwise the PO routes again by its own value.
Sample data. Harbourline Supplies Pte Ltd is not a real company.