What this domain asks
The daily control process for knowing which cash, account, currency, legal entity, bank, value date, restriction, and concentration state can support an accountable liquidity decision.
The domain should retain its own evidence, decision owner, materiality criteria, exception path, and consequence even when it shares organization identity, workflow, or technology with adjacent domains. Aggregation can support oversight; it should not erase the evidence behind different risks or operating outcomes.
Buyer questions
- Which account and balance types are included?
- What source and timestamp support each position?
- How are pending, restricted, pooled, and trapped balances represented?
- Which entity owns and can use the cash?
- How are missing or late statements resolved?
Mapped workflows
Cash Positioning And Balance Visibility
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for cash positioning and balance visibility within this domain.
Bank Connectivity And Statement Ingestion
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for bank connectivity and statement ingestion within this domain.
Bank-Account Management And Signatory Governance
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for bank-account management and signatory governance within this domain.
Cash And Bank Reconciliation
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for cash and bank reconciliation within this domain.
Cash Pooling Concentration And Sweeping
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for cash pooling concentration and sweeping within this domain.
Treasury Master-Data Normalization And Lineage
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for treasury master-data normalization and lineage within this domain.
Audit Trail Control Evidence And Record Retention
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for audit trail control evidence and record retention within this domain.
Authority context
ISO 20022
ISO 20022 provides a common methodology, business model, and message repository for financial communications.
Swift CBPR+
Swift's CBPR+ programme applies ISO 20022 messages and market-practice rules to cross-border payments and cash reporting.
Relevant operating models
- Enterprise Treasury Management And Risk Platform
- ERP-Native Treasury And Cash-Management Suite
- Bank Connectivity Payment And Account-Control Platform
- Cash Visibility Forecasting And Liquidity-Planning Platform
Evidence boundary
Treasury Operations Review is not a bank, broker, dealer, payment processor, investment adviser, accounting firm, law firm, tax adviser, sanctions authority, regulator, auditor, cybersecurity assessor, or software provider. Its records support research and operational review; they do not establish legal or regulatory compliance, accounting treatment, tax outcome, sanctions permissibility, payment authorization, fair value, investment suitability, hedge effectiveness, audit sufficiency, security, liquidity, or fitness of any system for a particular organization. A provider's documented capability can identify a research candidate but cannot establish buyer-specific adequacy for this domain.