Purchase order best practices for 2026 finance teams (Singapore guide)

Key takeaways:

• A strong purchase order process gives finance teams visibility into committed spend before invoices arrive, not after

• 3-way matching, where you compare the PO, invoice, and goods receipt (or delivery confirmation), is one of the highest-impact controls for catching errors before money moves.

• Airwallex Purchase Orders connects the full cycle from request to payment in one platform, without the complexity of enterprise procurement software

Purchase order best practices help you gain control of spending before invoices arrive, rather than trying to explain costs after the fact.

By putting the right approval workflows, matching controls, and spend visibility in place, you can reduce budget surprises, speed up month-end, and create a more reliable audit trail.

This guide walks through five practical best practices that growing businesses can implement without the complexity of enterprise procurement software.

We'll also show you how Airwallex Purchase Orders helps you put these best practices into action by connecting requests, approvals, invoices, and payments in one platform.

Why purchase orders matter

Most finance teams only see spend after it happens. An invoice lands, someone chases an approval, and the payment gets processed, sometimes weeks after the original commitment was made.

The problem is that no one captured the spend decision before it happened.

A purchase order fixes this. It's a formal document raised before any money moves, confirming what's being bought, from whom, and at what price. More importantly, it tells your finance team that this spend exists, before the invoice arrives.

That shift from reactive to pre-commit matters more as your business grows. With a handful of suppliers, informal approvals are manageable. At 50 or 100 suppliers, they're not.

Budget overruns creep in through purchases no one tracked. Forecasts become unreliable because committed spend isn't visible. Month-end close slows down because approvals are missing.

A PO process gives you the visibility to know what's already been committed, so you're not caught off guard when the invoice arrives.

The purchase order workflow, step by step

Before getting into best practices, it helps to see the full PO cycle in one place. Each step builds on the last, and gaps at any stage create problems downstream.

1. Raise a purchase request. An employee identifies what they need to buy and submits a request with key details: item description, estimated cost, vendor, and the reason for the purchase.

2. Approve the request. The request is routed to the right approver based on spend amount, category, or department. Larger purchases may require sign-off from multiple people.

3. Generate and send the PO. Once approved, a purchase order is created and sent to the vendor. This is the moment your business formally commits to the spend.

4. Vendor confirms the order. The vendor acknowledges the PO and agrees to fulfil it under the stated terms. This confirmation is your record that both parties are aligned.

5. Receive goods or services. The vendor delivers. The relevant team confirms that what arrived matches what was ordered.

6. Match the invoice to the PO. When the invoice arrives, your finance team compares it against the PO and the delivery confirmation. This is called 3-way matching, and it's covered in detail in best practice three below.

7. Approve and pay. If everything matches, the invoice is approved and payment is scheduled. With a clean PO trail behind it, this step is fast.

The whole cycle only works if step one is easy enough that people actually follow it. If raising a PO feels like a burden, teams find workarounds, and the process breaks down before it starts.

Airwallex Purchase Orders is built with this in mind. Employees can submit requests in a few clicks, with no training required. Approvers get notified automatically, and finance gets a full audit trail from request to payment. Learn more about our Purchase Orders or sign up now.

Best practice 1: Set clear approval thresholds and delegated authority

One of the most common reasons PO processes break down is that approval rules are unclear. When employees don't know who to ask or how long it will take, they find shortcuts.

The fix is a simple threshold structure that routes requests to the right approver automatically, based on spend amount, category, or department. A basic framework might look like this:

You can add a second dimension by category. Software subscriptions, contractor fees, and capital expenditure may each carry different risk profiles, so they might trigger different approval chains regardless of amount.

A few rules that make threshold frameworks work well:

• Define what counts as a single purchase. A S$500 monthly subscription is a recurring commitment, not a one-off.

• Set an escalation path for when the approver is unavailable. Unanswered requests are one of the biggest sources of delay.

• Review thresholds at least once a year. What made sense at 50 employees may not fit at 200.

Delegated authority only works when the rules are written down and everyone knows them. A policy that lives in someone's head is not a policy.

Best practice 2: Build a pre-spend approval culture, not a bureaucracy

The most well-designed PO process will fail if your teams see it as an obstacle. The goal is to make the approved path the easiest path, not the most painful one.

