Create Payment Events and Payments

Once the payment records are moved to the staging area, the system creates payment events for the payment data file in the background when the Payment Upload (PUPL) batch is invoked. You can configure the Payment Upload (PUPL) batch such that it is executed at regular intervals. When the Payment Upload (PUPL) batch is invoked, the system checks whether there are any deposit control, tender control, payment tender, and payment staging records in the Pending status. If there are staging records in the Pending status, the system creates the following entities:

• Deposit Control

• Tender Control

• Payment Events

• Payment Tenders

• Payments

• Payment Segments

• Financial Transactions (when the payments are frozen)

The status of the deposit control, tender control, payment tender, and payment staging records is changed to Complete. If any error occurs while creating payment event for a payment record, the status of the deposit control, tender control, payment tender, and payment staging records is changed to Error. In addition, the status of the payment record in the pre-staging area is changed to Error in Staging.

Traditionally, the Payment Upload (PUPL) batch considered staging records which are in the Error or Pending status. If a staging record is in the Error status, the system used to reset the status to Pending and then further processed the staging record. This system behavior still exists for staging records which are not uploaded through the Payment Upload process. If the staging records are uploaded through the Payment Upload process, you need to manually correct the staging records and change the status of deposit control, tender control, payment tender, and payment staging records to Pending. The corrected staging records will then be processed when the Payment Upload (PUPL) batch is invoked at subsequent interval.