Financial services
Financial Services EDI, API & Secure File Transfer
Payments, statements and remittance, exchanged securely and audited
Banks, processors and corporate treasury teams exchange payment files, statements and remittance data every day. ECOM runs those exchanges securely and reliably, with the audit trail regulators and clients expect.
Zero Trust experience. ECOM has implemented Zero Trust EDI and Zero Trust MFT for financial institutions.

- Who we help
- Banks, payment service providers, and corporate treasury, accounts payable and cash application teams.
- What we connect
- Your ERP, treasury and banking systems to payment, statement and remittance files, over the connection each bank requires.
- Problems we solve
- Many bank file formats, files that fail silently, thin audit trails and manual reconciliation.
- Even without EDI
- Some partners send PDF statements or remittance by email. ECOM can bring those into structured data as well.
What is financial EDI and file exchange?
Financial institutions exchange payment and reporting data with corporate clients and other institutions using standards such as X12 820 and 823, ISO 20022 XML messages, BAI2 statements and NACHA ACH files, typically over secure file transfer channels such as SFTP, Connect:Direct or AS2. Reliability, security and auditability are critical because the data moves money.
Who you connect with
Who a financial institution or treasury team exchanges files with
Money moves through banks and networks; the files describe each step.
-
Banks
Payments, statements, balances
SFTP, AS2, bank formats -
Corporate clients
Instructions, reports
Files and APIs -
Payment processors
Batches, settlements
Secure file transfer -
Payees and suppliers
Remittance advice
EDI and email -
Regulators and auditors
Reports, evidence
Agreed reports
Your role
Who uses it, and the scenarios ECOM solves
Banks, treasury teams, lockbox operations and service providers use the same formats differently. Each scenario below shows the problem, what ECOM does about it and the business benefit.
-
Banks serving corporate clients
Banks onboarding corporate clients that send payment files and expect reports.
- How it runs
- Clients send files in supported formats. You acknowledge them, process payments and return statements and balance data.
- Documents
- 820 Payments and Remittance
- pain.001
- camt.053
- BAI2
- Systems
- Payments engine, file gateway, client onboarding.
- Typical problem
- Each corporate client sends its own variation of a file, so every onboarding becomes a mapping and testing project, and a malformed file is often found only after the client asks where its payment is.
- How ECOM helps
- ECOM sets up each client connection and format, validates every file on arrival, matches acknowledgments and rejections to the file and its items, and alerts the bank team when a file fails or misses its cut-off.
- Business benefit
- New clients go live with less manual work, failed files are found sooner, and the bank can show what happened to every file.
-
Corporate treasury and payables
Companies paying suppliers and tracking cash across several banks.
- How it runs
- Payment batches are sent to each bank in its format. Statements and balance reports are loaded and matched.
- Documents
- pain.001
- camt.053
- BAI2
- Systems
- ERP, treasury system, bank connections.
- Typical problem
- Payment files go to several banks, each with its own layout and connection method. A rejected file or item can go unnoticed until a supplier asks about a missing payment.
- How ECOM helps
- ECOM builds each bank's payment format from ERP data, sends it over the connection that bank requires, tracks the acknowledgment and loads statements and balance reports for cash positioning.
- Business benefit
- Treasury sees accepted and rejected payments as the bank reports them, cash positions rest on statements that arrived, and there is one record of every file sent.
-
Lockbox and cash application
Teams that receive payments and need the remittance detail to apply them.
- How it runs
- Lockbox and remittance data arrive from the bank or customer and are matched to invoices.
- Systems
- Bank files, ERP, cash application.
- Typical problem
- Payments arrive without remittance detail the cash application team can use, or the detail arrives in a different format from the payment, so items sit unapplied and customers are chased for information the bank already had.
- How ECOM helps
- ECOM brings lockbox, 820 and statement data into structured form, including remittance that arrives as PDF or email, and passes it to cash application and the ERP; items that cannot be matched go to the team that owns them as exceptions.
- Business benefit
- Fewer unapplied payments, less manual keying of remittance and faster, better-documented reconciliation.
-
Payment and file service providers
Providers that move files between clients and institutions.
- How it runs
- Files are received, validated, transformed and delivered, with delivery records for each client.
- Documents
- pain.001
- camt.053
- Systems
- File gateway, transformation, monitoring.
- Typical problem
- Clients expect proof that every file was delivered and acted on, but file movement is spread across scripts, older transfer servers and mailboxes that are hard to monitor or audit.
- How ECOM helps
- ECOM runs governed secure file transfer, including on IBM Sterling, with per-client scope, monitoring against cut-off windows and a delivery record for every file.
- Business benefit
- A single audit trail for client and regulator questions, fewer missed windows and less dependence on aging scripts and servers.
How to read this page: a standard or system named here shows where a requirement is published or what ECOM can connect. It does not mean ECOM has a verified partnership with any named company, and your own contracts and partners define the final requirements.
How the workflow runs
From payment file to settlement: four different confirmations
A file that arrived is not a payment that was accepted, and an accepted payment is not yet settled. Each step below answers a different question, and each can fail separately.
- Corporate client→Bank pain.001 Payment file delivered Transport delivery: the secure connection shows the file arrived.
- Bank→Corporate client pain.002 Technical acknowledgment and status File and item status: readable, valid, or rejected with a reason.
- Bank→Payee Settlement Funds move on the bank's schedule and the payment network's rules.
- Corporate client→Payee 820 Remittance advice Which invoices the payment covers, where this is used.
- Bank→Corporate client camt.053 Account statement Booked entries: the account record of what settled.
- Bank→Corporate client BAI2 Balance report Balances and transactions, where the bank offers it.
- 01
Prepare the payment file
Payments are built from ERP data in the bank's required format and validated before they are sent.
- 02
Transport delivery
The file travels by the connection the bank supports, such as SFTP or AS2. A successful transfer shows the file arrived, not that the bank accepted it.
- 03
Technical acknowledgment
The bank reports whether the file and its items were readable and valid. Status messages are matched to the file and to each item, so a rejected payment does not go unnoticed.
- 04
Business acceptance and settlement
The bank accepts the payment under its own rules and cut-off times, and funds settle on the payment network's schedule. Timing depends on the bank and the payment type.
- 05
Statements, reports and audit trail
Statements and balance reports are loaded for cash positioning and reconciliation, and every file keeps a record of who sent it, when and what happened to it.
Beyond EDI
Every way payment and statement data arrives
Payment and statement data comes in standard formats, bank layouts and documents. ECOM prepares each for your systems.
How it arrives
- XMLISO 20022 pain.001 and camt.053
- Flat fileBAI2 and bank-specific files
- EDI820, 823 and 822
- APIBank and platform APIs
- SpreadsheetPayment lists and reports
- PDF or emailStatements and remittance advice
ECOM
- Validate every file or message
- Map to each partner's rules
- Deliver, acknowledge and monitor
Where it goes
- Bank instructions
- Treasury systems
- Cash application
- Audit records
Challenges
Integration challenges in financial services
Many client formats
Corporate clients use different ERPs and file formats for payments and reporting.
Security and audit pressure
Every transfer must be encrypted, controlled and traceable.
Legacy file infrastructure
Older transfer platforms and scripts are difficult to maintain.
How we help
How ECOM supports financial services companies
-
Secure file transfer
Secure SFTP, FTPS, AS2 and Connect:Direct exchanges, including on IBM Sterling.
-
Format transformation
Convert between ERP payment files and bank formats such as ISO 20022, BAI2 and NACHA.
-
Client onboarding
Set up and test new corporate client connections.
-
Monitoring and alerting
Track time-critical files against cut-off windows.
-
IBM Sterling administration
Support for Sterling File Gateway and Connect:Direct environments.
-
Controlled access and audit
Each partner connection is limited to what that relationship needs, transfers are monitored, and every file leaves an audit record, so exposure is smaller and security reviews have evidence to work from.
Systems integration
The systems a financial file exchange touches
File exchange sits between corporate systems and bank systems, so it carries both sets of controls.
From
- ERP payment files
- Bank statements
- Remittance data
- Client files
ECOM · Financial exchange
- Validate each file
- Transform per bank
- Secure delivery
To
- Bank instructions
- Treasury systems
- Cash application
- Audit records
Scroll sideways to see every column. With a keyboard, select the table and use the left and right arrow keys.
| System | What flows | What to plan for |
|---|---|---|
| ERP and payables | Payment batches out; statements and remittance back. | Payment data must be complete before a file is created, or the bank rejects it. |
| Treasury management | Balances and statements in; payment instructions out. | Cash positions depend on statements arriving on time. |
| Bank and network connections | Secure transfer of files and acknowledgments. | Each bank specifies protocols, certificates and schedules. |
| Cash application and reconciliation | Remittance and statement data matched to invoices. | Unmatched items are returned as exceptions to the team that owns them. |
Bank guides
Bank guides and related pages
Large banks publish their own file requirements. These guides summarize common ones.
-
JPMorgan Chase
Documents, formats and connection requirements for JPMorgan Chase.
JPMorgan Chase in detail -
Wells Fargo
Documents, formats and connection requirements for Wells Fargo.
Wells Fargo in detail -
Bank of America
Documents, formats and connection requirements for Bank of America.
Bank of America in detail -
Citi
Documents, formats and connection requirements for Citi.
Citi in detail
Financial services and insurance
Banking file exchange is not insurance data exchange
Both involve money and files but they differ in formats, parties and controls.
-
Financial services (this page)
Payment instructions, statements, balances and remittance between banks, clients and service providers.
-
Insurance
Policy, enrollment, premium and claims between carriers, administrators and employers.
Insurance in detail -
Professional services
Service firms invoicing through client procurement networks and billing formats.
Professional services in detail -
Financial document automation
Converting invoices, remittances and statements into data your systems read.
Financial document automation in detail
Documents and standards
Common transactions
Examples of financial formats and documents exchanged between institutions and their clients.
Scroll sideways to see every column. With a keyboard, select the table and use the left and right arrow keys.
| Code | Document | What it does |
|---|---|---|
| 820 | Payments and RemittanceX12 name: Payment Order/Remittance Advice | Payment instructions and remittance details. |
| 823 | Lockbox ReportsX12 name: Lockbox | Reports lockbox deposits. |
| 822 | Account Analysis | Reports account service charges. |
| pain.001 | ISO 20022 Customer Credit Transfer Initiation | Payment initiation from client to bank. |
| camt.053 | ISO 20022 Bank to Customer Statement | End-of-day account statement. |
| BAI2 | Cash Management Balance Reporting | Balance and transaction reporting. |
Scenarios
Typical integration scenarios
A client's payment file is rejected overnight
Problem: the file fails validation and nobody sees it until the client calls. ECOM validates on arrival, matches the status message to the file and its items and alerts the owning team. Benefit: the team learns of the rejection when the bank reports it, not when the client asks, and can correct and resubmit within the bank's cut-off times.
A statement does not arrive before the cash-positioning cut-off
Problem: treasury plans cash on balances that have not arrived. ECOM monitors expected statements and balance reports against their windows and raises the miss. Benefit: the team knows early and can chase the bank or use an alternative source.
Remittance detail does not match the payment
Problem: a payment arrives with remittance that is missing, late or in another format, so it stays unapplied. ECOM structures the remittance, matches it to the payment and sends unmatched items to the owning team. Benefit: more payments applied without manual keying and fewer customer chases.
Moving off an aging transfer server
Problem: scripts and older servers carry client files with little monitoring and no clear owner. ECOM moves the connections to a governed secure file transfer platform with scoped access and logging. Benefit: a supportable platform and an audit trail that stands up to client and regulator review.
Trading partners
Financial Services partners we connect with
Examples of financial services trading partners ECOM can connect your business with.
Logos are trademarks of their respective owners. Their display does not imply endorsement of ECOM Specialist.
Frequently asked questions
Which secure protocols do you support for banks?
Common protocols include SFTP, FTPS, AS2 and IBM Sterling Connect:Direct, with PGP encryption where required.
Can you convert ERP payment files to ISO 20022?
Yes. PRISM can transform ERP payment output into ISO 20022 and other bank formats, subject to each bank's specifications.
Does ECOM work with corporate treasury teams too?
Yes. ECOM helps corporates connect to multiple banks as well as helping institutions connect to clients.
What is the difference between BAI2 and ISO 20022 camt.053?
Both report account activity. BAI2 is a long-used fixed-format layout. camt.053 is an XML message in the ISO 20022 family. Which one a bank offers depends on the bank and the account.
Does a successful file transfer mean the bank accepted the payment?
No. A completed transfer shows the file arrived. The bank's status or acknowledgment message says whether the file and its items were readable and valid, and the bank accepts and settles the payment under its own rules and cut-off times. Matching each of these to the file, and alerting on rejections, is how a failed payment is found before the payee asks.
Why do banks require different formats?
Banks support standards through their own implementation guides, with their own required fields and versions. A client sending to several banks usually needs a mapping for each.
What audit records are kept for file transfers?
Records show what was sent or received, when, by whom and what happened next. The retention period and detail are agreed with your compliance teams.
How to get started
Tell us who you trade with and what you run
- Send the basics. Your trading partners, the documents they require, your ERP or other systems, and any deadline.
- We review the requirements. An ECOM specialist looks at the partner programs, document formats and connections involved.
- You decide how to proceed. We outline the options, including managed services or software, for you to compare.
Helpful to share, but not required
You do not need an implementation guide or a finished requirements list to contact us. If you have these, they speed things up:
- Your banks and the formats and connections they require.
- Your ERP and treasury systems.
- Whether you are a bank, service provider or corporate client.
- Any compliance requirements on the files.
See how ECOM works with customers: case studies ERP integrations compare delivery options (software, managed or team-based)
Talk to an EDI/API expert
Tell us about your partners, systems and goals. We will show you how PRISM and our team can help.



















