Field note

Wire investigations become structured workflows

A wire investigation is the moment confidence breaks - the payment has moved and the clock is running. The Fedwire Funds Service changes planned for November 2026 turn investigation messages into structured workflows and add a Create Payment Return feature. Treat it as a rail feature, not a back-office patch.

Feb 2, 2026 · Navin Agrawal · Strategy · 2 min read

Wire investigations become structured workflows

Visual brief

Visual brief

Wire investigations become structured workflows

As of February 2026

A wire investigation is the moment confidence breaks. The payment has already moved, the clock has started, and everyone wants a clean answer and a clean trail. The Fedwire Funds Service changes planned for November 2026 are aimed right at that moment.

From an architect’s view this is not a format update. It is a workflow redesign, and the systems that treat it that way will turn a scramble into a process.

What is planned

The Federal Reserve says the November 16, 2026 Fedwire Funds Service release will enhance the camt.110 and camt.111 investigation messages to better structure common investigation use cases, and will add a Create Payment Return feature for past messages in FedPayments Manager. The changes open for DIT2 testing in May 2026, with the investigation messages specifically available from June 18, 2026. That gives teams a real window to build against before the live date.

Why it is a workflow, not a format

Structured investigation messages only pay off if the system around them is structured too. A better camt.110 does nothing for you if the case it belongs to lives in an inbox and a spreadsheet. The release is an invitation to make investigations a first-class lane rather than an exception everyone improvises through.

Planned release

Nov 16 2026

the Fedwire Funds Service release enhancing investigation handling (FRFS).

Messages

camt.110/111

investigation request and response messages restructured for common investigation use cases.

New feature

Create Return

a Create Payment Return feature for past messages arrives in FedPayments Manager.

Wire investigations become structured workflows (as of February 2026): the Fedwire Funds Service plans a November 16, 2026 release that enhances the camt.110 and camt.111 investigation messages to better structure common investigation use cases; it adds a Create Payment Return feature for past messages in FedPayments Manager; the changes open for DIT2 testing in May 2026, with the investigation messages available from June 18, 2026; and the design answer is to build investigations as a first-class lane with a single case record, defined decision states, audit-ready evidence capture, and a measurable ops view.
Structured messages are the prompt. A structured case record, owner, and audit trail are what actually make investigations fast.
When investigations get structured, your control plane has to be structured too. Treat this as a rail feature, not a back-office patch.

Was this useful?

Choose once.

Filed under

Strategy
Share
Back to Field Notes

Related Posts

View All Posts »
Real-time payments break your treasury org chart before they break your tech

Real-time payments break your treasury org chart before they break your tech

Your real-time rails settle in fifteen seconds. Your treasury org chart was built around an end-of-day cutoff. The gap between them is where the next reconciliation loss lives, and it shows up in three roles - cash positioning, exception ops, and intraday risk - long before it shows up in the tech stack.

Multi-rail is baseline now. The operational tax is the work

Multi-rail is baseline now. The operational tax is the work

The multi-rail debate is over - most US banks enabling instant payments now run both RTP and FedNow. The cost moved from the strategy deck to the operations floor, where exception handling becomes a decision tree, reconciliation becomes real-time position-keeping across two liquidity models, and routing is a per-transaction decision in milliseconds.

The operating model kills payment modernization, not the tech

The operating model kills payment modernization, not the tech

A bank buys a modern payment platform and keeps the 2019 team structure, the same escalation matrix, the same three-person on-call rotation. The platform ships daily. The governance model says 90 days. Most modernization failures are operating-model failures, and the org chart defeats the architecture every time.

Design open banking for the rule that keeps moving

Design open banking for the rule that keeps moving

The CFPB finalized US open banking under Section 1033 in October 2024, a federal court enjoined enforcement a year later, and the rule is now back in reconsideration. The data layer that survives that whiplash is the deliverable, not the API. Build for reversals, not launch day.