This starts with how you introduce the process. Finance teams that present POs as a compliance requirement tend to get resistance. Teams that frame them as a way to get purchases approved faster, with less back-and-forth, tend to get buy-in.

A few things that make a real difference:

• Keep the request form short. Ask for what finance genuinely needs to approve a purchase: item, cost estimate, vendor, and business reason. Every unnecessary field is a reason to skip the process.

• Set a response time expectation. If employees know that routine requests under S$1,000 will be approved within 24 hours, they have no reason to go around the system.

• Make status visible. People abandon processes when they feel like requests disappear into a void. A simple tracker showing where a request sits in the approval chain removes that frustration.

• Lead from the top. When senior leaders follow the same process, it signals that the rules apply to everyone.

Pre-spend approval culture is not about control for its own sake. It's about making sure your finance team has the information they need before a commitment is made, not weeks after.

Best practice 3: Use 3-way matching to catch errors before you pay

3-way matching is the process of comparing three documents before approving a payment: the purchase order, the invoice from the vendor, and the goods receipt or delivery confirmation. All three need to align before money moves.

It's a step up from 2-way matching, which only compares the PO against the invoice. The third document, the delivery confirmation, is what tells you the goods or services were actually received as agreed.

When all three match, the invoice is cleared for payment. When they don't, the exception needs to be resolved first.

What a mismatch looks like

The most common mismatches are:

• The invoice amount is higher than the PO, often due to price changes or additional charges the vendor added

• The quantity on the invoice doesn't match what was received

• The invoice references a PO that was never raised, which is a red flag for unauthorised spend

How to handle exceptions

Every mismatch needs a clear owner and a resolution path. Here’s a workable approach:

1. Flag the discrepancy and notify the relevant team and vendor

2. Determine whether the difference is within your tolerance threshold (small rounding differences may be acceptable; price increases require re-approval)

3. If within tolerance, approve with a note on file. If outside tolerance, raise a revised PO or request a corrected invoice before proceeding.

Without a defined exception process, mismatches sit unresolved, payments get delayed, and vendor relationships suffer. The matching step is only as useful as the process that handles the cases where it fails.

Best practice 4: Standardise PO data and vendor information

A PO is only useful if it contains the right information. When fields are missing, inconsistent, or filled in differently by different teams, matching breaks down and approvals slow down.

Every PO should include the same core fields:

• Item or service description

• Quantity and unit price

• Total amount and currency

• Vendor name and payment details

• Cost centre or GL code

• Delivery terms and expected date

• PO number for cross-referencing

The vendor side matters just as much. If the same supplier is listed under three different names across your system, your matching process will fail to connect the PO to the invoice automatically.

Maintaining a clean vendor master list, with verified payment details and a single canonical name for each supplier, removes a significant source of matching errors.

The same logic applies to cost centre coding. When requesters assign the wrong code at the request stage, finance has to correct it manually downstream. A short dropdown list of valid codes, built into the request form, prevents most of these errors before they happen.

Best practice 5: Track committed vs. actual spend in real time

Approved POs represent money your business has committed to spend, even if the invoice hasn't arrived yet. If your finance team can't see that committed spend, your budget numbers are incomplete.

This is one of the most common gaps in early-stage PO processes.

A team checks their budget, sees S$100,000 available, and approves another purchase — unaware that S$80,000 of open POs are still waiting to be billed. When the invoices land, the budget is blown and the forecast is wrong.

The fix is tracking two numbers alongside each other: what has been approved but not yet invoiced, and what has actually been spent. The gap between those two figures is your exposure.

This means your PO tool needs to update committed spend as soon as a PO is approved, not when the invoice arrives. Waiting for the invoice to appear in your accounts payable queue is too late for meaningful budget management.

Choosing the right purchase order software

Once your PO process is defined, you need software that fits where your business actually is, not where it might be in five years.

What to look for in PO software

The right purchase order software for a growing finance team should cover four things:

• Up and running quickly, without a lengthy implementation project

• Approval workflows that are easy to configure and adjust as your business changes

• Real-time visibility into committed spend, not just invoices that have already arrived

• POs, invoices, and payments managed in one place, not spread across separate tools

That last point matters more than it might seem. When your PO system and your payment platform are separate, there is always a reconciliation step in between. Data gets manually transferred, errors creep in, and your committed spend figures lag behind reality.

Where Airwallex fits

Airwallex Purchase Orders is built for mid-market finance teams that need spend control without enterprise-grade complexity.

