Procurement & purchase order systems
Control the commitment at the point it is made
Procurement problems are rarely about buying. They are about the gap between a request, the approval that should precede it and the goods that eventually arrive.
We build requisition-to-receipt systems that follow your approval model, hold the commitment as a record, and hand clean data to whichever system owns payment.
| Reference | Vendor | Committed | Status | Next action |
|---|---|---|---|---|
| PR-4181 | Halstead Packaging | $1,840 | Requested | Awaiting budget owner |
| PO-4172 | Northline Mechanical | $12,600 | Approved | Ready to issue |
| PO-4166 | Corva Data Systems | $28,400 | Ordered | Delivery confirmed for the 22nd |
| PO-4158 | Ravenna Print Co. | $3,210 | Partially received | 2 of 5 lines outstanding |
| PO-4149 | Brightfield Logistics | $7,950 | Exception | Invoice exceeds PO by $612 |
| PO-4131 | Halstead Packaging | $980 | Complete | Closed and matched |
The operating problem
Where purchasing loses control
Each of these is survivable at low volume. Together, at scale, they remove the ability to forecast spend.
Spend is committed before it is approved
Orders are placed by phone and reconstructed later from invoices.
Approval depends on availability
A request stalls because one person is away and there is no delegation rule.
No line of sight from request to receipt
Nobody can say what has been ordered, what arrived and what is still outstanding.
Invoices arrive without context
Finance matches invoices to memories rather than to an approved commitment.
Routing
Requisition to purchase order
The path a request takes depends on value, category and exception state. Select a scenario to follow it.
Example system view
- Requisition
- Budget owner
- Vendor approval
- Finance
- PO issued
A new supplier pulls the vendor record into the path, so purchasing cannot commit before onboarding is complete.
Capabilities
What the system does
Requisition capture
Structured requests with cost centre, project, justification and supporting quotes.
Approval routing
Threshold, category and budget-owner rules with delegation and escalation.
Purchase order issue
Approved requests become orders with clear lines, terms and expected dates.
Receiving
Full, partial and rejected receipts recorded against the order line.
Exception handling
Price, quantity and delivery discrepancies routed to a named owner.
Spend visibility
Committed versus received versus invoiced, available without an export.
Record ownership
Which system is authoritative for what
Procurement touches vendors, budgets and finance. The design decision is not where data appears, but where it is owned.
Example system view
Requisition & approval
Owner: Procurement system- Request and justification
- Cost centre and project
- Decision path and history
Vendor record
Owner: Vendor management- Approved status
- Terms and rates
- Compliance state at order time
Commitment & receipt
Owner: Procurement system- Purchase order lines
- Expected dates
- Received and outstanding quantities
Invoice & payment
Owner: Finance / ERP- Invoice matching
- Posting
- Payment execution
Extend, replace or build
Operating value
What changes
Spend is visible while it is still a decision
Commitment is recorded at approval, not discovered at invoice.
Approvals keep moving
Delegation and escalation rules mean absence does not stall purchasing.
Finance receives clean input
Invoices match an approved order and a recorded receipt.
FAQ
Frequently asked questions
No. Accounting owns the ledger and payment. Procurement owns the requisition, the approval and the commitment, and passes the approved purchase order downstream.
Yes. Routing is driven by rules such as value thresholds, category, project, site or budget owner, and those rules are configurable rather than hard-coded.
Receipt is recorded against the order line. Short, over and damaged deliveries raise an exception with an owner instead of being resolved in email.
Often the right first step. Approval routing delivers control quickly, and receiving and reporting can follow once the request record exists.
Map your requisition-to-receipt process
Bring your approval thresholds and current tools. We will show where control is lost and what a system would own.