Financial account child objects for transactions, holdings, balances and cards
Key Takeaway
In the standard financial account model, each transaction, balance, investment holding, and card is its own child record of Financial Account: Financial Account Transaction, Financial Account Balance, Securities Holding, and Issued Card.
A financial account in Agentforce Financial Services represents a client's financial instrument, such as an investment account, a bank account, or a credit card. The Financial Account record holds the basics. Related child objects hold the detail: transactions, balances, investment holdings, and issued cards. These objects come in two versions, standard objects and managed package objects. The two versions differ in object names and structure. To meet a business requirement, you need to know which object holds each detail and which version of the objects the org uses.
The Financial Account object
Financial Account is the anchor object that stores information about a client's financial instruments, such as investment accounts, bank accounts, and credit cards. The transaction, balance, holding, and card objects all relate back to Financial Account.
Financial Account is central to the product. Financial Account drives these features:
- Financial summary rollups
- Financial plans and goals
- The retail banking console
- AI-generated wealth summaries
- Branch Management features
Clients connect to a financial account through Financial Account Party, a junction object between Account and Financial Account. Financial Account Party also records the client's role on the account, such as owner, beneficiary, or trustee.