U04 End of Period

U0415 Batch Payments

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

Sequential Updates: This EOP module runs as part of U0411 Sequential Updates.

Interactive: This functionality is also available in the interactive update U0305 Batch Payments.

Utility 111 "Copy the batch payment and PAP files into LeasePak" must be run prior to End of Period when running this module.

• Overview
  • Interest Bearing Loans
  • Cash Control
  • Preauthorized Payments (ACH)
  • Suspense
  • Batch Payment Audit Report
  • Batch Change Key
  • Notes Payable
  • Session
• Batch Payment Input File
• Exception Messages
• Batch Payment Exceptions Report
• Batch Payment Audit Report

Overview

This update, available only as part of the Batch Payments module, performs batch (as opposed to one-off or manual) lease payment processing. It may be used to process lockbox payments or as an alternative to interactive lease payment processing. Batch payment processing automates payment processing, with manual intervention required only on exceptions. Batch payments is also used to process payments made through the Preauthorized Payments module.

This module is run daily as part of U0411 Sequential Updates. Its status does not appear separately on U0402 Status Review or U0403 Status Listing, but is reflected in the status of Sequential Updates.

The input file is a normal ASCII text RMS sequential file and may be created through a program or, more simply, by creating and editing a file. Each day that batch payments are to be processed, a file with the portfolio number and root name should be created with the payments to apply. LeasePak automatically deletes the batch payment input file after it completes processing the payments for the portfolio. It is advisable to retain a copy of this input file in a separate directory in case future reference is necessary.

For greatly improved efficiency, the Batch Payment input file for each portfolio should be sorted by the company, region, and office of the leases and/ or invoices to be paid. Lease utility 111 performs this sort, and should be run before EOP is submitted.

If an input file of payments will be downloaded during EOP, Utility 111 "Copy the batch payment and PAP files into LeasePak" must be run prior to EOP. It may be executed before EOP begins, while users are still on the system. This utility loads the batch payment input file into the database so it can be efficiently processed by U0415 Batch Payments. It also creates a table of any exception items it was not able to process.

U0415A Batch Payment Exceptions and U0415B Batch Payment Audit reports are created by this module. Problems found during payment application are reported through Batch Payment Exceptions. These payments should be applied interactively through U0102 Payments, if possible. Batch Payment Audit, showing amounts applied and amounts unprocessed, is also created. It should be verified. See the sections below on these reports for more information.

If the Multiple Banks module is purchased, a bank code may be included in the payment input file to indicate the bank where the payment was deposited.

Skip Comments: If this module is skipped, any unprocessed payments must either be processed interactively or included in the next day's Batch Payment process. LeasePak does not automatically process unfinished batch payments from a previous day. Therefore, special arrangements may have to be made when setting up the payments to be processed by the next End of Day Batch Payment update.

Interest Bearing Loans

With purchase of the 1994 JULE Fund enhancements, full or partial payments on interest bearing loans can be processed. Open receivables on IBLs can be paid through batch payments, but any overpayment amounts appear on the Batch Payments Exception Report and must be manually applied through interactive U0102 Payments. Interest adjustments on IBLs are automatically made to reflect early or late payments. However, since overpayments are not automatically processed, interest adjustments resulting from overpayments are not supported.

Batch payments do not support interest-only IBLs for interest-only leases with lease accrual method RIF6.

Batch Payoff/IBL A Method users: While processing an A method, RAX* IBL batch payment, if the program encounters any of the following exceptions and the switch AUTO BATCH PAYOFF FOR IBL BATCH PAYMENT SUSPENSE (Y/N) is set to 'Y' in the Miscellaneous Customizations option of U0212 Portfolio, it will create a Batch Payoff Detail record using the suspense item (created for the payment amount due to the occurrence of an exception) for the specified IBL. The resultant batch payoff detail record will be used by the Batch Payoff program to payoff the affected IBL.

