Transmission Processed Notification Task

The transmission processed notification task automates reporting the status of financial transmissions between institutions. It initiates transmission processed notifications without user interaction, saves processing costs, and conforms to industry standards. It supports XML technology, using common programming tools, to easily transform data to any supported format. The following sections provide more details about transmission processed notification.

The transmission processed notification task sends reports to the financial institution that sent the electronic transmission. As the transmission is processed, transmission processed notification reports may be sent as the batch (ICL) reaches various stages of processing and as errors are corrected. The reports acknowledge to the financial institution that its electronic deposit file has been received and is being processed.

The transmission processed notification task is configured to run in Services Framework and is managed by the general task management of the Control Center. Services Framework provides a consistent interface for its configured tasks. It uses a plug-in architecture to enable the web-based user interface to monitor and interact with the service engine of a task. The user interface for this task allows the user to monitor the transmission processed notifications, check them for errors, and reissue them as needed.

When the outbound mapping for a transmission is complete and the transmission is sent using the appropriate channel, a message is sent to Distribution to cause the status of the outbound transmission to be set to transmitted. If the transmission is configured for file to file or batch (ICL) to batch (ICL) delivery, Distribution checks if all of the outbound transmissions for the inbound transmission have been sent. When all of the necessary outbound transmissions have been sent, Distribution sets the status for the inbound transmission to FILE_PROCESSED, which indicates that it has completed processing and the partner can be notified. Use the Transaction Server scheduler to configure an event to run the transmission processed notification task when the FILE_PROCESSED status is reached for a transmission.

When Services Framework receives a transmission processed notification task initiation message from Transaction Server on its message queue, it searches its tasks for one that matches the receiving point ID in the message. The transmission processed notification task must be configured to run before it is called. Transmission processed notification uses the unique deposit group ID to retrieve information about the transmission from the database and to construct a normalized notification XML file. The XML file, some routing information, and a signal file are placed in an output directory to indicate the notification files are ready to be sent. A file tracking entry is also created for tracking further status.

By default, transmission processed notification uses Gateway Server to send the notifications by placing the files in the Gateway outgoing directory. When the transmission processed notification file set appears in its directory, Gateway Server uses the specifications from the routing information file to deliver the notification.

After the notification is delivered, Gateway updates the file tracking status to transmitted. An Transaction Server event configured to run when the file tracking status changes to transmitted calls the transmission processed notification task. The task then sets the transmission processed notification sent status.