A wire in the repair queue is a payment someone promised to send today and cannot yet. This guide covers what repair means in a US wire room, how ISO 20022 changed the work, the footing under UCC Article 4A and OFAC's reporting rules, and which steps an AI employee can run while people keep the decisions. Rules and dates were checked against primary sources in October 2026.
What is wire payment repair?
Why do wires fall out of straight-through processing?
Most repair items trace back to a short list of causes, and each one needs a different fix.
- Beneficiary data: a missing account number, a beneficiary name that does not match the account, or an address that is incomplete for the message format.
- Bank identification: an ABA routing number that no longer exists, a BIC that does not match the named bank, or an intermediary that is not valid for the currency.
- IBAN format: the wrong length or a failed check digit on a cross-border payment.
- Purpose and remittance data: a required purpose code or reference left blank.
- Compliance holds: a screening hit held for review. Screening is covered in OFAC sanctions screening automation and the sanctions screening glossary entry, so this guide covers only what surrounds the hold.
- Timing: a payment that missed its rail's cut-off and needs a value-date decision.
A wire transfer moves value bank to bank, so an error that reaches the beneficiary's bank is much harder to unwind than one caught in your own queue. Repair is a control before release.
What changed with ISO 20022 on Fedwire, CHIPS and cross-border wires?
The Federal Reserve's Fedwire Funds Service implemented ISO 20022 on July 14, 2025, according to the Fed's ISO 20022 format FAQ. The Clearing House reported that CHIPS migrated to the ISO 20022 message format on the April 8, 2024 banking day, in its April 10, 2024 announcement. The same Fed FAQ describes the postal address rules as aligned with the CBPR+ cross-border guidelines, which add a "hybrid end-state" address option in November 2025.
Two details from that FAQ matter for a repair queue this quarter.
- Structured addresses: as of November 16, 2026, the Fedwire Funds Service will require the hybrid postal address format for all parties and agents, and a payment can no longer carry only unstructured address lines. That format requires at least a country code and town name and allows up to two free-form lines of 70 characters each. Wires that carry only free-form address lines are likely to land in repair once the rule applies.
- Investigations: the Fed names the Investigation Request (camt.110) and Investigation Response (camt.111) messages as the way to handle exceptions and investigations on Fedwire wires for use cases that the other messages do not cover.
Structured data changes repair work in a plain way. Free-text beneficiary lines had to be read and retyped. ISO 20022 gives each party, address and reference its own element, so a repair item becomes "the creditor town name is missing" instead of "the beneficiary line looks odd." That precision suits an automated first pass.
What does UCC Article 4A say about erroneous and unauthorized wires?
Funds transfers between banks and their customers are governed largely by UCC Article 4A, as enacted by each state. The sections below, from the uniform text on Cornell's Legal Information Institute site, bear on repair. Your state's version and your funds transfer agreements control, so have counsel confirm the specifics.
- Security procedures: under Section 4A-202, an order verified under an agreed security procedure is effective as the customer's order, whether or not authorized, if the procedure is commercially reasonable and the bank proves good-faith compliance.
- Unauthorized orders: under Section 4A-204, a bank that accepts an order that is not effective as the customer's order must refund the payment with interest. The customer can lose the interest by failing to notify the bank within a reasonable time, not exceeding 90 days after notification of the debit.
- Erroneous orders: Section 4A-205 addresses orders that name the wrong beneficiary, overstate the amount or duplicate an earlier order, where the sender followed an agreed error-detection security procedure and the bank did not.
- Name and number mismatch: under Section 4A-207, a beneficiary's bank that does not know a name and account number refer to different persons may rely on the number. If it knows they differ, the rules change, which is one reason a mismatch is worth catching before release.
- Cancellation and amendment: Section 4A-211 says that after a payment order is accepted, cancellation or amendment is not effective unless the receiving bank agrees or a funds-transfer system rule allows it.
For a wire room, the repair record is evidence: what the original said, what changed, and who approved it.
What must a bank report when a repaired wire hits a sanctions block or reject?
When a wire is blocked or rejected under OFAC regulations, a reporting clock starts. Under 31 CFR 501.603, reports of blocked property are due within 10 business days from the date the property becomes blocked. Under 31 CFR 501.604, reports of rejected transactions are due within 10 business days of the rejected transaction, and the section expressly includes wire transfers in its definition of a transaction.
The details these reports require, such as parties, banks and reference numbers, are the fields repair touches. Disposition stays with the sanctions team. The AI employee's job is to have the facts assembled before day nine.
How are recalls and returns handled differently from repairs?
A repair fixes a payment before it leaves. A recall or return deals with one that has already been sent or received. Under Section 4A-211, a cancellation after acceptance depends on the receiving bank's agreement or a system rule, so a recall request is a request, not a command. On Fedwire, the investigation messages named above are the structured channel for it. Each recall still needs tracking to an outcome. For the ACH equivalent of this work, see our guide to ACH returns and NOC handling automation.
What does an AI employee do in a wire repair queue, and what stays with people?
An AI employee can take the repetitive investigative steps so each repair item reaches a person already prepared.
- Classify the exception by reading the rejection reason and the message elements, and sort it into one of the types in the table below.
- Validate and enrich the beneficiary data against internal records, prior successful payments to the same beneficiary and bank directories, and flag where sources disagree.
- Draft the repaired message, with each changed element listed beside its original value.
- Route the draft to a maker-checker for release. The separation between preparer and approver is the control described in segregation of duties and in our piece on four-eyes approval for AI agents in payments.
- Chase missing information from the originating customer or the correspondent bank, and track the reply.
- Document every change and the reason for it in the case record.
People keep release approval, sanctions dispositions and any customer-facing conversation where fraud is suspected. The AI employee prepares the file and does not decide those. The broader screening trade-off between speed and risk is covered in payment screening and compliance speed.
Exception type | What the AI employee does | Who approves |
|---|---|---|
Missing or invalid beneficiary data | Checks internal records and payment history, drafts the corrected element, requests the missing item from the customer | Maker-checker approves release |
Bad routing number or BIC | Validates against bank directories, proposes the correct identifier, notes the source | Maker-checker approves release |
IBAN format error | Runs the format and check-digit tests, returns the failing element to the originator | Maker-checker approves release |
Name and account mismatch | Compares the name to the account on file, flags the discrepancy, stops the payment | Wire room lead, with fraud review if suspicious |
Missing purpose or remittance data | Drafts the request to the customer, fills structured fields from the supplied reply | Maker-checker approves release |
Structured address missing | Splits the free-text address into structured elements, shows the original and the draft | Maker-checker approves release |
Sanctions hit held for review | Assembles transaction facts and prior history for the reviewer, with no disposition | Sanctions officer |
Blocked or rejected transaction | Prepares the data for the OFAC report, tracks the 10-business-day deadline | Sanctions officer files |
Cut-off miss | Identifies affected items, drafts the value-date change or customer notice | Wire room lead |
Recall or return | Tracks the request to an outcome and records the counterparty response | Wire room lead |
How a Zamp AI employee works a wire repair queue
A Zamp AI employee runs from an Agent Operating Procedure (AOP), a plain-language brief written by the process owner. For a wire repair role, we would have the wire room lead write into it the required elements per message type, the sources of truth and which one wins when two disagree, the approval limits, and the escalation paths. The same document records what the agent's own identity may not do. Each Zamp agent has its own identity with least-privilege access, so a repair agent can be given the ability to draft a corrected message but not to release it, and not to contact a customer about suspected fraud.
When a case falls outside that scope, such as a sanctions hit, a missing source record or a pattern the AOP has not seen, the agent sets Needs Attention and routes it to a person with the context already assembled. Before a case closes, the PEV loop has a validate step that checks the agent's own output, for example that every changed element is listed with its original value and that the draft meets the message rules. The reasoning is written into the team's own case system. In a biopharma procurement deployment, the agent wrote its reasoning for each decision directly into SAP Ariba, so reviewers could read the logic rather than re-check every detail.
When a reviewer corrects the agent, the correction becomes an AOP change. The change is made on a branch, tested against evals including a golden set of behavior the agent already has to get right, reviewed, and merged, with no engineering ticket. A high manual-review rate at launch is the safety mechanism. In that same biopharma deployment, 64% of requests went to manual review in week one; as reviewed corrections built up, the decision rate rose from 36% to 85% and manual review fell to 15%. The full account is in the procurement case study.
For payment data that must stay inside the bank's own environment, Zamp supports BYOC deployment on AWS, Azure or GCP, and on-premises deployment inside the customer's data center.
How should a wire room start?
Pick one exception type with a clear fix and a clear approver, such as missing structured address elements ahead of the November 16, 2026 Fedwire change. Run the AI employee in draft mode with every item going to a maker-checker. Track how often the reviewer changes the draft and why, and widen scope only as those corrections fall. For the wider picture, see our AI employees for banking and financial services guide.
