Loading
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Considerations for Using Financial Account Management Standard Objects

          Considerations for Using Financial Account Management Standard Objects

          Keep these considerations in mind if you’re currently using objects from the Financial Services Cloud managed package, and plan to use Financial Account and related standard objects. Plan ahead to make the transition easier for your user teams, partners, and clients.

          Required Editions

          Available in: Lightning Experience
          Available in: Professional, Enterprise, and Unlimited Editions
          • Plan your metadata and data migration before you start using the standard Financial Account and its related objects. To understand the object and field mapping between the managed package and standard objects, see API name mapping between the managed package and standard objects.
          • Thoroughly review the documentation for the standard objects to understand the fields, picklists, and any other details.
          • Consider the effort and complexity involved in customizing the objects to suit your business needs.
          • When the Financial Account Management Standard Objects setting is turned on and you have the Financial Services Managed managed package installed, both standard object and objects from the managed package are visible in your org. It's important to consistently use either the Financial Services Cloud managed package objects or the standard objects, and avoid mixing both when setting up the financial account and its related features.
          • The Financial Account standard object doesn’t support record types. As an alternative, you can break up your financial account record details with Dynamic Forms. With Dynamic Forms, you can migrate the fields and sections from your page layout to individual components in Lightning App Builder. 
          • Prebuilt field validations aren’t shipped for the Financial Account and related standard objects. For example, the end date must be after the start date. Salesforce recommends you to add the field validations according to your business needs.
          • For the Financial Account standard object, field encryption is supported only for the Name and Financial Account Number fields.
          • When installing the CRM Analytics app, manually enable access to all fields. Even after assigning the FSC Analytics Integration permission set to the Analytics Integration User, some fields in standard objects remain restricted due to field-level security.
          • Starting in Spring ’25, the auto-generated prefix for the financial account party record name is changed from FAR to FAP. To ensure continued functionality and accuracy of the records, review and update any object records, custom queries, Apex class queries, and report filters that currently use the FAR prefix to the new FAP prefix.
           
          Loading
          Salesforce Help | Article