Permission reference: Payments & refunds
Control who can create payments, view payment history, and process refunds.
Jul 11, 2026
Permission Reference: Payments & Refunds
This table lists all permissions that control access to payment and refund functionality in Usystems.
| Permission | What It Controls | Allowed Actions |
|---|---|---|
| payment.view | View payments | Users can see the payment list, view payment details, and review payment history for invoices and purchases. |
| payment.create | Create payments | Users can record customer payments (from invoices) and vendor payments (against bills). |
Refund & Return Permissions
While refunds are not in the explicit permission system, they are controlled by related permissions:
| Action | Required Permissions | Notes |
|---|---|---|
| Create a customer refund (from overpayment) | payment.view + invoice.view | User must be able to see the invoice and payment to issue a refund. |
| Process a return | invoice.view + invoice.update | Return documents are linked to the original invoice. |
Which roles typically need these?
- Cashiers → payment.create (for recording daily cash receipts)
- Accountants → payment.view, payment.create (for cash reconciliation and posting)
- Accounts receivable clerk → payment.view, payment.create (for customer collections)
- Accounts payable clerk → payment.view, payment.create (for paying vendors)
- Finance manager → all permissions (for oversight)
- Admin → all permissions (full control)
What happens without these permissions?
Without payment.create, users cannot record payments. Without payment.view, the payment history and records are hidden.
Was this helpful?