MENU
How are identification documents, other assets, liabilities, goals, and revenue modeled, in an existing Financial Services Cloud org using the individual account model?
In the Individual Account model, Agentforce Financial Services uses purpose-built custom objects to represent important aspects of a customer's financial profile, including identification information, assets and liabilities, financial goals, and revenue. These records are related to the customer's Account, which is the central customer entity in the Individual Account architecture. Salesforce's Financial Services data model states that custom objects are used to represent other assets, liabilities, goals, and revenue and that, in the Individual Account model, these objects relate to the Account object. This enables financial institutions to maintain structured, reportable financial data rather than storing those details in generic attachments or notes. This distinction is important because the Individual Account model differs from the Person Account model. In a Person Account deployment, the underlying Account and Contact architecture is presented as a unified individual record. In the Individual Account model, the financial-information objects remain explicitly associated with the Account representing the customer. Identification records similarly belong to the Financial Services structured data model rather than being treated merely as Salesforce Files or Attachments. Using dedicated objects allows organizations to manage document types, identifiers, financial values, goals, and revenue information with appropriate relationships, permissions, reporting, and automation. Therefore, the correct modeling approach is custom Financial Services objects related to the Account.