Access and permissions in Invoicing
The Invoicing screens require the Invoicing capability and the permission for the task. Documents are tenant-scoped, and the service checks your business-unit access.
Permissions by task
| Task | Permission | Other requirement |
|---|---|---|
| Search/open sales invoices | sales.invoice.view | Invoicing capability and allowed business unit |
| Create from a sales order | sales.invoice.create | Eligible source order; viewing also needed to inspect the result |
| Post an invoice | sales.invoice.post | Draft with lines and positive total |
| Cancel a draft | sales.invoice.cancel | Draft only |
| Read linked credit notes | sales.credit-note.view | Source/details visibility where needed |
| Credit create/post/cancel permissions | sales.credit-note.create, .post, .cancel | Writes remain disabled in the browser |
| Open the source sales order | sales.order.view | Sales access and source business unit |
| Change draft journal accounts | sales.invoice.accounts.update and accounting.account.view | Accounting enabled; invoice and two-entry journal both Draft |
| View customer payments | payment.view | Payment access for the Payments workspace |
| Record payment through the order's payment workflow | payment.create and payment.allocate | Posted/Partially paid invoice with a positive balance |
| Use standalone customer receipt steps | payment.create, payment.post, payment.allocate as appropriate | Payment module; these are separate tasks |
The sales.invoice.* prefix is used even though the workspace is Invoicing. There is no separate invoicing.invoice.create permission to request.
Example role split
| Person | Example access |
|---|---|
| Omar | Sales order access and invoice viewing, if needed |
| Farah | Invoice view/create/post/cancel and relevant payment access |
| Senior accounts reviewer | Invoice viewing, journal-account update and account viewing |
| Collections colleague | Invoice view, payment view and the appropriate receivables reports |
Separating preparation and review can be good working practice, but invoice posting does not have the Purchasing submitter-versus-approver rule. Do not assume the system requires two users to post a customer invoice.
Business units and lookups
The invoice inherits its unit and customer from the sales order. Choose the right order; there is no customer/business-unit override on the invoice creation form.
The register shows invoices within permitted units. No allowed units can produce an empty result. Customer, warehouse and business-unit selector loading also depends on access to those source modules. A lookup failure is not the same as no invoices.
Example: Farah can view invoices for the Main Shop but not another unit. Searching all statuses does not grant access to the other unit. Ask the administrator to check the actual unit grant.
Missing controls
- Check your active tenant and sign-in session.
- Ask the administrator to check Invoicing and the exact permission above.
- Check the document's unit and current status.
- Check related Sales/Payment/Accounting access for links leaving Invoicing.
- Reload or sign in again after access changes.
The page Invoicing unavailable offers Refresh access and Dashboard. Credit-note write restrictions are different: those actions stay unavailable even when permissions are present.