Managed package versus standard Financial Account objects
Key Takeaway
In the standard data model, owners, balances and addresses move off the Financial Account record into related objects. Ownership comes from Financial Account Party records, each with a Role such as Owner or Borrower, instead of primary owner and joint owner lookup fields.
Agentforce Financial Services can model financial accounts in two ways. One uses custom objects from its managed package. The other uses standard objects (Financial Account and related objects) that work without installing the managed package. When you configure objects and fields for a project, you need to know how the two models differ, how their objects map to each other, and what the standard objects handle differently, such as record types. An org should commit to only one of the two models.
The two data models
The managed package models financial accounts with its own custom objects. The standard data model uses Financial Account and related standard objects instead, and you don't need to install the Agentforce Financial Services managed package to use them.
The "Financial Account Management Standard Objects" setting turns on Financial Account and the related standard objects. The setting is available in Lightning Experience in Professional, Enterprise, and Unlimited Editions.
The standard set includes objects such as Financial Account, Financial Account Party, Financial Account Transaction, Financial Account Balance and Financial Account Address. The standard objects give greater control and flexibility over the data model and make integration easier.
The two models also store details differently. The managed package keeps details such as owners, balances and addresses as fields on one Financial Account record. The standard data model moves those details into separate related objects.