TREASURY OPERATIONSREVIEW

The operating record for cash, risk, and control.

Coverage desk

Treasury exceptions

Source-backed reporting and analysis connected to the companies, capabilities, authorities, and operating domains it affects.

Wallstreet Suite exceptions need queue, owner, and aging proof

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.

A Coupa “exported” flag does not prove complete bank-file custody

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.

A Fennech reconciliation match is not settled cash

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.

Cashfac virtual balances need pooled-account reconciliation

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.

A Ripple Treasury wallet balance is not available cash

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.

A Nomentia cash forecast is not a funding instruction

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.

A 360T FX execution does not set treasury risk appetite

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 keeps treasury deal entry separate from settlement

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.

ISO 22301 makes treasury continuity more than uptime

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 frames risk governance—not hedge effectiveness

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.