5.1 CCD/CCD+ and CTX: Corporate Payments, Addenda & EDI / ASC X12 Formatting

5.1 CCD/CCD+ and CTX: Corporate Payments, Addenda & EDI / ASC X12 Formatting

Core Principle: Business-to-Business (B2B) Automated Clearing House (ACH) transactions represent the largest dollar-volume segment of the ACH Network. Commercial payments are classified under specialized Standard Entry Class (SEC) codes designed to transmit corporate funds alongside complex electronic remittance data. The two primary commercial architectures are Corporate Credit or Debit (CCD/CCD+) and Corporate Trade Exchange (CTX), whose credit entries fall within Uniform Commercial Code Article 4A while their debit entries rely on the Nacha Rules, authorization agreements and other applicable law.

---

1. Commercial Payments Architecture: CCD vs. CTX Overview

Commercial entities utilize the ACH Network for treasury management, supplier disbursements, vendor settlements, tax remittances, intra-company cash concentration, and trade payments. Unlike consumer transactions governed by the Consumer Financial Protection Bureau's (CFPB) Regulation E, commercial entries operate under business-to-business legal standards where speed, remittance capacity, and finality are paramount.

+---------------------------------------------------------------------------------------------------------+
|                                 COMMERCIAL SEC CODE TAXONOMY                                            |
+---------------------------------------------------------------------------------------------------------+
| SEC Code | Full Name                     | Addenda Capacity    | Primary Business Use Case              |
+----------+-------------------------------+---------------------+----------------------------------------+
| CCD      | Corporate Credit or Debit     | 0 Addenda Records   | Cash concentration, simple vendor pay  |
| CCD+     | CCD with Addenda Record       | Exactly 1 Addenda   | Tax payments (TXP), Child support (DED)|
| CTX      | Corporate Trade Exchange      | 0 to 9,999 Addenda  | Supply chain EDI, ANSI ASC X12 820/835 |
+---------------------------------------------------------------------------------------------------------+

---

2. Technical Blueprint of CCD and CCD+

Corporate Credit or Debit (CCD)

A CCD entry is a commercial transaction used to consolidate or disburse corporate funds within an enterprise or between independent business entities. A baseline CCD entry consists of a Company/Batch Header Record (Type 5), one or more Entry Detail Records (Type 6), and a Company/Batch Control Record (Type 8) without any accompanying Addenda Records.

• Payment Direction: Can be originated as an ACH Credit (e.g., vendor disbursement, corporate dividend) or ACH Debit (e.g., cash concentration, authorized corporate account pull).
• Addenda Record Indicator: Field 10 (Position 79) of the Type 6 record is set to 0 (indicating no addenda record follows).
• Common Applications: Intra-company sweeps between subsidiary operating accounts and master concentration accounts, commercial loan fundings, and simple one-to-one B2B transfers.

CCD with Addenda (CCD+)

When an Originator needs to transmit a modest amount of structured remittance information alongside a payment, it appends exactly one (1) Addenda Record (Type 7) to the CCD Entry Detail Record. This structure is universally known as CCD+.

• Addenda Record Indicator: Field 10 (Position 79) of the Type 6 record is set to 1.
• Addenda Record Structure (Type 7):
  • Record Type Code (Position 01): Constant 7.
  • Addenda Type Code (Positions 02–03): Constant 05 (Payment Related Information).
  • Payment Related Information (Positions 04–83): An 80-character free-form or structured alphanumeric field.
  • Addenda Sequence Number (Positions 84–87): Numeric 0001.
  • Entry Detail Sequence Number (Positions 88–94): 7-digit number matching positions 88–94 of the preceding Type 6 record.

CCD+ RECORD RELATIONSHIP
+---------------------------------------------------------------------------------------------+
| Type 6: Entry Detail Record (Positions 01-94)                                               |
| [RTN: 9 digits] [Acct: 17 chars] [Amount: 10 digits] [Addenda Ind: '1'] [Trace: 15 digits]   |
+---------------------------------------------------------------------------------------------+
                                              │
                                              ▼
+---------------------------------------------------------------------------------------------+
| Type 7: Addenda Record (Addenda Type Code '05') (Positions 01-94)                           |
| [Type: '7'] [Code: '05'] [Payment Related Info: 80 characters] [Seq: 0001] [Entry Seq: 7d] |
+---------------------------------------------------------------------------------------------+

Standardized Banking Conventions in CCD+ Addenda

