2.2.2 US Fedwire 2026 Changes

Hybrid address enforcement: Fully unstructured addresses are not allowed. Structured/hybrid addresses are enforced with a maximum of two Address Lines, using existing maintenance (PMDNWADD).

Outbound camt.110 input/view enhancements (PSDOIRID, PSDOIRVW, PSSOIRVW): Added new Fedwire-compliant fields, including Underlying Instrument Code (as an LOV), Request Originator Party/Agent details (postal, identification, and agent details), and Underlying Other Identification. This field has also been added to the summary search criteria and results.

camt.110 standalone investigation handling: Original Transaction Reference is now non-mandatory for Fedwire standalone requests. If an inbound camt.110 carries the Underlying Other node, the system treats it as a standalone request and skips matching to underlying payment, return, or drawdown messages.

Outbound camt.111 input/view enhancements (PSDOIRPI, PSDOIRPV): Added Response Originator Party/Agent structures; confirmation-tab account, proxy, and reference fields; charges and charges-agent details; tax details; and transaction-status originator details, with corresponding population in the view screens.

Inbound screen parity for both message types: The outbound fields added above are also exposed in inbound view screens (PSDIIRVW for camt.110 and PSDIIRPI for camt.111) so users can review the full received investigation content.

Message generation and schema control: Outbound camt.110 and camt.111 messages are generated against the Fedwire 2026 XSDs, validated via PSDGRXSP schema maintenance, and populated only with network-allowed fields along with user-entered additional fields.