Payments, remittance and statements
Payment files, remittance advice and account statements move between named systems with partner-specific identities, so each connection can only reach the files meant for it.
Financial Services integration
A guide for finance teams automating payments and bank reporting with Citi through CitiConnect and CitiDirect.
At a glance
The industry, the document flow and the outcome for your team. Illustrations only: they show typical practice, not a specific Citi program or a customer relationship.
Tell us which documents you exchange with Citi, which ERP you run and when you need to be live. A specialist will outline the connection, mapping and testing plan. This page is a guide based on typical practice; it does not mean ECOM works with Citi.
Prefer to call? Sales 972-836-7750 or email sales@ecom-specialist.com.
Integration and onboarding
Overview
Who this is for: Corporate treasury and finance IT teams banking with Citi across one or more countries.
Citi serves many multinational corporations, which often need to send payments and receive reporting across many countries through a consistent channel. Citi's connectivity offering for files, CitiConnect, lets corporate systems exchange payment and reporting files with the bank automatically, while CitiDirect provides online access.
According to Citi's own country pages, CitiConnect for files supports ISO XML as its most widely used format, along with formats such as EDIFACT and SAP IDoc, and supports secure transport including FTPS, SFTP, AS2 and HTTPS. ISO 20022 XML has been accepted for file import for many years, and the industry continues to move from older message types to ISO 20022.
Supported formats and payment types can differ by country, so multinational clients should confirm the specifications for each country and account with their Citi team. ECOM helps finance teams generate bank-ready files from ERP payment runs and load reporting back for reconciliation.
Workflows
General guidance: typical flows in this industry, not Citi's published process.
Documents and APIs
General guidance. We could not verify Citi's EDI requirements from a published source, so these are documents commonly exchanged in this industry, not Citi's confirmed requirements. Confirm the list, versions and programs with Citi.
Scroll sideways to see every column. With a keyboard, select the table and use the left and right arrow keys.
| Document | Name | Direction | Program | Status | Purpose |
|---|---|---|---|---|---|
| pain.001 | ISO 20022 Customer Credit Transfer Initiation | To Citi | Not stated | General guidance | Initiates payments. |
| pain.002 | ISO 20022 Payment Status Report | From Citi | Not stated | General guidance | Reports payment acceptance or rejection. |
| camt.053 | ISO 20022 Bank to Customer Statement | From Citi | Not stated | General guidance | Provides account statements. |
| EDIFACT | EDIFACT payment and reporting messages | Both directions | Not stated | General guidance | Supported in some countries and setups. |
| IDoc | SAP IDoc formats | Both directions | Not stated | General guidance | Supported for SAP-based clients in some setups. |
Connectivity
Automated file exchange using FTPS, SFTP, AS2 or HTTPS, according to Citi.
General guidance
Citi's online banking platform supports file import and reporting.
General guidance
Challenges
Formats and payment types can vary by country, which complicates global payment factories.
Moving from legacy formats to ISO 20022 requires remapping and testing.
Payment files need encryption, approval workflows and audit trails.
Automation options for Citi clients
ECOM helps you automate the exchange, connect it to your systems, and see what needs action. Citi sets its own requirements; ECOM confirms which options fit yours.
Automate trading partner transactions and ERP integration through our iPaaS, SaaS, and EDI Team as a Service offerings.
Learn more about Fully Automated EDI/APIReceive orders and manage trading partner transactions through a browser-based portal, without requiring direct ERP integration.
Learn more about WebEDIConvert documents received through email or in PDF, Excel, Word, JPG, PNG, and other supported formats into structured data for automated processing, reducing manual data entry.
Learn more about SmartConvertAutomate repetitive order processing and transaction tasks in third-party portals such as SAP Ariba, Coupa, and other customer or supplier portals, reducing the work customer service representatives must log in and complete manually.
Learn more about WebConnectPRISM Supply Chain Automation Foundation
One platform beneath every option. Use one, or combine them for different partners and documents.
Connect order processing, shipping documentation, trading partner requirements, and performance monitoring through one coordinated workflow. These capabilities help teams improve shipment accuracy, reduce manual work, address compliance risks, and respond to exceptions before they affect customers.
ECOM connects ERP payment factories and cash management to Citi, including SAP environments that exchange IDoc or ISO 20022 files.
Generate country-specific bank files and load reporting into your ERP.
ProductExchange files with Citi securely with monitoring and audit trails.
IndustrySee how ECOM supports financial data exchange.
Zero Trust for financial data exchange
Financial exchanges with Citi carry payment instructions, remittance detail, account data and personal information. A Zero Trust design assumes no connection, file or user is safe by default.
ECOM has implemented Zero Trust EDI and Zero Trust MFT for financial institutions, and applies the same practices in trucking.
For a financial exchange this means fewer exposed credentials, same-day visibility of a missing or changed payment, remittance or settlement file, faster reconciliation and exception handling, and a transfer record that supports audits and partner security reviews. The design is scoped to your systems and requirements.
Every connection proves who it is: partner-specific accounts with SSH keys or certificates over SFTP, FTPS, HTTPS or AS2, never a shared login.
Business outcome: A lost or reused credential affects one partner, not all of them.
Each partner and user reaches only its own folders, file types and actions. Internal user permissions are managed centrally and reviewed with you.
Business outcome: A mistake or compromise in one account stays limited to what that account could reach.
Partners are kept apart by account and file area. Where your design calls for it, a proxy or DMZ keeps outside connections away from internal systems. The design follows your architecture.
Business outcome: Outside connections do not land directly on your internal systems.
Encrypted protocols in transit and PGP for files at rest. Encryption protects the data. It is one control, and not Zero Trust on its own.
Business outcome: Less exposure if a file is intercepted or a file store is reached.
Partner keys and certificates are managed centrally. Renewal and rotation are planned with you, so an expiring certificate does not stop a flow.
Business outcome: Fewer outages caused by an expired certificate or key.
Real-time transfer status and alerts for late, missing or failed files, so unexpected access or a broken flow is seen quickly.
Business outcome: Late, missing or failed files are noticed early, before they hold up cash application or reconciliation.
Every transfer is logged with sender, receiver, time and outcome, which supports your own review and audit work.
Business outcome: You can answer who sent what and when, for your own audits and partner reviews.
Payment files, remittance advice and account statements move between named systems with partner-specific identities, so each connection can only reach the files meant for it.
Balance and lockbox reports reach cash application and treasury systems without shared logins or open folders.
Settlement files and reconciliation reports are matched to what was expected, and late or missing files raise an alert.
Fintech partners, vendors and subsidiaries each connect with their own credentials and limited scope, and every connection can be reviewed or removed on its own.
Zero Trust is an approach, not a product or a certification. ECOM covers the EDI and file-transfer side. Your identity, network and endpoint controls stay yours, and so does the assessment of your own compliance obligations. ECOM does not guarantee compliance or any security outcome. Citi may set its own security requirements, which come first.
Talk to an EDI/API Expert about Zero Trust Managed file transferSecure proxy and DMZ designSecurity at ECOM
General EDI flow
The documents, their order and the timing are Citi's to set; this is the general sequence most programs of this kind follow.
pain.001 ISO 20022 Customer Credit Transfer Initiation
From you to Citi
Initiates payments.
pain.002 ISO 20022 Payment Status Report
From Citi to you
Reports payment acceptance or rejection.
camt.053 ISO 20022 Bank to Customer Statement
From Citi to you
Provides account statements.
EDIFACT EDIFACT payment and reporting messages
Both directions
Supported in some countries and setups.
IDoc SAP IDoc formats
Both directions
Supported for SAP-based clients in some setups.
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.
Next step
Each request goes to an ECOM EDI specialist with Citi's name attached, so the reply starts from your program.
Send us Citi's guide or your program details; we explain the documents, rules and options for meeting them.
Request a requirements reviewOrders in, ship notices and invoices out, from the ERP and warehouse systems you already run.
Discuss ERP integrationBuild, test and certify each Citi document, then go live with monitoring from the first file.
Plan testing and certificationCitiConnect is Citi's connectivity offering that lets corporate systems exchange payment and reporting files with Citi automatically.
Citi's country pages list ISO XML as the most popular format, with others such as EDIFACT and SAP IDoc. Confirm support for your countries and accounts.
Yes. ECOM can generate country-specific payment files from your ERP and manage secure delivery and reporting.
This page is an integration guide and does not indicate a partnership with Citi. ECOM builds integrations to the bank's published specifications.
This guide summarizes publicly available information as of October 2026. Citi sets its own requirements and can change them at any time; your Citi implementation guide, supplier portal or account contact is the authoritative source for your program.
Citi is a trademark of its owner. Its mention does not imply endorsement of, or a partnership with, ECOM Specialist.
Related integrations
How EDI, file and API integration with Carlyle typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Carlyle.
How EDI and API integration with Charles Schwab typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Charles Schwab.
How EDI and API integration with Chime typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Chime.
How EDI, file and API integration with Churchill Mortgage typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Churchill Mortgage.
How EDI, file and API integration with Citizens Bank Home Mortgage typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Citizens Bank Home Mortgage.
How EDI, file and API integration with CMG Financial typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with CMG Financial.
Tell us about your Citi program, documents and ERP. We will outline the connection, mapping and testing plan.