The operating record for cash, risk, and control.
Source-backed reporting and analysis connected to the companies, capabilities, authorities, and operating domains it affects.
ION describes Wallstreet Suite as using configurable alerts and an exception-based back office across integrated treasury activity. Automation is governable only when the team can prove which events enter the exception population, who owns them, how clocks and escalation work, and which downstream financial states remain unresolved.
Coupa documents standard and custom exports of original treasury files to sFTP, distinguishes bank files from account statements, and says some jobs select recent unexported files before marking them exported. That state still needs source identity, population reconciliation, secure delivery, target receipt, legal-entity assignment, retention, and downstream processing evidence.
Fennech presents a platform spanning cash visibility, payments, reconciliation, and liquidity operations. A match can explain why two records appear related, but settled and available cash still require bank evidence, account and entity identity, value date, ledger treatment, exceptions, approval, and a controlled cutoff.
Numerix describes pricing and valuation analytics across derivatives and risk workflows; treasury still needs to preserve instrument terms, model version, market-data snapshot, adjustments, purpose, and accountable review before using an output.
Cashfac documents virtual-account management that can represent pooled bank accounts through many virtual accounts and support cash, receivables, payment, and account workflows. A virtual balance becomes treasury evidence only when it reconciles to the legal bank account, bank statement, customer or entity subledger, transactions, value dates, restrictions, fees, interest, exceptions, and accountable close.
Ripple Treasury documents traditional and digital-asset visibility plus an enterprise wallet. A displayed balance still needs entity, ownership, custody, restriction, valuation, liquidity, and reconciliation evidence.
Nomentia presents transaction-based cash forecasting and projected liquidity views across entities, currencies, and dates. A forecast can surface a potential shortfall, but authorized treasury owners still have to validate the exposure and decide whether, when, how much, and through which instrument to fund.
360T presents electronic foreign-exchange trading, workflow, market data, automation, and integration services. An execution can evidence the terms agreed with a counterparty, but it does not define why the organization assumed or hedged the exposure, how much risk it accepts, or whether the trade fits policy.
SAP's Treasury and Risk Management documentation distinguishes front-office transaction creation from back-office settlement and records changes across the lifecycle. That separation is an operating control: a captured order or contract still needs counterparty confirmation, authorization, settlement processing, cash evidence, valuation, accounting, and exception review.
Coupa positions treasury, cash, payments, and spend workflows within a connected platform, and its current documentation exposes treasury cash-flow, account-balance, bank-file, and integration records. A procurement approval can authorize an obligation inside the enterprise; it does not by itself authorize a bank release, prove bank acceptance, establish settlement, or complete reconciliation.
PCI DSS supplies baseline technical and operational requirements for protecting payment account data. It does not apply to every treasury workflow or certify an entire treasury platform because one module supports card-related payments.
The business-continuity standard points buyers toward critical activities, dependencies, recovery objectives, alternate processes, exercises, evidence, and improvement. A hosted platform or disaster-recovery statement does not prove end-to-end treasury recovery.
ISO 31000:2018 remains the current published edition while a revision is under development. Its general principles, framework, and process can organize treasury risk decisions, but they do not decide an accounting designation or market outcome.
COSO's Internal Control—Integrated Framework treats control as a connected system serving operations, reporting, and compliance objectives. A payment approval, reconciliation rule, or automated journal can be one control activity without proving that the wider treasury control is designed or operating effectively.
