The xMatix Procurement module runs the buying cycle end to end: someone asks for items, the request becomes a purchase order, goods arrive and are received into stock — with an inspection step for items that require it — and the supplier's bill is recorded and linked back to what was ordered and received. Alongside that document chain, rules-based auto-ordering suggests what to buy from your own stock and consumption numbers, with the arithmetic behind every suggestion stored on the suggestion itself.
Everything lives in the Procurement app: Requisitions, Auto Orders, Purchase Orders, Shipments, Goods Receipts and Bills in the app menu, plus reports. Each list opens the saved document, whose tabs (Lines, Details and document-specific tabs) are where the procedures in this section are carried out. A purchase order proves commercial intent; a goods receipt supplies quantity and condition evidence; a bill supplies payable and tax evidence. The three-way comparison between them exists as a backend service without a standard product screen, so its page documents the contract and limitations rather than a UI.
The document chain
| Document | What it is |
|---|---|
| Requisition | An internal request for items, released into a purchase order — or into a stock transfer when you fulfill it from your own warehouses. |
| Purchase order | The commitment to a supplier, and the hub every later document links back to. |
| Shipment | An inbound consignment on its way from the supplier; released into a goods receipt on arrival. |
| Goods receipt | What actually arrived, posted into stock — with a goods-inspection step for flagged items. |
| Bill | The supplier's invoice. Order-side invoice release can preserve both order-line and receipt-line links when receipts exist; receipt-side Release Bill currently preserves only the receipt-line link. |
| Auto order | A worksheet of rules-based purchase suggestions that you review and turn into purchase orders. |
Documents connect through release actions: a requisition releases into a purchase order, and a purchase order releases into a goods receipt or a bill. Goods receipts can also release a bill. Selective variants exist for the requisition and purchase-order paths. Pending counters are derived from downstream line quantities; on purchase-order receipt progress, the current aggregate uses the goods-receipt line's Ordered Quantity, so it represents quantity staged onto receipt lines rather than proof that Perform Receive posted that quantity.
In this section
- Requisitions: from request to purchase order — raise a requisition and release its lines into an order.
- The purchase order lifecycle — full and selective releases, pending quantities, supplier schemes.
- Receive goods against a purchase order — receiving, goods inspection, and releasing the bill.
- Supplier bills — where bills come from and how they stay matched to orders and receipts.
- Auto-order: rules-based purchase suggestions — the three replenishment engines and the arithmetic snapshot on every line.
- Three-way match implementation reference — the backend comparison contract, its link requirements and the current absence of a standard screen.
- Frequently ordered item suggestions — the ranked shortlist offered while building orders.
- Procurement configuration reference — the admin settings that shape all of the above.
- Troubleshooting procurement — stuck receipts, flagged bills, surprising suggestions.
Related topics
- Procurement product overview
- Inventory product overview — stock levels, warehouses and transfers that procurement replenishes
- Getting started with xMatix