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.
Editorial figure by Treasury Operations Review. Source context: 360T official platform record.
Begin with the governed exposure and objective
360T's official record supports an electronic FX execution and workflow role. The direct answer is that a trading venue can help a treasury transact after the organization has defined the decision; it cannot decide the organization's tolerance for currency risk. The useful pre-trade record names the legal entity, exposure source, currency pair, amount, certainty, timing, forecast or committed status, hedge objective, accounting intent, policy authority, limit consumption, and accountable approver.
Teams should distinguish economic exposure from an ERP forecast, invoice, purchase order, intercompany position, bank balance, financing obligation, or forecast aggregation. They should also preserve netting, natural hedges, existing trades, timing differences, probability adjustments, and data corrections. A precise execution against an incomplete or duplicated exposure can increase risk while every trade field appears valid.
Test the policy-to-execution handoff
The workflow should demonstrate how approved policy and limits become executable instructions: eligible entities and users, instruments, currencies, counterparties, venues, tenors, amounts, price controls, request-for-quote rules, approval levels, segregation of duties, and exception handling. A platform permission is evidence of technical ability, not necessarily evidence of corporate authority for the transaction.
A representative evaluation should include an ordinary spot or forward workflow plus a stale exposure, amended amount, exceeded limit, unavailable counterparty, off-market price, rejected quote, partial execution, canceled trade, manual trade, delegated user, emergency transaction, and changed settlement instruction. Reviewers should see which rules prevent, warn, escalate, approve, record, and later reconcile each event.
Reconcile execution through settlement and reporting
Execution is one stage in a longer chain. The record should join the approved exposure and hedge decision to quote evidence, trade confirmation, counterparty record, settlement instructions, cash forecast, payment controls, bank confirmation, accounting entry, valuation, collateral or lifecycle events where relevant, and management reporting. Trade status should not be inferred from a single system when downstream acceptance or cash movement can differ.
Treasury teams should test identifiers, timestamps, timezones, market data, duplicate prevention, interface retries, amendments, cancellations, confirmations, settlement failures, and historical retention. Performance measures should separate process speed and electronic coverage from price quality, policy adherence, operational risk, forecast quality, hedge effectiveness, counterparty exposure, and financial outcome.
Keep 360T's claims inside the source boundary
The registered 360T page establishes current provider positioning for electronic FX trading, workflow, data, automation, connectivity, and related market services. It does not establish a customer's risk appetite, exposure accuracy, hedge policy, authority, liquidity, execution quality, counterparty suitability, settlement, accounting, compliance, or financial outcome. Any benefit or market-quality statement requires its population, timing, method, and applicability to be reviewed separately.
Treasury Operations Review reviewed the registered source on August 14, 2026 and did not operate a customer environment, observe a live market, or assess a transaction. Buyers should verify current instruments, venues, counterparties, workflows, market data, permissions, limits, approvals, integrations, confirmations, exports, retention, resilience, and support with representative exposures and accountable treasury, risk, finance, accounting, legal, and security owners.
Enterprise buyer test
Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.
A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.
What we will watch next
Treasury Operations Review will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.