Shield Platform Encryption

Accounting supports Salesforce's Shield Platform Encryption on all current standard fields (except Billing Address, Opportunity Name, and Shipping Address), and also supports the encryption of files and attachments.

When encryption is enabled for a field, disabling the encryption later does not remove the querying restrictions on that field. This means any current or future packages installed in your org that use the field must continue to support encryption on that field. For example, when searching for records, users will be unable to filter by a field that is, or was, encrypted because the querying restrictions imposed by encryption don't allow filtering on encrypted fields.

Refer to the Salesforce Shield Platform Encryption Implementation Guide if you are considering enabling encryption in your org. Contact your Salesforce representative before making any decisions.


If you enable encryption, you may not be able to achieve the same volumes as before and may receive an “Apex CPU time limit exceeded” message.

If you only type a few letters into an account name field, sometimes the account may not be found. You must be as specific as possible when typing the account name.

When selecting vendor account names on the Payment Selection page, you must use Multi-select. It is not possible to search for vendor account names that contain a particular string, or to enter a From/To range.

When you use a Type 2c integration rule to automatically generate sales invoices, encrypted fields are not displayed in the list of fields available for use as selection criteria.

If you use Cash Entry Extension to manage cash entry line Items, some fields, such as Account Payment Method, are automatically populated, based on the Account Name, when you create a new cash entry line. If you have Platform Encryption enabled, these fields cannot be automatically populated and an error message displays. You can manually populate these fields to create your cash entry line.