xMatix
Sign in Request demo
xMatix
PRODUCTS
SalesField SalesCRMRewardsClaimsInventoryProcurementWarehouse ManagementField ServiceServiceSupportTelephony & MessagingFinance & AccountingPayrollExpense ManagementCommercePortalsAnalytics & ReportingData StudioMobile AppSee all products →
PLATFORM
Platform overviewApp BuilderAutomationIntegrationsSecurity & GovernanceChange ManagementDevelopers
SENSE AI
Sense AI overviewSense AssistSense ControlSense VisionAI StudioTrust & governanceIn Claude & ChatGPTUse cases
SOLUTIONS
FMCG & DistributionManufacturing & Dealer NetworksAutomotive & DealershipsPharma & HealthcareConsumer DurablesAgri-InputsBuilding MaterialsService NetworksWarehousing & 3PLFinancial AccountingERP SoftwareIndia GST ComplianceUAE VAT & e-InvoicingSaudi ZATCA & VATAll solutions →
RESOURCES
Knowledge CenterDeveloper & CLIBlogGuidesWhat is xMatix?Company facts
COMPANY
AboutCareersPartnersEventsContactAuthorsLegal
Sign in Request demo
Home/Docs/Role Guides/Role guide: procurement user
OVERVIEW · Last reviewed

Role guide: procurement user

This guide is for the buyer. Your xMatix day follows one chain — requisition, purchase order, goods receipt, supplier bill — and your job is keeping that chain moving and honest: ordering what the business actually needs, chasing what hasn't arrived, and only paying for what was ordered and received.

Where you work

The first-party Procurement app carries the whole document chain on its bar: Requisitions, Auto Orders, Purchase Orders, Shipments, Goods Receipts and Bills, plus Reports, Dashboards and a Settings entry that opens the procurement masters (items and the module settings). Documents connect through release actions rather than through a wizard — a requisition releases into a purchase order (or a stock transfer), a purchase order releases into a goods receipt or a bill, and a goods receipt can release a bill — so most of your work happens on a document's detail page and its action buttons. Supplier balances and the bills' accounting side are read in the Finance app's AR and AP subledgers; the stock a receipt creates is read in the Inventory app's ledger.

Procurement app, All Purchase Orders view: last-30-day cards above the order register with branch, supplier account, total amount and status columns
The All Purchase Orders view in the Procurement app — the buyer's queue, read by supplier and status before any new document is created.UI captured
  1. 1

    The Procurement bar carries the whole chain — Requisitions, Auto Orders, Purchase Orders, Shipments, Goods Receipts, Bills — so each document is one click from the one it was released from.

  2. 2

    All Purchase Orders is the active saved view; the Recent strip underneath reopens the orders you were last working.

  3. 3

    The cards count last-30-day orders and how many have progressed to a bill or a goods receipt — a quick read of how much is still open.

  4. 4

    Search, column filters and refresh scope the queue by supplier, branch or status before you open an order or raise a new one.

  5. 5

    Status is the release trail — Draft until a downstream document exists, then Goods Receipt or Bill — and Total Amount shows the commitment; user columns are hidden in this capture.

The All Purchase Orders view is the buyer's queue. The cards above the register count the last 30 days' orders and how many have progressed to a goods receipt or a bill; the register underneath carries document number and date, branch, supplier account, total amount and status. Status here is the release trail — Draft until a downstream document exists, then Goods Receipt or Bill — so filter by status and supplier to find what is still open, open the order, and read its lines' pending quantities before creating anything new.

Access you need

xMatix does not ship a buyer profile — of the seeded profiles, only the administrative ones carry the procurement entities — so your administrator grants a procurement profile read, create and update on Requisition, Purchase Order, Shipment, Goods Receipt, Bill, Auto Order and their lines, view access to the Procurement app, and the release and receive actions explicitly: each of Release Purchase Order, Release Goods Receipt, Release Bill, Perform Receive and the inspection actions is an entity action a profile can allow or withhold. That separation is deliberate — a buyer can be allowed to raise and release orders while only the warehouse may run Perform Receive, and only finance may post. Purchase-order approval, where your organization uses it, is an approval process on the order rather than a permission. Procurement is licensed as its own product; if the app or an action is missing, start with Troubleshooting: a user can't see something.

Your path

  1. xMatix Procurement — the product overview; the document chain your day runs on.
  2. Requisitions: from request to purchase order — where demand enters, what is pending, and the release to an order or a transfer.
  3. The purchase order lifecycle — the central document: header, lines, how line quantities drive the lifecycle, and the two release paths.
  4. Receive goods against a purchase order — the three quantities on a line, receiving into stock, inspection, releasing the bill, posting the accrual.
  5. Supplier bills — recording what the supplier is asking to be paid, and where it lands in finance.
  6. Three-way match: order, receipt and bill — how the comparison works, the link contract, and the release-path limitation that decides whether a bill is matched at all.
  7. Auto-order: rules-based purchase suggestions — letting reorder rules draft the routine buying for you.
  8. Frequently ordered item suggestions — faster lines on the orders you place by hand.
  9. Receiving into the warehouse — what the floor does with your order when the truck arrives.

Day to day

Mornings start with the queue: new requisitions to review and release, and auto-order suggestions to accept or trim before they become purchase orders. As deliveries land, goods receipts record what arrived against the order — the warehouse's receiving puts it into a storage location — and as bills arrive, the three-way match tells you which agree with order and receipt and which need a conversation with the supplier. Orders still in Draft status with pending quantities on their lines are your chasing list. Stock questions — did the receipt really land, what did it cost — are answered in the inventory ledger and valuation.

Common questions

A bill disagrees with the order — why isn't it blocked?

Because the match service compares and reports; it does not itself block posting or payment. Three-way match explains exactly which numbers are compared, and the link contract that decides whether a bill is even in scope — a bill released from the receipt keeps only the receipt-line link, so release bills from the order when receipts exist.

Does a goods receipt change stock, or just paperwork?

Both, in two steps: creating the receipt stages quantities, and Perform Receive posts real stock into the storage location named on each line. Receive goods against a purchase order walks the three quantities on a line; the inventory ledger shows the movement it creates.

Why does a line still show pending quantity after we received?

Pending counters are derived from downstream line quantities, and the order's receipt progress reads the receipt line's ordered quantity — staging, not proof of posting. Check the receipt's own status and lines; The purchase order lifecycle and Troubleshooting procurement cover the exact refusals and counters.

Who approves my purchase orders?

Whoever the approval process names — orders can be gated the same way any record is. Approval processes explains the mechanics; the thresholds are your organization's own configuration.