Key Takeaways
- Vero, Transformance’s AI agent, matches the payments on your bank statements to open items, whichever route the statement takes: EBICS, SFTP, a bank API or your ERP.
- The channel is not the format: one camt.053 file can travel by EBICS, SFTP or your ERP’s bank interface.
- For cash application, ask the bank for the narrowest access that retrieves statements and releases no payments.
- US banks commonly deliver BAI2 prior-day files over SFTP; banks in Germany, France, Switzerland and Austria commonly use EBICS.
- Agree seven things with bank and IT before the first statement flows, from accounts and rights to who owns the access.
In This Article
- Key Takeaways
- How do bank statements reach cash application?
- What is EBICS, and how does a connection get set up?
- What changed in 2025 and 2026 that affects the statement channel?
- When do SFTP, host-to-host and US bank files fit better than EBICS?
- Where do bank APIs fit, and what do they not replace?
- How does each ERP bring a bank statement in?
- How does Transformance get your bank statement data?
- What should you agree with the bank and IT before go-live?
How do bank statements reach cash application?
Agents like Transformance’s Vero match statement lines to open items once the statement arrives by EBICS, bank-hosted SFTP, a bank API or your ERP’s bank interface.
Bank statement channels: who sets them up, what they carry and when they fit
Our summary of bank and ERP documentation; the Effort column is our assessment.
What a bank connection is. A bank connection is the agreed route by which your bank delivers your account postings to your finance system. camt.053, MT940 and BAI2 describe the file; EBICS, SFTP and APIs describe how it travels. Field-level format detail is in the guide to BAI2, camt.053 and MT940 in cash application.
Why AR should care. Matching starts only when the statement line is there. A late, duplicated or truncated statement shows up as unapplied cash on your desk, not as an IT ticket. See also payment rails, remittance advice sources and posting after a match.
Takeaway: Pick the channel first, then the format; the channel decides who owns the access and when the data arrives.
What is EBICS, and how does a connection get set up?
EBICS, the Electronic Banking Internet Communication Standard, is a signed and encrypted file exchange between a company and its bank, used by banks in Germany, France, Switzerland and Austria.
Origin and reach. The German banking industry developed EBICS, and it has been mandatory in Germany since 2008. France signed a cooperation agreement in November 2008, Switzerland joined in January 2015 and Austria in July 2020. The standard’s steering committee aims to extend its use to other European countries (EBICS website). A group with accounts in the US or Asia typically needs another channel for those accounts.
Who is who. In the EBICS specification, the customer is the company, and the bank assigns signature classes to the users under it. Classes E, A and B authorise orders such as payments, alone or jointly. The transport class T only covers submitting an order, not authorising it, and authorisations can be set per transaction type. Each bank defines the details. For cash application, ask for statement retrieval only, with no signing right, and have the bank confirm the exact terms in writing.
EBICS set-up in seven steps
- Agree access with the bank. Settle accounts, users and statement download orders. The bank sends its EBICS URL, host ID and supported versions.
- Install the EBICS software. It can sit in the ERP, a treasury system or a stand-alone client; enter the bank’s details.
- Create the keys. The software creates three key pairs: authentication (X002), encryption (E002) and signature (A005 or A006). The public keys go to the bank with the INI and HIA orders.
- Sign the initialisation letter. The software prints it; the user signs it and sends it to the bank that holds the account.
- Wait for activation. With the signed letter, the bank activates the user.
- Check the bank’s keys. Download the bank’s public keys (order HPB) and compare their hash values with those the bank gives you.
- Fetch a first statement. Retrieve a statement and check the balance, the number of transactions and the remittance text.
Steps follow the EBICS specification; your bank sets the exact order.
What EBICS 3.0 changes for the person setting it up. Business transaction formats (BTF) take the place of the old order types, and the specification sets a minimum key length of 2,048 bits (the EBICS specification). Ask your bank and software provider early about EBICS 3.0 support.
What EBICS does not do. It moves files from the bank to your software. It does not match anything or fix a missing invoice reference.
Takeaway: EBICS is transport; what matters is the retrieval right, the format and a well-set-up user.
What changed in 2025 and 2026 that affects the statement channel?
Since November 2025, German banks have been moving EBICS statements from MT940 to camt.053 and intraday data from MT942 to camt.052; each bank sets its own switch date for existing accesses.
What the change means. The channel stays EBICS; the file inside changes. Check your bank’s EBICS page for its date (the timeline is in the formats guide); US BAI2 files are not affected. Check three things before the switch:
- Matching rules: rules written against text patterns in the MT940 remittance field need a fresh test against camt.053, which spreads the information across structured fields.
- Batch bookings: if a batch booking appears only as a total on the end-of-day statement, ask whether camt.054 delivers the items; otherwise the batch stays an exception.
- Statement numbers: ask whether daily statement numbering restarts after the switch, and adjust your gap check so it neither false-alarms nor misses a real gap.
Our advice. Where the bank offers it, take both formats in parallel for a test period and compare balances and transaction counts before you switch the feed to camt.053.
Takeaway: The route stays, the file changes; test old and new formats side by side.
When do SFTP, host-to-host and US bank files fit better than EBICS?
SFTP or host-to-host fits when the bank hosts a folder for your statement files, which is common for US banks and for accounts outside the four EBICS countries.
How it works. The bank gives you a server, a directory and a file-name rule; you give the bank an SSH public key and often a list of allowed IP addresses; a scheduled job picks up new files. ERPs document their side: NetSuite’s Auto Bank Statement Import connects to the bank’s server through SFTP with a file-name pattern (NetSuite Help Center), and Oracle Fusion Cloud retrieves statements over SFTP with a password or an SSH key (Oracle documentation).
The US files. BAI2 is the usual US file for prior-day reporting. Check payments with invoice detail typically arrive as a separate file through the bank’s lockbox service.
Who owns it. The bank hosts the folder, IT holds the keys and the scheduler, and AR decides what happens when a file is missing. Set up one rule on day one: an alert when no file has arrived by the bank’s stated delivery time.
Takeaway: SFTP is the file route where EBICS is not offered; the missing-file alert matters more than the protocol.
Where do bank APIs fit, and what do they not replace?
A bank API returns balances and transactions on request, so it suits on-demand views, but it delivers transactions, not a signed end-of-day statement, and coverage differs by bank.
ERPs. Business Central offers the Envestnet Yodlee Bank Feeds service as an alternative to statement files (Microsoft Learn). Odoo synchronizes through providers such as Plaid and Yodlee and notes that some banks only allow fetching three months back, or no automatic fetching at all (Odoo documentation).
What an API does not replace. In our reading, the end-of-day statement with its opening and closing balance remains the record you reconcile against. Ask your bank:
- Does it offer an account information API for corporate clients?
- Does the API return the full remittance text?
- How long does consent last, and how are tokens renewed?
- Is there a sandbox to test against?
Takeaway: Use the API for intraday balances; keep the statement file as the record.
How does each ERP bring a bank statement in?
Every ERP imports bank statements its own way, from file upload to scheduled connection, so the cleanest cash application feed is often the one your ERP already receives.
How each ERP brings a bank statement in (as documented by the ERP vendor)
Sources: Oracle, NetSuite, Microsoft (Finance), Microsoft (Business Central: conversion service, SEPA CAMT), Odoo (synchronization, import formats), all accessed 17 November 2026.
In SAP S/4HANA, the function is the electronic bank statement; the format versions your release reads are in SAP’s documentation for that release. How Transformance reads and writes in SAP is in the SAP S/4HANA integration guide.
If your treasury already feeds the ERP, cash application often needs no new bank route: Transformance reads the statement where it already lands. What it reads and writes back is in the guide to AR automation and the ERP.
Takeaway: Check how your ERP gets the statement today; a second bank route pays off only when the first is missing or late.
How does Transformance get your bank statement data?
Transformance reads your bank statements by the route that fits your setup: from your ERP’s bank interface, or through EBICS, SFTP, a bank API, a file drop or a mailbox.
The route follows your setup. Transformance builds the connections through its integrations hub, runs and monitors them and fixes what breaks; you approve access and production changes. If a system has an API, a database, a file drop or a mailbox, it can be connected. Which rights the bank grants for statement retrieval is agreed between you and your bank.
Who builds it. Transformance’s integration agents read the system documentation and your setup answers, propose field mappings, draft the workflow, run the test plan and report the results. A person approves every change that reaches a customer system or production.
What happens during onboarding. Bank, ERP and mailbox connections are set up step by step with your IT team in the loop, and the statement formats your banks deliver are captured and tested. Credentials go into dedicated secure slots, never email. Balances and bank statements are tied out between the old process and the new one, and tests run on your own transactions in a staging environment. During testing, Transformance has read-only access to your ERP; write access starts at rollout. The ERP connection typically takes 2-3 days, and your IT team may be involved; the bank’s own steps follow the bank’s timetable. What to hand over first is in the onboarding data request guide.
After retrieval. ClearMatch auto-matches 95% of payments and runs end to end in under 8 minutes (Transformance customer data, 2026). Every posting is validated, and nothing posts without human sign-off. When a payment cannot be matched, Vero investigates from Customer 360, its working memory for each customer, pulls in internal and external information and proposes the match with evidence; a person approves. Data stays in your region.
Takeaway: You choose the route with your bank, Transformance builds and runs the connection, and a person approves what reaches the ERP.
What should you agree with the bank and IT before go-live?
Agree seven things before the first statement flows: accounts, rights, format, frequency, batch bookings, duplicate and gap checks, and who owns the access when someone leaves.
Seven things to agree with the bank and IT before the first statement flows
- Accounts and entities: every bank account with its legal entity, country and ERP bank account (owner: treasury).
- Rights: the narrowest access that retrieves statements and releases no payments, confirmed by the bank in writing (owner: treasury and the bank).
- Format and version: camt.053 for end of day, camt.052 only for intraday data, camt.054 for batch booking detail; name any BAI2 or MT940 accounts explicitly (owner: treasury, with AR for the matching impact).
- Frequency and cut-off: when the bank publishes the prior-day file or end-of-day statement, and what you do when it is late (owner: IT and AR).
- Batch bookings: how multi-payment bookings arrive and where the item detail sits (owner: AR and the bank).
- Duplicates and gaps: statement number or date sequence, balance check, alert when a file is missing (owner: IT and AR).
- Access ownership: named user, technical user or service key, the key rotation date, and what happens when the owner leaves the company (owner: IT and treasury).
A test set for the first statements. Run a full business day, a batch booking, a bank fee, a payment with no invoice reference and a duplicate delivery. If opening and closing balances agree with the bank portal, the route is ready. See UAT, parallel run and cutover for planning tests, and master data cleanup before cash application for wrong bank details in customer master data.
Takeaway: Each of the seven points has a named owner; the bank activates access, but you own it.
Who Transformance is for
- ERPs: teams whose bank statements reach 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, by EBICS, SFTP, a bank API or the ERP’s own bank interface; Oracle and Infor are supported.
- Size: mid-market to large enterprise, 250 to 2,000+ employees, including groups with several entities and shared service centres.
- 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 the channel by bank and owner, then test the file
Choose the channel your bank supports and your IT can own, ask for the narrowest access that works, and prove the first statements against balances before you switch matching on. This week, list every bank account with its country, bank, channel, format and owner, run the test set, then connect cash application. For the other systems that feed AR besides the bank, see the guide to AR data sources beyond the ERP. Book a Call to see how Vero matches your bank statements.
Key terms
- Cash application: matching incoming payments to open items; Vero proposes each match with its evidence and a person approves.
- camt.053: the end-of-day bank statement in ISO 20022 XML.
- MT940: the SWIFT end-of-day statement message that camt.053 replaces.
- BAI2: the US file for prior-day bank reporting.
- Lockbox: a US bank service that processes checks and paper remittances into a file.
- Bank reconciliation: comparing bank statement lines with ledger entries.
Related guides
- Which ERP systems does Transformance integrate with?
- BAI2, camt.053 and MT940 in cash application
- Where remittance advice comes from and how to capture it
- What AR automation reads from and writes to the ERP
- Which systems besides the ERP feed accounts receivable?
- What master data cleanup is needed before automating cash application?
Frequently Asked Questions
Do I need EBICS to get bank statements into cash application?
No. EBICS is the standard route for banks in Germany, France, Switzerland and Austria, while US banks and accounts elsewhere typically use bank-hosted SFTP, a bank API or your ERP’s own bank interface. Transformance reads the statement by whichever route you agree with your bank.
What is the difference between EBICS, SFTP and a bank API?
EBICS is a standardized, signed file exchange with a key exchange. SFTP is a bank-hosted folder you collect files from. A bank API returns balances and transactions on request, not a closed statement.
Which EBICS permission does cash application need?
A right to retrieve statements without releasing payments. In the EBICS specification, signature classes E, A and B authorise orders such as payments, so ask for a user without them; your bank defines and confirms the exact terms in its own agreement.
Which statement format should I ask my bank for: camt.053, camt.052 or MT940?
Ask for camt.053 as the end-of-day statement, add camt.052 only if you want intraday postings, and camt.054 for batch booking detail. German banks have been replacing MT940 and MT942 with camt since November 2025; US banks typically deliver BAI2.
Which ERPs, company sizes and payment volumes does this work for?
Transformance reads bank statements for teams on SAP S/4HANA, SAP ECC, NetSuite, Microsoft Dynamics 365 Finance & Operations and Business Central or Odoo, all in production with customers; Oracle and Infor are supported. It suits companies with 250 to 2,000+ employees and from under 1,000 to over 100,000 payments a month.
How long does it take to connect bank statement data?
The ERP connection typically takes 2-3 days, and your IT team may be involved. Full rollout takes up to 4-8 weeks, and a proof of value runs in 4-5 weeks on one entity (Transformance customer data, 2026). The bank’s own steps, such as activating an EBICS user, follow its timetable.
What does it cost to connect bank statements?
It depends on scope and the number of entities, so there is no single figure. Book a Call and we scope your accounts, banks and entities 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.




