'B' Method IBLs: refer to the
Interest Accrual After Maturity section of the Interest Bearing Loans overview document for more information on how LeasePak handles PAP/ACH for loans with interest accrued after maturity.
The Preauthorized Payments (PAP) update [U0304] is used to interactively generate preauthorized payment records. This allows lease payments billed to a lessee to be automatically deducted from the lessee's chosen bank account.
If the PRENOTE USED switch is set to Y for the portfolio, time criteria will be verified as NACHA Rules require and prenotifications will be created for all qualifying lessees who have not yet been prenotified. (A lessee with CCD Standard Entry Class Code will be prenotified only if PRENOTE CCD switch is set to Y for the portfolio.) If the time criteria are not satisfied, the entry will be included in an Exception Report and live dollar entry will not be sent.
The lessor selects a clearing bank to process the payments. The payment file is created in a form acceptable to the clearing bank and submitted one or more days prior to the due date of the payment. This is accomplished through either the interactive or End of Period version of the update
Payments on interest bearing loans can now be processed through preauthorized payments. LeasePak will support both A and B type IBL methods. The Bank File and Batch file created will now include all IBL accrual types that meet the criteria selected in PAP/ACH Control File in the Portfolio [U0212] update, to be run interactively or through EOP.
The PAP/Preauthorize Payments module is divided into 2 areas. The first creates a scratch file of the lease payments due. The second then reads this scratch file and generates 2 output files, one for the bank and the other for LeasePak's batch payments process.
When the BANK FILE LAYOUT TYPE in the PAP/ACH Control File option of the Portfolio [U0212] update is set to 'WDE' Australian WestPac Direct Entry, LeasePak will display additional fields in this update.
Additionally, when the 'WDE' is selected, LeasePak will produce 3 files in the users data directory, the scratch file, Bank file and Batch Payment file. Once re-PAP has been processed, all three files will contain 're' for retry.
PAP Account information for ACH and/or Canadian Bank File types may be modified for a lease. Changes made to the account information at the lease level, does not affect the account information entered in the Lessee [U0203] update. The user may modify the PAP/ACH information at the lease level in the Master Financial [U0202] update or in the Miscellaneous Billing Info [U0227] update.
Approximately 3 days after the due date of the lease, the bank returns a printed report of rejected payments. The user manually backs out rejected payments on Payment Reversal [U0102PR] and researches the problems. Unless otherwise selected, PAP/ACH will automatically pick up the invoice again next month for payment, or it may also be processed interactively.
Several static variables are used on each PAP/ACH record. These variables are the same on each PAP/ACH record. They can therefore be entered once into the control file through Portfolio PAP/ACH Control File [U0212] and will automatically be copied to the PAP/ACH file at the appropriate time. The variables are:
For more information, refer to documentation of the PAP/ACH Control File option of the Portfolio Update [U0212].
In order for the module to function properly, essential elements must be set up within the system:
During the Book Lease process, certain fields need to be coded correctly:
Preauthorized payments will be processed on leases in a suspended status (NHLD etc.) as invoices are generated. If this is not desired, PAP may be turned off through the Master Financial update [U0202]. Set the PAP switch to N. If the lease is reinstated, this switch may be reset to Y and all outstanding invoices will be processed together on the next PAP run for the due date.
The Preauthorized Payment program will create a scratch file for the payment due date(s) calculated. The file will be called: RSPP-xx-YYMMDD.DAT where YYMMDD represents the primary payment due date and xx represents the portfolio. These files will accumulate and therefore should be periodically deleted.
For each active lease, the program will:
Example: Today is Tuesday Aug 21, 2001 Grace days are 3. Thus the primary due date would be Friday Aug 24, 2001. Since that is a Friday, Saturday and Sunday will also be processed. If Monday were a holiday it, too, would be included. Having determined the appropriate due day(s), the program will search from that date backward for all outstanding records due on that day.
Note: Interest bearing loans are not eligible for preauthorized payment processing because of their dynamic recalculation of interest.
Field | Data File |
---|---|
Lease number | RAR |
Invoice number | RAR |
Amount due minus Amount paid | RAR |
Payment Due Date (Julian format) | RAR |
Payer Institution ID # | RAL |
Payer Account # | RAL |
Lessee long name | RAL |
Originator Reference (Lease # and/or Invoice #) | RAR |
After the scratch file has been created, 2 output files will be created from it.
The first file created will be an output file for the bank called Pxx-BANK- YYMMDD.DAT, where YYMMDD is the primary due date and xx is the portfolio. This file would include payments due on Saturday, Sunday and any consecutive holidays next week.
The second file created is for batch payment processing. PAP/ACH will create one file for each portfolio and due date as required, in the form Pxx- BATCH-YYMMDD.DAT where xx is the portfolio number and YYMMDD is the date the file is to be posted.
In addition to the 2 data files, the program will generate the bank's required summary report (used by tape formats only, but always generated). This report summarizes the bank data file and will include the following information:
Note: After the batch payment input file is created, it is necessary for the user to run a lease/util 111 before the EOD process. This utility loads the batch payment file into the Sybase table that will run with the EOD. Not running lease/ util 111 will not process the payments. This may also add an additional day to the EOD process.
Note: Interest bearing loans are not eligible for preauthorized payment processing because of their dynamic recalculation of interest.
The Batch Payments module must be turned on in EOP and should be left on permanently. This module is used for lockbox payments as well as PAP/ACH. Batch Payments will first look for lockbox or user-entered payments. Then, any PAP/ACH files due to be posted on or before today will be located.
All payment records will be grouped and sorted by P/C/R/O/Lease. Batch payments will proceed posting the payments during EOP. All PAP/ACH payments will be automatically processed by lease number and if an overpayment occurs, a credit memo will automatically be created. Each payment will be posted with an effective date of the payment due date from the PAP/ ACH scratch file, regardless of the EOP date.
An exception report is generated for those payments the system is unable to process. The user will need to research these problems and apply payment manually. When batch payments has completed, the input file(s) will be deleted automatically.
If batch payments is inadvertently skipped in EOP it may be caught up the next day with no adverse effects, other than the payments will be posted a day later while still retaining the effective date. All payments will be posted to the cash account option as stated in the Batch Payments documentation.
Using the information on the rejection report supplied by the bank, the user researches the problem and reverses the payment manually using the [U0102PR] update.
Note: On the next PAP/ACH scratch file built for that payment due day, PAP/ ACH will automatically attempt to pay the past due invoice again (including late charges if any). This happens if the portfolio level switch in the PAP/ACH control file is N.
This feature may be deactivated so only the current payment is debited and delinquent invoices are ignored. Set portfolio level switch in the PAP/ACH control file to Y or O. When this switch is Y or O only the amount due on the current invoice is debited. When Y, payment will be applied through Batch Payments by invoice to the actual invoice. When O, payment is applied by lease to the OLDEST unpaid invoice. If there are funds left over the next oldest invoice will be paid until the money is exhausted.
If PAP/ACH has failed due to NSF's or other reasons, and the user does not wish to include the lease on the next run, the PAP/ACH switch at the lease level may be set to N to exclude that lease. An alternative is changing the PAP/ACH effective date. Both are accomplished through [U0202]. This must be done prior to the next PAP/ACH run for that due date. If this option is selected, Batch Payments will apply those payments by invoice so that any delinquencies remain unpaid.
This screen is displayed when the only the Portfolio number is entered and N is the default for the first field.
RETRY
FAILED DEBITS Y/N
Enter
Y for all leases with the PAP
switch set to 'R' to be re-submitted. Enter 'N' for failed debits not to be re-submitted.
'N' is the default value.
Enter 'Y' for LeasePak to process failed retries.
PROCESS PAP, CONTINUE Y/N
When 'N' is selected, this
field is displayed. Enter 'Y' or 'N' for the PAP process to continue.
When 'Y' is entered, LeasePak will re-PAP leases interactively.
When 'N' is selected, no processes will occur and LeasePak will cancel out of the update.
This screen appears when 'Y' is entered for Retry Failed Debits.
Preauthorized Payments
- Detail Report [U0304A] reports at the lease level and provides the following
information for each lease processed:
PAP Exception Report - Detail Report [U0304C] reports at the lease level and provides the following information for each lease processed:
LeasePak Documentation Suite
©
by NetSol Technologies Inc. All rights reserved.
The information contained in this document is the property of NetSol Technologies Inc. Use of the information contained herein is restricted. Conditions of use are subject to change without notice. NetSol Technologies Inc. assumes no liability for any inaccuracy that may appear in this document; the contents of this document do not constitute a promise or warranty. The software described in this document is furnished under license and may be used or copied only in accordance with the terms of said license. Unauthorized use, alteration, or reproduction of this document without the written consent of NetSol Technologies Inc. is prohibited.
This message should disappear within 5-15 seconds, depending on the size of the document and the speed of your connection to the Documentation Suite.
If you can still see this message after 20 seconds, try clicking the Refresh or Reload button on your Web browser.
If your document still does not load, refer to Document Load Troubleshooting for instructions on how to fix possible problems with either your Documentation Suite installation or Web browser setup.
If you do not have read access to the parent docsuite directory, you will not be able to load the Document Load Troubleshooting document. In this case, contact your network administrator for assistance.