Integration user access to Financial Account standard objects
Key Takeaway
An API-only integration user can load data into Financial Account and its related standard objects without extra Agentforce Financial Services licenses. You update its permission set license to grant the object permissions. The user needs access to the related objects that store account holders, balances, and addresses, not just to Financial Account.
An integration user is a dedicated Salesforce user that an external system, such as a core banking system, uses to send data into Salesforce through the API. When an org uses the Financial Account and related standard objects, this user can load financial account data without extra Agentforce Financial Services licenses. You give it an API-only profile and grant the object permissions it needs through its permission set license. The standard objects spread one account's data across several related objects, so the integration user needs access to each object it loads.
Financial Account standard objects
Financial Account and its related standard objects model financial accounts without the Agentforce Financial Services managed package. Financial Account Party and Financial Account Transaction are two examples of the related objects. To use them, turn on the "Financial Account Management Standard Objects" setting. The setting is available in Professional, Enterprise, and Unlimited Editions in Lightning Experience.
If the Agentforce Financial Services managed package is also installed while the setting is on, both sets of objects are visible in the org. Use either the managed package objects or the standard objects consistently, and don't mix them. When you map integration fields, use the API name mapping between the two models so that each field points at the right object.