Requisitions to purchase orders

← All documentation

Overview

Purchasing lives under Purchasing → Requisitions and Purchasing → Orders. The flow is the classic spine: someone requests (a requisition), the request is approved, and approved lines are converted into purchase orders to suppliers.

Each stage moves money through the budget: an approved requisition reserves it, an issued order commits it to the supplier, and received goods turn it into spend — the same three words you see on every cost centre. See Setting and reading budgets.

Raising a requisition

A requisition carries line items — product or SKU, quantity, unit of measure, expected unit cost — and the cost centre the spend belongs to. Save as a draft while you assemble it, then submit. Submitted requests show in the budget's Projected figure so finance can see what's in flight before deciding anything.

Approval and the budget check

Submission routes the requisition through your organisation's approval rules — conditional tiers like "over $25k" send bigger requests up longer chains. Approval is also the moment the budget reservation is taken: the cost centre's Available figure drops, and the movement lands in the ledger with the requisition as its source.

Converting to purchase orders

Approved lines are converted into one or more purchase orders — split lines across suppliers, or gather several requisitions' lines for one supplier. Issuing the PO moves the money from reserved to committed and starts the supplier-facing lifecycle: acknowledgement, promised dates, shipments, and receiving (see Receiving goods).

Releasing money: closing or amending a requisition releases what it still holds; cancelling or short-closing a PO releases the unreceived remainder of its commitment. Actual spend can't be released — that's what adjustments are for.

Related guides

Can't find what you need?

Email support@arthiva.ai or use the contact page — we aim to respond within two business days.

Contact support