Trading partner network

Financial Services EDI and API integration

Banks, asset managers, payment networks, fintechs and insurers. ECOM connects your business with financial institutions through EDI, APIs, managed file transfer and portal automation, integrated with your ERP.

Trading partner network

Financial institutions we connect with

Through its network, ECOM can connect your business with 3.1M+ trading partners. The 142 financial institutions below are highlights, by name and business segment. Companies with an integration guide link to it, and each guide says whether it rests on the company’s own documents or on typical industry practice.

How the exchange works

How financial institutions exchange business documents

Exchange with banks is mostly about payments and cash reporting. Banks accept payment files and send back statements and lockbox data in their own formats, often several per bank, so the work is mapping each bank’s format to your ERP and treasury processes.

Common documents with financial institutions
DocumentWhat it does in this relationship
EDI 820Payment Order/Remittance Advice Payment order and remittance advice: what is being paid and which invoices it covers.
EDI 823Lockbox Lockbox data: customer payments received by the bank, with remittance details.
ISO 20022 The XML message standard banks use for payment initiation and account statements.
BAI2 A bank file format for prior-day and intraday balance and transaction reporting.
NACHA The file format for US ACH payments.

What onboarding a new financial services partner usually involves

  1. Collect each bank’s file specifications and its connectivity and security requirements.
  2. Map payment runs, statements and lockbox files to your ERP and cash application process.
  3. Test with the bank’s test environment, including rejected payments, before sending live files.

Integration guides

Financial Services integration guides

Detailed guides covering documents, workflows, connectivity and ERP options for specific companies. A selection is shown here; search all 128 financial institutions guides in the directory above.

Adyen EDI integration

How EDI and API integration with Adyen typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Adyen.

Read the guide

Allianz EDI integration

How EDI and API integration with Allianz typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Allianz.

Read the guide

American Express EDI integration

How EDI and API integration with American Express typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with American Express.

Read the guide

Apollo Global Management EDI integration

How EDI and API integration with Apollo Global Management typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Apollo Global Management.

Read the guide

Bank of America EDI integration

A guide for corporate finance teams automating payments, bank statements and remittance data with Bank of America.

Read the guide

BlackRock EDI integration

How EDI and API integration with BlackRock typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with BlackRock.

Read the guide

Blackstone EDI integration

How EDI and API integration with Blackstone typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Blackstone.

Read the guide

Block EDI integration

How EDI and API integration with Block typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Block.

Read the guide

BNY EDI integration

How EDI and API integration with BNY typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with BNY.

Read the guide

Capital One EDI integration

How EDI and API integration with Capital One typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Capital One.

Read the guide

Charles Schwab EDI integration

How EDI and API integration with Charles Schwab typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Charles Schwab.

Read the guide

Chime EDI integration

How EDI and API integration with Chime typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Chime.

Read the guide

General EDI flow

How EDI with your trading partner typically works

Many trading partners do not publish their EDI or API specifications. This is the general sequence most programs of this kind follow.

  1. 850 Purchase order

    From your trading partner

    The buyer sends the order: items, quantities, prices, ship-to and requested dates.

  2. 855 Order acknowledgment

    From you to your trading partner

    You confirm, change or reject the order, where the partner asks for it.

  3. 856 Advance ship notice

    From you to your trading partner

    You tell the buyer what is on the shipment, with the carton and label details the buyer needs to receive it.

  4. 810 Invoice

    From you to your trading partner

    You bill for what shipped, in the format the buyer's payables system expects.

  5. 997 Functional acknowledgment

    Both directions

    Each side confirms that every file it received was readable. A rejected file is corrected and resent.

Need help with the specification?

Tell ECOM which program you are in and what the partner has given you. We help you read it, confirm the applicable requirements, map them to your systems and test against them. Do not send passwords or EDI identifiers with your request.

Connecting with a financial services partner not listed here?

ECOM connects businesses with partners of every size using their published EDI, API or file requirements.