BAI2 Billing Extract Task

The purpose of the BAI2 billing extract task is to provide a bank's customers early notice of forthcoming charges (billing) for payment transactions processed by the bank for a given customer in a common format. For a given business day, the task extracts on-us payment transactions for either all originators or a list of specific originators. It creates a single BAI2 file for each originator.

The BAI2 billing extract task extracts payment transactions and related data from the FTM database. The task creates files according to the BAI2 format specification and uses the extracted data to populate those files. The BAI2 format is a national standard for bank reporting, readily accepted and widely used in the industry.

The files are then transmitted to the originating financial institution from which the payment transactions were sent.

This Services Framework task has a set of configuration parameters that are used to provide run time options for each instance of the task. The parameters specify such options as the outgoing directory in which the files are to be placed, the originator ID(s), and the business day categories for which files are to be generated. For more information about the parameters used by this task, see Services Framework task registration and configuration.

This task must be added to the Services Framework runtime engine. Once added, it must be registered and configured using the Services Framework user interface to be available for processing. For more information about registering and configuring the BAI2 billing extract task, see Services Framework task registration and configuration.

This task is typically configured to run at the end of the day. It can also be run manually at any time.

The BAI2 billing extract task has the runtime characteristics shown in Table 1
Table 1. BAI2 Billing Extract Task Runtime Characteristics
Characteristic Setting Description
Manual run Allowed The task can be run manually
Scheduled run Allowed This task can be scheduled to run using the Services Framework timed interface
Concurrent run Not Allowed The task can not run concurrently on separate inbound batches
Transaction Server event Allowed This task may be invoked by Transaction Server events at any time, including as end of day tasks