You are previewing IBM Financial Transaction Manager for Automated Clearing House Services.
O'Reilly logo
IBM Financial Transaction Manager for Automated Clearing House Services

Book Description

Automated Clearing House (ACH) payment volume is increasing every year. NACHA estimates that ACH payments crossed 21 billion several years ago. Financial institutions are re-evaluating their current payment platforms. Financial Transaction Manager is a single interface that can handle ACH needs that cross various platforms. IBM® Financial Transaction Manager for ACH Services provides pre-built support for processing all ACH transactions that flow through financial systems. This includes ingestion, validation, transaction management, and distribution. The robust rules-based environment handles payment routing and exception management, and an automated import and export facility handles ACH processing rules. Further functions include administration, process management, data warehousing, and reporting and extracts.

This IBM Redbooks® publication is written for the business analyst (banker), and the computer administrators responsible for configuration of the system. A business analyst can use this book to see what process within Financial Transaction Manger are associated with their banking terms. A bridge is built from banking terms to configuration terms. A system administrator can look into this publication to see exactly how to configure Financial Transaction Manager for ACH to the needs of their financial institution. By creating reference points for both the business analyst and the system administrator, communication and understanding is enhanced as both teams understand each other's terminology and how to use Financial Transaction Manager for ACH.

Table of Contents

  1. Front cover
  2. Notices
    1. Trademarks
  3. IBM Redbooks promotions
  4. Preface
    1. Authors
    2. Now you can become a published author, too!
    3. Comments welcome
    4. Stay connected to IBM Redbooks
  5. Chapter 1. Introduction
    1. 1.1 Overview of Financial Transaction Manager for ACH
    2. 1.2 High-level architecture and key components
      1. 1.2.1 Gateway server
      2. 1.2.2 Gateway engine
      3. 1.2.3 Business rules process server
      4. 1.2.4 Notification of Change (NOC) and Death Notification Entry (DNE)
      5. 1.2.5 Transaction server
      6. 1.2.6 Risk management
      7. 1.2.7 Distribution
      8. 1.2.8 Settlement
      9. 1.2.9 Services framework
      10. 1.2.10 Web services
      11. 1.2.11 Component interaction
    3. 1.3 End-to-end processing overview
      1. 1.3.1 Ingestion
      2. 1.3.2 Remediation and auxiliary processing
      3. 1.3.3 Distribution to receiving point
    4. 1.4 Overview of the operational user interface
      1. 1.4.1 Control Center
      2. 1.4.2 Technical support team
      3. 1.4.3 Business analyst
      4. 1.4.4 Operations team
      5. 1.4.5 Exception management team
      6. 1.4.6 Finance team
    5. 1.5 Importing and exporting system configuration
      1. 1.5.1 Microsoft Excel workbooks
      2. 1.5.2 Property files
      3. 1.5.3 Command line tool
    6. 1.6 Feature comparison of Financial Transaction Manager between ACH, Check Services, and Corporate Payment Services
      1. 1.6.1 Financial Transaction Manager for Corporate Payment Services
      2. 1.6.2 Financial Transaction Manager for Check
  6. Chapter 2. Streamline customer onboarding using products and services
    1. 2.1 Products and services overview
    2. 2.2 Incorporating billing for products and services
      1. 2.2.1 Service area and billing tiers
    3. 2.3 Creating an inbound product
      1. 2.3.1 Using the Control Center
      2. 2.3.2 Using the data setup utility (DSU)
    4. 2.4 Creating an inbound service
      1. 2.4.1 Using the Control Center
      2. 2.4.2 Using the data setup utility (DSU)
    5. 2.5 Adding inbound services to an inbound product
      1. 2.5.1 Using the Control Center
      2. 2.5.2 Using the data setup utility (DSU)
    6. 2.6 Creating an outbound product
      1. 2.6.1 Using the Control Center
      2. 2.6.2 Using the data setup utility (DSU)
    7. 2.7 Creating an Outbound Service
      1. 2.7.1 Using the Control Center
      2. 2.7.2 Using the data setup utility (DSU)
    8. 2.8 Adding outbound services to an outbound product
      1. 2.8.1 Using Control Center
      2. 2.8.2 Using the data setup utility (DSU)
  7. Chapter 3. Validating, enriching, and routing of payments
    1. 3.1 Validation configuration
      1. 3.1.1 Gateway validation
      2. 3.1.2 Data Validation
    2. 3.2 Enrichment
      1. 3.2.1 Same Day Settlement
      2. 3.2.2 SettlementAccumulatorsNode
    3. 3.3 Routing and Endpoints assignment
    4. 3.4 Troubleshooting
  8. Chapter 4. Product and clearing date selection workflow
    1. 4.1 Processing overview
      1. 4.1.1 Identify processing bank
      2. 4.1.2 Product code
      3. 4.1.3 Clearing date for this batch
    2. 4.2 Creating the workflow
      1. 4.2.1 Workflow XML descriptor
      2. 4.2.2 Node XML descriptor
      3. 4.2.3 Task XML descriptor
      4. 4.2.4 Data XML descriptor
    3. 4.3 Configuring the gateway
  9. Chapter 5. Remediation and auxiliary processing workflow
    1. 5.1 Workflow overview and common configuration tasks
    2. 5.2 Transmission acknowledgment
    3. 5.3 Risk Management
    4. 5.4 Risk authorization
    5. 5.5 Settlement
      1. 5.5.1 Register Events in Scheduler.xml
    6. 5.6 Inbound billing
    7. 5.7 Distribution
      1. 5.7.1 PresentmentStateChange
      2. 5.7.2 PaymentExceptionChange
      3. 5.7.3 EndOfDayCheck
      4. 5.7.4 BusinessDayPurgeEvent
      5. 5.7.5 BusinessDayStatusChange
      6. 5.7.6 HoldoverBusinessDayEvent
      7. 5.7.7 SendEndOfDayFilesEvent
    8. 5.8 Outbound billing
  10. Chapter 6. Onboarding a partner
    1. 6.1 Defining a partner
      1. 6.1.1 Using the Control Center
      2. 6.1.2 Opening the Partner Details view
      3. 6.1.3 Using the data setup utility (DSU)
    2. 6.2 Configuring general properties
      1. 6.2.1 Address
      2. 6.2.2 Contacts
      3. 6.2.3 Attributes
      4. 6.2.4 Sub-Partners
      5. 6.2.5 Custom attributes
      6. 6.2.6 Client identifiers
      7. 6.2.7 Accounts
      8. 6.2.8 Logo
      9. 6.2.9 Using the data setup utility (DSU)
    3. 6.3 Configuring a sending point
      1. 6.3.1 Inbound Message Standard Service Subscription
      2. 6.3.2 Transmissions
      3. 6.3.3 Authorized originators
      4. 6.3.4 Expected Transmissions
      5. 6.3.5 Using the data setup utility (DSU)
    4. 6.4 Configuring an originator
      1. 6.4.1 Inbound Products Subscriptions
      2. 6.4.2 Attributes
      3. 6.4.3 Authorized Destinations
      4. 6.4.4 Authorized Message Types
      5. 6.4.5 Exposure Limit Monitors
      6. 6.4.6 Batch/ICL Limits
      7. 6.4.7 Transaction Limits
    5. 6.5 Configuring a receiving point
      1. 6.5.1 Endpoints
      2. 6.5.2 Transmission Deliveries
      3. 6.5.3 Attributes
      4. 6.5.4 Expected Transmissions
      5. 6.5.5 Transmission configuration
      6. 6.5.6 Account rules
      7. 6.5.7 Using the data setup utility (DSU)
  11. Chapter 7. Delivery of payments to receiving points
    1. 7.1 Creating an outbound channel
      1. 7.1.1 Adding basic channel information
      2. 7.1.2 Adding FILE routing mode information
      3. 7.1.3 Adding FTP routing mode information
      4. 7.1.4 Adding email routing mode information
      5. 7.1.5 Adding EXIT routing mode information
      6. 7.1.6 Adding FTM Workflow routing mode information
      7. 7.1.7 Adding Connect:Direct routing mode information
    2. 7.2 Creating a transmission definition
    3. 7.3 Configuring an endpoint
    4. 7.4 Creating custom format files
  12. Back cover