• OVERPAYMENT/PAYDOWN AMOUNT EXCEEDS PRINCIPAL
• UNABLE TO ADJUST ACCRUED PRINCIPLE
• CANNOT PAY LAST INVOICE FOR MATURED LEASE
• CANNOT PAY LAST INVOICE, PRIN HAVE BEEN EXCEEDED

Interest Bearing Loan B method users: LeasePak IBL B Method allows the user to clear the negative amount when invoice includes a negative principal amount. Also, the payments allow the user to make early and late payments with the adjusted amount of interest to charge for payments. For payments the interest amount applied to the principal amount cannot be greater than the sum of interest amount due plus negative principal amount due.

Application of Overpayment to Principal

For overpayments on IBLs, you can control whether or not to apply the amounts to the principal or place them in suspense. At the porfolio level, you can do this through the field Principal Pay Down (Y/N) in U0212 Portfolio→Miscellaneous Customizations. At the individual loan level, you can do this with the field in either U0101 Book Lease or U0202 Master Financial.

Payment Application to IBL with Open Suspense Item

If an IBL has an existing suspense item, an incoming payment will not be applied interest or principal, but will create a new suspense item tied to the IBL. Amounts from suspense items must be applied or cleared before normal payment application resumes. U0420 Auto Apply Suspense for IBL now sorts suspense items by effective date and applies each of the suspense items by oldest effective date first. If LeasePak is unable to apply a suspense item, it generates an exception message to the U0420A Auto Apply Suspense for IBL Exceptions report and stops applying suspense items, so that only the first failed application will show an exception message.

Cash Control

When the Cash Control module is purchased, LeasePak will automatically assign a trace reference information from the Payment Origination code. The trace reference will appear in the R0926 Cash Control Payment History report.

Preauthorized Payments (ACH)

If the Preauthorized Payments (ACH) module is purchased, a file containing the payments to be posted is created by LeasePak. One file is created for each due date. If Batch Payments is not run for a few days, when it is run again it will process any PAP files with due dates less than or equal to the date EOP is run (not necessarily when submitted). It will catch up these unposted days. Batch Payments will treat PAP file(s), in addition to the standard user-supplied file, as one big file. All records in all files being posted today will be sorted by Portfolio/Company/Region/Office/Lease. No subtotals by due date are given. All records in all files will appear together on the standard audit reports. All standard error/exception messages will apply. When successfully posted, Batch Payments will delete the PAP input file(s). Please refer to the PAP documentation for further information in the file naming convention as well as how and when these file(s) are created.

Suspense

When a Suspense item has been tied to the lease, LeasePak will automatically default the trace reference information to the Suspense Review [R0203] report.

Off Lease Billing

When the Off-Lease Billing module has been purchased and the lease is an inactive status (Nxxx), LeasePak will allow Batch Payments to be made to the lease if a Payoff [U0103] or Termination [U0103] has been performed. The G/L calculation for an INVOICE (RENT) payment (field in Payoff and Termination) will be calculated:

Batch Change Key

A Batch Payment input file named (portfolio number)_sctzpmt.dat may be automatically created as part of the Batch Change Key process, $uexe/lpadriver.exe /util 212. This process changes a group of leases from one accounting unit (portfolio/company/region/office) to another. If payments have been applied on any of the affected leases since the effective date of the change, those payments are automatically reversed through the Reverse Payments to Effective Date program. In turn, a Batch Payments file is created to reapply those payments in the new accounting unit.

The following example defines the name of the input file with the root name of "btchpmnt.dat", located in LeasePak's data directory. The root name is not the actual file name of the batch payment input file. The portfolio number appended to the front of the root name is the actual file name.

For example: p1_btchpmnt.dat is the batch payment input file for all the payments to be processed for leases belonging to portfolio 1.

Notes Payable

Under some circumstances, payment processed through Batch Payments will affect a note payable. Any payment applied to a lease will automatically be applied to an active note to which that lease is attached, if the following conditions are all met:

