Financial Services integration

Citi payment and reporting integration

A guide for finance teams automating payments and bank reporting with Citi through CitiConnect and CitiDirect.

At a glance

Citi integration, in three pictures

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.

Illustration of a bank building with columns and coins, representing the financial services industry that Citi operates in.
Industry. Financial Services: where Citi operates.
Workflow diagram: your ERP and finance systems exchange documents with Citi through ECOM. You send pain.001; you receive pain.002, camt.053; EDIFACT and IDoc acknowledgments go both ways. Your systems ERP · treasury · finance ECOM integration map · validate · connect · monitor Citi pain.001 pain.001 pain.002 camt.053 pain.002 camt.053 EDIFACT IDoc both ways
Workflow. Documents in each direction. Orange: you send. Blue: you receive. Typical, not confirmed.
Comparison diagram: without integration, documents are re-keyed, files are emailed and rejections are found late; with ECOM, documents are mapped to your ERP, validated and monitored, and exceptions are visible early. Without integration Payments and remittance re-keyed Files emailed or uploaded Rejections found late With ECOM Documents mapped to your ERP Every file validated and monitored Exceptions visible early
Outcome. From manual handling to a monitored flow. No figures: results depend on your setup.

Talk to an EDI/API Expert about Citi

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.

  • Review of Citi's requirements with you, once you have them
  • EDI and API integration with your ERP and finance systems
  • Monitoring and managed service after go-live, if you want it

Prefer to call? Sales 972-836-7750 or email sales@ecom-specialist.com.

Takes about 30 seconds. Phone and note are optional.

Your request is about

Trading partner
Citi

When should we talk?

Times are in your time zone. We use this to schedule the conversation.

We use your details only to respond to your request. See our privacy notice. Prefer to talk? Call Sales at 972-836-7750.

Integration and onboarding

How Citi integration fits your systems

Your systemsERP, treasury and accounting
ECOMMapping, validation, connectivity and monitoringCitiConnect for files · CitiDirect
CitiIts program, documents and requirements
  1. ConfirmConfirm your Citi program, role and the documents it requires.
  2. MapMap each document to your ERP fields and business rules.
  3. ConnectConfigure the connection and security the program needs.
  4. TestTest against the applicable specifications and acknowledgments.
  5. Go liveGo live with monitoring, alerts and exception handling.
Typical implementation path. Exact requirements are confirmed against the applicable specifications during onboarding.

Overview

Understanding Citi integration

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

Typical Citi business workflows

General guidance: typical flows in this industry, not Citi's published process.

Multi-country payment initiation

  1. 1Approve payments in ERP
  2. 2Generate ISO 20022 payment file
  3. 3Transmit via CitiConnect
  4. 4Receive status reports
  5. 5Update payment status

Documents and APIs

Citi documents by program

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.

DocumentNameDirectionProgramStatusPurpose
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

How companies connect

  • CitiConnect for files

    Automated file exchange using FTPS, SFTP, AS2 or HTTPS, according to Citi.

    General guidance

  • CitiDirect

    Citi's online banking platform supports file import and reporting.

    General guidance

Challenges

Common integration challenges

  • Country differences

    Formats and payment types can vary by country, which complicates global payment factories.

  • Format migration

    Moving from legacy formats to ISO 20022 requires remapping and testing.

  • Security and approvals

    Payment files need encryption, approval workflows and audit trails.

Automation options for Citi clients

Four ways to automate. One foundation.

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.

PRISM Supply Chain Automation Foundation

One platform beneath every option. Use one, or combine them for different partners and documents.

Compliance and actionable visibility

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.

Discuss Your Trading Partner Requirements

Zero Trust for financial data exchange

Zero Trust EDI and MFT for your Citi connection

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.

  • Authentication

    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.

  • Least privilege

    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.

  • Isolation

    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.

  • Encryption

    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.

  • Certificate and key management

    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.

  • Monitoring and access controls

    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.

  • Audit trail

    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.

What this means for your data

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.

Account and lockbox reporting

Balance and lockbox reports reach cash application and treasury systems without shared logins or open folders.

Settlement and reconciliation

Settlement files and reconciliation reports are matched to what was expected, and late or missing files raise an alert.

Third-party and fintech access

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.

General EDI flow

How EDI with Citi typically works

The documents, their order and the timing are Citi's to set; this is the general sequence most programs of this kind follow.

  1. pain.001 ISO 20022 Customer Credit Transfer Initiation

    From you to Citi

    Initiates payments.

  2. pain.002 ISO 20022 Payment Status Report

    From Citi to you

    Reports payment acceptance or rejection.

  3. camt.053 ISO 20022 Bank to Customer Statement

    From Citi to you

    Provides account statements.

  4. EDIFACT EDIFACT payment and reporting messages

    Both directions

    Supported in some countries and setups.

  5. IDoc SAP IDoc formats

    Both directions

    Supported for SAP-based clients in some setups.

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.

Next step

Get help with your Citi program

Each request goes to an ECOM EDI specialist with Citi's name attached, so the reply starts from your program.

  • Review Citi's requirements

    Send us Citi's guide or your program details; we explain the documents, rules and options for meeting them.

    Request a requirements review
  • Connect Citi to your ERP

    Orders in, ship notices and invoices out, from the ERP and warehouse systems you already run.

    Discuss ERP integration
  • Testing and certification

    Build, test and certify each Citi document, then go live with monitoring from the first file.

    Plan testing and certification

Citi integration FAQs

What is CitiConnect?

CitiConnect is Citi's connectivity offering that lets corporate systems exchange payment and reporting files with Citi automatically.

Which formats does Citi support for files?

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.

Can ECOM support a multi-country payment factory with Citi?

Yes. ECOM can generate country-specific payment files from your ERP and manage secure delivery and reporting.

Is ECOM a Citi partner?

This page is an integration guide and does not indicate a partnership with Citi. ECOM builds integrations to the bank's published specifications.

Sources and accuracy

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.

Request Citi integration assistance

Tell us about your Citi program, documents and ERP. We will outline the connection, mapping and testing plan.