November 2026 Release Frequently Asked Questions
Postal Address
- How does the hybrid address format work?
The hybrid postal address format will apply to all parties/agents across all ISO® 20022 messages.
- The Postal Address component can only be used when the Name element is used.
- If Postal Address is used, then at a minimum, the structured elements Town Name and Country are always required.
- Additional postal address information (e.g., Street Name, Building Number, Post Code) should be provided using the structured elements to the extent possible.
- If needed, two occurrences of a free-formatted Address Line element (up to 70 characters each) may be used. However, these should never be used as standalone elements; rather, they are supplemental to the minimum requirement — the structured Town Name and Country elements.
- Information present in structured elements should never be repeated in the free-formatted Address Line elements.
- With the November 2026 release, is the creditor's postal address required in a customer credit transfer (pacs.008) or drawdown request (pain.013) message?
There is no change with the November 2026 release. While the Fedwire® Funds Service's message format specifications do not require the creditor's postal address in a pacs.008 or pain.013 message, you should consult your compliance and legal departments on what information (e.g., creditor's postal address) you may need to include in messages to satisfy your compliance obligations. A Fedwire sender should also check with the Fedwire receiver and any other bank that may process the transfer to understand additional requirements that they may have to ensure straight-through processing (e.g., creditor's postal address in addition to the creditor's name).
- We are already using the fully structured postal address. Can you confirm there is no impact to us?
If you are already using the fully structured postal address format for your originations, no additional changes are needed. Customers currently using the fully unstructured address format must be ready to use the fully structured or hybrid postal address format.
- How do we handle a return payment on or after Nov. 16, 2026, if the original payment includes the unstructured postal address format?
This specific use case is addressed in Payments Market Practice Group's “Industry guidance on the introduction of the hybrid postal address” document on Payment Market Practice Group's webpage (Off-site).
- Can we start using the hybrid address format for the debtor and creditor before Nov. 16, 2026?
No. The hybrid address format will be available as of Nov. 16, 2026, for the debtor and creditor.
- Can we use “not provided” in the Town Name field after the November 2026 release?
Although the Fedwire Funds Service does not validate the contents of the Town Name field, we strongly recommend entering the correct city or town name to facilitate straight-through processing and prevent transaction repairs or rejections.
- Which address fields are truly required and which are optional?
When postal address information is provided for a party or agent, you must include at minimum the Town Name and Country in structured fields.
- How do we confirm that third-party providers are prepared and ready for the postal address changes?
If you rely on third-party providers for your wire operations, you should work with them immediately to ensure readiness for the November 2026 release. Your institution is responsible for ensuring your technology partners and service providers meet the necessary requirements.
Investigation Messages
- If we receive a camt.110 message prior to Nov. 16, 2026, what code do we use for the camt.111 message Underlying Instrument field as this is a new required field?
If the camt.110 contains an IMAD of the original transaction, you can include URGP (Wire) or XBCT (cross border payment) in the Underlying Instrument field in the camt.111 message.
- If we receive a camt.110 message prior to Nov. 16, 2026, without a Requestor Investigation Identification because this field is optional, how do we generate the camt.111 message when either Requestor Investigation Identification or an EIR is required?
Post-Nov. 16, 2026, a camt.111 message requires either Requestor Investigation Identification or an EIR. If you do not have this information, you may need to ask the sender to resend a camt.110 message using the November 2026 version.
DIT2 Peer-to-Peer Testing and Saturday Production Testing
- For peer-to-peer testing, will FRFS provide test scenarios that we should follow?
You can download the testing scenarios document from the MyStandards® platform under the Fedwire Funds Service 2026 Release (PLANNED) page or contact our Wholesale Testing Services to obtain a copy when you register for the peer-to-peer testing.
- How do we register for peer-to-peer testing?
Registration is available at the Fedwire Funds Service Release DIT2 Peer-to-Peer Test Schedule page. For questions, please contact our Wholesale Testing Services.
- How do we register for Saturday production testing? And is this required?
Two Saturdays will be available for testing in the production environment prior to the November 2026 release: Sept. 19 and Oct. 31. While not required, we recommend that you take advantage of this testing opportunity to coordinate peer testing with counterparties leading up to the implementation weekend (Nov. 14-15). If you plan to participate in production testing, you must register 10 business days in advance of the designated Saturday you plan to test. You can register for this testing by completing the Production Application Test Request Form.
FedLine Advantage® Templates
- Which production templates will be deleted with the November 2026 release?
With the introduction of the response message buttons, the following templates will be deleted:
- Drawdown response (pain.014)
- Return request response (camt.029)
- Investigation response (camt.111)
Note: Investigation request (camt.110) templates will also be deleted due to low usage and significant format changes that prevent conversion to the newer version.
- Which templates will continue to be supported after the November 2026 release?
Following the Nov. 16 release, you will still be able to create and save the following templates:
- Customer credit transfer (pacs.008)
- Financial institution credit transfer (pacs.009)
- Payment return (pacs.004)
- U.S. Treasury tax payment (pacs.008)
- Drawdown request (pain.013)
- Return request (camt.056)
- Which production templates will FRFS copy over for the November 2026 release?
If you have any of the following templates saved in production, we will convert them to the November 2026 version:
- Customer credit transfer (pacs.008)
- Financial institution credit transfer (pacs.009)
- Payment return (pacs.004)
- U.S. Treasury tax payment (pacs.008)
- Drawdown request (pain.013)
- Return request (camt.056)
Go-Live and Contingency Planning
- What happens if the Fedwire Funds Service encounters an issue with the November 2026 release after go-live?
Consistent with prior customer-facing initiatives, FRFS will not fall back to the previous version of the Fedwire Funds Service if issues arise after the deployment of the November 2026 changes to the production environment. Instead, we will follow a “fix in place” strategy, implementing software updates once a fix has been identified and fully tested.
- Will FRFS make a formal go/no go announcement for the November 2026 release?
The November 2026 release will be implemented on Nov. 16, 2026. There will be no formal go/no go announcement process for this release. Unlike the July 2025 ISO 20022 migration, this is a smaller upgrade with limited scale and impact to the Fedwire Funds Service. Additionally, this implementation date is coordinated with Swift® and CHIPS®, so any delay for the Fedwire Funds Service could cause interoperability issues.
Tools and System Functionality
- How will prior-day retrievals work for FedLine Direct® users?
Customers should keep copies of their messages leading up to the November 2026 implementation weekend. Prior-day retrievals will be supported as follows:
- On Monday, customers can only retrieve November 2026 version messages from the current day (Monday)
- On Tuesday, customers can retrieve November 2026 version messages from the current day (Tuesday) and only one prior business day (Monday)
- On Wednesday, customers can retrieve November 2026 version messages from the current day (Wednesday) and two prior business days (Monday and Tuesday)
- On Thursday, customers can retrieve November 2026 version messages from the current day (Thursday) and two prior business days (Tuesday and Wednesday)
- Will the FedTransaction Analyzer® tool change with the November 2026 release?
A minor change will be made to the FedTransaction Analyzer tool to handle
rare cases where postal addresses exceed 600 characters, by truncating the address and adding a '+' indicator at the end.