• The Notes Payable module is purchased.
• The Multiple Banks module is purchased.
• The APPLY PAYMENT TO NOTE parameter on the New Lease option of the Portfolio update [U0212] is set to Y.
• A Lease number was entered on the Book Note Payable update [U0901BK], attaching the note to the lease.

Session

Session assignments are not required to process Batch Payments.

Batch Payment Input File

The batch payment input file should contain one line for each invoice or lease to process. Each line must contain at least the following 2 mandatory elements, separated by a comma:

• The invoice or lease number of the payment to apply. It must be preceded by an I (for invoice) or L (for lease). No space is allowed between the character I or L and the lease number.

  Note: Batch Payments can process payments for interest bearing loans, but only by lease number, not by invoice number. Preauthorized payments for interest bearing loans are not supported.

• The payment amount to apply. It must be stored with the cents portion but without the decimal point.

In addition to the 2 mandatory elements, each line of the batch payment input file may contain up to 5 optional elements, separated by commas. The optional elements must be placed after the mandatory elements. While the 2 mandatory elements must be in the sequence listed above, the optional elements may be entered in any sequence desired. They are:

• The Invoice Due Date
  This element must be preceded by a 'U'. It must be in YYMMDD format. LeasePak ignores this element when 'I' invoice is provided. The element searches for the invoice number by using provided lease number and invoice due date. Interest bearing loan leases are not supported by invoice due date field.

