Lockbox update error messages
When you update imported EDI 820 Payment Order/Remittance Advice documents, these types of errors can occur:
- Errors at the header level
- Exceptions at the header level
- Errors at the line level
The errors are displayed in the Electronic Transaction Control Center (ETCC).
Header-level messages
This table shows the errors and exceptions that can occur at the header level when you receive inbound EDI 820 Payment Order/Remittance Advice documents. The cause or corrective action is also shown. Unless otherwise stated, the message is an error message.
| Message | Cause or corrective action | Error # |
|---|---|---|
| Report Name Not Set Up in Report Parameter Setup - SAPB | The report identified as the stored report is not set
up as a stored report. The report name might be specified on a business rule
in SA Business Rule Setup or is
pointing to the stored @areli report. Create the stored report in Customer Entry Lockbox Import Report, and then update the transaction in ETCC to reprocess it. |
1 |
| Bank Not Set Up in Check Reconciliation - CRSB | The bank number is not set up in CR Bank Setup. Set up the bank record, and then update the transaction in ETCC to reprocess it. |
2 |
| CRSB Account Code Not Set Up in the Chart of Accounts - GLSA. | The GL account number is not set up in CR Bank Setup. Set up the bank record to include the GL account number, and then update the transaction in ETCC to reprocess it. |
3 |
| ARELU is not setup in SASSR | The SASSR metadata record for the Customer Entry Lockbox Update Report is not
set up. Manually create the record in SA Administrator Options, and then update the transaction in ETCC to reprocess it. SASSR metadata records are typically created by a system administrator. |
4 |
| Invalid Dummy Customer Number | The customer that is specified in the Dummy Customer for Unmatched Checks option on the Customer Entry Lockbox Import Report is
invalid. If the dummy customer is incorrect, specify the correct customer on the stored report, and then update the transaction in ETCC to reprocess it. If the dummy customer on the stored report is correct, verify that the dummy customer is set up correctly. If required, set up a record for the dummy customer in Customer Lock Box Setup. Update the transaction in ETCC to reprocess it. |
5 |
| Can Not Find arelipe Program to Process Lockbox File | The arelipe.p program
cannot be found by the system to process the EDI data.Contact the Infor Cloud team to install the correct code and then update the transaction in ETCC to reprocess it. |
6 |
| No detail for check | The transaction contained check data, but detail
transactions were not included. Cancel the transaction in ETCC. Manually enter the payment information in Customer Lock Box Entry. |
7 |
| Overpayment | The transaction contains an overpayment. This message is an exception. |
8 |
| Shortage | The transaction contains a shortage. This message is an exception. |
9 |
| Multiple Transmission in Lockbox File | The data contained more than one lockbox transmission. | 10 |
| Lockbox File's Transmission Already Processed | The transaction was previously received and processed. Cancel the transaction in ETCC. | 11 |
| Invalid Company Wide Lockbox | The lockbox number from the transaction was not found
in the system. If Yes is selected for the Create ARSL Records? option on the Customer Entry Lockbox Import Report, this message is an exception. If No is selected for the Create ARSL Records? option on the Customer Entry Lockbox Import Report, this message is an error. To correct the error, set up the lockbox in Customer Lock Box Setup, and then update the transaction in ETCC to reprocess it. |
12 |
| Batch Already Exists/Batch Ignored | The batch was previously processed. If the lockbox is valid, Batch Already Exists is displayed in ETCC. If the lockbox does not exist, Batch Ignored is displayed in ETCC. Cancel the transaction in ETCC. |
13 |
| New ARSL Created for Cust# | A Customer Lock Box
Setup record was created for the lockbox number. This message is an exception. |
14 |
| Invalid MICR# [####] Could Not Determine Customer – ARSL Not Created | A miscellaneous credit/scheduled payment was applied to
the dummy customer account on the stored report. The error occurs if these
conditions are met:
Manually apply the payment to the correct customer in Customer Lock Box Entry. |
15 |
| Customer Already has ARSLs - Please Verify! | A lockbox record was created for a customer that
already has one or more records in Customer Lock
Box Setup. This message is an exception. |
16 |
| ** transaction code and transaction number | The check type is displayed if the check is not real.
This message is an exception. |
17 |
| Check Already Exists in Batch | The check was attached to a previous lockbox batch record. It cannot be imported and updated again. Cancel the transaction in ETCC. | 18 |
| DUPL Batch [####] Check [####] | The transaction was attached to a previous lockbox batch record. It cannot be imported and updated again. Cancel the transaction in ETCC. | 19 |
| Orig Cust# [####} | If split is selected for the Split Transactions
option on the Customer Entry Lockbox Import
Report, then the transaction is posted as a suspended
transaction. Unsuspend the transaction in Customer Lock Box Entry. |
21 |
| *** Bad MICR miscellaneous credit number, edit Cust# *** | The customer and lockbox number could not be
determined. A miscellaneous credit/scheduled payment was posted to the
account for the dummy customer from the Customer
Entry Lockbox Import Report. Manually apply the miscellaneous credit to the correct customer in Customer Lox Box Entry. |
22 |
| Customer # not in ARSC | A customer record does not exist for the customer
associated with the transaction. In ETCC, specify the correct customer number, and then update the transaction to reprocess it. |
22 |
| DUMMY Cust# Used | A miscellaneous credit was posted to the account for
the dummy customer that was specified on the Customer Entry Lockbox Import Report. This message is an exception. |
22 |
| Customer # is inactive on ARSC | The Customer
Setup record for the customer identified in the transaction is
inactive. Edit the Customer Setup record to activate the customer record, and then update the transaction in ETCC to reprocess it. |
22 |
| Customer #/name | The customer number and name. This message is an exception. |
22 |
Line-level messages
This table shows the errors that can occur at the line level when you receive inbound EDI 820 Payment Order/Remittance Advice documents. The cause or corrective action is also shown.
| Message | Cause or corrective action | Error # |
|---|---|---|
| [####] Invalid Incoming Invoice Number | The invoice is a non-numeric value. In ETCC, update the invoice number, and then update the transaction to reprocess it. | 20 |
| [####] Not Found: Edit or Charge Back | The invoice number is a valid numeric value but cannot be matched to a customer’s credit or Receive on Account transactions. In ETCC, update the invoice number and then update the transaction to reprocess it. | 20 |
| [####] Not Found: Edit or Roll to UC | The invoice number is a valid numeric value but cannot be matched to a customer’s scheduled payments. In ETCC, update the invoice number, and then update the transaction to reprocess it. | 20 |