The 80-character Payment Related Information field in a CCD+ entry frequently uses standardized syntax conventions:

1. Tax Payment (TXP) Convention: Used by corporate taxpayers to remit federal, state, and municipal payroll and excise taxes through the Electronic Federal Tax Payment System (EFTPS) or state departments of revenue.
   • Example TXP Segment: TXP*123456789*94101*260930*T*500000*P*0*I*0*\ (Contains Taxpayer ID, Tax Form Type 941, Tax Period Ending Date, and Tax Amount).
2. Deduction (DED) Convention: Standardized format for remitting child support and employee wage garnishments to State Disbursement Units (SDUs).
   • Example DED Segment: DED*CS*123456789*261015*125000*DOE*JOHN*\ (Contains Case ID, Social Security Number, Pay Date, Amount, and Employee Name).
3. Single Touch Payroll / Payment (STP) Convention: Structured format used for specialized automated disbursements.

---

3. Corporate Trade Exchange (CTX) & Electronic Data Interchange (EDI)

The Architecture of CTX

The Corporate Trade Exchange (CTX) SEC code is engineered for sophisticated supply chain payments where a single payment order settles dozens, hundreds, or thousands of individual invoices, credit memos, discounts, and trade allowances.

• Payment Direction: Originated as an ACH Credit or Debit.
• Addenda Record Capacity: Each CTX Entry Detail Record (Type 6) can be accompanied by 0 to 9,999 Addenda Records (Type 7).
• Addenda Formatting: Every Addenda Record uses Addenda Type Code 05 and provides 80 characters of Payment Related Information. Across 9,999 addenda records, a single CTX entry can convey up to 799,920 characters of electronic business data.

CTX DATA STREAM HIERARCHY
+-------------------------------------------------------------------------------------+
| Type 6: CTX Entry Detail Record (Addenda Indicator = '1')                           |
+-------------------------------------------------------------------------------------+
  ├── Type 7: Addenda Record #0001 (Type Code '05') -> ISA/GS EDI Envelope Headers    
  ├── Type 7: Addenda Record #0002 (Type Code '05') -> ST / BPR Payment Order Segment 
  ├── Type 7: Addenda Record #0003 (Type Code '05') -> TRN / N1 Name & Remittance Seg 
  ├── Type 7: Addenda Record #0004 (Type Code '05') -> RMR / REF Invoice #1 Details   
  ├── Type 7: Addenda Record #0005 (Type Code '05') -> RMR / REF Invoice #2 Details   
  │   ... (Up to 9,999 consecutive Addenda Records)                                   
  └── Type 7: Addenda Record #N    (Type Code '05') -> SE / GE / IEA EDI Envelopes    

ANSI ASC X12 & EDI Standards

Electronic Data Interchange (EDI) is the computer-to-computer exchange of standard business documents. CTX entries encapsulate structured EDI messages formatted according to the American National Standards Institute (ANSI) Accredited Standards Committee (ASC) X12 syntax.

Key ASC X12 Transaction Sets in CTX:

• ANSI ASC X12 820 (Payment Order / Remittance Advice): The universal standard for B2B payment instructions and remittance details. It breaks down payment gross amounts, invoice numbers, line-item purchase order data, discount allowances, and freight charges.
• ANSI ASC X12 835 (Healthcare Claim Payment / Advice): Mandated under the Health Insurance Portability and Accountability Act (HIPAA) for electronic healthcare claim reimbursement from health plans to healthcare providers.

Anatomy of an ASC X12 820 Segment Stream in CTX Addenda:

EDI data is structured using data elements separated by element delimiters (commonly *) and segment terminators (commonly \ or ~):

ISO 20022 XML Integration

In modern payments modernization frameworks, CTX addenda records can also encapsulate structured ISO 20022 XML payment messages (such as pain.001 Customer Credit Transfer Initiation and pacs.008 Financial Institution Customer Credit Transfer) or ISO remittance messages (remt.001), allowing domestic ACH to bridge directly into international XML messaging architectures.

---

4. Legal & Regulatory Governance: UCC Article 4A

