Lockbox Payment Processing
Running the Lockbox Payment Processing is completed through
a Batch/TRS job. This process generates reports and populates the lockbox
holding master and lockbox holding detail tables. The following process
explains how lockbox receipts are processed in Personify.
LCK100
LCK100 is a process which automatically accepts receipts
into a system by creating records in the lockbox holding table. It is designed
to upload the lockbox batches, which are typically received from financial
institutions. LCK100 reads and validates a lockbox file based upon mapping
tables; load the batch detail, runs error checks against each record, and post
information in Personify.
The way this works is an association receives the batch
control information on a report or email from the financial institution when a
file is transferred electronically. From here, the finance department creates
a batch control record with the totals and deposit date provided by the
financial institution. The user may then run the LCK100 in LIST mode to verify
that the batch being red match the batch control record. The finance
department may also run the application in POST mode to post the transactions
against the given orders.
If users run this process and receive an error message, it
may be because it does not match what is defined in the mapping. Errors may
also occur if the customer in the file doesn’t match correctly; the order
information isn’t correct, etc. The error message will typically let you know
what the issue is, so users can go back and fix these before attempting to run
the process again.
How often the report is run is dependent on the use case.
This may be a process ran daily, weekly but the frequency is based upon the
frequency of the payments flowing into the association.