Guided buying
Requesters shop the catalogue or describe a need, with coding and budget shown before they submit.
Buy under policy: requests, approvals, orders, receipts and suppliers on one record.
Procurement takes a request from anyone in the business, checks the budget and the contract, turns it into a purchase order that goes through approval, and records what was received. Suppliers register in a portal and are screened before they can be used, and spend is reported by supplier, category and cost centre.
Requesters shop the catalogue or describe a need, with coding and budget shown before they submit.
Approval follows amount and category, and no one approves their own request or order.
Orders are checked against contract prices and off-contract spend is flagged before it is bought.
Suppliers fill in their own details, are screened and approved by another person, and bank details go through four-eyes control.
What is received feeds Payables and stock once, so bills match what was ordered and received.
Search or filter. Planned items are labelled; everything else is available now.
Anyone can ask to buy something by shopping the catalogue or describing the need, with coding and budget shown before they submit.
8 featuresThe items people can buy, with prices, suppliers and the spend categories that decide default coding.
7 featuresOrders are raised for active suppliers, approved, issued and changed under control, with every version kept.
11 featuresRecord what arrived or was done against an order, in parts, and what went back.
7 featuresSuppliers register themselves, are screened and approved by another person, and then see only their own business with you.
10 featuresAgreed prices and caps are recorded and orders are checked against them.
7 featuresSee where the money goes and what is left, with maverick spend and contract coverage in view.
6 featuresEvery procurement policy is a company setting with a safe default, and AI prepares work that people decide.
7 featuresIt prepares the work. A person confirms it.
The same four building blocks, specific to Procurement.
Requisitions, orders, change orders and new suppliers follow the approval routes the company sets on the shared authority matrix.
Spend and purchasing reports by supplier, category, cost centre, project and month, with three persona dashboards.
Datasets
Dashboards
Procurement publishes resources and events; Payables, Warehouse and the contract hub link to it by events and ports.
/v1 resources: requisitions, purchase orders, receipts, suppliers
Events
Connectors
Supplier records can come in through the finance packs of a legacy ERP. Open purchase orders and procurement-suite packs are not built yet.
Requests, approvals and receiving have phone routes today. A native app is planned.
Issued orders and receipts feed the three-way match and the goods-received accrual; approved suppliers become vendors.
Receipts of stocked items book stock; reorder suggestions become draft requisitions; drop-ship lines create draft orders.
Executed supplier contracts become contracts and frame agreements here, with a call-off check on orders.
Requisition, order, change and supplier decisions run on the shared authority matrix.
Planning budgets are read to check requests and orders.
Spend is coded to GL account, cost centre and project; postings are made by Payables and Warehouse.
Only as far as the company's policy allows. Requests follow an approval route by amount and category, and maverick lines are flagged to the approver.
They are invited by email, complete their own profile and documents in the portal, are screened, and are approved by a second person before orders can be raised.
A change order is approved the same way and becomes the next version. The supplier is asked to acknowledge it and a line cannot go below what was received.
Orders under a contract are checked against its prices and cap. The company decides whether a breach warns or blocks.
They go to Payables' bank-change control with a call-back and a second person. Procurement does not keep them.
No. It drafts requests and orders and prepares changes. Approving, issuing and sending stay with people.
Not yet. Both are in the design and not built.