Bulk vendor wires
Wire Transfer File Software for Bulk Vendor Wires and ISO 20022 pain.001 Files
Try it now, capture a real invoice
Your file is used only for this demo and deleted automatically within hours.
Wire transfer file software builds one bank-ready file from a batch of approved vendor bills, so nobody keys wires into the bank portal one at a time. AutoPayables writes an ISO 20022 pain.001 file from each wire payment run, with US vendors paid by ABA routing number and foreign vendors by SWIFT/BIC and IBAN. You upload the file to your bank and release the wires there. It is part of the $49 Growth plan, with no fee per wire.
pain.001
ISO 20022 file your bank imports
1
Transaction per vendor, invoices listed in remittance
$0
AutoPayables fee per wire sent
$49
Growth plan per month, wire files included
Accounting sync
Everything the wire file needs, taken from bills you already approved
The file is the last step of the payment run, so the data comes from the same records your approvers signed off.
ISO 20022 pain.001 output
Each wire run produces a pain.001.001.03 file checked against the official ISO 20022 schema, ready for your bank's file import or bulk payments screen.
Domestic wires by ABA
US vendors are paid by ABA routing number, including US territories, and the routing number must pass the ABA checksum before the file can be downloaded.
International wires by SWIFT
Foreign vendors carry a SWIFT/BIC on their vendor card, and the account goes out as an IBAN when it passes the IBAN check, or as a plain account number when it does not.
Problems listed before the bank sees them
Missing legal name, a past payment date, a vendor without bank details or cents in a currency that has none are listed in plain English before download.
Locked on first download
The first download freezes payer and vendor data. Later downloads return the identical file with the same message ID, and payments in it cannot be cancelled.
Remittance your vendors can apply
Every wire carries the invoice numbers it pays in the remittance field, so the vendor's receivables team knows which bills to close.
From approved bills to wires released at your bank
Four steps, and the money never passes through us.
Capture and approve the bills
Invoices are read by AI, coded to GL accounts, checked for duplicates and PO matches, and approved by whoever owns the spend.
Create a wire payment run
Pick the approved bills, set the payment date and tick Build a wire file for my bank. AutoPayables groups the bills into one wire per vendor.
Download the pain.001 file
Fix anything on the pre-check list, then download. The file and the run are locked from that moment so the records match what the bank received.
Upload and release at your bank
Import the file in your bank's file upload or bulk payments screen and release the wires under your bank's own approval rules.
Keying wires by hand vs sending a wire file
The bank fee is the same either way. What changes is the retyping and the risk.
Keying each wire into the bank portal
- Beneficiary name, routing and account retyped for every wire
- Invoice numbers typed into a free text memo, if at all
- Nothing ties the wire back to an approved bill
- Mistakes show up when a vendor calls about a missing payment
- Bills marked paid by hand after the bank confirms
AutoPayables wire transfer file
- Bank details come from the vendor card, entered once
- Invoice numbers written into the remittance field automatically
- Every wire comes from bills that passed approval and matching
- Bad routing numbers and missing details are caught before download
- Bills marked paid in the same run the file came from
Teams that send vendor wires in batches
Wires are for the payments where size, timing or geography rules out ACH.
Importers paying overseas suppliers
Factories and freight forwarders abroad are paid by SWIFT/BIC and IBAN in the invoice currency, with the invoice numbers carried through.
Construction and real estate
Subcontractor draws and closing costs go out on fixed dates, and every wire traces back to an approved bill.
Distributors with a few large suppliers
Six figure supplier payments go out in one upload instead of a morning of retyping account numbers.
Controllers tightening wire controls
Approval in AutoPayables plus release rules at the bank gives two separate sign-offs on every outgoing wire.
Wire transfer file software in one paragraph
Wire transfer file software turns a batch of approved vendor bills into one file your bank can import, so nobody keys beneficiary names, routing numbers and amounts into the bank portal one wire at a time. AutoPayables builds that file in the ISO 20022 format, pain.001.001.03, straight from a payment run. You download it, upload it to your bank's file or bulk payments screen, and approve the wires there. The money leaves your own account, under your bank's own controls, and the bills in AutoPayables are already marked as paid with the file attached to the run.
What goes into the pain.001 file
Every file we write is checked against the official ISO 20022 schema for pain.001.001.03 before it reaches you. A file that breaks the schema gets rejected by the bank as a whole, so we would rather catch the problem on our side. This is what each part of the file carries.
| Part of the file | What AutoPayables writes | Where it comes from |
|---|---|---|
| Message ID and control sum | A unique message ID, the number of wires and the total of the run | The payment run |
| Requested execution date | The payment date you picked for the run | The payment run, which must be today or later |
| Debtor (you) | Your legal name, address and the account the wires are drawn from | Settings, Payment account |
| US beneficiary bank | The ABA routing number, with the SWIFT/BIC added when you have it | The vendor card |
| Foreign beneficiary bank | The SWIFT/BIC, and the account as an IBAN when the number passes the IBAN check | The vendor card |
| Amount and currency | One transaction per vendor in the run's currency, whole units only for currencies without cents | The approved bills in the run |
| Remittance information | The invoice numbers the wire pays, so the vendor can apply the cash | The bills in the run |
| Charges and priority | Shared charges (SHAR) and the urgent service level used for wires | Fixed for wire runs |
Before you can download, AutoPayables lists anything the bank would refuse: a missing company legal name, a routing number that fails the ABA checksum, a payment date already in the past, a vendor with no bank details, or a cents amount in a currency that has none. You fix the vendor card and the same run picks up the change, because nothing is frozen until the first download.
Does Fedwire's ISO 20022 switch change how I send vendor wires?
It changed the bank side, not your upload screen. The Federal Reserve moved the Fedwire Funds Service to ISO 20022 messages in a single-day cutover on July 14, 2025, replacing the older FAIM format. That is the message one bank sends another. The file a company sends its own bank is a different ISO 20022 message, pain.001, and it carries the same structured fields: separate address lines, beneficiary bank identifiers and remittance text. Sending your bank a pain.001 file means your data is already in the shape the interbank wire needs, instead of free text someone retyped.
Wire file vs NACHA ACH file for vendor payments
Most AP teams need both. ACH is cheaper and fine for routine domestic bills. Wires are for the payments where speed, size or geography matters. AutoPayables builds both from the same payment run screen, so the choice is per run, not per tool.
| ISO 20022 wire file (pain.001) | NACHA ACH file | |
|---|---|---|
| Typical use | Large, urgent or international vendor payments | Routine domestic vendor bills |
| Speed | Same day once your bank releases it | Same day or next day, depending on the batch window |
| Bank fees | Per wire, set by your bank | Usually far lower per item, set by your bank |
| International vendors | Yes, by SWIFT/BIC and IBAN | No, US accounts only |
| Reversal | Effectively final once sent | Limited return rights |
| Remittance detail | Invoice numbers in the remittance field | Invoice numbers in the CCD+ addenda |
If most of your vendors take ACH, start with our NACHA file software for accounts payable and keep wires for the exceptions. For the trade-offs in more depth, see ACH vs wire transfer.
How do I stop a vendor wire from going out twice?
Wires are hard to claw back, so the controls sit before the bank. Duplicate invoice detection flags the same invoice number from the same vendor, and two-way or three-way PO matching stops a bill that does not agree with its purchase order. Then the file itself is locked: the first download freezes the payer and vendor data, every later download returns the identical file with the same message ID, and most banks refuse a second upload of a message ID they have already processed. Payments inside a downloaded file cannot be cancelled in AutoPayables either, so the records cannot drift away from what the bank received. Our duplicate payment detection page shows the checks on the invoice side.
How much does wire transfer file software cost?
Wire files are part of the AutoPayables Growth plan at $49 a month, which includes 200 invoices a month with AI capture, approvals, ACH files, check printing with a Positive Pay file, and wire files. Scale is $149 a month with unlimited invoices and API access, and annual billing halves both prices. We charge nothing per wire. Your bank's wire fee still applies, the same as when someone keys the wire by hand. Full details are on the pricing page.
The usual alternatives cost more in time or money. Keying wires into the bank portal costs nothing extra but invites typos in account numbers. ERP payment modules and treasury platforms can write pain.001, but they are priced for companies that already run those systems. A payment network will send the wire for you, often with a per payment fee or an FX margin you do not see.
What wire file software does not do
AutoPayables does not move the money. Your bank sends every wire, and your bank's approval rules, limits and callbacks still apply, which is what most auditors want. We do not quote FX rates; a wire in a foreign currency is converted under your bank's terms. And your bank has to accept file uploads: most commercial banking platforms offer a file import or bulk payments module, but some small business accounts only allow wires keyed one at a time. Ask your treasury contact whether your upload screen accepts ISO 20022 pain.001.001.03 before your first run.
Who uses a wire transfer file instead of keying wires
Controllers paying a handful of large suppliers by wire every week, where one mistyped digit sends six figures to the wrong account. Importers and distributors paying overseas factories by SWIFT. Construction and real estate teams wiring subcontractors and closing costs on tight dates. In each case the bills are captured, coded and approved once, and the wire file is the last step of the same AP payment run, not a separate job in the bank portal.
Upload one real vendor invoice at the top of this page to see the capture that feeds the run. Teams on QuickBooks can pair the wire file with our QuickBooks NACHA file workflow for the ACH side of the same week.
Frequently asked questions
A wire transfer file is a single file that holds many outgoing wires, which you upload to your bank instead of keying each wire by hand. Most banks accept the ISO 20022 pain.001 format for this. Each entry carries the beneficiary, the beneficiary bank, the amount and remittance text, and you release the batch in your bank's portal.
AutoPayables writes ISO 20022 pain.001.001.03, the Customer Credit Transfer Initiation message, and checks every file against the official schema before you download it. Ask your bank whether its file upload accepts that version; most commercial banking platforms with a bulk payments or file import module do.
Yes. A foreign vendor needs a SWIFT/BIC on its vendor card, and the account number goes out as an IBAN when it passes the IBAN check. The wire is in the run's currency, and your bank applies its own exchange rate and wire fee. Currencies without cents must have whole amounts.
No. Your bank sends every wire after you upload the file and release it there, so your bank's limits, dual approval and callback rules still apply. AutoPayables builds the file, marks the bills as paid in the run and keeps the file attached for your audit trail.
You get the identical file with the same message ID, because the data is frozen on the first download. Most banks refuse a second upload of a message ID they have already processed, which protects you from paying the run twice. Payments inside a downloaded file cannot be cancelled in AutoPayables.
Wire files come with the AutoPayables Growth plan at $49 a month, alongside 200 invoices of AI capture, approvals, NACHA ACH files and check printing with Positive Pay. Scale is $149 a month for unlimited invoices. There is no per wire fee from us; your bank's normal wire fee applies.
Neither is better overall. ACH is cheaper and suits routine domestic bills, while wires suit large, urgent or international payments and are effectively final once sent. AutoPayables builds both from the same payment run screen, so you choose per run.
Send next week's vendor wires as one file
Start with your own invoices. Growth is $49 a month with wire, ACH and check files included and no fee per payment.