Abstract: Reconciliation and subscription-model permissions of data stored across independent ledger instances of a database. A system includes a resource manager coupled to a plurality of client accounts. The system includes an execution platform and a shared permissioned ledger comprising independent processing and storage nodes for executing data operations for the plurality of client accounts. The resource manager defines a settlement group comprising one or more client accounts and authenticates an observer node associated with the settlement group. The resource manager assigns ingested data an encryption level on a key hierarchy based on content of the ingested data.

Abstract: Reconciliation and subscription-model permissions of data stored across independent ledger instances of a database. A system includes a resource manager coupled to a plurality of client accounts. The system includes an execution platform and a shared permissioned ledger comprising independent processing and storage nodes for executing data operations for the plurality of client accounts. The resource manager defines a settlement group comprising one or more client accounts and authenticates an observer node associated with the settlement group. The resource manager assigns ingested data an encryption level on a key hierarchy based on content of the ingested data.

Abstract: Partitioning data across shared permissioned database storage for multiparty data reconciliation. A system includes an execution platform comprising a plurality of processing nodes and a shared permissioned ledger comprising a plurality of ledger instances, wherein each of the plurality of ledger instances is assigned to one client of a plurality of clients, and wherein storage resources on the shared permissioned ledger are independently scalable from the plurality of processing nodes on the execution platform. The system includes a resource manager in communication with each of the execution platform and the shared permissioned ledger, wherein the resource manager comprises a data ingestion engine.

Abstract: Reconciliation and subscription-model permissions of data stored across independent ledger instances of a database. A system includes a resource manager coupled to a plurality of client accounts. The system includes an execution platform and a shared permissioned ledger comprising independent processing and storage nodes for executing data operations for the plurality of client accounts. The resource manager defines a settlement group comprising one or more client accounts and authenticates an observer node associated with the settlement group. The resource manager assigns ingested data an encryption level on a key hierarchy based on content of the ingested data.

Abstract: Analysis of data streams consumed by high-throughput data ingestion and partitioned across permissioned database storage. A system includes a resource manager coupled to a plurality of client accounts. The system includes an execution platform and a shared permissioned ledger comprising independent processing and storage nodes for executing data operations for the plurality of client accounts. The system includes a data ingestion engine comprising a plurality of node-specific ingestors and node-specific normalizers for consuming and normalizing data stream even channels pushed by the plurality of client accounts.

Abstract: Example transaction netting systems and methods are described. In one implementation, a financial management system receives information associated with multiple trades and calculates overall obligations and exposures by assets and counterparties. The financial management system further identifies multiple thresholds associated with the multiple trades and selects trades for a particular netting cycle which align with the overall bilateral netted obligations and exposures between counterparties.

Abstract: Example risk and liquidity management systems and methods are described. In one implementation, a financial management system identifies data associated with a plurality of events in a financial market in substantially real time. The financial management system analyzes the data associated with the plurality of events and, based on the analysis, determines a liquidity demand, a liquidity profile, and a risk profile associated with a particular financial institution. The financial management system then communicates the financial institution's liquidity demand, liquidity profile, and risk profile to the financial institution.

Abstract: Example data ingestion systems and methods are described. In one implementation, a financial management system identifies multiple financial orders, where each financial order is executed with one or more trades. The financial management system receives real time data associated with the trades and aggregates the real time data. The financial management system also identifies settlement data related to the settlements in real time, associates the settlements with the related trades in real time, and reports the aggregated data and the settlement data in real time.

Abstract: Example financial management systems and methods are described. In one implementation, a financial management system receives a request to transfer assets from a first account at a first financial institution to a second account at a second financial institution. The financial management system initiates a debit of the first account by the transfer amount and initiates a credit of a first suspense account at the first financial institution by the transfer amount. The financial management system then initiates a settlement of the transferred assets between the first suspense account and a second suspense account at the second financial institution. Finally, the financial management system initiates a debit of the second suspense account by the transfer amount and initiates a credit of the second account by the transfer amount.

Abstract: Example multiparty reconciliation systems and methods are described. In one implementation, a financial management system receives a request to transfer assets between a first principal and a second principal. The financial management system receives metadata identifying at least one debit and at least one credit associated with the transfer of assets. The metadata is stored in a shared ledger that is accessible to the first principal and the second principal. State changes associated with the transfer of assets are identified and stored in the shared ledger. The financial management system also receives additional metadata identifying payments to each client of the first principal and the second principal. Additionally, the financial management system communicates reconciliation data to the first principal and the second principal.