Managed-Account Transaction Architecture for Real-Time Asset Rebalancing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional computing architectures for managed-account transactions face challenges due to reliance on settlement-date data, shadow accounting, and lack of data schemas and quality checks, leading to reporting and reconciliation issues.
Innovation Solution
A computing system that receives investment allocation data from multiple managers, generates strategies, instantiates sleeve objects for asset allocation, and dynamically adjusts based on market valuations and client requests, enabling reallocation of assets and handling dividend payments while ensuring compliance with tax implications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional shadow accounting and settlement-date data are used, then existing computing architectures can process transactions, but reporting and reconciliation challenges arise
Solution Approach 1:
The patent segments the computing architecture into distinct modular components: account information manager, portfolio information manager, transaction manager, and pricing manager. Each component handles specific functions independently, eliminating the need for shadow accounting by distributing data management responsibilities across specialized modules that directly interact with the core banking system.
Solution Approach 2:
The patent extracts the accounting and reconciliation functions from the conventional shadow accounting approach and integrates them directly into the core banking system through dedicated managers. This extraction eliminates the parallel shadow accounting system entirely, with each manager pulling data directly from authoritative sources (account information manager from core banking system, portfolio information manager from portfolio management system) to ensure single-source truth.
2Productivity
If real-time market valuation adjustments are implemented, then asset allocation optimization improves, but data processing requirements increase
Solution Approach 1:
The patent implements preliminary action by having the pricing manager proactively retrieve current market prices for all portfolio assets and calculate mark-to-market valuations before allocation decisions are made. This advance pricing allows the transaction manager to optimize asset allocation in real-time without requiring intensive on-demand processing, as valuation data is prepared in advance and made readily available for decision-making.
Solution Approach 2:
The patent establishes continuous feedback loops where the transaction manager receives real-time pricing data from the pricing manager, compares current valuations against target allocations, and automatically executes rebalancing transactions when deviations exceed thresholds. This feedback mechanism enables efficient asset allocation optimization by continuously monitoring and adjusting portfolios based on current market conditions without requiring manual intervention or excessive processing power.
3Measurement precision
If data schemas and quality checks are integrated throughout the system, then data quality improves, but system complexity increases
Solution Approach 1:
The patent applies local quality by implementing data validation and quality checks at each specific manager level rather than requiring a centralized complex validation system. Each manager (account information manager, portfolio information manager, transaction manager, pricing manager) validates and ensures quality of the specific data it handles and processes. This distributed approach to data quality ensures high measurement precision for each data type while keeping individual manager complexities manageable.
Data Source
AI summary
An improved computing architecture for managed-account transactions is presented. In accordance with embodiments, responsive to receiving a request to purchase a number of units of an asset for an account of a client, a computing system may instantiate, in a client object associated with the client, objects, comprising variables for storing bases for the units and may instantiate, in an account object stored within the client object and associated with the account, objects representing the units. And for each of the units, responsive to receiving data indicating a price and time at which the unit was purchased, the computing system may store, an indication of the price and time and data associating the indication with one of the objects that represents the unit and may store data indicating the price at which the unit was purchased in one of the objects for storing bases for the units.