Why wires are the reconciliation nobody can afford to get wrong
A wire is the one payment type where the money is gone the moment it is sent. Fedwire funds transfers are final and irrevocable, so an outgoing wire posted to the wrong account, released twice or sent for the wrong amount is not corrected with a return file the way an ACH debit is. It is corrected with a phone call, a recall request and sometimes a loss. That is why wire operations managers and controllers treat the daily wire reconciliation as a control and not as housekeeping.
The task is simple to describe and tedious to do. Every wire touches at least three records that must agree: the wire system or payment hub that released it, the posting on the core and the general ledger, and the settlement evidence on the Fed account or the correspondent statement. Most institutions compare them by eye in a spreadsheet, once a day, after the wire room has closed.
3 records
Final
Daily
$1,200
What each wire path leaves as evidence
US institutions send wires over a few different paths, and each one leaves different proof. A bank that uses more than one has several reconciliations that look like one line in the general ledger.
| Fedwire Funds Service | CHIPS | SWIFT messages through a correspondent | |
|---|---|---|---|
| Typical user | Domestic wires from nearly every bank and many credit unions | Larger banks with high volume of USD payments, often international | Cross border and foreign currency wires |
| Message reference | IMAD on the wire you send, OMAD from the Fed on the wire you receive | CHIPS sequence and universal identifier | MT103 reference, often with a UETR on gpi payments |
| Settlement evidence | Entries on the Fed account statement and the wire system activity report | Settlement position and activity reports from the operator | Correspondent statement in MT940, camt.053 or BAI2 |
| Where it hits the GL | Due from Federal Reserve Bank and a wire clearing account | Due from correspondent or CHIPS settlement account | Nostro account in the correspondent's name |
| Common break | Posted to the core with a different date or amount than the wire | Net settlement does not equal the sum of the payments | Intermediary fees and FX differences taken from the principal |
The Fed side of the first column is the same Daily Statement of Account described on federal reserve account reconciliation software. The SWIFT column overlaps with nostro reconciliation automation and correspondent bank reconciliation software, which cover the statement formats in detail.
Where wire reconciliations break
| Break | What it looks like | How it is cleared |
|---|---|---|
| Posted, not released | The core shows an outgoing wire that never left the wire system | Flagged the same day, because the customer has been debited for money that did not move |
| Released, not posted | The wire left but no debit reached the customer account | Flagged as an exposure and assigned at once |
| Amount difference | The core shows 10,000.00 and the wire system 1,000.00 | Surfaced as a near match on reference with a different amount |
| Duplicate wire | Two releases of the same instruction, one reference reused | Two items against one reference, marked as a duplicate |
| Incoming not credited | The Fed shows a credit that has not reached the customer | Assigned immediately, because the customer is waiting |
| Fees | Incoming and outgoing wire fees, intermediary charges, FX spread | Cleared by rule to the fee income or expense GL |
| Return or recall | A returned wire arrives days later as a new credit | Linked to the original wire by reference |
The first two rows are why the control should run daily. A wire that posted and was never released is a customer harmed, and a wire that was released and never posted is a loss waiting to be noticed. Everything beyond them goes to the queue described on payment exception management software.
A worked example from one wire day
Input
- Wire system activity report · 63 outgoing wires 4,812,640.00 USD · 41 incoming wires 3,120,455.00 USD
- Core postings to the wire clearing GL · 63 debits 4,812,640.00 USD · 40 credits 3,095,455.00 USD
- Federal Reserve statement · Fedwire debits 4,812,640.00 USD · Fedwire credits 3,120,455.00 USD
Output
- Matched 63 outgoing wires matched one to one on the reference to the wire system, the core and the Fed statement.
- Matched 40 incoming wires matched to the Fed credit and the core posting.
- Open 1 incoming wire for 25,000.00 USD credited by the Fed and not posted to a customer account, assigned to the wire room and aged from its value date.
The totals show the problem before anyone opens a line. Credits on the Fed statement are 3,120,455.00, credits on the core are 3,095,455.00, and the difference is 25,000.00. The match names the wire. On a manual process that difference is a number to hunt for at 4 p.m.; here it is one wire with a reference, a sender and an owner before the branch cuts off customer inquiries.
How banks and credit unions reconcile wires today
| Route | Works well when | Where it runs out | Price signal |
|---|---|---|---|
| Wire system reports | A handful of wires a day and one wire operator who also reviews the posting | Proves what the wire system released, not whether the Fed or correspondent and the GL agree | Included with the wire system |
| Spreadsheet comparison | Low volume and an experienced analyst | Done after the day closes, so a broken wire is found the next morning at best | Staff time |
| Core or hub vendor tools | You run the vendor's whole stack and accept their report formats | Rarely covers the Fed statement and correspondent statements in the same view | Included or quoted |
| Enterprise reconciliation suite | A large bank with licenses and a project team | A long implementation for one payment type, priced by quote | Quote only |
| BankAutomation | Wires reconciled daily with ACH, card and Fed accounts in the same queue | Reads files and does not release, recall or post wires | $1,200, $3,900 or $9,500 a month |
If you send ten wires a day and one person owns both release and review, that person can reconcile by hand. The case for software starts when volume passes what one person can tie before the cutoff, when you add a second path such as CHIPS or SWIFT, or when an examiner asks who reviewed the wire reconciliation and when. Instant payments follow similar logic on different rails and are covered on instant payments reconciliation software.
Who buys wire transfer reconciliation software
- Wire operations managers at community and regional banks who need a daily proof that is separate from the person who releases wires.
- Controllers and accounting managers who sign off the wire clearing GL every month and want it to tie every day.
- Credit union operations teams that send wires through a corporate credit union and reconcile the settlement account by hand.
- Internal audit and BSA teams who need an independent record of which wires were reviewed, by whom and when.
- Treasury managers who need the Fed account balance explained before they decide the next funding move.
Going live in four steps
Step 01
Choose the path
Start with Fedwire, the highest volume path at most institutions. Add CHIPS and SWIFT after the first month.
Step 02
Save the evidence as files
Wire system activity report, Federal Reserve statement or FIRD file, core postings to the wire clearing GL, and correspondent statements as CSV, BAI2, MT940 or camt.053.
Step 03
Approve the rules
Match on reference and amount, tolerate nothing on amount, clear fees by rule. One person proposes each rule and a second approves it.
Step 04
Run parallel for a month
Compare with the current spreadsheet through one month end, then retire it.
What it costs
Pricing is published and set per institution, not per user or per wire. Operations is $1,200 a month for 250,000 matched items, three source connections and up to 10 users, which covers wires, ACH and a Fed account at most community institutions. Platform is $3,900 a month for 2,000,000 items, unlimited sources, up to 50 users, SSO and maker-checker approvals. Institution is $9,500 a month with unlimited items and users, and Enterprise is $14,900 a month for private or VPC deployment. Annual billing halves each monthly rate. Every limit is on the pricing page.
The resolver at the top of this page runs the matcher on sample USD settlement data, so you can see matching, fee clearing and break classification before you talk to anyone. Wire message formats are covered on ISO 20022 payment automation.
BankAutomation is an independent product. It is not affiliated with, endorsed by or certified by the Federal Reserve Banks, CHIPS or SWIFT. Fedwire, CHIPS and SWIFT are named only to describe the evidence the software reads.
Questions about wire transfer reconciliation software
What is wire transfer reconciliation?
Wire transfer reconciliation is the daily comparison of each wire your institution sent or received across the wire system report, the core and general ledger posting, and the Federal Reserve or correspondent statement. Every wire must match on reference and amount. Anything that does not is a break to be explained, assigned to a person and cleared the same day.
How do you reconcile Fedwire transfers?
Match each wire on your wire system activity report to the core posting and to the Fedwire entry on your Federal Reserve statement or FIRD file, using the IMAD or OMAD and the amount. Totals of debits and credits should tie to the Fed statement for the day. Any wire that appears in only one of the three records is an exception to investigate before the next business day.
How often should wires be reconciled?
Daily, because Fedwire transfers are final and a wire that posted but did not leave, or left but did not post, needs action immediately. A monthly reconciliation finds the problem weeks after the money moved. Most institutions reconcile the wire clearing account at the end of each wire day and review open items at the start of the next.
Can software reconcile CHIPS and SWIFT wires as well as Fedwire?
Yes, if it reads the evidence each path leaves. BankAutomation matches Fedwire wires to the Fed statement and wire system report, and SWIFT and CHIPS payments to correspondent statements in MT940, camt.053 or BAI2. The same queue holds all three, so a bank with several paths sees one list of open wires.
Does BankAutomation send, recall or release wires?
No. BankAutomation does not connect to Fedwire, CHIPS or SWIFT and cannot release or recall a payment. It reads the reports your wire system, core and correspondents already produce and matches them. Nothing is installed on the wire system and nothing posts back, so control of wires stays where your policy puts it.
How much does wire reconciliation software cost?
Enterprise reconciliation suites are quoted per customer and rarely publish a price. BankAutomation publishes its plans: $1,200 a month for 250,000 matched items and three sources, $3,900 a month for 2,000,000 items with unlimited sources and maker-checker approvals, and $9,500 a month for unlimited volume. The price is per institution, not per wire, and annual billing halves each monthly rate.