Inbound and processing batch (ICL) overview

There are two levels of batches (ICLs), inbound and processing batches (ICLs). Each inbound batch (ICL) contains one or more processing batches (ICLs).

Inbound transmissions contain one or more batches (ICLs). Each batch (ICL) that is in the transmission becomes an inbound batch (ICL), which is then divided into one or more processing batches (ICLs). A processing batch (ICL) represents the work within a single inbound batch (ICL) that is processed on a given day. If all of the work in an inbound batch (ICL) is to be processed on a single day, there is only one processing batch (ICL) for that inbound batch (ICL). Transactions are always related to processing batches (ICLs) and never to inbound batches (ICLs).

In the Transaction Server scheduler file for the reference implementation, SchedulerReference.xml, most of the processing occurs on the processing batches (ICLs). Occasionally, processing occurs on an inbound batch (ICL), such as for risk analysis. When an inbound batch (ICL) is being processed, the status for the processing batches (ICLs) that are associated with the inbound batch (ICL) is set to the same state in progress status as the inbound batch (ICL). Conversely, when the status changes for a processing batch (ICL), the inbound batch (ICL) is not affected. When there is a 1:1 ratio of inbound batches (ICLs) to processing batches (ICLs), the processing batches (ICLs) page shows the status information for all of the current batches (ICLs).