INVALID TRAN CODE

Check your csv spreadsheet and make sure valid tran codes and modifiers are listed in Column 3 and 4. Adjust any entries and resubmit your csv file.

BATCHTRN: LOAN NOT FOUND

Verify on your spreadsheet that the account number is correct. The account number must include the office, like so: OOOOAAAAAA.

INVALID PAYMENT METHOD FOR TRAN

This error can occur for many reasons. One of the most common is that you attempt to run a Write-off transaction (tran code 2510-05) on a precomputed loan. Write-off transactions can only occur if the account is payment method 6 (interest bearing). You will need to first convert the account from precomputed to interest-bearing (tran code 2741-01), and then you can run the Write-off transaction on the account.

SKIPPED AS DUPLICATE

The transmission cannot run duplicate transactions on the same account in the same transmission unless one of two adjustments are made:

1.You have the JCL Option set up for your institution that turns off duplicate monitoring.

2.You enter different text in Column 11 for each transaction. For example, you could type “First payment” for the first transaction and “Second payment on 02/01/2021” for the second transaction. The batch transmission will run successfully for both transactions. Remember: The information you type in Column 11 will be added to Collection Comments unless an option is set during the transmission run. See JCL Options for more information.

ACCOUNT IS NOT OPENED

This error might occur if the borrower paid off the account by the time the .csv was created and transmitted. It might also be a clerical error due to the wrong account number being entered. Check your .csv file or the account in CIM GOLD to ensure proper processing.

MISSING TRAN AMOUNT

See the Available Tran Codes table for important fields that must accompany each transaction. If processing a Spread Payment (tran code 690), you must include all three Amount fields (Columns 8-10):

•Amount Field #1: Amount to principal

•Amount Field #2: Amount to interest

•Amount Field #3: Amount to reserves

 
These three amounts are totaled to determine the total transaction amount.

NO BACKDATING PAST CUST LAST TRAN DATE

This error message only appears if a JCL Option is set that blocks transactions with an effective date backdated before the last transaction date (LNTRAN). If that JCL option is NOT set, the effective date of the transaction will instead be adjusted to match the last transaction date (so the transaction will not fail).

**WARNING: EVENT CODE NOT RECOGNIZED. USING DEFAULT OF H – OTHER ACTUAL DISCHARGE

This message is just a warning. This warning appears when you include accounts to be written off (tran code 2510-05) but fail to include an event code (Column 6). If you fail to include an event code, the transaction will still run, but the system will assign event code H (other actual discharge) to the account. See the following topics for more information:

•Tran Code 2510-05, Full Write-off

•IRS Form 1099-C Screen

**WARNING: GENERAL CATEGORY NOT RECOGNIZED. USING DEFAULT OF 82 – CHARGE OFF NONREAL ESTATE

This message is just a warning. This warning appears when you include accounts to be charged off (tran code 2200-01) but fail to include a new general category (Column 6) on the charged-off account. If you do not include a new general category, the transaction will still run, but the system will assign general category 82 (charge-off non-real estate). See Tran Code 2022-01 for more information.

**WARNING: FEE CODE NOT RECOGNIZED. USING DEFAULT OF 1 – MISCELLANEOUS

This message is just a warning. This warning appears when you include fee assessment transactions (tran code 660) but fail to include which miscellaneous fee you want to assess to the account (Column 6). If you do not include a miscellaneous fee code, the transaction will still run, but the system will assign Fee Code 1 (Miscellaneous). See the following topics for more information:

•Tran Code 660, Assess Loan Fees

•Miscellaneous Fees

•Miscellaneous Fee Processing

•Miscellaneous Fees list view table on the Marketing and Collections screen

**WARNING: PAYMENT MODIFIER NOT RECOGNIZED. USING DEFAULT OF 35 – LOCKBOX IN FOLLOWING TRANSACTION

This message is just a warning. This warning appears when you include payment transactions (tran code 2600-25) but fail to include which modifier to assign the payment transaction to show in History. If you do not include a payment descriptor (Column 6), the transaction will still run, but the system will assign Descriptor Code 35 (Lockbox). See Tran Code 2600-25 for more information.