U04 End of Period

U0458 Customer/Group Batch Payments

For more information about End of Period,
refer to U04 End of Period Overview.

Related: Utility 111 "Copy the batch payment and PAP files into LeasePak" can be used to populate the rbp Batch Payment table. Contact your NETSOL representative for more information.

This module takes information from the rbp Batch Payment table and uses it to post Customer/Group payments through EOP End of Day. Information can be added to the Batch Payment table directly or through the Batch Payment Input File processing utility (LeasePak Utility). For LeasePak users not using the Cash Control optional license module, the utility provides support for processing payments with only the customer specified.

If there are any recurring charges accounted for accrual basis (A) then users will need to setup recurring charge type from U0212 Portfolio → Assessment Customizations option "Acctg (A/C)". For accrual basis recurring charges users must own " Accrual Basis Recurring Charges" module.

For processing payments in a batch using an external file, LeasePak requires the user to create a simple text file with all the payment records to process in it. Each payment record must be on a single line. The data for each record is separated using the comma (,) character and needs to be in a pre-defined format understandable by the utility that will process the file. The name of the input file needs to be based on the following convention:

pX_btcusgrp.dat

Where 'X' represents the Portfolio for the records in the file.

The Batch File Format

This section describes the structure of the input batch file.

The LeasePak utility processing the input file reads the file line-by-line and applies payments accordingly. Each payment record in the batch file, therefore, must exist on a separate line.

For every payment record there can be two different types of data elements: mandatory and optional. The mandatory elements will be the starting elements of a records and the optional will follow.

The Mandatory Elements (In Alphabetical Order)

• Customer
  Syntax: 'C' (1 character) + Customer Number (1 to 9 alphanumeric characters)

• Group
  Syntax: 'G' (1 character) + Group Number (1 to 3 alphanumeric characters)
  
  If no group number is supplied, LeasePak will only process the leases tied to the customer. This group number will be mandatory for users running LeasePak with the Cash Control module.

• Payment Amount
  Syntax: XXXX (0 to 9 numeric values without decimal)
  
  The payment amount to apply for the specified customer or customer/group. Do not include decimals in your values as LeasePak by default takes the last two digits of the figure for the cents. For example: Enter $150.00 as 15000 in the file.
  

Payment Amount must be the first item to follow the mandatory elements. The optional elements may be in any sequence desired.

The Optional Elements (In Alphabetical Order)

• Payment Effective Date
  Syntax: 'D' (1 character) + Payment Effective Date (6 characters).
  
  The date must be in "YYMMDD" format. If not provided for a record, the effective date for the payment defaults to the current system date for non-IBL leases.

• Batch Number
  Syntax: 'B' (1 character) + Batch Number (20-digit, format-specific batch number).
  
  For LeasePak users running Cash Control, the program generates a new batch number if it does not exist for a payment record. The format for batch number consists of a 6-digit date (YYMMDD), a 6-digit batch number which increments with each group of payments, and an 8-digit sequence number which increments with each new check number.

• Check Number
  Syntax: '#' (1 character) + check number (1 to 10 alphanumeric characters).
  
  For LeasePak users running Cash Control, the program automatically assigns the check number value of '9999999999' if it does not exist for a payment record.

• Bank Code
  Syntax: 'A' (1 character) + bank code (1 to 3 alphanumeric characters).
  
  The bank code is applicable if Multiple Banks module is running. Valid codes are 1, 125-144, and 499-520.

• CLR
  Syntax: 'CLR'
  
  If CLR is entered as an element on a line of the batch payment input file, the payment is posted to clearing. If no CLR is found on a data line, the payment is posted to cash.

Examples

Following are some of the examples of how to specify payments in a batch file using the above mentioned elements.

Example 1: C45,G10,15000,D950523,#5555,A130,B95060100000100000132

Example 2: C45,15000,D950523,#5555,A130

Loading the Batch File into LeasePak

Once the batch file is created, use Utility 111 "Copy the batch payment and PAP files into LeasePak" or other means to load the batch file into LeasePak.