Unlike consumer ACH entries governed by the Electronic Fund Transfer Act (EFTA) and Regulation E, commercial credit transactions (CCD, CCD+, CTX credits) are governed by Article 4A of the Uniform Commercial Code (UCC 4A), which has been adopted in all 50 U.S. states.

                                  UCC ARTICLE 4A REGULATORY SCOPE
                               ┌───────────────────────────────────┐
                               │ UCC Article 4A: Wholesale Credits │
                               └─────────────────┬─────────────────┘
                                                 │
                     ┌───────────────────────────┴───────────────────────────┐
                     ▼                                                       ▼
       ┌───────────────────────────┐                           ┌───────────────────────────┐
       │ Security Procedures       │                           │ Payment Finality &        │
       │ (Commercially Reasonable) │                           │ Receiver Discharge        │
       └───────────────────────────┘                           └───────────────────────────┘

Key Principles of UCC Article 4A in ACH:

1. Wholesale Funds Transfers: UCC 4A governs commercial credit transfers. It does not apply to debits or to any transaction covered by Regulation E.
2. Commercially Reasonable Security Procedures: An Originator and ODFI must establish a written agreement defining a security procedure (e.g., multi-factor authentication, callback verification, dual control, digital tokens) to verify the authenticity of payment orders.
   • If the security procedure is commercially reasonable and the ODFI proves it accepted the payment order in good faith and compliance with the procedure, the customer/Originator bears the loss of an unauthorized credit entry, unless the customer proves the breach originated from a source outside its control.
   • If the ODFI fails to offer or enforce a commercially reasonable security procedure, the ODFI bears the loss.
3. Payment Finality & Discharge: When the RDFI accepts an ACH credit entry (by crediting the Receiver's account or notifying the Receiver), the underlying debt between Originator and Receiver is legally discharged under UCC 4A-406.
4. Notice of Erroneous Orders (14-Day / 1-Year Rule): Under UCC 4A-304, an Originator must notify its bank within a reasonable time not exceeding 90 days (or a contractually reduced period, commonly 14 to 30 days) of discovering an erroneous payment order to preserve interest compensation claims, with an absolute statutory bar at one year (UCC 4A-505).

---

5. Commercial Returns & Return Reason Code R29

Commercial transactions do not possess the 60-calendar-day dispute right provided to consumers for unauthorized debits. The Nacha Operating Rules enforce strict exception timelines for corporate debits.

The Two-Banking-Day Commercial Return Window

If a commercial entity discovers an unauthorized or erroneous debit to its account (originated under CCD, CCD+, or CTX), the RDFI must transmit the return entry such that it is made available to the ODFI no later than opening of business on the second banking day following the settlement date of the original entry.

$\text{Commercial Return Deadline} = \text{Settlement Date (Day 0)} + 2 \text{ Banking Days (Opening of Business)}$

Return Reason Code R29 (Corporate Customer Advises Not Authorized)

• Application: Used exclusively for commercial SEC codes (CCD, CCD+, CTX) when the corporate Receiver notifies its financial institution that a debit entry was not authorized by the corporate entity.
• Deadline: Strict 2-banking-day rule. If the corporate customer notifies the RDFI after the 2-banking-day window has expired, the RDFI cannot return the transaction through the ACH Network using R29. The corporate customer's sole remedy is direct commercial litigation or arbitration outside the ACH rails.

B2B Trading Partner Agreements

To prevent commercial disputes, corporate trading partners execute bilateral Trading Partner Agreements (TPAs). A robust TPA specifies:

• Authorized SEC codes (CCD+ vs CTX).
• Agreed EDI segment standards (e.g., ANSI ASC X12 version 004010 or 005010).
• Responsibilities for extracting, parsing, and storing remittance records.
• Contingency protocols for handling rejected or returned payment orders.

---

6. Zero-Dollar Remittance Entries

In complex B2B supply chains, trading partners frequently need to transmit remittance data when no actual funds transfer is required—such as when trade credit memos, product returns, or rebates completely offset current invoice liabilities.

Mechanics of Zero-Dollar Entries

• SEC Codes: Originated under CCD or CTX with attached addenda records.
• Amount Field: Formatted with exactly ten zeros (0000000000).
• Transaction Codes (Non-Monetary Demand/Savings/GL Credits):
  • 24: Demand Credit (Zero-Dollar Remittance)
  • 34: Savings Credit (Zero-Dollar Remittance)
  • 44: General Ledger Credit (Zero-Dollar Remittance)
• Function: Moves through the ACH Operator and posts to the RDFI without altering customer account balances, while delivering complete ANSI ASC X12 820 or CCD+ remittance data to the corporate payee's accounts receivable system.

---

7. Comparative Technical Matrix: CCD, CCD+ & CTX