1. Loan Servicing User Guide
  2. Batch Transactions
  3. Payments
  4. Bulk Upload of Payment Transactions

17.3.4 Bulk Upload of Payment Transactions

OFSLL supports bulk upload of payment transactions into the system in addition to the option of manually creating the records in the Payment Entry tab.

During the bulk upload process, a set of payment transactions can be grouped together into a single file, in a specific file format and uploaded into the system using the Process File interface. The upload file is then processed through a batch and after successful validation, individual records are created automatically in Payment Entry tab with appropriate status.

While creating the upload file, it is necessary to maintain the details in specific format and to ensure that all the payment transactions are uploaded correctly without any issues during validation. The bulk upload file format supports One Header and Multiple Detail records and the currency defined in the header is applicable for all the records. Example of header record is indicated in the following table:

Table 17-8 Header Record

Company Currency Mode Reason Total # Total Amt Action
US01 USD CASH PAYMENT MANUAL 3 3000 POST / REVERSE / VOID

In the header record, all the fields are mandatory except Reason. Each field information is validated with the data maintained in the system and in case of any discrepancies, the entire payment upload batch is rejected. For example, when the specified company code or currency code is not maintained, or if Total Amount contains a non numeric data, the entire batch is rejected from processing.

The details of each transaction need to be maintained in the following format as indicated with system defined validations:

Table 17-9 Payment Transactions Format

Field Name Expected Values Mandatory (Y/N) Validation
Account # Account Number Y

Mismatch in Account # is posted as Suspense (Account Number as 0) against Company specified in header.

For suspense account, system defaults the spread where Status, Condition, and State = ALL.

Pmt Date Payment Date Y Payment date cannot be beyond the GL date.
Pmt Amount Payment Amount Y Payment Amount should not contain non-numeric or negative amount.
Spread

Spread

(Spread Code)

 N

Spread Code has to be valid.

If left blank, default spread is applicable based on spread matrix or value defined in contract.
Reference Free Text N NA

Based on the value defined in CLOB system parameter CMN_FILE_PROCESS_TO_LOB, the file is either processed through Process Files interface (if value is Y) or Database Files system (if value is N). For database file upload, the payment transactions file has to be placed in IBU directory for upload and for process files interface, the file is shared in common access folder and uploaded by accessing it from the Incoming Process File tab. For more information, refer to DashBoard > Process Files section.

On initiating the file upload in Process Files screen, new batch job IPUPRC_BJ_100_01, under Batch Job Sets SET-IFP is created to process the same. Each batch can process specific number of records as per the Parameter Value defined in the system parameter LBX_TXN_GROUPING_CNT (BATCH SIZE OF PAYMENT UPLOAD RECORDS). Note that a batch can get rejected from processing if the total number of records exceed the parameter value or the Total # specified in the file header.

While uploading the batch, ensure that the following lookup details are maintained in Lookup Code PAYMENT_UPLOAD with Sub Code as PAY in Lookup Type GROUP_SUB_TYPE_CD.

Once the batch is successfully executed after validation, system identifies the Header and Detail records in payment file and creates individual records with the same batch name in Payments and Payment Txns sections automatically. The status of the Batch is updated depending on the status defined in system parameter PMT_BATCH_POSTING (PAYMENT BATCH POSTING PREFERENCE) as OPEN or HOLD or POSTED.

This section consists of the following topic:

Parent topic: Payments