• The Payment Effective Date.
  This element must be preceded by a "D". It must be in YYMMDD format.
  
  
  • If no effective date is entered on a line, the effective date for this payment defaults to the current system (today's) date (non-IBL type leases).
    
    
• For interest bearing loans, if no effective date is entered on a line, LeasePak will default the Effective Date as established in the Payment Effective Date Default (C/D/X) field in the Lease Form [U0721] update.

  For IBLs in NMAT (matured) status and with Capitalize Interest set to 'N', you can specify an effective date as far forward of the accrued-to date as needed.

The Payment Effective Date is displayed on the Batch Payment Audit report [U0415B] and the Individual Account Payment History report [R0909]. It is used in calculating interest for interest bearing loan accrual types and also in calculating late charges under the actual days delinquent (GFT or GFL) late charge calculation methods.

Note: For interest bearing loans the input file must be in effective date order by lease. That is, if more than one check is to be applied to an IBL in a single batch, the earliest check should be processed first.

• The Check Number of the Payment.
  This element must be preceded by a "#". The check number may be from 1 to a maximum of 10 characters or digits.

If the Batch Number Payment Reversal module is purchased, check number is mandatory.

• A Batch Number
  If the Batch Number Payment Reversal module is purchased, batch number is mandatory and must be unique. Otherwise it is optional.
  

This element must be preceded by a "B". The batch number must be 20 digits.

For Batch Number Payment Reversal, the format 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.

• The "Post to Clearing" symbol.
  This symbol is "CLR." If CLR is entered as an element on a line of the batch payments input file, the payment is posted to clearing. If no CLR is found on a data line, the payment is posted to cash.
  
  
• The Bank Code
  If the Multiple Banks module is purchased, a bank code may be included. This code must be preceded by an "A." Valid bank codes are 1, 125 to 144, and 499 to 520.
  
  


• Transaction Override 'T'
  For the batch payment, input file LeasePak allows data elements that are preceded by a 'T'. The 'T' indicates transaction override and works the same way update U0126 Cash Control works when something is entered in the column labeled Transaction. Element 'T' must be followed by a valid four-character transaction override code. The valid four character codes are any of the possible assessments or recurring charge codes. Following are also the valid codes:
  
  
  • PRIN – Principal Only (IBL)
  • INT – Interest Only (IBL)
  • SUSP – Suspense

  When a transaction code is sent in input file, that payment record will be applied first to the specific type of charge indicated by the T code before starting to apply to remaining open charges by using the appropriate payment hierarchy. If 'SUSP' follows the T, than all of the cash will be placed into suspense directly. If it indicates bank number, than the cash will come from that bank instead of using that bank number set up for automatic suspense through U0212 Module Customization.

  Processing a batch payment with a bank number specified, that bank number be used unless there is an error that forces the money to be placed in suspense. In this case the bank number indicated in U0212 Module Customization as default bank for automatic suspense. This bank number will not be used when 'TSUSP' is sent to override the transaction and place the amount in suspense. When 'TSUSP' is sent, the bank number sent will be used. However, if no bank number is sent with the TSUSP element, than the bank indicated through U0212 will be used instead of the default bank for batch payments that is 129.

  
  

• Note or Comment with Transaction 'N'
  For the batch payment, input file LeasePak allows data elements that are preceded by a 'N'. The 'N' indicates note or comment and it will save the comment with the transaction. Each batch payment line can be no longer than 80 characters or it will be truncated due to space limitations. A comma (,) indicates a break from the previous element. Users must use escape characters when stating a comma in a comment or note. The escape characters for a comma are [& #44; (without space)] and can be placed anywhere in the comment or note that are required by the user to appear. The N should be the last element in a line if used.
  

Examples

Following are examples of data lines for the batch payments input file:

L6654,1035000
This data line directs the Batch Payments module to process $10,350.00 for lease 6654. The effective date is defaulted to the current system date. The payment is posted to cash.

I23090,43298
This data line directs the Batch Payment module to process $432.98 for invoice number 23090. The effective date is defaulted to the current system date. The payment is posted to cash.

L102,2000,#1126
This data line directs the Batch Payment module to process $20.00 for lease 102. The check number of the payment is 1126. The effective date is defaulted to the current system date. The payment is posted to cash.

L1,99839,U890401
This data line directs the Batch Payment module to process $99839.00 for lease 1. The invoice due date of the payment is 890401.

I876543210,1000,CLR
This data line directs the Batch Payments module to process $10.00 for invoice number 876543210. The effective date is defaulted to the current system date. The payment is posted to clearing.

L100,2500,D960115,#1125,CLR
This data line directs the Batch Payments module to process $25.00 for lease 100. The effective date of the payment is 960115. The check number of the payment is 1125. The payment is posted to clearing.

L1234,15000,D950523,#5555,A130,C25,B95060100000100000132
This data line directs the Batch Payments module to process $150.00 for lease 1234. The effective date of the payment is 950523. The lessee's check number is 5555, cash is posted to bank 130, and the lessee number is 25. The batch number, required for Cash Control, indicates that the check was posted on June 1, 1995, it was the 132nd check posted that day. The payment is posted to cash.

Note that leading spaces (padding) for lease number, invoice number, check number, etc. are not required. Also, if decimal points are entered for the payment amount, misinterpretation is possible (e.g., I23090,432.98, the payment amount is interpreted as $4.33).

The following processing rules apply:

• Payments to groups are not allowed. However, payments to individual leases or invoices which belong to a group are permitted.
  
  
• Payments to advanced invoices are not allowed.
  
  
• The total dollar amount in the file is processed, if possible. Therefore, there may be partial payments, full payments, or multiple payments.
  
  
• If applying payments for a lease, not to a specific invoice, the most delinquent invoices are processed first.
  
  
• If applying payments for a lease, a credit memo is generated if there is a remaining amount to apply and no more outstanding invoices for the lease. If applying a payment directly to an invoice, any overage amount is reported on the exception report and is not placed in a credit memo.
  
  
• If Cash Control module is purchased, check number and batch number are required. All records for the same check and same batch number must be physically next to each other in the file. If the same batch number is encountered later in the file, the payment will not be applied and will appear on the exception report as a duplicate key.
  
  
• If applying an overpayment to an interest bearing loan, accounts receivable will be paid in full, but no principal paydown, prepayment, credit memo, nor suspense amount will result. Any amount received above the accounts receivable will display on the exception report and must be processed interactively.

  Note: When the Principal Payment Down (Y/N) switch is set to Y, LeasePak will apply overpayments to the Principal Pay Down if no account receivable records exists.

• If a Batch number for an IBL payment is selected for reversal, and is not the most recent payment made the most recent payment made for the selected batch payment amount will be reversed instead. This is due to IBL restriction on order of payment reversal where the most recent payment always has to be reversed first.

Informational, warning, and error messages are printed to the Batch Payment Exceptions report [U0415A].

• Informational messages notify the user of payment transactions that differ from the normal, but may not necessarily be incorrect.
  
  
• Warning messages notify the user of payment transactions that are suspected of being incorrect.
  
  
• Error messages notify the user of unprocessable items.

In general, payment application for the full amount to apply is performed for informational and warning messages, but not for error messages.

Exception Messages

The following list contains the messages (listed alphabetically) for both the Batch Payment and Assumed Payment modules, since many of the processing errors encountered are the same for the two modules. If a particular message is applicable only to one module, it is so noted. All Batch and Assumed Payment errors and/or unprocessable items should be processed interactively through the Payments update [U0102].

ACCOUNTS RECEIVABLE RECORD IS LOCKED
This is an error message. The Accounts Receivable (RAR) record cannot be accessed. No payment was processed. Try processing the payment interactively.

AMOUNT TO APPLY IS GREATER THAN 5 TIMES THE NORMAL LEASE PAYMENT
This is a warning message (Batch Payments module only). The amount to apply is more than five times the normal lease payment. Payments were processed. This situation is reported because it may be an input file data error. Verify the amount applied and make the necessary adjustments if incorrect.

AMOUNT TO APPLY IS LESS THAN ZERO
This is an error message (Batch Payments module only). There is a negative amount to apply. This may be an input file data error. No payment was processed. Verify the amount to apply to the lease or invoice. Apply the correct amount interactively or through the next End of Day Batch Payment update.

AMOUNT TO APPLY IS ZERO
This is an error message (Batch Payments module only). There is a zero amount to apply. This may be an input file data error. No payment was processed. Verify the amount to apply to the lease or invoice. Apply the correct amount interactively or through the next End of Day Batch Payment update.

BATCH PAYMENT NOT ALLOWED FOR NON-ACCRUAL LEASE
This is an error message (Batch Payments module only). The amount to apply is to an invoice of a non-accrual lease or to a non-accrual lease. No payment was processed.

BATCH PAYMENT NOT ALLOWED ON AN ADVANCED INVOICE
This is an error message (Batch Payments module only). The invoice number entered is an advanced invoice, i.e., the 1994 JULE Fund Advanced Invoicing module is in effect and the LEASE FORM code controls timing of invoice production. Receivables are not accrued until a maximum of 30 days before the due date. No payment was processed.

CANNOT PAY LAST INVOICE, PRIN HAS BEEN EXCEEDED. USE [U0103]
This error message will show if payment received is equal or greater than the outstanding principal balance.

CREDIT MEMO CREATED
This is an informational message (Batch Payments module only). The amount to apply exceeded the outstanding invoices for the lease, so a credit memo for the overage was created. This situation is reported because it may be an input file data error. If so, reverse the payments applied and reprocess the payment correctly. This message is generated only if payment is made by lease number. Credit memos are not generated if payment is made by invoice number.

DUE DATE NOT ALLOWED FOR IBLs
This is an error message that appears when the input file contains an interest bearing loan with an invoice due date. IBLs are not supported when using the invoice due date to process batch payments.

DUE DATE IS REQUIRED WITH(U) OPTION
This is an error message that appears when the input file does not have a due date defined with element U.

FAILED TO GET NEW INVOICE NUMBER FOR CREDIT MEMO
This is an error message (Batch Payments module only). A new invoice number to be assigned to the credit memo could not be obtained. Outstanding payments were processed, but the credit memo for the remaining amount to apply was not created. If this message appears, determine the amount that should be placed on a credit memo and contact your NetSol representative. This message is generated only if payment is made by lease number. Credit memos are not generated if payment is made by invoice number.

FILE NOT FOUND: <file name>
This is an error message (Batch Payments module only). The batch payment input file name does not exist. If no payments are to be processed for this portfolio, then no action needs to be taken on this message. Otherwise, apply the payments interactively or append the information to the input file for the next End of Day Batch Payment update.

INVALID AMOUNT TO APPLY: <amount>
This is an error message (Batch Payments module only). An input file data error was detected. The amount to apply is the second item on the input line and should contain a string of numeric characters (zero through nine). Characters other than zero through nine were detected. No payment was processed. Verify the amount to apply to the lease or invoice. Apply the correct amount interactively or through the next End of Day Batch Payment update.

INVALID DUE DATE: <input>
This is an error message. The due date specified on the input line is invalid. Verify that the due date format is YYMMDD.

INVALID INPUT: <input>
This is an error message (Batch Payments module only). An input file data error was detected. The input line should consist of at least 2 elements: the lease or invoice number and the payment amount. No payment was processed. Verify the line in the input file. Apply the correct amount interactively or through the next End of Day Batch Payment update.

INVALID DATE
This is an error message (Batch Payments module only). An error was made entering the effective date in the input file. No payment was processed. Verify the line in the input file. Enter the correct date interactively or through the next End of Day Batch Payment update.

INVALID PAYMENT OPTION: <payment option>
This is an error message (Batch Payments module only). An input file data error was detected. The payment option is the first item on the line and should denote that payment is to be made to a lease or to an invoice by adding an L or I in front of the lease or invoice number. A character other than an L or I was encountered. No payment was processed. Verify the first item on the line in the input file. Apply the correct amount interactively or through the next End of Day Batch Payment update.

Note: Batch Payments can process payments for interest bearing loans, but only by lease number, not by invoice number.

INVALID TRANSACTION OPTION: <option>
This is an error message. Either a data corruption error or a program error caused this message. No payment was processed. If this message appears, determine the lease or invoice it was trying to process (by reviewing the last completed payment on the audit report) and contact your NetSol representative.

INVOICE HAS BEEN PAID
This is an error message (Batch Payments module only). The invoice number specified on the input line was already paid. No payment was processed. Verify that the invoice number was entered correctly. If not, apply the payment to the correct invoice interactively or through the next End of Day Batch Payment update.

INVOICE IS ON A DIFFERENT PORTFOLIO
This is an error message (Batch Payments module only). The invoice number specified on the input line belongs to a different portfolio. No payment was processed. Verify that the invoice number was entered correctly. If not, apply the payment to the correct invoice interactively or through the next End of Day Batch Payment update.

INVOICE NUMBER WAS NOT FOUND
This is an error message (Batch Payments module only). The invoice number specified on the input line is invalid. No payment was processed. Verify that the invoice number was entered correctly. If not, apply the payment to the correct invoice interactively or through the next End of Day Batch Payment update.

INVOICE TO BE APPLIED IS A CREDIT MEMO
This is an error message (Batch Payments module only). The invoice number specified on the input line is a credit memo. No payment was processed. Verify that the invoice number was entered correctly. If not, apply the payment to the correct invoice interactively or through the next End of Day Batch Payment update.

LEASE IS IN A GROUP
This is an informational message. The lease to which a payment was applied is part of a group. Verify that the payment was applied properly. If not, reverse the payment and reapply it to the correct invoice interactively or through the next End of Day Batch Payment update.

LEASE IS ON A DIFFERENT PORTFOLIO
This is an error message (Batch Payments module only). The lease number specified on the input line belongs to a different portfolio. No payment was processed. Verify that the lease number was entered correctly. If not, apply the payment to the correct lease interactively or through the next End of Day Batch Payment update.

LEASE NUMBER WAS NOT FOUND
This is an error message (Batch Payments module only). The lease number specified on the input line is invalid. No payment was processed. Verify that the lease number was entered correctly. If not, apply the payment to the correct lease interactively or through the next End of Day Batch Payment update.

LEASE RECORD IS LOCKED
This is an error message (Batch Payments module only). The Lease (RLS) record could not be accessed. No payment was processed. Try processing the payment interactively.

MASTER FINANCIAL RECORD IS LOCKED
This is an error message (Assumed Payment module only). The Master Financial (RLS) record could not be accessed. No payment was processed. Try processing the payment interactively.

MULTIPLE INVOICES WERE PROCESSED
This is an informational message (Batch Payments module only). More than one invoice was processed for the lease (payment by lease number only). Verify that the amount to process was entered correctly. If not, reverse the incorrectly applied payments.

MULTIPLE DATA ITEMS
This is an error message (Batch Payment module only). Multiple occurrences of check number, effective date, or the 'CLR' symbol were encountered. No payment was processed. Verify the line in the input file.

ONLY LEASE PAYMENT FOR INTEREST BEARING LOANS
This is an error message. IBL payments can only be applied at the lease level, not by individual invoice.

OVERPAYMENT CANNOT BE MADE USING THE INVOICE OPTION
This is an error message (Batch Payments module only). Payment is made to an invoice and the amount to apply is greater than the amount due for the invoice. The invoice is fully paid; however, the remaining amount to apply is not processed any further. Verify that the amount to process was entered correctly. If not, reverse any incorrectly applied payments. If the amount was entered correctly, interactively apply the remaining amount as a prepayment to the lease. This message is generated only if payment is made by invoice number. Credit memos are generated if payment is made by lease number.

OVERPAYMENT NOT APPLIED
This is an error message. For interest bearing loans, outstanding, billed receivables are satisfied, but any excess is not processed. The overpayment appears on the exception report.

PARTIAL PAYMENT WAS APPLIED
This is an informational message (Batch Payments module only). A partial payment to an invoice was applied. Verify that the amount to process was entered correctly. If not, reverse the incorrectly applied payments.

PARTICIPATION PAYABLE RECORD DOES NOT EXIST
This is an error message. The Participation Payable (RPP) record does not exist. No payment was processed. If this message appears, determine the lease or invoice it was trying to process (by reviewing the last completed payment on the audit report) and contact your NetSol representative.

PARTICIPATION PAYABLE RECORD IS LOCKED
This is an error message. The Participation Payable (RPP) record cannot be accessed. No payment was processed. Try processing the payment interactively.

PAYMENT DUE "date due" (in YYMMDD) REVERSED PREVIOUSLY. MUST BE MANUALLYPAID
This is an informational message (Assumed Payment module only). Any reversed assumed payments are not reapplied. They must be processed manually. (Refer to the section EOP: Assumed Payment [U0414].)

PORTFOLIO IS LOCKED
This is an error message (Assumed Payment module only). The portfolio cannot be accessed. No payments were processed. Try processing the payments interactively or through the next Assumed Payment module.

TAX AMOUNT COULD NOT BE FULLY APPLIED
This is an error message. Possible data corruption with the Tax Payable (RTP) file is indicated. No payment was processed. If this message appears, determine the lease or invoice it was trying to process (by reviewing the last completed payment on the audit report) and contact your NetSol representative.

TAX PAYABLE LIMIT EXCEEDED
This is an error message. Internal program array sizes were reached. No payment was processed. This payment must be processed interactively.

TAX PAYABLE RECORD IS LOCKED
This is an error message. The Tax Payable (RTP) record cannot be accessed. No payment was processed. Try processing the payment interactively.

TAX RELEASED LIMIT EXCEEDED
This is an error message. Internal program array sizes were reached. No payment was processed. This payment must be processed interactively.

TAX RELEASED RECORD IS LOCKED
This is an error message. The Tax Released (RTR) record cannot be accessed. No payment was processed. Try processing the payment interactively.

THE FULL AMOUNT TO APPLY WAS NOT PROCESSED (LEASE IS MATURED)
This is an error message. A remaining amount to apply exists. Under normal circumstances, the overage amount would be placed on a credit memo for the lease. However, this lease is matured and prepayments cannot be made to a matured lease. Outstanding payments were processed, but the credit memo for the remaining amount to apply was not created. Verify that the amount to process was entered correctly. If not, reverse any incorrectly applied payments. If the amount was entered correctly, place the overage in suspense until a determination on its disposition is made.

TOO MANY DATA ITEMS
This is an error message (Batch Payment module only). More than 5 data items were encountered on one data line. No payment was processed. Verify the line in the input file.

UNABLE TO ADJUST ACCRUED PRINCIPAL BALANCE
If for whatever reason, the payment applied results to a negative outstanding principal balance, LeasePak reports this error message.

UNEXPECTED DATA ITEM ENCOUNTERED
This is an error message (Batch Payments module only). The third, fourth or fifth data item does not begin with a # (check number), a D (effective date), or CLR (clear symbol). No payment was processed. Verify the line in the input file.

UNABLE TO FIND INVOICE
This error message appears when no matching invoice is found for the specified lease number and invoice due date in the input file.

Batch Payment Exceptions Report

The Batch Payment Exceptions report [U0415A] reports at the lease or invoice level and includes the following information:

• LEASE
  The lease number, if applying payments by lease number, is displayed.
  
  
• INVOICE
  The invoice number, if applying payment to an invoice, is displayed.
  
  
• TYPE
  The type of message (INFORMATIONAL, WARNING, or ERROR) is displayed. Informational messages notify the user of payment transactions that differ from the normal, but may not necessarily be incorrect. Warning messages notify the user of payment transactions that are suspected of being incorrect. Error messages notify the user of unprocessable items. In general, payment application is performed for informational and warning messages, but not for error messages.
  
  
• MESSAGE
  The informational, warning, or error message is displayed. Refer to the Messages section for a list of messages and their meanings.
  
  
• AMOUNT APPLIED
  The amount applied, or processed, is displayed.

  Note: If a partial payment amount is applied, only the amount unprocessed is listed in this report. Refer to the Batch Payment Audit report for more details on how the payment was processed.

• UNPROCESSED AMOUNT
  The amount unapplied, or unprocessed, is displayed.

  Note: Additional unprocessable exceptions may appear in the Sybase table populated by LEASE/UTIL 111.

Batch Payment Audit Report

The Batch Payment Audit report [U0415B] reports at the lease or invoice level and includes the following information:

• LEASE
  
  
• INVOICE NUMBER
  The invoice number is displayed. There may be several invoices applied for one lease.s
  
  
• PAYMENT DUE DATE
  The payment due date for the INVOICE NUMBER is displayed.
  
  
• EFFECT DATE
  The effective date for the payment is displayed.
  
  
• CHECK NUMBER
  The check number of the payment is displayed.
  
  
• AMOUNT APPLIED TO CASH OR CLEARING
  CSH is displayed if the payment is posted to cash. CLR is displayed if the payment is posted to clearing.
  
  
• PAYMENT AMOUNT APPLIED
  The amount applied against the payment is displayed. If the lease is a simple interest lease, the principal portion paid is displayed.
  
  
• OTHER AMOUNT APPLIED
  The amount applied against an assessment amount is displayed. If the lease is a simple interest lease, the interest portion paid is displayed. There may be several OTHER AMOUNT APPLIED items for the invoice.
  
  
• TYPE OF OTHER AMOUNT APPLIED
  The type of the OTHER AMOUNT APPLIED is displayed (e.g., USE TAX, LATE CHARGES, INTEREST, etc.).

  If the Name Assessment by Portfolio is purchased, the customized assessment names will be displayed.

• TOTAL AMOUNT APPLIED
  The total amount applied for all invoices for the lease is displayed.
  
  
• AMOUNT UNPROCESSED
  The total amount not applied for the lease is displayed. The totals are separated into total amount posted to cash and total amount posted to clearing.