You are here:
Salesforce Billing Permission Requirements
To support admin and user processes for Salesforce Billing, customize profile permissions. Each profile permission contains read, create, edit, or delete access to different objects. (Salesforce Billing Managed Package)
Required Editions
Important Where possible, we changed noninclusive terms to align with our
company value of Equality. We maintained certain terms to avoid any effect on
customer implementations.
| Available in: All Salesforce Billing Editions |
Salesforce Billing comes with a permission set that grants permissions for the package’s custom objects. However, some Billing actions involve or are related to standard objects. As a managed package, Salesforce Billing can’t give permissions for standard objects, so you must provide those permissions to users manually.
- Some Salesforce Billing objects, such as invoices and payments, have a master-detail relationship to the Account object. When you assign permissions for objects with a master-detail Account relationship, include access to the Account object as well.
- The Order and Order Product objects are standard objects with standard fields, Salesforce CPQ fields, and Salesforce Billing fields. When you assign permissions for objects related to orders and order products, include access to the Order or Order Product as needed.
Note In Salesforce Billing, you can adjust picklist value labels, but adjusting picklist value
API names isn’t supported. While it’s possible to adjust picklist value API names in Salesforce,
doing so causes any instance of the picklist to malfunction.
Invoice Actions
| Action | Read | Create | Edit | Delete |
|---|---|---|---|---|
| Create an invoice using Bill Now |
|
|
|
None |
| Run an invoice scheduler |
|
|
|
None |
| Post an invoice |
|
|
|
None |
| Cancel an invoice using the Cancel & Rebill button |
|
|
|
None |
| Apply taxes through a tax integration such as Avalara |
|
|
None | None |
| Apply standard tax |
|
|
None | None |
Payment Actions
| Action | Read | Create | Edit | Delete |
|---|---|---|---|---|
| Allocate a Payment |
|
|
|
None |
| Allocate a Credit Note |
|
|
|
None |
| Allocate a Debit Note |
|
|
|
None |
| Create a credit note |
|
|
|
None |
| Post a credit note |
|
|
None | |
| Create a debit note |
|
|
|
None |
| Post a debit note |
|
|
None | |
| Create a payment |
|
|
|
None |
| Use the Payment Center |
|
|
|
None |
| Refund |
|
|
|
None |
Usage Actions
| Action | Read | Create | Edit | Delete |
|---|---|---|---|---|
| Create a usage record |
|
|
|
None |
| Upload usage to a usage summary |
|
|
|
None |
Customer Asset Lifecycle Management
| Action | Read | Create | Edit | Delete |
|---|---|---|---|---|
| View lifecycle-managed assets |
|
None | None | None |
In addition to the access in the table, give these permissions.
- Sales reps: Field-level security access to objects and fields that reps update as part of asset lifecycle management
- Developers using Customer Asset Lifecycle Management APIs: Access Customer Asset Lifecycle Management APIs and API Enabled permissions
Did this article solve your issue?
Let us know so we can improve!

