Skip to content

Procurement Software | Purchase Orders

POs against active budgets. Vendor compliance verified at save.

Multi-line, multi-currency, multi-location POs. Budget checked at save against cost-centre, project and period. Vendor register status and GST registration checked live. Approver chain routes per matrix. Templates pre-fill for repeat purchases.

Purchase Orders

What the system does

Capability, input, output.

  • Multi-line PO

    Input
    Items + quantities + prices + dates
    Output
    Validated PO ready for approval
  • Multi-currency

    Input
    Foreign-currency line items + your rate source
    Output
    Budget-currency equivalent, with the rate kept on the PO
  • Budget check

    Input
    PO amount + cost-centre / project / period
    Output
    Allow / block / override path
  • Vendor compliance

    Input
    Vendor UEN and GST registration
    Output
    Live status check at PO save
  • Approval routing

    Input
    PO + approval matrix
    Output
    Approver chain with channel preference
  • PO dispatch

    Input
    Approved PO + vendor contact
    Output
    Email delivery + portal entry

Compliance + integrations

POs that respect budget, compliance and audit.

Budget enforcement is the internal control, and the vendor check is what stops a PO being raised against an entity that no longer exists. The audit trail captures every PO from creation to dispatch.

Regulations we work within

  • Internal controls

    Budget authority evidenced at the PO rather than asserted in a policy document.

  • GST Act

    Vendor registration status checked at the PO, before anything downstream claims input tax.

  • Audit trail

    PO lifecycle preserved, including every amendment and who approved it.

Connects to

  • ACRA / IRAS Live vendor status
  • Xero PO sync
  • SAP Business One Native connector
  • Vendor portal PO delivery and acceptance

Purchase Orders FAQ

What buyers ask.

Can we have different PO formats for different categories?

Yes. PO templates per category (capex vs opex, services vs goods, domestic vs import). Each template has its own GL coding, approver chain and required fields. Sales rep / requester picks the template; the rest fills in automatically.

What if a PO needs amendment after dispatch?

Amendments (line addition, quantity change, price revision) are versioned. Each amendment routes through approval (often a higher tier than the original). The vendor sees the amendment on the portal; the PO history is preserved.

How does multi-currency work for PO budgets?

The PO amount converts to the budget currency at your configured rate, and the budget check happens in that currency, so a budget does not quietly stretch because the dollar moved. The rate used is kept on the PO, and the FX exposure is tracked separately for treasury rather than being buried in the commitment.

Vendor portal acceptance. What does it cover?

Vendor logs in (OTP) to the portal, sees the PO, confirms acceptance or proposes changes. Acceptance captures the PO version, the vendor confirmation timestamp, and triggers production / dispatch on the vendor side.

Raise your next PO with the budget check on screen.

Connect one entity, free. Configure one cost-centre budget. The next PO checks the budget, verifies the vendor live, routes for approval. The full cycle on your data.