Requests, approvals, and PO generation sit in the same platform as Bill Pay, Corporate Cards, and Expense Management. Committed spend, invoices, and payments are visible in one view.

Because the PO module and the payment infrastructure are part of the same platform, there is no gap between approval and execution. Learn more about Airwallex Purchase Orders or sign up now.

4 common purchase order mistakes to avoid

Even well-designed PO processes develop blind spots over time. These are the mistakes that finance teams run into most often:

1. Skipping POs for small purchases

Low-value purchases are easy to wave through informally. But small purchases add up, and they are often where the most budget leakage occurs. Apply your PO process consistently across all spend above a defined minimum threshold.

2. No escalation path when approvers are unavailable

If a request can only be approved by one person and that person is travelling, the process stalls. Every approval tier needs a designated backup.

3. Manual matching at scale

Comparing POs and invoices by hand works for a small number of transactions. Beyond that, errors multiply and reconciliation becomes a significant time drain. Automate matching as early as possible.

4. Treating the PO process as a finance-only concern

The PO process touches every team that spends money. If department heads are not bought in, requests will bypass the system. Finance teams that involve department leads in designing the process get far better adoption.

How Airwallex supports every step of the PO process

If you want to improve your PO process and get real visibility into committed spend before invoices land, Airwallex is the best way to do that. Here's what you get with Airwallex:

• Pre-commit visibility. Committed spend is tracked from the moment a PO is approved, not when the invoice arrives. Budget figures stay accurate in real time.

• Approval workflows. Set rules by amount, department, or category. Requests are routed automatically, with a full audit trail at every step.

• 3-way matching. AI-powered OCR reads and extracts invoice data, then matches it against the corresponding PO and goods receipt. Exceptions are flagged for review rather than passed through.

• Integrated payment execution. Approved invoices move directly into Bill Pay for payment. There is no manual handoff between your procurement process and your payment platform.

For finance teams that also use Airwallex Corporate Cards and Expense Management, all your spend, including POs, card transactions, and reimbursements, is visible in a single view.

Frequently asked questions (FAQs)

What are the most important purchase order best practices for a growing business?

The five that make the biggest difference are: setting clear approval thresholds, building a process your team will actually follow, using 3-way matching before every payment, standardising PO data and vendor records, and tracking committed spend in real time. Most businesses see the biggest gains simply from formalising the approval step before any commitment is made.

What is 3-way matching in the purchase order process?

3-way matching compares three documents before a payment is approved: the purchase order, the vendor invoice, and the goods receipt or delivery confirmation. All three need to align. It's a stronger control than 2-way matching, which only checks the PO against the invoice, because it confirms the goods or services were actually received as agreed.

What happens when a purchase order doesn't match the invoice?

The invoice should be held and the discrepancy flagged for review. Minor differences within a pre-defined tolerance threshold can be approved with a note on file. Larger variances need to be resolved before payment — either by requesting a corrected invoice from the vendor or raising a revised PO if the scope of the purchase genuinely changed.

How do you set purchase order approval thresholds?

Start with spend amount as the primary dimension: route low-value requests to department managers and escalate larger amounts to finance or the CFO. You can add a second dimension by category, since some spend types carry higher risk regardless of amount. Review your thresholds at least once a year as your business grows.

Do small and mid-sized businesses in Singapore need a formal PO process?

Most businesses benefit from formalising their PO process once they reach around 50 employees or are managing more than a handful of regular suppliers. At that point, informal approvals start causing budget gaps and audit gaps. Airwallex Purchase Orders is designed for teams at exactly this stage, without the complexity of large enterprise procurement systems.

Can you manage purchase orders without dedicated procurement software?

You can, but only at a small scale. Manual matching and spreadsheet-based tracking become error-prone quickly as transaction volume grows. Dedicated purchase order software automates the approval routing, matching, and payment steps that take the most time, and gives finance teams a reliable audit trail without manual effort.

This publication does not constitute legal, tax, or professional advice from Airwallex, nor does it substitute seeking such advice, and makes no express or implied representations / warranties / guarantees regarding content accuracy, completeness, or currency. If you would like to request an update, feel free to contact us at [[email protected]]. Airwallex (Singapore) Pte. Ltd. (201626561Z) is licensed as a Major Payment Institution and regulated by the Monetary Authority of Singapore.