Introduction to Account Summary

Account Summary is a single, shared table that consolidates account and instrument-level data across Funds Transfer Pricing Cloud Service (FTPCS), Profitability Management Cloud Service (PFTCS), Process Automation Cloud Service (PACS), Asset Liability Management Cloud Service (ALMCS), and Cash Flow Edits Cloud Service (CFECS). FTP and PFT currently update the Instrument tables, so the Account Summary table is populated with output from both applications in a common structure. This avoids the need to maintain separate common and application-specific account summary tables, and avoids joining large result sets between them.

Account Summary provides the following key benefits:

• Common Account Summary for FTP, PFT, and other applications: Data can be extracted from Account Summary for FTP only, PFT only, both FTP and PFT, or all other applications.
• Avoids joins between a common Account Summary table and application-specific Account Summary tables, which reduces query complexity and improves performance for downstream reads and extractions.
• Dimension-based analysis: Analysis on dimensions can be performed directly on the Account Summary table using dimension IDs. Where additional descriptive attributes are required, you can perform selected joins to dimension tables as needed.
• Performance benefits: A single data push operation loads Account Summary, instead of separate pushes into multiple application-specific summary tables. The Account Summary table is populated based on the currently executed rules and their available outputs, regardless of how many times data is loaded.
• Automatic selection of output columns: The Account Summary population process automatically identifies the relevant output columns produced by FTP and PFT rules that have been executed, so the table reflects the currently available outputs without manual handling for each rule.
• Traceability: Each record in Account Summary retains a reference to its source Instrument table, so the origin of account and instrument-level data can be traced.
• Read availability during data push: Account Summary uses a staging and swap-based load approach instead of a repeated delete-and-insert pattern. This keeps the table readable while the population process is running, so reporting, analysis, and extraction are not blocked.
• Scheduler-based population: The Account Summary population process is available as a Scheduler task, so it can be triggered as part of a controlled post-execution workflow. For information about creating and running a Scheduler task, see Scheduler Services.

Each population of Account Summary includes a snapshot timestamp, which allows you to identify when the data was generated and loaded.

Note:

Asset Liability Management (ALM) and Cash Flow Edits (CFE) do not output to the Instrument tables, and are therefore not currently reflected in Account Summary.