Guides
  1. DDM
  2. Configuration & Setup

Data Exchange & File Options

The DDM Program relies on the exchange of data between the Participating Institution and R&T. Depending on the institution's technology stack and volume, this exchange is managed through either an automated file process or a manual "DDM Lite" self-service process.

Role of Data Exchange

The Data Exchange layer is responsible for:

  • Receiving inbound data from Participating Institutions
  • Validating and normalizing data formats
  • Ensuring data integrity prior to processing
  • Distributing outbound data and reporting

This layer abstracts differences across core systems and integration methods, enabling consistent processing within the DDM Program.

Data Exchange Methods

Participating Institutions can exchange data with R&T using one of the following methods:

  • File-Based – The most common approach, using batch file transfers aligned to end-of-day or scheduled processing
  • API-Based – Enables programmatic, real-time or near real-time interaction with DDM Program capabilities
  • Portal-Based (CAP / DDM Lite) – Manual, user-driven interaction through the Client Access Portal (CAP)

The appropriate method depends on:

  • Core system capabilities
  • Transaction volume
  • Desired level of automation

Automated Process (Standard)

Most Participating Institutions use automated file transfers generated during their end-of-day (EOD) processing. R&T works with various software providers (e.g. bank core processors, trust system accounting platforms) and service bureaus to facilitate these connections.

Intake Files from Participating Institution to R&T

  • Account Registration File: Used to open new accounts or update existing account details.

  • Transaction File: Contains the daily deposit and withdrawal activity.

If a transaction is received for an account not yet created, the system will automatically open a "no registration" template account to prevent deposit transactions from being rejected.

Note: Accounts without registration data cannot receive access to deposit insurance coverage until data is provided.

Outbound Files from R&T to Participating Institution (Optional)

  • Balance File: Provides daily Customer balances and Month-to-Date (MTD) accrued interest.

  • Client Deposits per Bank (CDB) File: Lists account balances at each specific Receiving Institution for transparency.

  • Interest Posting File: Available in ASCII or NACHA formats to record interest credits.

  • Automated Entry/GL File: A customized file formatted to automate the posting of daily entries (e.g., accruals)to the institution's General Ledger.

Non-Automated Process (DDM Lite)

For Participating Institutions that do not utilize automated file transfers, R&T provides a manual option. This requires the use of the Client Access Portal (CAP) to utilize the self-service capabilities to manage account creation/updates and transaction activity.

Note: DDM Lite users do not receive outbound files from R&T.

Data Exchange Responsibility Models

Depending on the institution’s setup, data may be transmitted by:

  • The Participating Institution directly
  • A Core Processor or service provider on behalf of the Participating Institution
  • A third-party system aggregating or managing data transmission

This impacts:

  • File format alignment
  • Testing coordination
  • Ongoing operational support

Core Integration

R&T maintains relationships with many core banking processors and trust accounting system platforms. Implementation requirements vary by provider. Contact your Relationship Manager or Sales Executive to discuss existing integrations and determine the appropriate implementation approach for your organization.

  • Modules: Some providers require a specific software module to generate R&T-compatible files.

  • Queries: Other providers use specific database queries to extract the necessary registration and transaction data.

  • Core Fact Sheet: Technical specifications for file formats, headers, and required fields are provided during implementation and onboarding.

API-Based Integration (Advanced)

In addition to file-based exchange, some Participating Institutions may integrate with R&T using APIs.

APIs enable:

  • Real-time or near real-time data exchange
  • Programmatic access to account and transaction data
  • Reduced reliance on batch file processing

API adoption depends on:

  • Core system capabilities
  • Integration maturity of the institution

What's Next

Updated 18 days ago

Did this page help you?

R&T Deposit Networks, LLC, R&T Deposit Marketplace, LLC, R&T Deposit Solutions, LLC and R&T Deposit Programs, LLC (each d/b/a R&T Deposit Solutions), each a Delaware limited liability company, (together, “R&T”) provide administrative, recordkeeping, and/or other services to banks, credit unions, trust companies, wealth management firms, broker-dealers and other institutions with respect to deposit placement and sweep programs, including the Demand Deposit Marketplace® (DDM®), Certificate of Deposit Marketplace Exchange℠ (CDMX℠) and R&T Insured Deposits℠ (RTID®) programs, as well as other services. An affiliate of R&T, Stable Custody Group II LLC (“Stable”), acts as agent of participating sending institutions under the DDM and CDMX programs. R&T and Stable, together, “we”, “us” or “our”. All of our services are provided subject to the terms and conditions of the written agreements and/or agency appointments between us and our clients with respect to those services, and we provide no representations or warranties, express or implied, except as expressly set forth in those written agreements and/or appointments. Click here for our legal and other disclosures. We are not an FDIC or NCUA-insured institution. FDIC insurance only covers the failure of an FDIC-insured institution. NCUA insurance only covers the failure of an NCUA-insured institution. Certain conditions must be satisfied for FDIC and NCUA pass-through deposit insurance coverage to apply. Click here for a list of the FDIC and NCUA-insured institutions with which R&T has a direct or indirect business relationship for the placement of deposits under the DDM, CDMX, and RTID programs, and into which a participating institution may place deposits (subject to the terms of those programs and any opt-outs by the participating institution and/or its customers). While the DDM, CDMX, and RTID programs provide access to an expanded level of FDIC or NCUA deposit insurance coverage on funds placed into the programs (subject to program terms and applicable laws, regulations and guidance, including pass-through insurance coverage requirements), the DDM, CDMX and RTID programs, themselves, as well as our other service offerings, are not insured or guaranteed by the FDIC or NCUA, are not deposits, and may lose value. We are not an affiliate of an FDIC or NCUA-insured institution, we are not an office, division, or sub-division of the FDIC or NCUA, and we are not associated with the FDIC or NCUA or office, division, or sub-division thereof. The primary objective of the DDM, CDMX, and RTID programs is to provide customers with convenient access to expanded deposit insurance coverage on their funds (and not for investment enhancements, higher rates of returns or profits). R&T®, Reich & Tang®, Demand Deposit Marketplace®, DDM®, DepositView®, CDMX®, and RTID® are registered marks, and R&T Direct℠ is a pending mark of R&T Deposit Networks, LLC. of R&T Deposit Networks, LLC. IDEA℠, Certificate of Deposit Marketplace Exchange℠, R&T Insured Deposits℠ are unregistered service marks of R&T Deposit Networks, LLC.

© 2026 R&T Deposit Networks, LLC

Privacy Policy Privacy Policy – CA Terms of Use Legal Disclosures Receiving Institution Lists DDM Program Limit Do Not Share My Personal Information Cookies