Define the operating boundary
A useful definition names the triggering event, required inputs, governing source, accountable owner, decision or action, exception path, evidence retained, and downstream handoff. Buyers should adapt those elements to their own population, jurisdictions, policies, systems, and control model before writing requirements.
The most important distinction is between a label and an operational capability. A provider may document audit trail control evidence and record retention while depending on customer-supplied policy, licensed content, third-party data, integration partners, manual review, or services. The demonstration should expose those dependencies rather than hiding them behind a completed interface.
What a demonstration should prove
- Begin with representative source records and a named policy, standard, or controlled rule.
- Show the normal path, an ambiguous case, missing data, an exception, an override, and a material source change.
- Identify who can change rules, who can approve or reject, and how accountability is preserved.
- Trace every output back to inputs, versions, timestamps, user actions, and governing evidence.
- Export the resulting record and reconcile it with downstream systems and retained obligations.
Authority and operating context
ISO 20022
ISO 20022 provides a common methodology, business model, and message repository for financial communications. Treasury systems must preserve message version, market practice, field mapping, validation, status, and exception handling rather than treating an ISO label as interoperability proof.
Swift CBPR+
Swift's CBPR+ programme applies ISO 20022 messages and market-practice rules to cross-border payments and cash reporting. Corporate treasury teams need to distinguish bank readiness, message generation, truncation, enrichment, screening, acknowledgement, rejection, and reporting across each payment chain.
Fedwire Funds ISO 20022
The Federal Reserve migrated the Fedwire Funds Service to ISO 20022 messages and maintains implementation resources. Treasury buyers need proof that ERP, TMS, bank, middleware, screening, approval, reconciliation, and reporting paths preserve the required data and statuses.
Nacha Operating Rules
Nacha maintains operating rules for ACH entries, participants, warranties, authorization, returns, risk, and related processes. Treasury systems supporting ACH must preserve authorization, role, entry class, timing, account validation, monitoring, return, and evidence requirements by use case.
EU Instant Payments Regulation
The regulation introduces requirements around sending and receiving instant euro credit transfers, charges, and verification of payee. Corporate payment processes need a controlled record of service availability, beneficiary verification, sanctions checks, limits, approvals, status, and exception handling by entity and bank.
DORA
DORA establishes requirements for ICT risk management, incident reporting, resilience testing, third-party risk, and oversight in the financial sector. Treasury and payment services supporting regulated financial entities may enter ICT inventories, continuity plans, testing, incident, vendor, and contractual evidence chains.
FCA operational resilience
The FCA requires in-scope firms to identify important business services, set impact tolerances, map dependencies, test, and remediate vulnerabilities. Treasury and payment operations should map systems, banks, people, files, approvals, recovery paths, and service impacts rather than relying on platform uptime alone.
COSO Internal Control
COSO organizes internal control around environment, risk assessment, control activities, information and communication, and monitoring. Treasury evaluations should connect access, approval, segregation, limits, confirmations, reconciliation, review, exceptions, evidence, and management oversight.
ISO 31000:2018
ISO 31000 provides principles, a framework, and a process for managing risk. Treasury technology can support risk identification, measurement, treatment, monitoring, communication, and records, while risk appetite and accountable decisions remain organizational.
ISO 22301:2019
ISO 22301 specifies requirements for a business-continuity management system. Payment and liquidity operations need identified critical activities, dependencies, recovery objectives, alternate processes, exercises, evidence, and improvement beyond system availability.
ISO/IEC 27001
ISO/IEC 27001 specifies requirements for an information-security management system. Treasury buyers should inspect certification scope, legal entity, services, locations, exclusions, statement of applicability, shared responsibility, and current certificate evidence.
OFAC Framework
OFAC describes management commitment, risk assessment, internal controls, testing and auditing, and training as essential components. Treasury payment processes should preserve screening scope, lists, data, timing, matching, escalation, holds, releases, reporting, and management oversight.
IFRS 9
IFRS 9 addresses classification and measurement, impairment, and hedge accounting for financial instruments. Treasury systems may support instrument records, valuations, designations, effectiveness, journals, and disclosures, while accounting policy and judgments remain accountable decisions.
ASC 815
ASC 815 contains U.S. GAAP requirements for derivatives and hedge accounting. Treasury systems supporting U.S. GAAP must preserve instrument terms, designation, risk, method, assessment, measurement, journals, and disclosure evidence.
SEC money-market fund reforms
The SEC adopted reforms concerning liquidity fees, redemption gates, liquidity requirements, reporting, and related money-market fund controls. Corporate cash-investment platforms should preserve fund identity, eligibility, liquidity terms, settlement, policy limits, concentration, exposure, and disclosure rather than presenting yield alone.
BCBS 239
BCBS 239 sets principles for governance, data architecture, accuracy, integrity, completeness, timeliness, adaptability, reporting, and supervisory review. Treasury and liquidity platforms serving regulated banks must distinguish source data, transformations, reconciliations, controls, lineage, aggregation, reports, and exceptions.
PCAOB AS 2201
AS 2201 establishes requirements for audits of internal control over financial reporting integrated with financial-statement audits. Treasury-system changes can affect significant accounts, risks, controls, evidence, interfaces, reports, and change management within an ICFR assessment.
2021 ISDA Definitions
The 2021 ISDA Definitions provide standardized terms for interest-rate derivatives documentation. Treasury platforms handling interest-rate derivatives should preserve product terms, calendars, rates, fallbacks, calculations, events, confirmations, valuations, and lifecycle changes.
PCI DSS
PCI DSS defines technical and operational requirements for protecting payment account data. Treasury teams should identify whether cardholder-data environments, payment channels, providers, and integrations enter scope and preserve evidence by responsibility.
Operating domains
Cash positioning and liquidity visibility
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.
Payments, fraud, and release control
The end-to-end control chain from authorized obligation and beneficiary data through payment creation, validation, approval, screening, transmission, bank acceptance, settlement, rejection, return, and reconciliation.
Bank connectivity and message integrity
The governed transport and transformation layer connecting ERP and treasury records to banks while preserving identity, format, version, data, signature, status, correction, and evidence.
Bank-account, signatory, and mandate governance
The controlled record of bank accounts, legal owners, purposes, services, signatories, authorities, mandates, fees, documentation, reviews, changes, and closures.
Liquidity, funding, debt, and investment
The decision system for meeting obligations and deploying surplus cash through facilities, debt, deposits, money-market instruments, investments, and internal liquidity under policy and risk constraints.
Financial risk and hedging
The governed process for identifying FX, interest-rate, commodity, credit, and liquidity exposures; defining risk appetite; selecting treatment; executing; valuing; monitoring; and preserving accountable evidence.
Treasury accounting, reconciliation, and close
The evidence chain connecting bank events, treasury deals, valuations, accruals, settlements, classifications, journals, reconciliations, approvals, disclosures, and general-ledger close.
Intercompany liquidity and in-house banking
The operating structure for centralizing cash, payments, receivables, funding, FX, netting, and internal account relationships across legal entities while preserving legal, tax, accounting, and control boundaries.
Treasury data models and decision lineage
The governance of accounts, entities, banks, counterparties, instruments, currencies, rates, transactions, forecasts, statuses, transformations, models, overrides, and retained decision evidence.
Treasury operational resilience and third-party dependency
The capacity to sustain or recover critical cash, payment, funding, risk, and reporting services across banks, networks, vendors, people, facilities, credentials, data, and alternate processes.
Evidence and comparison limits
Official provider documentation can establish product positioning. Provider confirmation can clarify package or availability. Independent observation requires a disclosed scenario, environment, date, inputs, and reproducible result. None of those sources alone establishes buyer-specific legal, clinical, regulatory, quality, or operational fitness.
Buyer questions
- What exact outcome and evidence should audit trail control evidence and record retention produce?
- Which source, version, and customer facts govern the workflow?
- Which decisions remain human and who is accountable for them?
- What is native, configured, integrated, service-delivered, or planned?
- How does a changed source affect open and historical records?
Recent changes
ISO 20022 readiness needs message-by-message proof — The event changes the maintained payment-rail, standards, regulatory, accounting, product, or market record. Treasury teams should update affected workflows while keeping public-source facts separate from buyer-specific applicability, configured product behavior, control operation, and financial outcomes.
Hedge-accounting modules cannot collapse policy, valuation, and evidence — The event changes the maintained payment-rail, standards, regulatory, accounting, product, or market record. Treasury teams should update affected workflows while keeping public-source facts separate from buyer-specific applicability, configured product behavior, control operation, and financial outcomes.
Trovata expands from cash intelligence to a TMS decision — The event changes the maintained payment-rail, standards, regulatory, accounting, product, or market record. Treasury teams should update affected workflows while keeping public-source facts separate from buyer-specific applicability, configured product behavior, control operation, and financial outcomes.
Specialist cash platforms converge on forecasting—not one method — The event changes the maintained payment-rail, standards, regulatory, accounting, product, or market record. Treasury teams should update affected workflows while keeping public-source facts separate from buyer-specific applicability, configured product behavior, control operation, and financial outcomes.
EU instant payments turn verification of payee into a treasury control handoff — The event changes the maintained payment-rail, standards, regulatory, accounting, product, or market record. Treasury teams should update affected workflows while keeping public-source facts separate from buyer-specific applicability, configured product behavior, control operation, and financial outcomes.
Fedwire's ISO 20022 migration rewrites the U.S. high-value payment record — The event changes the maintained payment-rail, standards, regulatory, accounting, product, or market record. Treasury teams should update affected workflows while keeping public-source facts separate from buyer-specific applicability, configured product behavior, control operation, and financial outcomes.
DORA makes treasury-vendor resilience an operating record — The event changes the maintained payment-rail, standards, regulatory, accounting, product, or market record. Treasury teams should update affected workflows while keeping public-source facts separate from buyer-specific applicability, configured product behavior, control operation, and financial outcomes.