Database Schema

The database schema for Transaction Server has been modified to provide a more generic transaction repository.

The schema is also designed to provide inbound and outbound hierarchical relationships, based on batches (ICLs) rather than transmissions. All work entering the system must be part of a batch (ICL), where an inbound batch (ICL) is a financial settlement between the financial institution and an originator.

Each inbound batch (ICL) will always be part of an outbound transmission. An outbound transmission maintains a grouping relationship for the batches (ICLs) that were deposited as part of a single entity. For example, when ingesting an image cash letter file, the file contains several batches (cash letters), but they are all part of a single outbound transmission. This concept allows batches (ICLs) to be processed as they were delivered. Applications may take advantage of this (if the financial institution elects to do so) when sending work to a remote system.

A segment is a logical grouping of work based on a financial boundary. It is used to segment the work into financial groups of transactions to enable concurrent processing of a single batch (ICL) for performance reasons.

A transaction may either be a credit, debit, adjustment, or a control document.

As an example, Table 1 describes the transaction-to-batch (ICL) relationship for inbound work types.
Table 1. Transaction-to-Batch (ICL) Relationship for Inbound Work Types
  Inbound Work Type
Database Table Image Cash Letter CIFF File Paper Capture
Presentment Group File File  
Presentment Cash Letter File  
Segment Bundle ...  
Payment Credits/Debits Credits/Debits