Welcome to Procurement
AxisSynapse Procurement is the purchase-to-pay module — from identifying a need, sourcing a vendor, raising a PO, receiving the goods or services, matching the invoice, paying the vendor, and keeping the audit record that proves every dollar of spend was authorized. The module exists because spend without controls is the largest single source of preventable loss in most workspaces.
TL;DR — Open Procurement → Dashboard. Vendors is the supplier master; Requisitions + POs is the spend request flow; RFQs + Sourcing is the competitive-bid flow; Contracts holds the master agreements vendors transact under; Invoices is the AP queue. Approval chains run through every stage so the trail follows the dollar.
What the module covers
| Field | What it does | Accepted values / default |
|---|---|---|
| Vendor master | The supplier record + qualification + banking + tax docs. | Covered in [Vendor onboarding](/procurement/vendor-onboarding). |
| Requisitions + POs | Internal request → approved PO → receipt → matched invoice → payment. | Covered in [Purchase orders + approvals](/procurement/purchase-orders-and-approvals). |
| Sourcing events | RFI / RFQ / RFP for competitive spend. | Covered in [RFQ + sourcing events](/procurement/rfq-and-sourcing-events). |
| Contracts | Master agreements governing repeat purchases. | Threaded through vendors + POs; the contract record references the PO + vice versa. |
| Invoices + matching | AP queue; 3-way match against PO + receipt. | Drives payment release. |
The four audiences
| Field | What it does | Accepted values / default |
|---|---|---|
| Requester | Raises a request for goods or services. | Self-service requisition form; sees only their own requests + status. |
| Buyer | Sources, negotiates, raises POs. | Full UI; owns vendor relationships + POs in their commodity / category. |
| Approver | Authorizes spend at the configured threshold. | Inbox-driven; sees only items routed for their approval. |
| Auditor | Reads the end-to-end trail per transaction. | Read-only export of req → PO → receipt → invoice → payment. |
Why every transaction goes through PO
Skipping the PO ("just buy it, expense it later") is the single most common procurement failure mode. The PO is the workspace's authorization record + the basis for 3-way match + the binding commitment to the supplier. Without it:
- Authorization is reconstructed from email — fragile + slow.
- Supplier disputes have no anchor — quantity / price / terms rely on the supplier's invoice.
- AP cannot do 3-way match — invoices route to slower manual review.
- Year-end accruals are estimated rather than known.
- Audit findings tend to recur until the policy is enforced.
The module's approval chain is designed to be faster than the email-shortcut version when the workspace commits to using it — auto-routed approvals + electronic PO transmission + supplier self-service for receipt confirmation move at scale.
Where to start
- New to the module? Purchase orders + approvals walks the most common path.
- Bringing on a new supplier? Vendor onboarding.
- Running a competitive bid? RFQ + sourcing events.
How Procurement pairs with other modules
- Inventory receives the PO; the receipt is the second leg of the 3-way match. See Inventory → Receipts and putaway.
- Fixed Assets picks up capital items the moment a receipt crosses the workspace's capitalization threshold.
- HCM owns the buyer + approver directory; approval delegation cascades down the workspace's reporting tree.
Common gotchas
- "Requester bought without a PO." The expense exists, the PO doesn't, AP can't match. Open a retroactive PO to anchor the spend; document who authorized; the policy follow-up is on the requester's manager. Don't pretend it didn't happen.
- "The PO doesn't match the supplier's quote." Edits to approved POs follow the same approval ladder as the original — buyer can't unilaterally raise the value past the original approval threshold without re-routing.
- "The vendor was paid before the receipt posted." The 3-way match should have blocked. If it didn't, the workspace's matching tolerance is too loose or the receipt flow is too slow. Audit the recent payments + tighten.
Related