Access and permissions in Purchasing
You need the Purchase module, the feature for the task, the appropriate permission and access to the document's business unit. Lookup lists can also need permissions in Supplier, Catalog, Organization and Inventory.
Permissions by task
All codes below start with purchase.. For example, order.create means purchase.order.create.
| Task | Permission suffix | Feature |
|---|---|---|
| Search the Orders register | order.search | PURCHASE_ORDERS |
| Open an order | order.view | PURCHASE_ORDERS |
| Create / edit a draft | order.create / order.update | PURCHASE_ORDERS |
| Submit / reopen for correction | order.submit | PURCHASE_ORDERS |
| Approve / reject | order.approve / order.reject | PURCHASE_ORDER_APPROVALS |
| Issue / acknowledge | order.issue / order.acknowledge | PURCHASE_ORDERS |
| Cancel an order or line | order.cancel | PURCHASE_ORDERS |
| Close an order or a line's receiving/invoicing | order.close | PURCHASE_ORDERS |
| Refresh a draft supplier snapshot | order.update | PURCHASE_ORDERS |
| Amend agreed details | order.amend | PURCHASE_ORDER_AMENDMENTS |
| View approval / revision history | order.approval.view / order.revision.view | PURCHASE_ORDER_APPROVALS / PURCHASE_ORDER_REVISIONS |
| View receipts | receipt.view | PURCHASE_GOODS_RECEIPTS |
| Create or cancel a draft receipt | receipt.create | PURCHASE_GOODS_RECEIPTS |
| Post a receipt | receipt.post | PURCHASE_GOODS_RECEIPTS |
| View / create / post invoices | invoice.view / invoice.create / invoice.post | PURCHASE_INVOICES |
| View / post / allocate vendor payments | vendor-payment.view / vendor-payment.create / vendor-payment.allocate | Purchase module; no separate task feature in these screens |
Example: Ali can have receipt create/post/view and order view/search without invoice-posting access. Farah needs invoice viewing and vendor-payment creation, viewing and allocation to complete the payment workflow.
Business unit access
Ask an administrator to check User business unit access for the unit owning the order, receipt, invoice or payment. Stock operations also check the warehouse's business unit. A permission to create orders does not grant access to every unit.
Use the payment link from an invoice where possible: it carries that invoice's business-unit context into payment creation. The standalone payment form does not expose a business-unit selector.
Approval separation
A user cannot manually approve the order they submitted. Nadia must use her own account to approve Omar's submission. This is enforced, not simply a recommended division of duties. Eligible low-value orders may instead be auto-approved by policy at submission.
The recorded approval level is not a sequence of named manager/director buttons. The current screen has one Approve action. See the actual approval rules.
A missing button or unavailable page
- Check the module and feature with the administrator.
- Check both search/view permissions and the command permission. For example, creating an invoice also needs receipt viewing to load its source.
- Check business-unit access and lookup permissions.
- Check the document state: a posted receipt cannot be cancelled through these screens.
- Reload your access context or sign in again after permissions change.
If the page says Purchase unavailable, it needs the Purchase module, relevant feature and permission. Do not create a second document to bypass missing access.