Purchase orders and approval

Why every purchase needs a PO, and how approval limits protect the company.

Baca dalam Bahasa Indonesia

On this page
  1. Why every purchase needs a PO
  2. The life of a PO
  3. Approval limits
  4. Writing a good PO
  5. Example: from draft to commitment
  6. In Voltrus
  7. Checklist

A purchase order (PO) is the company's written promise to buy: this supplier, these items, this quantity, this price, delivered here by this date. Once the supplier accepts it, it is a contract. That is why good practice says no PO, no purchase: if anyone can commit the company's money by phone, nobody controls spending, and every supplier invoice becomes a surprise.

Why every purchase needs a PO

The PO does four jobs at once:

  1. Authorisation. Someone with the authority approved this spend before it happened, not after the invoice arrived.
  2. Commitment tracking. Approved but unreceived POs are money you have promised to spend. Budgets and cash forecasts need them.
  3. A reference for receiving. The warehouse checks deliveries against the PO, not against the supplier's delivery note.
  4. A reference for paying. Accounts payable compares the supplier's bill with the PO price and the received quantity (the three-way match).

A PO raised after the invoice (an "after-the-fact PO") does none of these. Track how often it happens and treat it as an exception that needs a reason.

The life of a PO

StatusMeaningWhat you can still change
DraftBeing prepared; not yet a commitmentEverything: supplier, lines, prices, dates
ApprovedAuthorised and sent to the supplierNothing on the lines; goods can now be received
ReceivedEvery line fully receivedReturns only
ClosedFinished; no more activity expectedNothing
CancelledWithdrawn before completionNothing

The rule that matters: lines are frozen once the PO is approved. If the supplier changes the price or quantity, cancel and re-issue, or agree the change formally, so the approval always covers what was actually ordered.

Approval limits

Most companies set an approval matrix by amount. A typical one for a mid-size manufacturer:

PO valueApprover
Up to Rp 10 millionPurchasing supervisor
Rp 10–100 millionDepartment head
Above Rp 100 millionDirector
Capital items (any value)Director, with budget reference

Two principles sit behind every matrix:

  • The approver is not the buyer. The person who negotiated the deal should not also authorise it.
  • Splitting is not allowed. Breaking one purchase into three POs to stay under a limit is a control breach, and auditors look for it (several POs to the same supplier on the same day just below a limit).

Budget checks

A second control is the budget: before approving, check that the cost centre still has budget left after counting what is already spent and what is already committed on open POs. Commitments are the part spreadsheets usually miss.

Writing a good PO

  • Use item codes, not free text. "Bearing 6205" typed by hand cannot be received into stock, planned or analysed.
  • Price every line from the agreed price list. If you type a different price, say why.
  • Set the expected date. Planning and supplier on-time measurement both depend on it.
  • Pick the receiving warehouse. It decides where stock lands.
  • Fill the cost centre and project when the purchase belongs to one, so the cost is reported in the right place.
  • Use the supplier's unit when you buy in it (boxes, rolls) and let the system convert to your stock unit.

Example: from draft to commitment

A buyer drafts a PO for 200 rolls of packing film at Rp 85,000, freight Rp 750,000, for cost centre Packing.

Amount
Goods (200 × 85,000)17,000,000
Freight750,000
PO value (before PPN)17,750,000

The packing budget for the year is Rp 150 million. Actual spend so far is Rp 118 million, and other approved but unreceived POs total Rp 20 million. Available: 150 − 118 − 20 = Rp 12 million. This PO needs Rp 17.75 million, so it would overrun the budget by Rp 5.75 million. Depending on policy, the approver either refuses, raises the budget, or approves with a recorded overrun.

Approving the PO posts nothing to the ledger. A PO is a commitment, not a transaction; the first journal comes at goods receipt.

In Voltrus

How approval works, and how to run an approval matrix with it:

  • Approval limit. In Settings → Inventory & trading, the Approvals and limits card holds an IDR amount for Purchase order (lines plus freight, before PPN; foreign currency compared in IDR). At or below it, any operations user may approve. Above it, only an Admin may: anyone else's approval goes to Approvals as a proposal that an Admin decides. Leave it empty for no limit.
  • No approving your own proposal. A proposal is approved by someone other than the person who proposed it. In a one-person company the proposer may approve it, and the audit trail records that; set Approving your own proposal to Never to forbid even that.
  • Budget check on approve. In the same card, Budget check on purchase orders is Off, Warn (the overrun is recorded in the audit trail) or Block (the approval is refused). It compares actual spend plus open commitments plus this PO against every approved budget on the PO's cost centre and the cost centres above it. Set up budgets under Budgets.
  • Proposals carry the approval. A user can send the approve step as a proposal instead of running it; it waits in Approvals with the before/after shown. AI agents always work this way: an agent can draft and propose a PO but never approve one by itself.
  • The audit trail records who approved. Review approvals periodically in Audit, filtered by purchase order.

Voltrus has one approval limit per document type, not a multi-level chain. To run a matrix like the one above, set the limit at the highest amount an operations user may approve (say Rp 100 million), give directors the Admin role, and keep the lower tiers as a written rule you review in the audit log.

A few gaps to plan around:

  • There is no purchase requisition and no blanket (framework) order. Use draft POs for requests, and a price list with validity dates for framework prices.
  • MRP can create draft POs for you: on the MRP page, select buy suggestions and convert them, one draft PO per supplier and warehouse.

Checklist

  • Publish the "no PO, no purchase" rule with its list of exceptions.
  • Write an approval matrix by amount and make sure buyers do not approve their own POs.
  • Set the purchase order approval limit and give the people above it the Admin role.
  • Load budgets per cost centre and decide whether overruns warn or block.
  • Always fill item codes, expected date, warehouse and cost centre.
  • Review after-the-fact POs and possible order splitting every month.

Run it in Voltrus ERP

Everything in these guides is built in: documents that post to the ledger as they happen, Indonesian tax, MRP and costing, with AI agents that propose and people who approve.

See Voltrus ERP