Salesforce Decode
Salesforcedecode
Back to questions
Data CloudAdvancedcalculated-insightsbankingtransactionsaggregation

Compute banking transaction aggregation insights for wealth segmentation

Real World Scenario

Wealth advisors need segments based on rolling deposit trends and investment inflows across checking, brokerage, and CD products. Raw transaction DLOs are too granular for marketers to query.

Expected Answer

• Build rolling window aggregations: 30/90-day inflow, outflow, net balance change per product category • Handle pending vs posted transactions with separate insight fields to avoid segment jitter • Exclude internal transfers between owned accounts to prevent false churn signals • Apply minimum transaction count thresholds before classifying trend direction • Refresh aggregations after nightly core banking batch completion window • Restrict segment fields visible to marketing vs advisor-facing operational segments • Validate aggregations against core banking reporting totals monthly

Follow-Up Questions & Answers

Click to expand — each follow-up includes a direct, interview-ready answer

Direct answer: Build rolling window aggregations: 30/90-day inflow, outflow, net balance change per product category Also consider: Handle pending vs posted transactions with separate insight fields to avoid segment jitter In practice: Exclude internal transfers between owned accounts to prevent false churn signals Optimize for scale and operational observability.

Architect Perspective

Banking insights must abstract transactions into campaign-safe derived attributes—never activate raw ledger detail to external platforms.