Transaction |
Tran |
Description |
Payment |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
022-01 |
This transaction performs a loan charge off for the full amount of the principal balance. It does not close the loan (also see the Charge-off transaction 2022-01). The Automatic Charge-Off transaction box displays the following fields:
This transaction performs the following file maintenance:
This transaction does not close the loan. The principal balance does not change. However, the General Ledger is adjusted as explained below. This transaction also performs account reclassification of the loan amounts in the General Ledger. Posting field number L-104 (principal charge-off/recovery), L-204 (principal charge-off contra), L-105 (interest recoveries), and L-205 (interest charge-off contra) allow you to further refine the posting to the General Ledger. The journal transaction will send the reference number to the G/L. If the Journal Reference Number field is left blank, the program will automatically input the loan number. This transaction appears on the Charged Off Loans Posting Journal and the Charged Off Loans Trial Balance Reports (FPSRP220). Precomputed loans must be converted to a daily simple interest (payment method 6) prior to processing this transaction. This is done on the Convert Precomputed Loans screen, using teller number 8960. The non-accrual book balance is written to history instead of the principal balance if the loan is in non-accrual status. The Automatic Charge-Off transaction can be initiated automatically by the system if institution option CODY is set up. In addition, afterhours update function 24 must be turned on. This sets the frequency when the system will check the delinquency levels of loans in order for the Automatic Charge-Off transaction to process. To have institution option CODY or update function 24 activated, please submit a work order. |
Correction: See Automatic Charge-Off Reversal Transaction. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
022-02 |
This transaction reverses the charge off by removing the information in the fields mentioned above (Automatic Charge-Off transaction) and replacing the general category with one that you select that is not an 80, 82, 83, 84, 86, 87, 88, or 89 (also see Charge-Off Reversal transaction 2022-02). This transaction also performs account reclassification of the loan amounts in the General Ledger. Posting field number L-104 (principal charge-off/recovery), L-204 (principal charge-off contra), L-105 (interest recoveries), and L-205 (interest charge-off contra) allow you to further refine the posting to the General Ledger. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Repossess Transaction | 022-03 |
This tran code functions identically to tran code 2203. |
Correction: See Reverse Repossess Transaction. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Reverse Repossess Transaction | 022-04 |
This tran code functions identically to tran code 2204.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Dealer Interest Decrease | 200-01 |
This is a journal transaction that decreases the Dealer Prepaid Interest/Premium. This transaction also does the offset to the General Ledger account via the Autopost. The Dealer Interest Decrease transaction box displays the following fields:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Dealer Interest Increase | 210-01 |
This is a journal transaction that increases the Dealer Prepaid Interest/Premium. This transaction also does the offset to the General Ledger account via the Autopost. The Dealer Interest Increase transaction box displays the following fields:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The 461 transaction is issued during the Cancel VSI Insurance transaction (tran code 2890). This transaction determines the amount of commissions earned based on the cancellation code and the effective date of tran code 2890. On a flat cancel, the entire amortized amount is reversed from the General Ledger. This leaves the remaining amount the same as the original unearned. A 100 transaction is then issued to clear the remaining unearned commissions. On an insured request, the 461 transaction will amortize the commissions from the Policy Effective Date to the Effective Date on the 2890 transaction. The difference between this unearned amount and the unearned amount on the policy is then adjusted in the General Ledger. A 100 transaction is then issued to clear the remaining unearned commissions. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Additional Advance | 500 |
This transaction works in conjunction with the Additional Advance CIM GOLD loan screen. Before using this transaction, the loan must be set up to allow advances. This is done on the Additional Advance CIM GOLD screen. Refer to the documentation for the Additional Advance screen for more details. The Additional Advance transaction (tran code 500) is used to disburse funds to the borrower that the institution had committed to at origination time but were holding back until a future date. Generally, a portion of the loan commitment was disbursed at origination time. This transaction is used to disburse some, or all, of the remaining commitment. This transaction processes a field debit (tran code 500) to the principal balance (a principal increase). The funds can then be given to the borrower by cash, check (mod 77), or using a journal transaction (mod 78). The Additional Advance transaction box includes the following fields:
When processed, the transaction will increase the loan principal balance. It will also update the Disbursed Amount and the Number of Advances on the Additional Advance screen. Before the transaction is completed, the program checks the Commitment Amount and the Disbursed Amount fields to ensure that the transaction amount does not exceed the commitment amount. It also checks the Advance Expiration date. If it is in the past, the transaction will fail. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
LOC Advance for Check/Cash | 500-50 | The LOC Advance transaction for check/cash (500-50) advances the customer money against their loan. It debits the applicable General Ledger account for that amount for disbursement directly to the customer via cash or check withdrawal. This transaction requires an SOV. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
LOC Advance for Journal | 500-52 | The LOC Advance transaction for journal (500-52) advances the customer money against their loan. It allows the advance to be run as a journal directly out of the LOC. This transaction requires an SOV. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Write-off a Charged-off Loan | 580 |
When a loan is written off, you are actually closing the loan by using the Pay-off transaction (tran code 580). You should use the Pay-off transaction code 580 by Journal In. This should be followed by a manual teller G/L debit transaction (tran code 1800) to reduce the Charge-off Recoveries G/L by Journal Out. These transactions close the loan account and remove all monetary balances from the G/L. Be sure the general category is correct as it will be reported to the credit repositories. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Pay-to-Zero But Leave With "Open" Status | 830 / 2830 |
For line-of-credit payment method 5, 9, 10, or 11 loans only, to pay a loan to zero but leave it with an "open" status, process this transaction for the amount and date selected from teller inquiry 197. When the transaction is processed, it will display history showing the portions to interest, principal, and late charges. Note: Reserves and miscellaneous fees must be cleared prior to the processing of this transaction. For commercial lines of credit (payment method 9, 10 or 11), this transaction will create a billing record that appears on the Billing Summary screen. If this transaction is corrected, the billing record will be deleted. If a loan is locked in for a payoff, the message "NO TRAN - LOAN LOCKED IN" will be displayed, and the transaction will not be processed. Note on 2830 Pay-To-Zero with Capitalized Interest: The Teller Tran 1160/10 calls the loan 2830 Tran, which in turn calls the 830 tran and credits the capitalized interest amount to the YTD interest. Pay to Zero 2830-00: Pay to Zero – 2830-01: |
Correction tran code: 838 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Charge-Off | 2022-01 |
This transaction performs a loan charge off for the full amount of the principal balance. It does not close the loan. This transaction is similar to the Automatic Charge-off transaction (tran code 022-01) except this transaction also reclassifies all miscellaneous fees. The Autopost determines how the fees are reclassified (also see the 022-01 transaction). A maximum of 10 different fee codes can be reclassified. If more than 10 different fee codes are on the account, the message "ERROR - MORE THAN TEN MISC. FEES" will appear. The Charge-Off transaction box displays the following fields:
If using CIM GOLD, you need to first convert the precomputed loan to an interest-bearing loan using the Convert Precomputed to Interest Bearing function, then open GOLDTeller and fill in the charge-off information for the Charge-Off transaction. This transaction performs the following file maintenance:
Transaction code 136 (Charge-Off Summary transaction) launches once a Charge-Off transaction has been run. The 136 transaction provides a summary of the charge off. The following fields are displayed as part of the Charge-Off Summary: charge-off balance, total of income fees, total of non-income fees, and total of insurance refunds. An institution option, COOP, is available that will allow this transaction to work differently depending on the number placed in the option. If this option is left blank, the Charge-Off transaction will continue to work as it has been. If the COOP option is set to "1," then the following will occur when the Charge-Off transaction is run:
If the COOP option is set to "2," the Charge-Off transaction will do everything option 1 does, in addition to the following:
This transaction does not close the loan. The principal balance does not change. However, the General Ledger is adjusted as explained below. This transaction performs account reclassification of the loan amounts in the General Ledger. Posting field numbers L-104 (principal charge-off/recovery), L-204 (principal charge-off contra), L-105 (interest recoveries), and L-205 (interest charge-off contra) allow you to further refine the posting to the General Ledger. In addition, posting field L-27 (miscellaneous fees code) within L-23 (miscellaneous loan fees) is also used to reclassify the miscellaneous loan fees to the charge-off G/L. This transaction appears on the Charged Off Loans Posting Journal and the Charged Off Loans Trial Balance Reports (FPSRP220). Precomputed loans must be converted to a daily simple interest (payment method 6) prior to processing this transaction. This is done on the Convert Precomputed Loans screen using teller number 8960. Insurance commissions will be finalized with this transaction. |
Correction: See Reverse Charge-Off. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Reverse Charge-Off | 2022-02 |
This transaction reverses the charge off by removing the information in the fields mentioned above (tran code 2022-01) and replacing the general category with one that you select that is not an 80, 82, 83, 84, 86, 87, 88, or 89. This transaction also reverses all history and reclassifies fees to the general category entered. This transaction also performs account reclassification of the loan amounts in the General Ledger. Posting field numbers L-104 (principal charge-off/recovery), L-204 (principal charge-off contra), L-105 (interest recoveries), and L-205 (interest charge-off contra) allow you to further refine the posting to the General Ledger. Transaction code 136 (Charge-Off Summary transaction) launches once a Charge-Off transaction has been run. The 136 transaction provides a summary of the charge off. The following fields are displayed as part of the Charge-Off Summary: charge-off balance, total of income fees, total of non-income fees, and total of insurance refunds. This transaction will not, however, reverse the loan back to a precomputed loan once its been converted to an interest-bearing loan, as described in the Charge-Off description above. Note: In order to run the Reverse Charge-Off transaction, the Charge-Off Summary history must be the last history on the account. If any file maintenance or monetary transactions have been processed on the account after the Charge-Off transaction, the charge-off reversal must be processed manually. Insurance commissions will be finalized with this transaction. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
30-Day Interest Inquiry | 2170-00 |
This transaction opens an inquiry screen, where you can enter the account number and effective date (the date to which you want interest calculated). Once you enter the account number and effective date, a new display screen appears showing:
This transaction also initiates the Interest-Only Payment transaction (tran code 2600-03) to appear. |
6 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Waive Interest Inquiry | 2180-00 |
This inquiry displays the amount of interest due. The inquiry transaction box displays:
Once you press <Enter>, it displays the following:
This inquiry initiates the Waive Interest transaction (tran code 2510-01). |
6 Correction: No (inquiry only) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Repossess Transaction | 2203 |
This transaction identifies that property securing the loan has been repossessed. The Repossess transaction box displays the following fields:
This transaction performs the following file maintenance:
The Repossession field is updated on the Credit Life & Disability screen with the principal balance. This transaction also performs account reclassification of the loan amounts in the General Ledger. The general category and charge-off date on the loan will not be changed with the Repossess transaction if the loan is charged off (the loan has a general category of 80, 82, 83, 84, 86, or 87). |
Correction: See Reverse Repossess Transaction. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Reverse Repossess Transaction | 2204 |
This transaction reverses the Repossess transaction by removing the information in the fields mentioned above (Repossess transaction). It requires that you enter a general category. The general category and charge-off date will not be changed with the Reverse Repossess transaction if the loan is charged off (general category 80, 82, 83, 84, 86, or 87). This transaction also performs account reclassification of the loan amounts in the General Ledger. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deferment Inquiry Transaction | 2270-01 |
This inquiry displays the deferment amount due on a loan. It displays the payment method, due date, effective date, principal balance, total loan fees, total late charges, and interest due for a deferment payment. The Deferment Inquiry transaction box displays:
On a simple interest loan (payment method 6), the interest is calculated from the date last accrued to the effective date. This can be in the future or the past. If the date is too far in the future or if the date is before the date of the last transaction, an error will appear. On a precomputed loan (payment method 3), the effective date is ignored and the "interest" is calculated as 1 percent of the principal balance. The Deferment Inquiry transaction also includes all outstanding late fees and miscellaneous fees. If the loan has a VSI policy (insurance type 90), then one month’s premium is included in the deferment amount due. The premium amount is calculated by subtracting the original P/I from the current P/I. This equals one month’s premium. All items are displayed separately with the total deferment amount at the end. The Deferment Payment transaction (tran code 2600-11) is then automatically initiated with the account number, deferment amount, and effective date already filled in. The Deferment transaction (tran code 2600-13) will automatically be displayed after the Deferment Inquiry transaction if the deferment Code found on the Consumer Fields screen is anything but 0 (California). The Deferment Notice transaction (tran code 2270-02) is automatically run after the Deferment transaction. Please see tran codes 2270-02 and 2600-13 below for more information concerning these transactions. Note: If the loan is two or more months delinquent, the Deferment Inquiry is displayed and the delinquency is noted at the bottom of the inquiry. When this occurs, the Deferment Payment transaction (2600-11) is not automatically initiated. Also see Deferment Payment transaction (tran code 2600-11) below. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deferment Notice | 2270-02 |
This transaction is automatically initiated after the Deferment transaction (tran code 2600-13). This transaction lists all the deferment activity associated with the account. The loan must be a payment method 3 (precomputed) or 6 (daily simple interest) loan in order for this transaction to process. See the Deferment transaction description below for more information. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Pre-Payment Penalty Interest | 2310-01 |
This transaction runs a General Ledger Miscellaneous Credit (310). It uses the Prepayment Penalty or Minimum Interest field on the GOLD Services > Autopost Setup > Loans > G/L Account Identifiers By Loan Type screen for the G/L account number. This transaction updates a loan's year-to-date interest (LNYTDI). This displays in loan history as a 310 transaction with the description "Pre-Payment Penalty Int." If this transaction is reversed, it runs a 318 transaction. The Loan Account Number will always be displayed in the Journal Reference Number field on reports when a 2310 transaction is run. Because of this, the Journal Reference Number field has been marked as a Host Hidden Field in GOLDTeller > Administrator Options > Transaction Design > Transaction Field Properties because it cannot be overwritten. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Partial Write-Off | 2510-00 |
This transaction reduces the principal balance by the amount of the transaction. It is used when you are charging off only a portion of the actual principal balance rather than the full principal balance. It would be used, for example, if you needed to reduce the principal balance so it would be below the state limit for filing small claims. For example, if the state limit for filing a small claim is $3,000, and your loan balance was $3,200, you would run the transaction for $200; leaving a principal balance of $3,000. This transaction automatically debits the General Ledger account by the amount of the transaction, and credits that amount to the principal balance. The General Ledger number is pulled from the G/L Account Identifiers by Loan Type screen (in Loans > System Setup or in GOLD Services). Institution option OP04 ANAC allows a partial charge-off if a loan is not in a non-accrual status. The history description for this transaction is "Prtl W/Off Cr." This transaction updates the Partial Write-Off field. It also feeds to the Daily Statistics Report (FPSRP210 and FPSRP211). If you need to do a full charge off, refer to the Charge-Off Transaction (tran code 022-01). This amount is not used in any regulatory reporting. If you report to the FDIC, use the Partial Charge Off fields (tran code 860). |
All Correction: Yes |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Waive Interest Transaction | 2510-01 |
The Waive Interest Transaction box displays:
With this transaction you can waive past interest or future interest. If you are waiving future interest, you must reduce the interest rate to equal what future interest you are waiving (enter it in the Effective Rate field on the transaction inquiry screen). If you are waiving past interest, the Waive Interest Inquiry (tran code 2180), explained above, shows the amount owing from the effective date to today. In the Tran Amount field, type the amount of interest that you are waiving. Processing this transaction will automatically change the Date Last Accrued to the date this transaction was run, and the Date Interest Paid To field will reflect the date the interest has been paid to using this transaction. The amount in the Accrued Interest field on the transaction shows the amount of past interest that can be waived. The history description for this transaction is "Waive Interest." This transaction updates the Interest Waive Date and Interest Waive Amount fields. |
6 Correction: Yes |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Judgment Transaction | 2510-02 |
This transaction is run once the institution has been awarded a judgment. It changes the principal balance of the loan to the amount of the judgment. The following fields are displayed; however, you do not need to enter data in all the fields.
Using this transaction increases or decreases the principal balance by the difference between the current principal balance and the judgment amount. This is done as a journal transaction. This transaction automatically debits or credits the General Ledger account number pulled from the G/L Account Identifiers by Loan Type screen (in Loans > System Setup or in GOLD Services) for the amount you write off. A different General Ledger number can be used for accounts that are charged off versus those that are not. The transaction also performs the following functions:
In addition, this transaction can change the future interest rate. This may be because the judge has included the ability to accrue future interest on the judgment amount at a different rate. You can also change the rate to zero if interest cannot be accrued beyond the judgment date. Precomputed loans (payment method 3) must be converted to a daily simple-interest loan (payment method 6) before running this transaction. Institution option OP14 PJPL prohibits the Judgment transaction on precomputed loans. It also forces the judgment amount to be the same as the principal balance. |
6 Correction: Yes |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Sale of Security | 2510-03 |
This transaction performs a credit to the principal balance for the amount of the transaction. The Sale of Security transaction box displays:
The history description for this transaction is "Sale of Security." This transaction does not check for CP2 eligibility. When this transaction is processed, the system will automatically update the Sale of Security date (L2RRSD) and amount (L2NASA) fields on the Valuation & Credit Risk tab of the CIM GOLD Loan Account Detail screen. The amount field is updated with the outstanding principal balance minus the LIP undisbursed balance at the time the transaction is processed—this is not the amount the principal balance was reduced by. If institution option OP03 CISS is set, the transaction will collect interest and pay late charges, fees, and principal following the order set up in the Payment Application group box on the Payment Detail tab on the Account Detail screen. It will also update the Date Last Accrued and Date Interest Paid To fields on the Balance & Dates tab on the Account Detail screen to the date of the transaction. If institution option OP02 APCO is set, this transaction can be run on charged-off accounts. |
3, 5, 6 Correction: Yes |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Curtailment from Partial Payment | 2510-04 |
This transaction will debit partial payments (tran code 500) and automatically credit the principal balance (tran code 510) as a curtailment at the same time. The same edits (SOV, TOV, etc.) are used as with all other field credit (510) and field debit (500) transactions. This transaction processes each transaction separately, and they will appear in history as two separate transactions. |
0, 5, 7 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Full Write-off Transaction | 2510-05 |
This transaction can only be run on payment method 6 loans (daily simple interest). If you need to run this transaction on any other payment method, the loan must be converted to payment method 6 prior to running the transaction. This transaction will do the following:
If institution option OP10-CIFW is set to "Y," all open insurance policies will be refunded and cancelled. In order to correct the Full Write-off transaction, the Full Write-off Summary history must be the last history on the account. If any other transactions or file maintenance have been processed after running the Full Write-off transaction, the transaction must be corrected manually. This transaction can be used on the Daily Statistics Report (FPSRP211) to show charged-off accounts moving from active charge-off status to non-active status (dead file). Insurance commissions will be finalized with this transaction. |
6 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Sale of Security w/Tax | 2510-06 |
This transaction performs a credit to the principal balance for the amount of the transaction. The Sale of Security transaction box displays:
The history description for this transaction is "Sale of Security." This transaction does not check for CP2 eligibility. When this transaction is processed, the system will automatically update the Sale of Security date (L2RRSD) and amount (L2NASA) fields on the Valuation & Credit Risk tab of the CIM GOLD Loan Account Detail screen. The amount field is updated with the outstanding principal balance minus the LIP undisbursed balance at the time the transaction is processed—this is not the amount the principal balance was reduced by. Note: The General Ledger number the Sales Tax will be credited to should be set up in GOLD Services, Autopost Setup Menu, G/L Account Identifiers by Loan Type. If institution option OP03 CISS is set, the transaction will collect interest and pay late charges, fees, and principal following the order set up in the Payment Application group box on the Payment Detail tab on the Account Detail screen. It will also update the Date Last Accrued and Date Interest Paid To fields on the Balance & Dates tab on the Account Detail screen to the date of the transaction. If institution option OP02 APCO is set, this transaction can be run on charged-off accounts. |
3, 5, 6 Correction: Yes |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Field Credit to Principal (check) | 2510-47 |
This transaction applies a field credit to the principal balance. Transaction origination codes (TORCs) identify which G/L (income or expense) the amortization should be posted to.
Overview This feature affects individual principal decreases posted in conjunction with a field credit to principal (tran code 2510-47 or 2510-48) or principal decreases posted in conjunction with a loan payment (tran code 2600-16 or 2600-17). The teller transaction (tran code 2510-47 (chk) and tran code 2510-48 (jnl)) must be used if you want to calculate the income on the principal decrease when it is posted as an individual principal decrease. When a principal decrease is posted (tran code 2510 (field credit to principal)) during the transaction, the following actions will occur: 1. The amount of the principal decrease will be divided by the current principal balance prior to the principal decrease to determine the percentage of the principal decrease. 2. The remaining fee is multiplied by the percentage and that amount will immediately be amortized. Example: Current principal balance is $100,000, and a principal decrease of $20,000 would equal a 20% reduction. If the remaining fees are $1,500.00, then 20% x $1,500.00 would be $300.00. The $300.00 would be posted to income or expense. This amount will appear in loan history as a separate item and will be posted to the G/L during the afterhours. 3. The date of last amortization will not be updated. This will allow the regular amortization to process at monthend. When the amortization of the principal decrease is processed, it will appear on the appropriate Deferred Fees and Costs daily reports: Deferred Costs/Premiums Amortization Report (FPSRP035), Deferred Fees/Discounts Amortization Report (FPSRP077), and Deferred MSRs Amortization Report (FPSRP156). The Bulk Activity Loan Payment transaction (tran code 2600-16 (chk)) must be used if you want to calculate the income on the principal decrease when it is posted as part of the payment. For more information on interest rate changes and principal decreases, see the Deferred Fees in CIM GOLD with Interest Rate Changes and Principal Decreases section in section 2.4, Deferred Fees and Income. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Field Credit to Principal (journal) | 2510-48 |
See Field Credit to Principal (tran code 2510-47 (chk)) for details.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Waive Multiple Late Charges | 2570-00 |
This transaction provides the ability to waive late charges either by a monetary amount or by the number of late charges. Example: Two late charges were assessed for $15.00 each, resulting in the amount of $30.00 in late charges due. You could enter "1" in the Waive No. of Lt Chrg box, and $15.00 would be waived. This transaction updates the Times Late, Times Waived, and Times Past Due fields. This will only waive late charges from live history. Once the late charges have been moved to dead history, they cannot be waived (dead history is history that is usually over a year old). |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Enhanced Payoff Transaction | 2580-00 |
The Enhanced Payoff Transaction (2580) should be used to process loan payoffs. If there are deferred amounts on a loan, this transaction will run a Modification Reapply first and then proceed with the loan payoff. The 2580 transaction performs both the reapply and the payoff in one. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Clear Non-Accrual/ Reclassify |
2584 |
This transaction will delete the checkmark in the Non-Accrual? field, clear the amount in the Non-Accrual Book Balance field, update the Non-Accrual End date field on the Valuation & Credit Risk tab of the CIM GOLD Loan Account Detail screen, and, in General Ledger, it will reclassify the balance between the principal balance and the non-accrual book balance. The transaction will send the loan number to the G/L if the Jnl Reference Nbr box on the transaction is left blank. Institution option STRN (Allow Special Transactions with Supervisor Override) is needed for this transaction. Note: This transaction replaces the 584 transaction (Remove Non-Accrual Status on a Loan). |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
CP2 Transaction (Exception Payment) | 2600-00 |
This is not a monetary transaction, although it can be processed in connection with a loan payment. This transaction can be run with or without the institution using the CP2 Transaction Processing Rules screen in GOLD Services. The CP2 Transaction box displays:
The CP2 Transaction advances the Due Date (LNDUDT) to a current status. Definition of Current: Once the due date is advanced to the month the transaction is processed, it then compares the due date to the CP2 Transaction date. If the new due date is within 10 days of the CP2 Transaction date, the due date is advanced by one frequency (if the loan has a frequency of "1," it would advance to the next month). The result is that the loan due date will always be advanced to at least 10 days greater than the date the CP2 was processed. Example: The due date is 02/08/05. On 04/05/05 the CP2 Transaction is processed. The due date would be advanced to the next month (05/08/05). Note: If the CP2 is processed in connection with a loan payment, remember that the loan payment will advance the due date one frequency, plus the CP2 transaction will advance the due date as mentioned in the above paragraph. The CP2 Transaction advances the loan Due Date (LNDUDT). Institution option OPO3 CP2R will advance the loan term and maturity date by the same number of frequencies by which the loan due date is advanced. This transaction also clears the amount in the Applied to Payment field. This transaction updates the CP2 Transaction Dates field. (There are four date fields. It updates the first empty field. Once all fields are full, it writes over the oldest date.) The history description for this transaction is "CP2." When any transaction that tests for CP2 eligibility is run (such as Insurance Payment), if the account is eligible, then the CP2 Transaction will automatically appear in GOLDTeller. If this transaction is run in conjunction with a payment, and the payment must be reversed, the CP2 Transaction must be reversed before reversing the payment. If the amount of credit insurance refunds and/or pre-computed interest refund is enough to pay off a loan, the message "REFUNDS COULD CLOSE LOAN/SEE PAYOFF" will be displayed when any of the following transactions are processed:
Be aware that these refunds may not in themselves be enough to pay off the loan; it may require a portion of the payment that is being posted. Example As you attempt to post the loan payment, the system will return with the following message: "REFUNDS COULD CLOSE LOAN/SEE PAYOFF." You would then process a Payoff transaction, which reduces the principal balance by $40.00, and then use a portion of the $75.00 to apply toward the remaining payoff amount. You would then refund the difference to the customer. |
3, 6 Correction: Yes |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Insurance Payment | 2600-01 |
This transaction is processed if the monthly loan payment is received from an insurance company (e.g., Accident & Health, Involuntary Unemployment). It is the same as posting a regular payment (tran code 600). The Insurance Payment transaction box displays the following fields:
This transaction includes an Insurance Type drop-list field and a Waived Fee Amount field. By indicating the Insurance Type, the information will be stored in history identifying where the payment was received from. If an amount is entered in the Waived Fee Amount field, the transaction will reduce the amount in the Late Charges Due field. Note: You may want to change the Waived Fee Amount description to "waived late charges" in the GOLDTeller setup to make it more clear. When making an insurance payment, an open policy must be in effect for the insurance type for which you are making the payment, or the transaction will not run. If you don’t enter a late charge amount:
Note: Some states don’t allow late charges to be collected after injuries or layoffs. You will need to determine what late charges were assessed before and after the injury, and waive the applicable charges. The history description for this transaction is the type of insurance you entered in the Insurance Type field on this transaction (for example, "A&H Ins Payment"). The Insurance Claim Amount and Insurance Claim Date fields are updated with the transaction amount and the transaction date. If the Claim Amount field already has an amount in it, the new transaction amount will be added to the amount in the field. The Insurance Claim Date will be changed to the new date from the transaction. The Insurance Claims Paid Report (FPSRP216) shows these transactions. This transaction will test for CP2 eligibility if the CP2 rules have been set up on the CP2 Transaction Processing Rules screen in GOLD Services. (Refer to the CP2 Transaction (2600-00) above.) If, after taking the payment into consideration, the amount of credit insurance refunds and/or precomputed interest refund is enough to pay off a loan, the message "REFUNDS COULD CLOSE LOAN/SEE PAYOFF" will be displayed when any of the following transactions are processed:
Be aware that these refunds may not in themselves be enough to pay off the loan; it may require a portion of the payment that is being posted. Example As you attempt to post the loan payment from the insurance company, the system will return with the following message: "REFUNDS COULD CLOSE LOAN/SEE PAYOFF." You would then process a Payoff transaction (on the Payoff screen), which reduces the principal balance by $40.00, and then use a portion of the $75.00 insurance payment to apply toward the remaining payoff amount. You would then refund the difference of $15 to the customer. |
3, 6 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Collection Payment | 2600-02 |
This transaction is processed when the loan payment is received by a third party (such as an attorney or collection agency). The attorney deducts his or her collection fee and forwards a new check to you, which is the payment amount minus his fee. Using this transaction increases the principal balance by the amount of the fee, and combines the principal increase amount with the check received and posts the full loan payment. (It does both a journal and a check transaction). The Collection Payment transaction box displays the following fields:
Note: This transaction is different from the Agency Payment transaction (tran code 2600-10) because this transaction increases the principal balance by the fee amount. Example: The actual loan payment amount is $160.00. The attorney received the borrower’s check for $160.00 but held back the attorney fee of $20.00. The attorney forwarded a check to you for $140.00. You would process the check as follows: In the Tran Amount field, enter "160.00." In the Collection Fee Amt, enter "20.00." In the Check In field, enter "140.00." The transaction will increase the principal balance by $20.00 (tran code 500 journal). It will then process a loan payment for $20.00 (tran code 600 journal), and another loan payment for $140.00 (tran code 600 check). The history description for this transaction consists of three descriptions: "Collection Fee, Collection Pmt, Collection Pmt." If the amount of credit insurance refunds and/or pre-computed interest refund is enough to pay off a loan, the message "REFUNDS COULD CLOSE LOAN/SEE PAYOFF" will be displayed when any of the following transactions are processed:
Be aware that these refunds may not in themselves be enough to pay off the loan; it may require a portion of the payment that is being posted. Example As you attempt to post the loan payment, the system will return with the following message: "REFUNDS COULD CLOSE LOAN/SEE PAYOFF." You would then process a payoff transaction, which reduces the principal balance by $40.00, and then use a portion of the $75.00 to apply toward the remaining payoff amount. You would then refund the difference to the customer. |
3, 6 Correction: No |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Interest-Only Payment | 2600-03 |
The amount of this transaction must be for at least 30 days of interest (even if 30 days of interest isn’t due), plus fees and late charges. The 30-Day Interest Inquiry identifies the interest amount (see 30-Day Interest Inquiry (transaction code 2170-00)). Option OP04 IPCL, if set to "N" (no), will stop the transaction if the loan is a contract (when the Originated or Purchased? Field is set to "Purchased"). Note: If institution option IORC (Interest-Only Requirement Code) is set to "1," then the following requirements must be fulfilled before an interest-only payment will be allowed:
The Interest-only Payment transaction box displays the following fields:
This transaction rolls the loan due date at least one payment frequency when the 30-day interest amount is paid. The transaction disregards the payment application (LNAPPL) and applies the money to fees, late charges, interest, and principal (in that order). Once the fees and late charges are paid, it then posts to all interest that is accrued, and if any amount is left over, it then applies that amount to principal. (If the amount of interest accrued is not at least as much as 30-days interest, you still must collect the 30-day interest amount and the difference is credited to the principal balance.) The Applied to Payment field is always cleared to zero. When you process this transaction:
This transaction does not affect variance fields. The history description for this transaction is "Int Only Payment." This transaction will test for CP2 eligibility if the CP2 rules have been set up on the CP2 Transaction Processing Rules screen in GOLD Services. (Refer to CP2 transaction (tran code 2600-00) above.) If the amount of credit insurance refunds and/or pre-computed interest refund is enough to pay off a loan, the message "REFUNDS COULD CLOSE LOAN/SEE PAYOFF" will be displayed when any of the following transactions are processed:
Be aware that these refunds may not in themselves be enough to pay off the loan; it may require a portion of the payment that is being posted. Example As you attempt to post the loan payment, the system will return with the following message: "REFUNDS COULD CLOSE LOAN/SEE PAYOFF." You would then process a payoff transaction, which reduces the principal balance by $40.00, and then use a portion of the $75.00 to apply toward the remaining payoff amount. You would then refund the difference to the customer. |
6 Correction: Yes |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Mail-in Payment | 2600-04 |
This transaction works like a regular payment (tran code 600) and follows the same rules.
The history description for this transaction is "Mail_In Payment." This transaction can be used with the CP2 Transaction Processing Rules screen in GOLD Services. Also see the CP2 Transaction (2600-00) description above. If the amount of credit insurance refunds and/or pre-computed interest refund is enough to pay off a loan, the message "REFUNDS COULD CLOSE LOAN/SEE PAYOFF" will be displayed when any of the following transactions are processed:
Be aware that these refunds may not in themselves be enough to pay off the loan; it may require a portion of the payment that is being posted. Example As you attempt to post the loan payment, the system will return with the following message: "REFUNDS COULD CLOSE LOAN/SEE PAYOFF." You would then process a payoff transaction, which reduces the principal balance by $40.00, and then use a portion of the $75.00 to apply toward the remaining payoff amount. You would then refund the difference to the customer. |
3, 6 Correction: Yes |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Walk-in Payment | 2600-05 |
This transaction works like a regular payment (tran code 600) and follows the same rules. The Walk-in Payment transaction box displays the following fields:
The history description for this transaction is "Walk_in Payment." This transaction can be used with the CP2 Transaction Processing Rules screen in GOLD Services. Also see the CP2 transaction (2600-00) description. If the amount of credit insurance refunds and/or pre-computed interest refund is enough to pay off a loan, the message "REFUNDS COULD CLOSE LOAN/SEE PAYOFF" will be displayed when any of the following transactions are processed:
Be aware that these refunds may not in themselves be enough to pay off the loan; it may require a portion of the payment that is being posted. Example As you attempt to post the loan payment, the system will return with the following message: "REFUNDS COULD CLOSE LOAN/SEE PAYOFF." You would then process a payoff transaction, which reduces the principal balance by $40.00, and then use a portion of the $75.00 to apply toward the remaining payoff amount. You would then refund the difference to the customer. |
3, 6 Correction: Yes |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Death Claim Payment | 2600-06 |
This transaction is processed when you receive a check from the insurance company upon death of one of the borrowers. The check may or may not be enough to pay off the loan. The Death Claim transaction box includes the following fields:
When processed, this transaction will accrue and pay interest on the current principal balance up to the date of the death, plus the number of days that were entered in the Interest Days field. If option 1 (see below) is used and nothing is entered in the Interest Days field, the program defaults to "30." Institution option DCOP has the following three options that will affect this transaction: Setting DCOP option 1 will do the following: Setting DCOP option 2 will do the following: Setting DCOP option 3 will do the following: Also, the principal balance is decreased effective the same date for which the interest was accrued (based on what was entered in the Interest Days field). The system then calculates interest up to today on the reduced principal balance. Note: Some state laws only allow you to collect interest up to 30 days after the date of death. Other states allow you to collect interest up to the date the claim check was received, or 30 days of interest, whichever is less. Note: This transaction will not run if the loan does not have a life insurance policy (INTYPC = 50-59). The history description for this transaction is "Death Claim." On the Credit Life & Disability screen for all policies, except the life insurance policy, the date of death is automatically entered in the Date Cancelled field, and a Cancellation Code of "4 - Insured Request" is entered. These policy amounts are also refunded (credited to the principal balance) with this transaction. For payment method 6 loans that refund interest back to the borrower, the interest will be credited to the principal balance. For the life insurance policy, a Cancellation Code of "8 - Death Claim" is added and the cancellation date is entered in the Date Cancelled field. This will cause the unearned premium for the life insurance to be fully earned at monthend. If you are using the Assurant Insurance Company transmission, the cancellation information for all policies will be sent with the next monthly transmission. If the claim check is for enough money to pay the loan off (including the rebates) this transaction will also close the loan. This transaction does not process fees or late charges. You must post or waive them prior to processing this transaction. If a pay-off record exists, you must drop it prior to processing this transaction. If the G/L account numbers for rebates are not set up in GOLD Services, the transaction will not process. WARNING: If the death claim check was not enough to pay off the loan and the DCOP institution option is not "3," these insurance policies are still cancelled. If you don’t want them cancelled, you should not use this transaction as the transaction refunds the unearned premiums and places the cancelled date on the policies on the Credit Life & Disability screen. If the Death Claim Payment is not enough to pay off the loan, interest and amortizing fees will not be refunded. The Insurance Pmt Amt Received and Insurance Pmt Received Date fields are updated with the transaction amount and the transaction date. If the "claim amount" field already has an amount in it, the new transaction amount will be added to the amount in the box. The insurance claim date will be changed to the new date. The Insurance Claims Paid Report (FPSRP216) shows these transactions. Insurance commissions will be finalized with this transaction. |
0, 3, or 6 Correction: Yes |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Regular Payment with CP2 Eligibility Test | 2600-07 |
This transaction works exactly like a regular payment (tran code 600). It follows all the same rules as a regular payment, except it tests the account to see if it is eligible for a CP2 (exception payment) transaction (tran code 2600-00). If the account is eligible, the message "ELIGIBLE FOR CP2" and the CP2 transaction window will both automatically appear on the screen. If the account is not eligible, the message "INELIGIBLE FOR CP2" will appear. The Regular Payment with CP2 Eligibility Test transaction box displays the following fields:
The history description for this transaction is "Regular Payment." Refer to the CP2 transaction (tran code 2600-00) for more details on how the loan due date advances. If the amount of credit insurance refunds and/or pre-computed interest refund is enough to pay off a loan, the message "REFUNDS COULD CLOSE LOAN/SEE PAYOFF" will be displayed when any of the following transactions are processed:
Be aware that these refunds may not in themselves be enough to pay off the loan; it may require a portion of the payment that is being posted. Example As you attempt to post the loan payment, the system will return with the following message: "REFUNDS COULD CLOSE LOAN/SEE PAYOFF." You would then process a payoff transaction, which reduces the principal balance by $40.00, and then use a portion of the $75.00 to apply toward the remaining payoff amount. You would then refund the difference to the customer. |
3, 6 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Automatic Payments From Partial Payments | 2600-08 |
The following items provide general information on partial payments. (See also transaction 2510-04—Curtailment from partial payment.) Update Function 84 Afterhours update function (84) will automatically debit the loan Partial Payment field and post a loan payment. It can be run daily, weekly, or monthly. When payments are automatically posted from partial payments, the debits from partial payments accompany each transaction instead of being accumulated and debited as a lump sum at the end. (There will be a separate debit from partial payment for each loan payment, late charge, and fee payments.) When using this update function, the loan must meet the following conditions:
This process functions as follows: With update function 84 set, but none of the institution options set, during the afterhours process, the system will compare the loan payment (P/I plus reserve 1 and/or 2) with the amount in partial payments. If there is enough money in partial payments to post a full payment, it will post a loan payment (tran code 600) and then debit partial payments. Three institution options pertaining to paying late charges and miscellaneous fees, allowing the loan to be paid "in the future," and processing excess funds as a curtailment are also available. They are as follows: OPPP PPLF—Partial Payments–Pay Late Charge/Fees? OPPP PPPA—Partial Payments–Pay Ahead? Examples: A. In July, if a loan has a due date in July or August, the payment would be posted. B. In July, if a loan has a due date of September or later, the payment would not be posted unless this option to pay in advance is used. OPPP PPPC—Partial Payments–Pay Curtailment? Note: None of the options will function without at least a full loan payment being posted at the same time. Any or all of the options can be set. Another institution option, UBAP, will cause update function 84 to use a 2510 transaction instead of a 510 for principal decreases. All transactions are posted with a supervisor override (SOV) and as a TORC 61. They are identified in loan history as a payment from partial payments except the loan fees. All transactions will appear on the Transaction Journal by Tran Origination Code Report (FPSRP041). Any transactions that fail will appear on the Afterhours Processing Exceptions Listing (FPSRP013). A failure of one these transactions may require a manual debit to partial payments. WARNING: Prior to using this transaction, please contact the FPS GOLD financial team as your Autopost may need to be adjusted for using TORC 61. Note: When a loan has a repayment plan and a partial payment is made, it must be run through the BAP or TBAP for the repayment plan to be updated. If the transaction has TORC 61 (which is only created when the afterhours has a payment from partial being applied to the loan), the repayment plan will be skipped. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
No Advance Payment Transaction | 2600-09 |
This transaction works similarly to a regular payment transaction (tran code 600), but does not roll the due date or increment the installment number. (Funds are posted to the loan based on the payment application code (i.e., interest, principal, late charges, fees, etc.)) The No Advance Payment Transaction box displays the following fields:
The history description for this transaction is "No Advance Payment." If the amount of credit insurance refunds and/or pre-computed interest refund is enough to pay off a loan, the message "REFUNDS COULD CLOSE LOAN/SEE PAYOFF" will be displayed when any of the following transactions are processed:
Be aware that these refunds may not in themselves be enough to pay off the loan; it may require a portion of the payment that is being posted. Example As you attempt to post the loan payment, the system will return with the following message: "REFUNDS COULD CLOSE LOAN/SEE PAYOFF." You would then process a payoff transaction, which reduces the principal balance by $40.00, and then use a portion of the $75.00 to apply toward the remaining payoff amount. You would then refund the difference to the customer. Note: If using the Roll Due Date Within feature (Payment Detail tab on the Account Detail screen), this transaction will clear the Remaining Portion Due field when it is run. This transaction will not take into consideration any data in these fields during processing. |
Correction: Yes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Agency Payment | 2600-10 |
This transaction performs a payment on a loan in which a collection agency received the full payment and subtracted their fee. The remaining money is then sent to the institution. The full payment amount should be placed in the Tran Amount field; the fee amount charged by the collection agency should be entered in the Collection Fee field; and the remaining check amount should be entered in either the Check In or Cash In fields. Note: This transaction always posts funds in the following order: principal balance, interest, then either late charges or loan miscellaneous fees, depending on what order they are set up for in the Payment Application field. Note: The remaining money must be either cash or check. The transaction won’t process mixed cash and check amounts. Note: This transaction is different from the Collection Payment transaction (tran code 2600-02) because this transaction does not increase the principal balance by the fee amount. The Agency Payment transaction box displays the following fields:
The transaction will post the transaction amount to the loan. The collection fee is debited to the General Ledger account specified. The General Ledger account for collection agency fees can be set up on the G/L Account Identifiers by Loan Type screen (in Loans > System Setup or in GOLD Services). Example The Agency Payment transaction should be run with $100.00 in the Tran Amount field, $25.00 in the Collection Fee field, and $75.00 in either the Check In or Check Out fields. Consequently, $100.00 will be posted to the loan, and $25.00 will be debited to the General Ledger account. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deferment Payment Transaction | 2600-11 |
The Deferment Payment Transaction does the following:
The last three deferments are displayed as follows:
The Deferment Payment Transaction box displays the following fields:
The Deferment Payment Transaction is correctable. However, you cannot correct it by pressing <F8> in the usual manner. You can correct it by selecting "Journal/Forwarding" from the Functions menu. Find the deferment transaction you want to correct, and correct it from there. Click the <Correct> button and the Deferment Payment Transaction box will come up with all fields filled in and the Correction box checked. You can click <Transmit> to correct the transaction. HINT: When setting up the Deferment Payment transaction on your GOLDTeller system, it is recommended that the Account Number, Tran Amount, and Effective Date be the first three fields. This is because these fields are automatically filled in when the transaction is initiated by the Deferment Inquiry Transaction (tran code 2270-01). The cursor will be on the first field after these three fields. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Allotment Payment | 2600-12 |
This payment posts by journal to the loan account and debits the General Ledger account specified in the Bank Account (NSF Check/Allotment Pmt) field on the G/L Account Identifiers by Loan Type screen (in Loans > System Setup or in GOLD Services). The Allotment Payment transaction box displays the following fields:
The history description for the transaction is "Allotment Payment." This transaction will check to see if the amount of the payment is greater than the payoff amount. If so, the message "REFUNDS COULD CLOSE LOAN/SEE PAYOFF" is displayed. |
3, 6 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deferment | 2600-13 |
This transaction processes deferment payments on accounts. It can be processed on delinquent accounts and will spread the funds according to the payment application. The transaction will calculate the deferment based on a code that can be different for each state. The Deferment transaction box displays the following fields:
The Deferment transaction processes deferments based on the deferment Code found on the Consumer Fields screen in the Loan System. This transaction is automatically displayed after the Deferment Inquiry transaction (tran code 2270-01) is run and the deferment Code on the Consumer Fields screen is anything but 0 (California). You can make any necessary changes and then run the transaction. The Deferment Notice transaction (tran code 2270-02) is automatically initiated after the Deferment transaction. You can process another Deferment Inquiry transaction after the notice has been processed. To run the Deferment transaction, the loan must meet the following criteria:
Additional reasons to disallow a deferment include:
|
3, 6 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
2600-16 |
This transaction will post a loan payment using a 600 transaction and, if extra funds are included, it will use the institution setup Payment Posting Priority screen to determine if the extra funds go to additional payments or will be posted as a principal decrease. The teller only has to post one transaction and the program will then post each item as a separate transaction. (See the Payment Posting Priority screen help in Loans > System Setup.) If a principal decrease is part of the transaction and if institution option AYPD is set, this transaction will also amortize the fee during the process. The monthend amortization continues to process but will use the new remaining amount. (See the Payment Posting Priority screen help in Loans > System Setup.) When the amortization of the principal decrease is processed, it will appear on the appropriate Deferred Fees and Costs daily reports: Deferred Costs/Premiums Amortization Report (FPSRP035), Deferred Fees/Discounts Amortization Report (FPSRP077), and Deferred MSRs Amortization Report (FPSRP156). The Bulk Activity Loan Payment transaction must be used if you want to calculate the income on the principal decrease when it is posted as part of the payment. The Bulk Activity Loan Payment transaction displays:
For more information on interest rate changes and principal decreases |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bulk Activity Loan Payment (journal) |
2600-17 | See Bulk Activity Loan Payment (chk) (tran code 2600-16 (chk)) for details. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Loan Payment-TBAP (check/cash) | 2600-18 | This transaction allows the teller to specify where any extra check/cash amount is applied. The categories are 1- Principal Curtailment, 2- Escrow, 3- Partial/Unapplied Payments, 4- Late Fees. This transaction overrides the order of application specified in the Payment Application (e.g., on the Account Detail screen, Payment Detail tab). TBAP Transaction Processing Payment Amount—Amounts in this field are applied toward the current payment owing on the loan by generating a 600 payment transaction. For amounts entered greater than the payment due: If an amount is entered greater than the current payment owing, future payments will be made until the amount remaining in the field falls below the current payment owing or goes to zero. For amounts entered less than the payment due: If an amount is entered less than the current payment (or for remaining funds after full future payments are made), the following will happen:
Escrow Amount—Amounts in this field are credited to the escrow on the loan (reserve 1) by generating a 510-62 transaction. Late Fee Amount—Amounts in this field are paid towards any late charges owing on the loan (LNLATE) by generating a 550 transaction. For any amounts greater than the late charges owing, the following will happen:
Partial Payment—For PM0, PM4, PM7 or PM8 loans, the amount in this field will generate a partial payment transaction (tran code 510-33) on the loan.
Principal Amount—The amount in this field will be applied to the loan as a Principal Curtailment (tran code 510-47).
Send in a work order to have this transaction and Loan Payment-TBAP (journal) (tran code 2600-19) set up. You can also set up the transactions yourself. To set up the Loan Payment-TBAP for Check/Cash Transaction in GOLDTeller,
Now you need to change the field name for the five fields listed in the table below.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Loan Payment-TBAP (journal) | 2600-19 | See Loan Payment-TBAP (check/cash) for details. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Death Claim Quote | 2606-00 |
This transaction opens an inquiry screen, where you can enter the account number, interest days, and effective date (date of death). Once you enter this information, a new display screen appears showing:
If the loan does not have an open life insurance policy, this transaction will not run. This transaction will also initiate the Death Claim Payment transaction (tran code 2600-06) to appear. |
Correction: No (Inquiry Only) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
NSF-Pmt Reversal (Reverse payment for nonsufficient funds) | 2608-01 |
This transaction is used to reverse payments for non-sufficient funds. This transaction does the following:
The following fields appear on the NSF-Pmt Reversal transaction box.
|
Correction: Yes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
NSF-Renewed Acct | 2660-01 |
This transaction is used when an account is renewed, the old account was paid off by check, and that check was returned due to non-sufficient funds. This transaction does the following:
The following fields appear on the NSF-Renewed Acct transaction box:
|
Correction: Yes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Reinstate Loan | 2800 |
This transaction closes an open loan and re-opens a paid-off loan. The purpose of this transaction is when a customer borrows more money to close out an existing loan and opens another loan. Then, a short time later, the customer decides not to keep the new loan and wants the old loan back. This transaction will then reverse all activity on both loans, close the new loan, and re-open the old loan. In order to use this transaction, institution option OP02 STRN must be set to "Y." The following fields appear on the Reinstate Loan transaction box. The information entered in these fields reflects that of the new loan.
There is no correction for this transaction. This transaction performs the following actions in the following order:
All transactions that are reversed are run as journal using the original TORC.
At this point, the loan that was opened is now closed. The system will now proceed to open the original loan (which is closed). Note: Any payments that were reversed on this loan will not be reapplied to the other loan. They must be handled separately after this transaction has successfully completed. For the closed loan:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Pay-To-Zero | 2830-00 |
Pay-to-Zero—Update the YTD interest for capitalized loans. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Pay Loan Fees | 2850 |
Pay Loan Fees—Use this transaction to pay a miscellaneous fee on a loan account, which will decrease the Total Loan Fees field. History will identify what the fees are for. Loan fees are assessed by a tran code 660. With Organization Option XFEE (Use Extended Loan Misc Fees) turned on, Miscellaneous Fee Codes will be displayed on the CIM > Loans > Account Information > Fees & Late Charges & Penalties screen. See Appendix I – Miscellaneous Fee Codes for a list of fees. See also tran code 850. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Force VSI Transaction | 2870-00 |
When this transaction is run, it does several things. It sets up an insurance record on the Credit Life & Disability screen and fills in many of the fields on that screen. Option OP06 AMVP allows more than one insurance type 90 (VSI insurance) on a loan. The Force VSI Insurance transaction box displays:
The transaction will also update the following fields:
The following are the fields on the Credit Life & Disability screen that are updated when this transaction is run:
An institution option (OP06 IVSI) is available that automatically calculates the interest on the premium using the calculation provided by CNI Insurance Company. For payment method 6 loans, the interest will be calculated and the new P/I payment will include the interest on the premium. It will be divided by the remaining term. For payment method 3 loans, the interest will be placed in the finance charge fields on the Credit Life & Disability screen. It will also be added to the principal balance of the loan. When the force-placed insurance is cancelled, the refund of the finance charge will be calculated and subtracted from the principal balance and the remaining finance charge amount. If an amount is left in the remaining finance charge, that amount will be taken at monthend. The following fields are pulled from the Insurance Premium G/L and Commission Percentages screen (in Loans > System Setup or in GOLD Services).
The following fields on the Credit Life & Disability screen are also set up.
This transaction also processes the following General Ledger transactions: 1810: G/L transaction to Unearned Interest account listed on the G/L Account Identifiers by Loan Type screen (in Loans > System Setup or in GOLD Services). 1811: G/L transaction to corporate and/or branch G/L number from the Insurance Premium G/L and Commission Percentages screen (in Loans > System Setup or in GOLD Services). |
3, 6 Correction: No |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Force Place Homegard Insurance | 2870-07 |
This transaction is similar to the Force VSI Transaction (tran code 2870-00), except this transaction deals with Homegard insurance instead of VSI insurance. Other differences include: The Amortization Method (INAMOR) on the Credit Life & Disability screen is updated to "12–Pro Rata Daily" whenever this transaction is run. Also, the Refund Rule on that same screen is updated to "0–1-day rule (365 base)." When this transaction is run, it does several things. It sets up an insurance record on the Credit Life & Disability screen and fills in many of the fields on that screen (as described below). Option OP06 AMVP allows more than one insurance type 97 (Homegard insurance) on a loan. The Force Place Homegard Insurance transaction box displays:
The transaction will also update the following fields:
The following are the fields on the Credit Life & Disability screen that are updated when this transaction is run:
An institution option is available (OP12 IHGL) that will assess a finance charge according to the following formula if the loan is a payment method 3 loan (precomputed): Finance charge = INOBAL * ((LNPICN * LNTRMO) - (LNPICN * (1 - ((1 + ((LNOAPR / 100) / 12)) ^ (- (LNTRMO))) * (12 / (LNOAPR / 100))) / (LNPICN * LNTRMO) - (LNPICN * LNTRMO) - (LNPICN * (1 - ((1 + ((LNOAPR / 100) / 12)) ^ (- (LNTRMO)))) * (12 / (LNOAPR / 100))) / (LNTRMO / 12)) / 12 * LNTRMO For payment method 6 loans (daily accrual), the institution option (OP12 IHGL) will assess a finance charge according to the following formula: Finance charge = INOBAL * ((LNPICN * INTERM) - (LNPICN * (1 - ((1 + ((LNRATE / 100) / 12)) ^ (- (INTERM))) * (12 / (LNRATE / 100))) / (LNPICN * INTERM) - (LNPICN * INTERM) - (LNPICN * (1 - ((1 + ((LNRATE / 100) / 12)) ^ (- (INTERM)))) * (12 / (LNRATE / 100))) / (INTERM / 12)) / 12 * (INTERM - Months already passed) The following fields are pulled from the Insurance Premium G/L and Commission Percentages screen (in Loans > System Setup or in GOLD Services).
For precomputed loans (payment method 3), the following fields are also set up. These fields are found on the Credit Life & Disability screen.
This transaction also processes the following General Ledger transactions: 1810: G/L transaction to Unearned Interest account listed on the G/L Account Identifiers by Loan Type screen (in Loans > System Setup or in GOLD Services). 1811: G/L transaction to corporate and/or branch G/L number from the Insurance Premium G/L and Commission Percentages (in Loans > System Setup or in GOLD Services). |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Force Place Flood Insurance | 2870-08 |
This transaction is similar to the VSI Force Place Transaction (tran code 2870-00). Changes were made to adjust the P/I payment by the change amount when any of these insurances is added. This allows for multiple insurances to be placed and/or removed. Only insurances placed after the addition of these new transactions will contain the information to make the adjustment upon removal. When insurance is force placed, the P/I change amount and the payment effective date are stored. This information is used to update P/I changes that are recorded in LNPINX/LNPIEF and LNPNX1/LNPEF1 - LNPNXC/LNPEFC. This same information is used to adjust these fields when insurance is removed. The change amount is added to or subtracted from any P/I amount that is effective after the payment effective date and before the term end. Note: The company and agent numbers are both zero, so this information should be added to the insurance record after it is placed. When this transaction is run, it does several things. It sets up an insurance record on the Credit Life & Disability screen and fills in many of the fields on that screen. Option OP06 AMVP allows more than one insurance type 98 (Flood insurance) on a loan. The Force Place Flood Insurance transaction box displays:
The transaction will also update the following fields:
The following are the fields on the Credit Life & Disability screen that are updated when this transaction is run:
An institution option (OP06 IVSI) is available that automatically calculates the interest on the premium using the calculation provided by CNI Insurance Company. For payment method 6 loans, the interest will be calculated and the new P/I payment will include the interest on the premium. It will be divided by the remaining term. For payment method 3 loans, the interest will be placed in the finance charge fields on the Credit Life & Disability screen. It will also be added to the principal balance of the loan. When the force-placed insurance is cancelled, the refund of the finance charge will be calculated and subtracted from the principal balance and the remaining finance charge amount. If an amount is left in the remaining finance charge, that amount will be taken at monthend. The following fields are pulled from the Insurance Premium G/L and Commission Percentages screen (in Loans > System Setup or in GOLD Services).
For precomputed loans (payment method 3), the following fields are also set up. These fields are found on the Credit Life & Disability screen.
This transaction also processes the following General Ledger transactions: 1810: G/L transaction to Unearned Interest account listed on the G/L Account Identifiers by Loan Type screen (in Loans > System Setup or GOLD Services). 1811: G/L transaction to corporate and/or branch G/L number from the Insurance Premium G/L and Commission Percentages (in Loans > System Setup or in GOLD Services). |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Force Place Fire Insurance | 2870-09 |
This transaction is similar to the VSI Force Place Transaction (tran code 2870-00). Changes were made to adjust the P/I payment by the change amount when any of these insurances is added. This allows for multiple insurances to be placed and/or removed. Only insurances placed after the addition of these new transactions will contain the information to make the adjustment upon removal. When insurance is force placed, the P/I change amount and the payment effective date are stored. This information is used to update P/I changes that are recorded in LNPINX/LNPIEF and LNPNX1/LNPEF1 - LNPNXC/LNPEFC. This same information is used to adjust these fields when insurance is removed. The change amount is added to or subtracted from any P/I amount that is effective after the payment effective date and before the term end. Note: The company and agent numbers are both zero, so this information should be added to the insurance record after it is placed. When this transaction is run, it does several things. It sets up an insurance record on the Credit Life & Disability screen, and fills in many of the fields on that screen. Option OP06 AMVP allows more than one insurance type 99 (Fire insurance) on a loan. The Force Place Fire Insurance transaction box displays:
The transaction will also update the following fields:
The following are the fields on the Credit Life & Disability screen that are updated when this transaction is run:
An institution option (OP06 IVSI) is available that automatically calculates the interest on the premium using the calculation provided by CNI Insurance Company. For payment method 6 loans, the interest will be calculated and the new P/I payment will include the interest on the premium. It will be divided by the remaining term. For payment method 3 loans, the interest will be placed in the finance charge fields on the Credit Life & Disability screen. It will also be added to the principal balance of the loan. When the force-placed insurance is cancelled, the refund of the finance charge will be calculated and subtracted from the principal balance and the remaining finance charge amount. If an amount is left in the remaining finance charge, that amount will be taken at monthend. The following fields are pulled from the Insurance Premium G/L and Commission Percentages screen (in Loans > System Setup or in GOLD Services).
For precomputed loans (payment method 3), the following fields are also set up. These fields are found on the Credit Life & Disability screen.
This transaction also processes the following General Ledger transactions: 1810: G/L transaction to Unearned Interest account listed on the G/L Account Identifiers by Loan Type screen (in Loans > System Setup or GOLD Services). 1811: G/L transaction to corporate and/or branch G/L number from the Insurance Premium G/L and Commission Percentages (in Loans > System Setup or in GOLD Services). |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Force Place LPD Insurance | 2870-71 |
This transaction is similar to the Force VSI transaction (tran code 2870-00), except this transaction deals with LPD (limited property damage) insurance instead of VSI insurance. Other differences include: When you run this transaction, certain fields will be affected by the State Code and Loan Type (both located on the Credit Life & Disability screen) applied to the loan. The following paragraphs explain these differences. If the State Code is anything besides 17, 18, 21, 29, or 47, then the transaction will be rejected.
When this transaction is run, it does several things. It sets up an insurance record on the Credit Life & Disability screen and fills in many of the fields on that screen (as described below). Option OP06 AMVP allows more than one insurance type 71 (LPD insurance) on a loan. The Force Place LPD Insurance transaction box displays:
The transaction will also update the following fields:
The following are the fields on the Credit Life & Disability screen that are updated when this transaction is run:
An institution option is available (OP12 IHGL) that will assess a finance charge according to the following formula if the loan is a payment method 3 loan (precomputed): Finance charge = INOBAL * ((LNPICN * INTERM) - (LNPICN * (1 - ((1 + ((LNRATE / 100) / 12)) ^ (- (INTERM))) * (12 / (LNRATE / 100))) / (LNPICN * INTERM) - (LNPICN * INTERM) - (LNPICN * (1 - ((1 + ((LNRATE / 100) / 12)) ^ (- (INTERM)))) * (12 / (LNRATE / 100))) / (INTERM / 12)) / 12 * INTERM For payment method 6 loans (daily accrual), the institution option (OP12 IHGL) will assess a finance charge according to the following formula: Finance charge = INOBAL * ((LNPICN * INTERM) - (LNPICN * (1 - ((1 + ((LNRATE / 100) / 12)) ^ (- (INTERM))) * (12 / (LNRATE / 100))) / (LNPICN * INTERM) - (LNPICN * INTERM) - (LNPICN * (1 - ((1 + ((LNRATE / 100) / 12)) ^ (- (INTERM)))) * (12 / (LNRATE / 100))) / (INTERM / 12)) / 12 * (INTERM - Months already passed) The following fields are pulled from the Insurance Premium G/L and Commission Percentages screen (in Loans > System Setup or in GOLD Services).
For precomputed loans (payment method 3), the following fields are also set up. These fields are found on the Credit Life & Disability screen.
This transaction also processes the following General Ledger transactions: 1810: G/L transaction to Unearned Interest account listed on the G/L Account Identifiers by Loan Type screen (in Loans > System Setup or GOLD Services). 1811: G/L transaction to corporate and/or branch G/L number from the Insurance Premium G/L and Commission Percentages (in Loans > System Setup or in GOLD Services). |
3, 6 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Cancel VSI Insurance | 2890-00 |
This transaction requires you to enter the account number, transaction amount, cancellation code, and effective date. The Cancel VSI Insurance transaction box displays the following fields:
This transaction triggers the Insurance Commission Adjustment transaction (tran code 461) to adjust the remaining commissions. See the Insurance Commission Adjustment transaction information above for more information on this transaction. This transaction also triggers a 100 transaction to clear remaining unearned insurance commissions and adjust the General Ledger accordingly. As the transaction is reversed and reposted, it is displayed in history as of the original transaction date. However, the actual date it was posted appears in the description section of the history. Payments are backed out and reapplied to the effective date, if the policy is cancelled "flat" (cancellation code 2). Late charges that are backed off are reassessed using the original P/I payment. If option OP15 AFCB is set to "Y," then the finance charge will only be refunded when a flat cancel is issued. The history description for this transaction is "Cancel VSI Insrn." |
3, 6 Correction: No |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Remove Homegard Insurance | 2890-07 |
This transaction is similar to the Cancel VSI Insurance (tran code 2890-00), but it is only used to cancel Homegard insurance (insurance type 97). To cancel other types of insurance, see tran codes 2890-00 (VSI), 2890-08 (Flood), 2890-09 (Fire), 2890-71 (LPD), and 2910-00 (Other). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Remove Flood Insurance | 2890-08 |
This transaction is similar to the Cancel VSI Insurance (tran code 2890-00). Changes were made to adjust the P/I payment by the change amount when any of these insurances is removed. This allows for multiple insurances to be placed and/or removed. Only insurances placed after the addition of these new transactions will contain the information to make the adjustment upon removal. When insurance is force placed, the P/I change amount and the payment effective date are stored. This information is used to update P/I changes that are recorded in LNPINX/LNPIEF and LNPNX1/LNPEF1 - LNPNXC/LNPEFC. This same information is used to adjust these fields when insurance is removed. The change amount is added to or subtracted from any P/I amount that is effective after the payment effective date and before the term end. Note: The company and agent numbers are both zero, so this information should be added to the insurance record after it is placed. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Remove Fire Insurance | 2890-09 |
This transaction is similar to the Cancel VSI Insurance (tran code 2890-00). Changes were made to adjust the P/I payment by the change amount when any of these insurances is removed. This allows for multiple insurances to be placed and/or removed. Only insurances placed after the addition of these new transactions will contain the information to make the adjustment upon removal. When insurance is force placed, the P/I change amount and the payment effective date are stored in the insurance record. This information is used to update P/I changes that are recorded in LNPINX/LNPIEF and LNPNX1/LNPEF1 - LNPNXC/LNPEFC. This same information is used to adjust these fields when insurance is removed. The change amount is added to or subtracted from any P/I amount that is effective after the payment effective date and before the term end. Note: The company and agent numbers are both zero, so this information should be added to the insurance record after it is placed. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Remove LPD Insurance | 2890-71 |
This transaction is similar to the Cancel VSI Insurance (tran code 2890-00), but it is only used to cancel Limited Property Damage insurance (insurance type 71). To cancel other types of insurance, see tran codes 2890-00, 2890-07, 2890-08, 2890-09, and 2910-00. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Cancel Other Insurance | 2910-00 |
This transaction is used to cancel credit insurance policies other than VSI, fire, and flood policies (types 90-99). For example, this transaction would be used if a new loan was originated with life and/or accident and health insurance, and the borrower did not want the insurance. You would use this transaction to cancel the policies. In addition, if during the term of the loan the borrower wants to cancel a policy, you would use this transaction to do so. Note: If institution option OP12 IHGL is on, you cannot cancel the 71 (limited property damage) insurance types with this transaction. Use the Remove LPD Insurance transaction (tran code 2890-71) instead. The transaction requires you to enter the account number, cancellation code, effective date, policy number, and an insurance policy type (types other than 90-99) or check the Cancel All checkbox. Institution option DRLP will allow the transaction to be run without the policy number. Note: If the Cancel All checkbox is checked and no policy number is entered, then all policies with no policy number will be cancelled (with the exception of policy types 90-99). The Cancel Other Insurance transaction box displays the following fields:
If the effective date on the transaction is not the same as the policy effective date (INOPND), that policy will be skipped. If the policy is cancelled "flat" (cancel code 2), payments are backed out and reapplied to the Effective Date using the original P/I payment. On an "insured request" (cancel code 4), only today’s date will be accepted in the Effective Date transaction field. The history description for this transaction is "Cancel Misc Ins." If institution option OP12 IHGL is on, the transaction will refund the finance charge amount (on payment method 3 loans) from the principal balance. The remaining finance charge will be earned at monthend. |
3, 6 Correction: No |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
2910-01 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Cancel Other Insurance Ck | 2910-02 |
This transaction is used to cancel credit insurance policies other than VSI, fire, and flood policies (types 90-99). For example, this transaction would be used if a new loan was originated with life and/or accident and health insurance, and the borrower did not want the insurance. You would use this transaction to cancel the policies. In addition, if during the term of the loan the borrower wants to cancel a policy, you would use this transaction to do so. The transaction requires you to enter the Account Number, Cancellation Code, Effective Date, Policy Number, and an Insurance Type (types other than 90-99), or check the Cancel All checkbox, fill in the Check Out Number, and fill in the Check Out Amount. Institution option DRLP will allow the transaction to be run without the policy number. Note: If the Cancel All checkbox is checked and no policy number is entered, then all policies with no policy number will be cancelled (with the exception of policy types 90-99). The Cancel Other Insurance Ck transaction box displays the following fields:
On flat cancels (Cancellation Code = 2), if the Effective Date on the transaction is not the same as the Policy Effective Date (INOPND) on the Credit Life & Disability screen, that policy will be skipped. On an insured request (Cancellation Code = 4), only today’s date will be accepted in the Effective Date transaction field. If the policy is flat cancelled, payments are not backed out like the Cancel Other Insurance transaction (tran code 2910-00) does. This transaction will change the insurance premium amount, but instead of adjusting the principal to balance with the premium changes, a check will be created to reflect what the principal change would have been. This transaction will never reverse history and reapply payments because the principal balance will not change. This transaction will not adjust the P/I payment. In General Ledger, rather than reducing the principal balance, a G/L tran code 1812 is created in the place where the principal reduction would normally be (tran code 920). At the end of the transaction, a General Ledger debit (tran code 1800) by check out will be run for the amount of premium adjustment (and finance charge, if applicable). The G/L account number used for this transaction will be the Teller Journal Clearing Account found on the G/L Account Identifiers by Loan Type screen (in Loans > System Setup or GOLD Services). Note: You must have teller 8940 set up before you can run this transaction. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Adjust Insurance Premium | 2940-00 |
This transaction is used to perform an adjustment to the account when an insurance premium must be changed. Several aspects of the account are affected. The adjustment is reported at the end of the month with regular insurance reporting. The Adjust Insurance transaction box displays the following fields:
If institution option OP09 BTAP is "Y," this transaction will not require a TOV whenever the P/I Payment (LNPICN) or the Next P/I Payment (LNPINX) changes. On the original insurance record it does the following (these fields are found on the Credit Life & Disability screen):
On the new insurance record, the transaction will cause the following to occur:
On the insurance reports (FPSRP204–Insurance-New and Cancelled VSI Insurance, FPSRP205–Insurance-Credit Life, Accident & Health, and Unemployment, and FPSRP207–Insurance-New and Cancelled Property Insurance), the old policy shows as cancelled and the new insurance record with the changes shows as a new policy. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Adjust Insurance Premium Ck | 2940-02 |
This transaction is used to perform an adjustment to the account when an insurance premium must be changed. Several aspects of the account are affected. The adjustment is reported at the end of the month with regular insurance reporting. Note: You must have teller 8940 set up before you can run this transaction. The Adjust Insurance Ck transaction box displays the following fields:
On the original insurance record, it performs the following file maintenance (these fields are found on the Credit Life & Disability screen):
On the new insurance record, the transaction will cause the following to occur:
On the Insurance reports (FPSRP204–Insurance-New and Cancelled VSI Insurance, FPSRP205–Insurance-Credit Life, Accident & Health, and Unemployment, and FPSRP207–Insurance-New and Cancelled Property Insurance), the old policy shows as cancelled and the new insurance record with the changes shows as a new policy. Changes in this transaction from the Adjust Insurance Premium transaction (tran code 2940-00) include:
|