Key Takeaways
- ACH carried close to 8.1 billion B2B payments in 2025, almost 10% more than in 2024 (Nacha, 2026), with 80 characters per addenda record (Nacha, 2024).
- A SEPA transfer has one 140-character remittance field (EPC, 2024) and a Fedwire payment is designed for 140 characters of unstructured text (Federal Register, 2021), so a long invoice list usually travels separately.
- ACH and Fedwire settle only on business days; SEPA Instant runs 24 hours a day, 365 days a year (ECB, 2026).
- Only ACH returns are routine: a SEPA Instant recall is limited to three reasons, and a wire can only be asked back.
- You cannot choose the rail, but you can choose the reference you print for it; ClearMatch then auto-matches 95% of payments (Transformance customer data, 2026).
In This Article
- Key Takeaways
- ACH vs wire vs SEPA Instant: what does your AR team receive from each rail?
- What does an ACH payment carry, and when does it arrive?
- What does a wire carry, and what is the cut-off?
- How do SEPA credit transfers and SEPA Instant differ for the receiver?
- Which payments can still be recalled or returned?
- What changes for cash application when payments arrive at any hour?
- What should your invoice ask each customer to send?
- How does Transformance work with payments from every rail?
ACH vs wire vs SEPA Instant: what does your AR team receive from each rail?
Customers choose ACH, wire or a SEPA rail on speed and cost; your AR team receives 80 to 140 characters of remittance text, and the invoice list often follows separately.
Payment rails at a glance: what arrives, when, and what can be undone
A payment rail is the network and rulebook a payment travels over: it sets how fast the money arrives, how much reference text rides along and what the sender can still pull back. Each cell is sourced in that rail’s section below.
ACH is where most US B2B volume sits: close to 8.1 billion B2B payments in 2025, plus 1.4 billion Same Day ACH payments worth $3.9 trillion (Nacha, 2026). Nacha expects more invoice payments on Same Day ACH once its per-payment limit rises from $1 million to $10 million on September 17, 2027 (Nacha, 2026).
The payer picks the rail. You pick the payment instructions on the invoice, set out rail by rail further down.
This page covers the payment and its rail. How the bank statement brings it into your ERP is in the BAI2, camt.053 and MT940 guide; remittances sent outside the payment are covered in how AI reads remittance advice and matches payments.
What does an ACH payment carry, and when does it arrive?
An ACH credit carries an optional 80-character addenda record, or up to 9,999 records in a CTX; Same Day ACH items settle at 1:00, 5:00 or 6:00 p.m. ET.
Nacha’s API documentation describes the addenda as “80 characters of payment related information provided by Originator per addenda record.” A CCD entry may have one record (hence “CCD+”), a CTX entry up to 9,999 (Nacha, 2024). The Federal Reserve’s Fundamentals of Financial EDI (Federal Reserve Financial Services, 2021) shows a CTX carrying an X12 820 remittance advice in those records.
A CCD without an addenda tells you who paid and how much, and little else. Whether addenda text reaches your statement depends on your bank’s reporting, so ask before you build matching rules on it.
Same Day items settle at 1:00, 5:00 and 6:00 p.m. ET for files sent by 10:30 a.m., 2:45 p.m. and 4:45 p.m. ET; other items settle at 8:30 a.m. ET on a later business day (Federal Reserve Financial Services, schedule effective 2022). Your customer’s bank sets earlier cut-offs.
The $1 million Same Day limit applies to each payment, with no aggregate limit on a batch or file (Nacha, rule effective 2022). An ACH credit can be returned by the receiving bank; codes and windows are in ACH return codes and SEPA R-transactions.
For cash application, the payment brings a short reference and the invoice list comes by email or EDI 820. Illustrative case: ten 8-digit invoice numbers with commas need 89 characters, more than one addenda record holds.
What does a wire carry, and what is the cut-off?
Fedwire’s ISO 20022 format is designed for up to 140 characters of unstructured remittance or 9,000 characters of structured data, and customer transfers stop at 6:45 p.m. ET.
The Reserve Banks planned to “support up to 140 characters for unstructured remittance information and up to 9,000 characters for structured” remittance data, following guidelines that favor structured data over free text (Federal Register, 2021). Fedwire implemented ISO 20022 on July 14, 2025 (Federal Reserve Financial Services, 2025). What arrives depends on what the sender’s bank fills in.
The Fedwire business day opens at 9:00 p.m. ET on the preceding calendar day and closes at 7:00 p.m. ET; Saturdays, Sundays and Reserve Bank holidays are not business days, and customer transfers stop at 6:45 p.m. ET (Federal Reserve Financial Services, 2026). A wire that misses Friday’s cut-off settles on Monday’s business day, which opens Sunday at 9:00 p.m. ET.
Cross-border, the Swift MT103 field 70 holds four lines of 35 characters, and the pacs.008 equivalent 140 characters (Bank of America, 2025). Intermediary banks sit in between, so ask your bank what reaches your statement. Currency handling is covered in intercompany and multi-currency cash application.
To undo a wire, Fedwire lists a return request message (camt.056) among its message types (Federal Reserve Financial Services, 2026). It is a request, nothing more.
Wires bring fewer, larger payments, so the payer reference is the field to ask for. A late-evening wire can carry a value date that differs from your booking date.
How do SEPA credit transfers and SEPA Instant differ for the receiver?
Both SEPA rails carry one 140-character remittance field, structured or unstructured; SEPA Instant makes the funds available within 10 seconds, at any hour, with no scheme-wide maximum amount.
The European Payments Council’s 2025 SEPA Instant rulebook, in force since October 5, 2025, lets the field carry structured or unstructured data of up to 140 characters. The EPC says it “enables automated reconciliation between receivables and payments by the Beneficiary” and recommends the ISO structured creditor reference for a payment that refers to a single invoice (EPC, 2024). Banks must forward that text “in full and without alteration.” The standard SEPA credit transfer rulebook defines the same field (EPC, 2024).
Speed is the difference. Instant payments make funds available “within ten seconds,” 24 hours a day, 365 days a year (ECB, 2026). The 2025 rulebook sets no maximum amount at scheme level (EPC, 2024); account holders can set their own limits (Deutsche Bundesbank, 2025).
The EU’s Instant Payments Regulation binds payment service providers, not your customers. Euro-area providers must receive instant payments since January 9, 2025, and send them and offer Verification of Payee since October 9, 2025; non-euro member states follow on January 9, 2027 and July 9, 2027 (ECB, 2026). Verification of Payee checks your name against your IBAN for the payer. It adds no remittance data.
Whether an instant credit arrives in the end-of-day camt.053 or in a separate notification depends on your bank (bank statement formats). Matching cadence is covered in real-time cash application and instant payments.
Which payments can still be recalled or returned?
Only ACH returns are routine; a wire can only be asked back, and the SEPA Instant rulebook allows a recall for just three reasons.
SEPA Instant. A recall is allowed only for duplicate sending, technical problems that caused an erroneous transaction, or fraud. The payer’s bank sends it within 10 banking business days, or 13 months for fraud, and your bank answers within 15 banking business days (EPC, 2024). Any other request is “no guarantee” the payer gets the funds back.
SEPA in general. The Bundesbank states that instant transfers, like conventional ones, are “grundsätzlich nicht widerruflich” (generally not revocable), and a refund depends on the recipient’s consent (Deutsche Bundesbank, 2025).
US instant. The Clearing House describes RTP payments as “Final, anytime, every day” (The Clearing House, 2026).
ACH and wire. ACH returns follow Nacha’s codes and windows, set out in ACH return codes and SEPA R-transactions. A wire return request is a message; the receiving side decides.
So apply instant and wire cash only when it matches. A wrong application is a posting you reverse in your ERP, not a payment you can pull back; see how payments post and clear open items from an external system.
What changes for cash application when payments arrive at any hour?
Instant rails remove the overnight window: a payment can land on a Saturday before its remittance email is written, so cash application must hold it and match it later.
Fedwire reopens at 9:00 p.m. ET on Sunday for Monday (Federal Reserve Financial Services, 2026), and ACH settles on business days. SEPA Instant never closes. RTP takes payments of up to $10 million around the clock (The Clearing House, 2026), and the Federal Reserve announced a rise of FedNow’s network limit to the same $10 million, effective November 2025, with banks free to set lower limits (Federal Reserve Financial Services, 2025).
In an illustrative case, a SEPA Instant credit of EUR 48,250.00 lands at 2:14 a.m. on a Saturday, and the customer’s AP team sends the advice on Monday:
- Payment lands. The bank credits your account on Saturday.
- The ERP shows the statement line. It appears with the next statement import or bank notification.
- The remittance arrives. Monday morning, by email.
- A match is proposed. Reference, amount and remittance point to the open items.
- A person approves. Only then does the clearing post.
Dates need care. A weekend payment carries the date your bank booked it, while your ERP clears with a posting date in an open period. A payment on the last Saturday of a month can fall into a period finance has already closed.
The cheapest fix sits on the invoice: one invoice-number format, printed the same way everywhere. If one document shows “INV-0204518” and another “204518”, the customer copies whichever it sees first. When no usable reference arrives, see how to match a payment with no reference; for what is already stuck, how to clear an unapplied cash backlog.
What should your invoice ask each customer to send?
Print the invoice number in one fixed format as the payment reference for every rail, and ask for a remittance email or EDI 820 when one payment covers several invoices.
Payment instructions by rail: what to ask for on the invoice
Two rule-owner facts sit behind the table. The EPC recommends the structured creditor reference (ISO 11649, the “RF” reference) for a payment that refers to a single invoice (EPC, 2024). An ACH addenda record holds 80 characters (Nacha, 2024), so a dozen invoices need a CTX with an EDI 820 or a separate advice.
An illustrative instruction line for invoice INV-204518 to a customer in Ohio:
Pay by ACH or wire to the account below. Reference: 204518. For a payment covering more than three invoices, send an EDI 820 or a remittance email to ar@yourcompany.example.
Customers decide whether they follow it; the instruction makes the right reference the easiest one to copy. E-invoicing improves the invoice, not the payment’s 140 characters (e-invoicing and cash application). Portal payers follow the portal’s rules (AP portals guide), and every other remittance source is mapped in where remittance advice comes from.
How does Transformance work with payments from every rail?
Transformance reads the remittances your customers send, in any format, and the bank statement lines your ERP has imported; ClearMatch then proposes the match for a person to approve.
The rail is a property of the payment. Transformance works from the statement line and the remittance, so the rail changes only what those two contain: 80 characters from an ACH addenda, 140 from a wire or SEPA transfer, or an email that turns up on Monday.
DocSense reads remittances with vision language models, not OCR plus regex: over 97% extraction accuracy across 100+ document types and 170+ languages, with zero template configuration (Transformance platform data, 2026). ClearMatch auto-matches 95% of payments and runs end to end in under 8 minutes, with 100% posting validation; nothing posts without human sign-off (Transformance customer data, 2026).
For the exception, such as an instant payment with no usable reference, Vero, the AI agent, investigates from Customer 360, its memory of each customer, and fetches internal and external information to find more matches. Vero proposes with the evidence; a person approves, and postings follow your approval thresholds by amount, entity and customer.
Transformance reads open items and bank statements from the ERP and writes clearing postings and journal entries back (what AR automation reads and writes). The ERP connection typically takes 2-3 days, and your IT team may be involved; a full rollout takes 4-8 weeks, with data hosted in your region. Syngenta, Eberspächer and PwC are among its customers across Europe, the United States and Australasia.
Who Transformance is for
- ERPs: teams receiving ACH, wire and SEPA payments into SAP S/4HANA (on-premises, private or public cloud), SAP ECC, NetSuite (including OneWorld subsidiaries), Microsoft Dynamics 365 Finance & Operations and Business Central, or Odoo, all running in production with customers; Oracle and Infor are supported.
- Size: mid-market to large enterprise, 250 to 2,000+ employees, including groups with several entities and shared service centers.
- Payment volume: from under 1,000 to over 100,000 payments a month.
- Industries: manufacturing, consumer goods and food and beverage, logistics, e-commerce, agriculture, energy and professional services.
- Scope: cash application alone, or the full order-to-cash (cash application, deductions, AR collections, cash forecasting).
Conclusion: choose what you ask for, not which rail the customer uses
You cannot pick the rail, but you can print the reference, request the remittance and plan cash application for 80 to 140 characters and payments at any hour.
Start with the three rails your largest customers use and fix one reference format for all of them. Then test a month of real payments on one entity; the rollout path is in how to automate cash application with AI.
Key terms
- ACH: the US batch payment network for credits and debits, run on Nacha rules.
- Same Day ACH: ACH items that settle on the same business day, in three windows.
- Wire transfer: a single, usually large or urgent bank-to-bank payment, such as over Fedwire.
- SEPA: the euro payments standard for credit transfers, including SEPA Instant.
- Remittance advice: the customer’s list of the invoices and deductions a payment covers.
- ISO 20022: the XML message standard behind SEPA, RTP and, since 2025, Fedwire.
Related guides
- Which ERP systems does Transformance integrate with?
- What do ACH return codes and SEPA R-transactions mean for AR?
- Where does remittance advice come from, and how is it captured?
- How do external systems post payments and clear open items?
- How do BAI2, camt.053 and MT940 files feed cash application?
- Real-time cash application and instant payments
- How do you get paid on time when customers use SAP Ariba or Coupa?
Frequently Asked Questions
What is the difference between ACH and wire for B2B payments?
ACH is a batch network: payments settle in set windows on business days and carry an optional 80-character addenda, or up to 9,999 records in a CTX. A Fedwire payment is sent individually during a business day from 9:00 p.m. ET the evening before to 7:00 p.m. ET, with room for 140 characters of unstructured remittance.
Does a SEPA Instant payment carry more remittance data than a normal SEPA transfer?
No. Both use one remittance field of up to 140 characters, structured or unstructured. SEPA Instant differs in speed: funds arrive within 10 seconds, at any hour.
Can an ACH, wire or instant payment be reversed?
ACH payments can be returned by the receiving bank, and a wire can be asked back with a return request. A SEPA Instant payment can be recalled only for duplicate sending, technical problems or fraud, and the Bundesbank notes that a refund depends on the recipient’s consent.
Which ERPs can Transformance work with when payments arrive over different rails?
Transformance runs in production with customers on SAP S/4HANA (on-premises, private or public cloud), SAP ECC, NetSuite, Microsoft Dynamics 365 Finance & Operations, Business Central and Odoo, and supports Oracle and Infor. The rail changes only what the imported bank statement line contains.
Does it work for groups with many entities and high payment volumes?
Yes. Transformance is built for 250 to 2,000+ employees and from under 1,000 to over 100,000 payments a month, and several SAP company codes, NetSuite subsidiaries or Dynamics 365 legal entities consolidate in one environment.
How long does it take to start with payments from every rail?
The ERP connection typically takes 2-3 days, and your IT team may be involved. A proof of value runs in 4-5 weeks on one entity, and the full rollout takes 4-8 weeks.
What does it cost to automate cash application across ACH, wire and SEPA payments?
The cost depends on scope and entities: cash application alone or the full order-to-cash, and how many entities you run. Book a Call and we size it with you.
SAP, SAP S/4HANA, Microsoft, Dynamics 365, Business Central, Oracle, NetSuite, Odoo and Infor are trademarks of their respective owners (SAP SE, Microsoft Corporation, Oracle Corporation, Odoo S.A., Infor). Transformance is not affiliated with or endorsed by them.
