Purchase Requisition Approval Automation in Singapore: A Practical Capex Workflow
Purchase Requisition Approval Automation in Singapore: A Practical Capex Workflow
Purchase requisition approval automation helps a Singapore SME record a proposed asset purchase, route it to the right approver, and show when purchasing may begin requesting quotes. The practical value is straightforward: fewer requests lost in email or chat, clearer responsibility for approval, and a traceable handoff before the business commits to spend.
Automation should organise and route the request, not make the spending decision. A named person should approve the requisition under the company’s written authority limits. Quote selection, purchase-order release, and invoice processing are separate steps.
This guide focuses on the pre-quote capex and purchase requisition gate: what information to collect, who should approve it, and how to automate reminders and records without silently approving a purchase or creating a PO. For a broader perspective on Singapore SME digitalisation, see IMDA’s Industry Digital Plans.
What purchase requisition approval automation does
A purchase requisition (PR) is an internal request to authorise a proposed purchase. It records the business need and estimated cost before the organisation proceeds to supplier selection or commitment. For capex, the request may concern equipment, IT hardware, a vehicle, fit-out, or another purchase that the company handles under its capital-spend policy. Accounting classification remains a matter for the business and its accounting advisers; the approval workflow is about authority to proceed.
A useful automated workflow can:
- collect a request through one shared form or mailbox;
- save supporting documents in a shared, access-controlled location;
- check that required fields are present and flag exceptions;
- route the request to the designated human approver;
- remind an owner or backup when a request is waiting; and
- record the decision and, if approved, mark the request ready for quote collection.
It should not treat a message such as “we need three laptops” as an approved PR, infer an authorised budget from incomplete information, or create a purchase order simply because a status changed.
The distinction between requisition routing and capital approval matters. One reference on capex best practices describes presenting purchase-requisition approvals consistently with other approval requests; the operational principle is to make the request and its decision easy to follow, not to remove the accountable approver. See the capex approval workflow guidance.
Keep the stages separate
A controlled purchase trail has distinct gates:
1. Need and PR: the requester states what is needed, why, and the estimated cost.
2. PR approval: the assigned manager, finance owner, or director authorises the request under the company’s policy.
3. Quote collection: purchasing seeks supplier options after the PR is approved.
4. Quote and PO decision: the relevant owner selects or releases the purchase order under the organisation’s process.
5. Invoice and receipt checks: the business handles the supplier bill and, where relevant, verifies delivery.
This article covers stages one and two, plus the handoff to quote collection. Keep quote-to-PO approvals in a separate process; see Lynqra’s quote-to-PO approval guide. In the same way, invoice handling belongs in a separate invoice workflow. A request to add a person rather than buy an asset follows the same request, cost and sign pattern, with a monthly cost and a job ad at the end, as set out in our headcount requisition and hiring approval workflow.
Set a written approval policy before automating
Automation cannot resolve an unclear authority policy. Before building a workflow, document:
- the relevant asset or spend categories;
- the approval threshold for each category, if thresholds differ;
- who approves requests below and above each threshold;
- whether a second approver is required for particular purchases;
- how related-party suppliers, first-time purchases, or exceptions are handled; and
- who covers approvals when the usual approver is unavailable.
Use the company’s actual limits rather than copying a generic dollar amount. A policy might assign routine IT requests to a manager and require a director’s approval for a higher amount or specified asset class. The right limits depend on the organisation’s authority framework.
Separate roles where practical. A requester should not be the sole approver of their own request. The person who gathers quotes should not be mistaken for the person authorised to approve the PR. Smaller firms may need people to hold more than one operational role, but the roles and any compensating review should be documented.
A practical PR workflow
1. Intake
Choose one recognised intake route, such as a shared mailbox or a form that writes to a tracker. Staff can still discuss a need in chat, but the discussion should point to the formal request rather than serve as the approval record.
2. Capture the request
Collect enough information for a person to make a decision:
- requester and department or cost centre;
- item or asset category and quantity;
- estimated amount, with the basis or quote if available;
- business reason and required-by date;
- project or location, where relevant; and
- links to specifications or other supporting documents.
Mark missing information as “needs information” instead of guessing. Keep attachments in a company-controlled folder with access for the approver and their designated backup.
3. Route and flag
Use the written policy to select the approver. The workflow can flag a missing estimate, an unlisted category, an amount above the configured limit, or an exception requiring additional review. A flag is a prompt for review; it is not a decision.
4. Record the human decision
Give the approver a clear summary and a direct link to the request. Record whether they approve, reject, amend, or return it for more information, with the decision date and approver identity. Reminders and escalation to a named backup can help with delays, but elapsed time should not count as approval.
5. Hand off only after approval
Once the authorised person approves the PR, update its status to “ready for quotes” and notify purchasing. This status means quote collection may begin under the company’s process; it does not mean a supplier has been selected or a PO has been released.
6. Keep a usable tracker
A simple tracker could include: PR ID, requester, department, category, quantity, estimated amount, approver, backup, due date, status, exception reason, document link, decision, and next-step reference. Use a small, controlled set of statuses, for example: New, Needs information, Awaiting approval, Approved, ready for quotes, Rejected, On hold, and Cancelled.
The tracker should let an authorised colleague see what is waiting and why without relying on someone else’s inbox or phone.
What to automate, and what to keep human
Good candidates for automation: filing attachments, checking required fields, assigning a PR ID, routing based on approved policy, sending a reminder, notifying a backup, and updating the decision log after an authorised person acts.
Keep under human control: judging whether a proposed purchase is justified, deciding exceptions, approving expenditure, selecting a supplier where policy requires judgement, and releasing a PO. Do not automatically approve a request because its estimated amount is below a threshold unless the organisation has explicitly designed and authorised that control, and an accountable decision and audit trail remain clear.
This boundary also reduces the risk of putting personal or commercially sensitive information into an unsuitable tool. Singapore’s PDPA overview explains the law’s scope over the collection, use, disclosure, and care of personal data. Apply appropriate access controls and use approved systems for request and supplier information.
Start with existing tools or consider procurement software?
A shared mailbox, form, spreadsheet, and document store may be enough when request volume is manageable, approval rules are simple, and an assigned owner can maintain the tracker. Start by checking whether the current setup can provide a single intake route, reliable access for approvers and backups, a decision history, and a clear approved-to-quote handoff.
Consider a dedicated procurement or ERP workflow when the business has multiple entities, complex approval matrices, high request volumes, or audit and reporting needs that its current tools cannot reliably meet. Decide from the process requirements rather than a product demonstration alone. IMDA’s Industry Digital Plans for SMEs offer sector-oriented guidance for planning digital adoption; they are not a substitute for defining internal spending authority.
Common failure points
- Requests remain informal: people begin seeking quotes before a PR exists. Make the intake route explicit and require a PR reference for the quote handoff.
- Thresholds are vague: “ask someone if it is a large purchase” does not route consistently. Write the limits and category exceptions down.
- Approval is assumed: a chat acknowledgement, silence, or a reminder deadline is not a recorded approval. Require an identifiable approver decision.
- No cover is assigned: a request stalls when the usual approver is away. Name a backup and define what they may approve.
- PR approval is confused with PO release: permission to request quotes is not permission to place an order. Preserve the separate downstream approval.
- The tracker is hard to maintain: too many free-text statuses make the queue unreliable. Keep the fields useful, the status list controlled, and ownership clear.
A checklist for getting started
Before configuring a workflow, confirm that you can answer these questions:
- What purchases must go through a PR, and which categories need special handling?
- What are the approved limits, and who signs at each level?
- What information must a requester supply before review?
- Who is the primary approver and who is the backup?
- What status explicitly permits quote collection?
- How will the business record decisions and exceptions?
- How will PR approval remain separate from quote selection, PO release, and invoice processing?
- Can the workflow be tested with sample requests and understood by its owners without the builder present?
Start with a small, representative set of requests and test missing information, above-limit cases, rejected requests, and approver absence. Review whether each decision can be reconstructed from the record before expanding the workflow.
Next step
If your team is unclear about who approves an asset request, or quote collection starts before the approval is recorded, map one recent, representative request from intake to the point where quotes may begin. Define the fields, authority limits, exception route, approver, backup, and handoff before choosing software.
Lynqra can help assess the workflow and whether existing tools are sufficient. Explore Lynqra’s services or contact the team to discuss a practical process review.