Multi-currency limitations in Agentforce Financial Services components
Key Takeaway
With multiple currencies enabled, Agentforce Financial Services packaged components follow the viewing user's currency, not the record's currency. If "Rollup By Lookup" is also on, an Account's total financial account value is accurate only when the user's currency and the account's currency both match the org default currency.
Agentforce Financial Services can run in an org with the multiple currencies setting turned on, but its packaged components and rollups have specific currency limitations. A consultant needs to know these limitations to set the right expectations for a multi-currency customer and to plan page layouts, user currency settings, and report filters. The currency limitations apply only when the multiple currencies setting is enabled in the org. Both person accounts and the individual object model are affected.
Components follow the user's currency
Agentforce Financial Services packaged components don't display record-specific currency settings. Instead, they display only user-specific currency settings, so a component follows the viewing user's currency, not the currency set on the record.
The Currency Iso Code field doesn't change currency symbols in packaged components either. Setting a record's Currency Iso Code to another currency won't switch the symbol those components show.
Lena's currency is EUR. Tom's currency is CAD. Both open the same client record, which has its Currency Iso Code set to GBP. The packaged components on the page display Lena's currency setting when Lena views the record and Tom's currency setting when Tom views it. Neither of them sees GBP in those components, because the components don't display the record's currency setting.
On the Financial Account Summary component, commas and currency symbols display correctly only when the user's locale in "Locale Settings" matches the user's currency. Locale and currency are two separate user settings, so both must line up.