Navigation:  Deposits > Deposit Screens > Definitions Screen Group > Transaction Options Screen > Transaction Condition Overrides tab > Condition Detail field group > Transaction Condition Override Definitions

This help page contains definitions and explanations of the transaction conditions displayed in the Transaction Condition Overrides list view on the Deposits > Definitions > Transaction Options screen.

 

 

1.   CONTRIBUTION TO A CONDUIT/ROLLOVER IRA

This transaction condition indicates when a retirement transaction other than a trustee transfer or a rollover has been requested for a conduit retirement account. If the Conduit/Rollover Account field on the Deposits > Account Information > Additional Fields screen is marked, and the requested transaction is neither a retirement trustee transfer nor a retirement rollover request, this transaction condition becomes effective according to its assigned override level. This transaction condition is ignored for all nonconduit retirement accounts.

 

2.   WITHDRAWAL WOULD TAKE ACCNT NEGATIVE

This transaction condition indicates that a transaction has been requested for a nonsweeping account which would cause the account balance to become negative.

The Sweep Funds In, Sweep Funds Out, and Can Account Go Negative fields on the Deposits > Account Information > Additional Fields screen must all be left blank. In addition, the transaction condition relating to the account’s feature (Checking, Savings, or Certificate), as well as transaction conditions 39 - CHECKING CANNOT GO NEGATIVE, 40 - CERTIFICATE CANNOT GO NEGATIVE, and 41 - SAVINGS CANNOT GO NEGATIVE, must be overridden for this transaction condition to become active. Also, if the account is allowed to go negative and the transaction will keep the account within the negative limit, then this transaction condition is used.

 

3.   BALANCE WOULD GO BELOW MINIMUM

This transaction condition indicates when a withdrawal or other nonclosing transaction has been requested for an account with insufficient funds to cover the transaction and still maintain the account’s minimum balance. If the account balance is taken below the minimum balance limit indicated in the Minimum Balance Limit field on the Deposits > Account Information > Additional Fields screen, this transaction condition becomes active.

 

If the transaction amount exceeds the account’s payable balance, excluding the uncollected funds and the minimum balance, the transaction will check whether the Can Account Go Negative field on the Additional Fields screen is left blank. If the account doesn’t allow a negative balance, transaction conditions 39 - CHECKING ACCOUNT CANNOT GO NEGATIVE, 40 - CERTIFICATE CANNOT GO NEGATIVE, or 41 - SAVINGS CANNOT GO NEGATIVE become active.

 

If the account does allow a negative balance, transaction condition 4 - BALANCE WOULD GO BELOW NEG LIMIT becomes active. If transaction condition 3 is set to be ignored in the afterhours, then accounts with minimum balance requirements and overdraft accounts can still go below the minimum balance. Under these circumstances, if an account attempts to post a transaction but doesn’t have sufficient funds to cover it, both the minimum balance and the overdraft amount available are used in posting the transaction. If transaction condition 3 is ignored, the balance of the account can be left below the minimum balance requirement.

 

4.   BALANCE WOULD GO BELOW NEG LIMIT

This transaction condition indicates that a transaction has been requested for a nonsweeping checking account with no assigned overdraft accounts. This would cause the account balance to go below the negative limit for accounts allowing negative balances. This transaction condition becomes active if the Can Account Go Negative field is marked and the amount of the transaction takes the account more negative than the account allows in the Negative Limit field (on the Deposits > Account Information > Additional Fields screen). This transaction condition is not active for accounts not allowing negative balances.

 

5.   CD - WITHDRAWALS NOT ALLOWED

This transaction condition indicates that a withdrawal has been requested for a certificate account currently not in grace. This transaction condition is used after transaction condition 11 - CERTIFICATE WITHDRAWAL DURING TERM is overridden or ignored. If there is a non-service fee withdrawal transaction on a certificate account not currently in grace (the transaction date is greater than the date in the Grace End Date field), and the Allow Withdrawals without Override field (on the Deposits > Account Information > Additional Fields screen) is left blank on the account, this transaction condition becomes active according to its assigned override level. This transaction condition is ignored for certificate accounts allowing withdrawals.

 

6.   DEPOSIT TO AN INACTIVE ACCOUNT

This transaction condition indicates that a transaction has been requested for an inactive account. If the transaction is processed, the Last Customer Contact Date (on the Deposits > Account Information > Additional Fields screen) is updated on the account. Interest postings processed through GOLDTeller (tran code 1710) use this condition. Interest postings in the afterhours do not look at account status, and this condition is ignored.

 

If the account status "INACTIVE" is displayed for the requested account in the Status field (located in the top-left corner of each screen), this transaction condition  becomes active according to its assigned override level. For your institution's online customers, options can be set to remove dormancy and inactivity statuses when customers log on to your institution's website. If set, the Last Customer Contact Date is updated, and the inactive or dormant status is removed on all accounts with the same owner. Send a work order to get these options turned on if you want to enable this feature. This transaction condition is ignored for active accounts.

 

7.   DEPOSIT TO A DORMANT ACCOUNT

This transaction condition indicates that a transaction has been requested for a dormant account. If the transaction is processed, the Last Customer Contact Date (on the Deposits > Account Information > Additional Fields screen) is updated on the account. Interest postings processed through GOLDTeller (tran code 1710) use this condition. Interest postings in the afterhours do not look at account status, and this condition is ignored.

 

If the account status "DORMANT" is displayed for the requested account in the Status field (located in the top-left corner of each screen), this transaction condition becomes active according to its assigned override level. This transaction condition is ignored for both non-dormant and interest withdrawal transactions processed in GOLDTeller. For your institution's online customers, options can be set to remove dormancy and inactivity statuses when customers log on to your institution's website. If set, the Last Customer Contact Date is updated, and the inactive or dormant status is removed on all accounts with the same owner. Send a work order to get these options turned on if you want to enable this feature. This transaction condition is ignored for active accounts.

 

8.   WITHDRAWAL FROM AN INACTIVE ACCOUNT

This transaction condition indicates that a withdrawal transaction has been requested for an inactive account. If the account status "INACTIVE" is displayed for the requested account in the Status field (located in the top-left corner of each screen), this transaction condition becomes active according to its assigned override level. This transaction condition is ignored for active accounts and interest withdrawal transactions processed in GOLDTeller. Interest withdrawals processed through GOLDTeller (tran code 1730) use this condition. Interest withdrawals processed in the afterhours do not look at the account status, so this condition is ignored.

 

9.   WITHDRAWAL FROM A DORMANT ACCOUNT

This transaction condition indicates that a withdrawal transaction has been requested for a dormant account. If the account status "DORMANT" is displayed for the requested account in the Status field (located in the top-left corner of each screen), this transaction condition becomes active according to its assigned override level. This transaction condition is ignored for both non-dormant and interest withdrawal transactions processed in GOLDTeller. Interest withdrawals processed through GOLDTeller (tran code 1730) will use this condition. Interest withdrawals processed in the afterhours do not look at the account status, so this condition is ignored.

 

10. CERTIFICATE DEPOSIT DURING TERM

This transaction condition indicates that a transaction has been requested for a certificate account during its term. If a non-interest posting transaction is requested for a certificate not currently in grace (the transaction date is greater than the date in the Grace End Date field) and the Allow Deposits Without Override field (on the Deposits > Account Information > Additional Fields screen) is left blank, this transaction condition becomes active. If the certificate is in grace and/or the account allows deposits, this transaction condition is ignored.

 

11. CERTIFICATE WITHDRAWAL DURING TERM

This transaction condition indicates whether withdrawals are allowed to certificate accounts currently not in grace. If this transaction condition is overridden or ignored, transaction condition 5 - CD - WITHDRAWALS NOT ALLOWED is used. If the certificate is not currently in grace (the transaction date is greater than the date in the Grace End Date field) and the Allow Withdrawals without Override field (on the Deposits > Account Information > Additional Fields screen) is left blank, and the request is a non-service fee withdrawal transaction, this transaction condition becomes active according to its override level. If the account is non-renewable and past the maturity date, this condition is used. If the certificate is in grace and/or the account allows withdrawals, this transaction condition is ignored, and transaction condition 5 - CD - WITHDRAWALS NOT ALLOWED is used.

 

12. EXCEEDS NO. OF CHECKS PER CYCLE LIM

This transaction condition indicates that the checking account receiving the check withdrawal will exceed its number of checks limit for the account’s current cycle. If the account’s number of checks per cycle (indicated in the Checks Count field) is greater than the Checks Limit field on the Deposits > Account Information > Activity Information screen, this transaction condition becomes active according to its assigned override level. This transaction condition is ignored if the check withdrawal request does not exceed the check limit.

 

13. EXCEEDS NO. OF DEPOSITS/CYCLE LIMIT

This transaction condition indicates that the account receiving the deposit will exceed its number of deposits limit for the current account cycle. If the account’s number of deposits per cycle (indicated in the Deposits Count field) is greater than the Deposits Limit field on the Deposits > Account Information > Activity Information screen, this transaction condition becomes active according to its assigned override level. This transaction condition is ignored if the deposit request does not exceed the deposit limit.

 

14. EXCEEDS NO. OF WITHDRLS/CYCLE LIMIT

This transaction condition indicates that the account receiving the withdrawal will exceed its number of withdrawals limit for the current account cycle. If the account’s number of withdrawals per cycle (indicated in the Withdrawals Count field) is greater than the Withdrawals Limit field on the Deposits > Account Information > Activity Information screen, this transaction condition becomes active according to the assigned override level. This transaction condition is ignored if the number of withdrawals per cycle does not exceed the withdrawal limit.

 

15. EXCEEDS NO. OF TRANSFERS/CYCLE LIMIT

This transaction condition indicates that the account making the transfer will exceed its number of transfers out limit for the current account cycle. If the account’s transfers out per cycle (indicated in the Transfers Out Count field) is greater than the Transfers Out Limit field on the Deposits > Account Information > Activity Information screen, this transaction condition becomes active according to the assigned override level. This transaction condition is ignored if the number of transfer out requests per cycle do not exceed the account’s transfer out limit.

 

16. SUSPECT STOP PAYMENT AMOUNT MATCH

This transaction condition indicates that the presented check amount matches the customer’s requested stop payment check amount. For any check cashing and withdrawal transaction requests where only the check amount matches the stop payment amount for non-expired stop payments, this transaction condition becomes active according to the assigned override level. This transaction condition is ignored if the presented check amount doesn’t match any active stop payment amount requests. If the Post Stop if Suspect field on the Deposits > Account Information > Restrictions & Warnings screen is marked for the account, this transaction condition is ignored.

 

17. SUSPECT STOP PAYMENT CHECK# MATCH

This transaction condition indicates that the presented check number is within the check number range found on a customer’s stop payment requests. For any check cashing and withdrawal transaction requests where the presented check number falls within an active stop payment check number range, this transaction condition becomes active according to the assigned override level. This transaction condition is ignored if the presented check number doesn’t match any active stop payment check number requests. If the Post Stop if Suspect field on the Deposits > Account Information > Restrictions & Warnings screen is marked for the account, this transaction condition is ignored.

 

18. STOP PMNT CHK# & AMT MATCH OR IN RNG

This transaction condition indicates any presented check whose amount matches the stop payment check amount, and the presented check number either matches the stop payment check amount or the presented check number is found within the check number range of the customer’s stop payment request. For check cashing and withdrawal transaction requests where both the presented check number and check amount find a matching active stop payment request, this transaction condition becomes active according to the assigned override level. This transaction condition is ignored if the presented check amount and check number don’t match any stop payment check amount and check number or check number range.If the Post Stop if Suspect field on the Deposits > Account Information > Restrictions & Warnings screen is marked for the account, this transaction condition is ignored.

 

19. PASSBOOK ACCT BOOK NOT PRESENT - DEP

This transaction condition indicates any monetary transaction requests to a passbook account without a passbook present. If a transaction request with no passbook present has been requested to an account with the Passbook Account? field (on the Deposits > Account Information > Additional Fields screen) marked, this transaction condition becomes active according to the assigned override level. This transaction condition is ignored if the passbook is present or the account is not a passbook account.

 

20. ACTIVITY TO EMPLOYEE ACCOUNT

This transaction condition indicates transaction requests for employee accounts from tellers without employee account security. If the teller’s security level doesn’t allow employee account access (see Field Level Security, Miscellaneous > Field Level Security), and the Employee Account field field (on the Deposits > Account Information > Additional Fields screen) is marked, this transaction condition becomes active according to the assigned override level.  This transaction condition is ignored for a teller with access to employee accounts, or for transaction requests to non-employee accounts.

 

21. ACCOUNT PAST MATURITY DATE

This transaction condition identifies transaction requests for certificates for which the maturity date has passed. If the requested certificate is open and the maturity date indicated in the Maturity Date field (on the Deposits > Account Information > Additional Fields screen) is less than the requested transaction as of date, this transaction condition becomes active according to the assigned override level. This transaction condition is ignored if the certificate is not open, the maturity date hasn’t passed, or the transaction is an interest- posting or an interest-transfer transaction with a TORC equal to 304, 333, or 357 with the Renew at Maturity field marked. The following transactions are not checked for this transaction condition: Mature/Renew Account (1180) and Update CDT (1951).

 

22. MAXIMUM CONTRIBUTION EXCEEDED

This transaction condition indicates contribution requests that will exceed the current or previous year maximum contribution limits. Maximum contribution limits vary according to your retirement plan. Retirement plans include: IRA Spousal, IRA, SEP, and Qualified. SEP plan limits for both current and previous year contributions are checked for all retirement plan accounts with the SEP field (on the Deposits > Account Information > Additional Fields screen) marked. Qualified plan limits for both current and previous year contributions are checked for all retirement plan accounts with the Qualified Plan field marked.

 

23. CHECK HOLD AMNT EXCEEDS AVAL BAL

This transaction condition indicates whether there is enough available balance to cover the addition of an over-the-counter hold for the presented check amount (transaction code 1400/3). If the over-the-counter hold amount for the requested check cashing transaction is greater than the available balance indicated in Available Balance (on the Deposit > Account Information > Account Information screen), the transaction condition becomes active. This transaction condition is ignored if the available balance is greater than the requested over-the-counter hold.

 

24. NEW ACCOUNT REQUIRES UCF

This transaction condition indicates check cashing or check deposit transaction requests with no local, non-local, or unspecified amounts for any new accounts requiring an uncollected funds hold. If a check cashing or check deposit transaction request lacks local, non-local, or unspecified amounts for a new account and the New Account Uncollected Funds Holds field (on the Deposits > Account Information > Additional Fields screen) is marked, this transaction condition becomes active according to the assigned override level. This transaction condition is ignored for accounts not requesting new account uncollected funds holds, or check transaction requests, which include local, non-local, or unspecified amounts.

 

25. ENFORCE UCF HOLDS - NONE ENTERED

This transaction condition indicates check cashing or check deposit transaction requests with no local, non-local, or unspecified amounts for an account enforcing uncollected funds holds. If a check cashing or check deposit transaction request lacks local, non-local, or unspecified amounts for an account with the Enforce Uncollected Funds Holds field (on the Deposits > Account Information > Additional Fields screen) marked, this transaction condition becomes active according to the assigned override level. This transaction condition is ignored for accounts not requesting enforcement of uncollected funds holds, or check transaction requests, which include local, non-local, or unspecified amounts.

 

26. EXTEND UCF HOLDS - NONE ENTERED

This transaction condition indicates check cashing or check deposit transaction requests without local, non-local, or unspecified amounts for an account extending an uncollected funds holds. If a check cashing or a check deposit transaction request lacks local, non-local, or unspecified amounts for a new account with the Extend Uncollected Fund Holds field (on the Deposits > Account Information > Additional Fields screen) marked, this transaction condition becomes active according to the assigned override level. This transaction condition is ignored for accounts not requesting enforcement of uncollected funds holds, or check transaction requests, which include local, non-local, or unspecified amounts.

 

27. LAST YEAR CONTRIBUTION-PAST APRIL 15

This transaction condition indicates that a retirement contribution transaction has been requested for the previous year after April 15 of the current year. If the previous year contribution request was initiated following April 15 of the current year for all retirement accounts with the Conduit/Rollover IRA field (on the Deposits > Account Information > Additional Fields screen) left blank for each account, this transaction condition becomes active according to the assigned override level. This transaction condition is ignored if the retirement contribution request transaction date is prior to or equal to April 15, or the requested account is a rollover/conduit account.

 

28. DRAWING ON UNCOLLECTED FUNDS

This transaction condition indicates a transaction request that would require use of the uncollected funds balance in order to process the withdrawal transaction amount requested. If the account’s uncollected funds (indicated in the Uncollected Funds field on the Deposits > Account Information > Account Information screen) plus the payable balance is greater than or equal to the transaction amount requested, this transaction condition becomes active depending upon the accompanying transaction condition override level. If the account’s payable balance plus its uncollected funds balance is less than the transaction amount, the account’s minimum balance is added back into the payable balance to determine whether the transaction should be processed according to both this transaction condition and transaction condition 3 - BALANCE WOULD GO BELOW MINIMUM.

 

29. ACCOUNT OWNER DECEASED - WITHDRAWAL

This transaction condition indicates that a withdrawal has been requested for an account whose IRS owner is deceased. If the account IRS owner is deceased, this transaction condition becomes active according to the assigned override level. This transaction condition is ignored if the account owner is alive. If the account is an IRA account and the owner is deceased, transaction condition 59 - IRA OWNER DECEASED is invoked.

 

30. ACCOUNT OWNER DECEASED - DEPOSIT

This transaction condition indicates that a deposit has been requested for an account whose owner is deceased. If the account IRS owner is deceased, this transaction condition becomes active according to the assigned override level. This transaction condition is ignored if the account owner is alive. If the account is an IRA account and the owner is deceased, transaction condition 59 - IRA OWNER DECEASED is invoked.

 

31. OVERDRAFTING LESS THAN CALCULATED

This transaction condition indicates whether the amount available for overdrafting is less than the amount needed to cover the withdrawal transaction. The account must have the overdraft feature set (Overdraft on the Deposits > Account Information > Account Information screen must be marked) and the Amount Code field on the Deposits > Account Information > Overdraft & Secured Loans screen must not be equal to "3" (even increments only) or "6" (increments take partial). This transaction condition is ignored for accounts with an Amount Code equal to 6. If the Amount Code equals 3, the transaction will cancel.

 

32. EXCEEDS NO. OF OTC CHECKS/CYCLE LIM

This transaction condition indicates that the account receiving the withdrawal will exceed its number of over-the-counter checks limit for the current account cycle. If the account’s over-the-counter checks per cycle number (indicated in the Over The Counter Checks Count field) is greater than the over-the-counter checks per cycle limit indicated in the Over The Counter Checks Limit field (on the Deposits . Account Information > Activity Information screen), this transaction condition override becomes active according to the override level. This transaction condition is ignored if the per cycle over-the-counter checks limit does not exceed the over-the-counter checks limit.

 

33. ATTEMPTED SIGN OFF IS OUT OF BALANCE

This transaction condition indicates out-of-balance teller signoff transaction requests for financial institutions requiring cash drawer balancing. If your financial institution requires cash drawer balancing using Institution Option OPT1/CSDR, and the teller’s journal in and journal out totals don’t match or the teller’s signoff transaction amount doesn’t equal the teller’s cash drawer balance, this transaction condition becomes active according to the assigned override level. This transaction condition is ignored if the institution doesn’t require cash drawer balancing, or the teller’s journal amounts are equal, or the teller’s signoff transaction amount does equal the teller’s cash drawer balance.

 

34. OVERRIDING EXISTING PRODUCT CODE

This transaction condition identifies product code differences for deposit open transactions for accounts previously opened through New Account Set-up. If the open transaction has requested a different Product Code than the Product Code set up in the New Account Set-Up, this transaction condition becomes active according to the assigned override level.  This transaction condition is ignored if the Product Code set up previous to the open transaction is equal to the Product Code requested with the open transaction.

 

35. MATURITY TOO FAR IN FUTURE

This transaction condition indicates a certificate-maturing transaction (1180) for a certificate account with a maturity date more than one business day in the future. If the certificate account’s maturity date (indicated in the Maturity Date field on the on the Deposits > Account Information > Additional Fields screen) is in the future, this transaction condition becomes active according to the assigned transaction condition override level. This transaction condition is ignored if the certificate account’s maturity date is not in the future.

 

36. CD - DEPOSITS NOT ALLOWED

This transaction condition identifies deposits not allowed for a certificate currently not in grace. If a non-interest posting deposit transaction has been requested for a certificate not currently in grace (the transaction date is greater than the date in the Grace End Date field) and the Allow Deposits Without Override field (on the Deposits > Account Information > Additional Fields screen) is left blank, this transaction condition becomes active depending upon the accompanying override level. This transaction condition is ignored for certificate accounts allowing deposits.

 

37. SOV NOT USED

This transaction condition is not currently used by GOLDPoint Systems.

 

38. AVAILABLE INTEREST IS ZERO ON CORR

This transaction condition identifies penalty correction transactions for certificate accounts with positive available interest that may have been affected by the original transaction.  If the penalty correction transaction has been requested for a certificate account with available interest equal to zero, this transaction condition becomes active. This transaction condition is ignored for certificates with available interest.

 

39. CHECKING CANNOT GO NEGATIVE

This transaction condition indicates that a transaction request has been requested for a checking account with insufficient funds to cover the transaction amount while ignoring the uncollected and minimum balances limits, and would take the account’s current balance negative. If a checking account cannot go negative (the Can Account Go Negative field on the Deposits > Account Information > Additional Fields screen is left blank), this transaction condition would become active according to the transaction condition override level. If this transaction condition has been overridden, then transaction condition 2 - WITHDRAWAL WOULD TAKE ACCNT NEGATIVE becomes active according to the transaction condition override level. If the checking account will be taken below its negative balance limit and needs to draw upon uncollected funds to process the requested transaction, transaction condition 4 - BALANCE WOULD GO BELOW NEG LIMIT becomes active according to the transaction condition override level.

 

40. CERTIFICATE CANNOT GO NEGATIVE

This transaction condition indicates that a transaction request has been requested for a certificate with insufficient funds to cover the transaction amount while ignoring the uncollected and minimum balances limits, and would take the account’s current balance negative. If the certificate cannot go negative (the Can Account Go Negative field on the Deposits > Account Information > Additional Fields screen is left blank), this transaction condition would become active according to the transaction condition override level. If this transaction condition is overridden, then transaction condition 2 - WITHDRAWAL WOULD TAKE ACCNT NEGATIVE becomes active according to the transaction condition override level. If the certificate will be taken below its negative balance limit and needs to draw upon uncollected funds to process the requested transaction, transaction condition 4 - BALANCE WOULD GO BELOW NEG LIMIT becomes active according to the transaction condition override level.

 

41. SAVINGS CANNOT GO NEGATIVE

This transaction condition indicates that a transaction request has been requested for a savings account with insufficient funds to cover the transaction amount while ignoring the uncollected and minimum balances limits, and would take the account’s current balance negative. If the savings account cannot go negative (the Can Account Go Negative field on the Deposits > Account Information > Additional Fields screen is left blank), this transaction condition would become active according to the transaction condition override level. If this transaction condition is overridden, then  transaction condition 2 - WITHDRAWAL WOULD TAKE ACCNT NEGATIVE becomes active according to the transaction condition override level. If the savings account will be taken below its negative balance limit and needs to draw upon uncollected funds to process the requested transaction, transaction condition 4 - BALANCE WOULD GO BELOW NEG LIMIT becomes active according to the transaction condition override level.

 

42. UPDATE PASSBOOK FOR AN INACTIVE ACCT

This transaction condition indicates that a passbook update, passbook balance forward, or a reconstruct passbook transaction has been requested for an inactive passbook account. If a passbook update, passbook balance forward, or reconstruct passbook transaction has been requested to a passbook account (Passbook Account on the Deposits > Account Information > Additional Fields screen is marked), with the account status "INACTIVE" displayed in the Status field (located in the top-left corner of each screen), this transaction condition becomes active depending upon the accompanying override level. This transaction condition is ignored for all active passbook accounts.

 

43. UPDATE PASSBOOK FOR A DORMANT ACCT

This transaction condition indicates that a passbook update, passbook balance forward, or a reconstruct passbook transaction has been requested for a dormant passbook account. If a passbook update, passbook balance forward, or reconstruct passbook transaction has been requested to a passbook account (Passbook Account on the Deposits > Account Information > Additional Fields screen is marked), with the account status "DORMANT" displayed in the Status field (located in the top-left corner of each screen), this transaction condition becomes active depending upon the accompanying override level. This transaction condition is ignored for all passbook accounts not dormant.

 

44. CONTRIBUTION TO A RETIREMENT ACCT

This transaction condition indicates that a contribution transaction has been requested for a retirement account. If the account for which the contribution has been requested is a retirement account (Retirement is marked on the Deposits > Account Information > Account Information screen), this transaction condition becomes active depending upon the accompanying override level. This transaction condition is ignored for all non-retirement accounts.

 

45. DISTRIBUTION FROM A RETIREMENT ACCT

This transaction condition indicates that a distribution was requested for a retirement account. If the account from which the distribution has been requested is a retirement account (Retirement is marked on the Deposits > Account Information > Account Information screen), this transaction condition becomes active depending upon the accompanying override level. This transaction condition is ignored for all non-retirement accounts.

 

46. BELOW SECURED LOAN LIMIT

This transaction condition indicates that a withdrawal transaction has been requested for an account without sufficient funds to provide collateral for its accompanying secured loan. If the account’s Avalable Balance (from the Deposits > Account Information> Account Information screen) is insufficient collateral for the accompanying secured loan for all withdrawal transaction requests except service fee withdrawals, this transaction condition becomes active according to its override level. This transaction condition is ignored if the collateral account will maintain sufficient collateral funds for its accompanying secured loan.

 

47. WDR TO 0 (CLOSE ACCT), ACCRUED NOT 0

This transaction condition indicates a withdrawal transaction for an account with a remaining interest accrual amount. If an account’s Accrued Interest (from the Deposits > Account Information > Interest Fields screen) is greater than zero when a closing transaction has been requested, this transaction condition becomes active depending upon the accompanying override level. This transaction condition is ignored if the account’s interest accrual amount is equal to zero.

 

48. POSTING NEGATIVE INTEREST

This transaction condition indicates accounts with a negative interest accrual balance for interest posting, withdrawal, and withholding transaction requests. If the account’s If an account’s Accrued Interest (from the Deposits > Account Information > Interest Fields screen) is negative for all interest posting, interest withdrawal, and withholding transactions, this transaction condition becomes active according to its accompanying override level. This transaction condition is ignored for accounts with interest accrual balances equal to or greater than zero.

 

49. XFER BETWEEN LN/DP, DIFFERENT HHLD #

This transaction condition indicates that a transfer transaction has been requested between a savings account and a loan account within different households. If the savings account household and the loan account household do not match for all 1160 transfer transaction requests, this transaction condition becomes active depending upon the accompanying override level. This transaction condition is ignored for all transfer requests between a loan and a deposit account with the same household.

 

50. MMDA/SVGS EXCEEDS # OF CKS/WDRS/XFRS

This transaction condition indicates accounts that are processing the seventh transaction and stops withdrawal transactions on money market checking accounts set up with general category 6 or savings accounts set up with general category 5.

 

Depending on the accompanying override level, this transaction condition becomes active if the total of the following factors (on the Deposits > Account Information > Activity Information screen) is greater than 6:

•the account’s number of withdrawals indicated in the Withdrawals Count field

•the number of checks indicated in the Checks Count field

•the number of Remote Banking transfers

•the total number of transfers

 

Checks that are converted to ACH Items standard entry class RCK, ARC, POP, or BOC, are counted as check items if a check number is sent with the ACH transaction TORC 305.

 

51. PASSBOOK ACCT BOOK NOT PRESENT - W/D

This transaction condition stops withdrawal transactions on passbook accounts when the book is not present. Every withdrawal transaction is stopped if the Passbook Account field on the Deposits > Account Information > Additional Fields screen is left blank and the account is a passbook account.

 

52. TELLER SIGNING-ON WITH A FUTURE DATE

This transaction condition stops tellers from signing onto the system too far in the future. A maximum of five days in the future is allowed with the override your institution has set up.

 

53. OTC HOLD AMNT EXCEEDS AVAL BAL

This transaction condition stops over-the-counter check transactions (transaction codes 1400-5 and 1400-6) from being processed if there are not enough available funds (as indicated in the Available Balance field on the Deposits > Account Information > Account Information screen).

 

54. MAT/REN/ROLL ACCT INACTIVE / DORMANT

This transaction condition stops the file maintenance transactions "mature, renew, and roll" (1880 transaction codes) when the account is inactive or dormant. The status of an account is found in the top left corner of all deposit screens. Inactive and dormant statuses are calculated by using the Last Customer Contact Date, Term Until Dormant, and Term Until Inactive fields on the Deposits > Account Information > Additional Fields screen.

 

55. OD WOULD NOT COVER UCF

This transaction condition indicates when an account’s payable balance is already negative because a teller did an override on a previous non-sufficient transaction that allowed uncollected funds to be drawn on. This transaction condition will allow your institution to overdraft enough to maintain the negative payable balance the account already had. This transaction condition should only be used when your institution does not allow uncollected funds to be drawn upon (transaction condition 28 - DRAWING ON UNCOLLECTED FUNDS) and you overdraft to cover these uncollected funds (Institution Option OPT6-UCOD).

 

56. ACCOUNT HAS ANALYSIS FEATURE

This transaction condition stops transactions from being processed if the account uses business account analysis based on the Account Analysis field on the Deposits > Account Information > Additional Fields screen. This transaction condition alerts the teller that account analysis may need to be updated manually.

 

57. TEST ANALYSIS FEATURE SET ON ACCOUNT

Transaction condition 57 - TEST ANALYSIS FEATURE SET ON ACCOUNT stops transactions from being processed if the account uses the test feature of business account analysis based on the Account Analysis field on the Deposits > Account Information > Additional Fields screen. This transaction condition alerts the teller that account analysis may need to be updated manually.

 

58. NSF PAYABLE BAL ON DEPOSIT W/CASHOUT

This transaction condition stops transactions from being processed on deposits where the cash-out amount exceeds the account’s current payable balance. This condition can be overridden, and when it has been, the new payable balance is a negative amount.

 

59. IRA OWNER DECEASED

This transaction condition indicates that a contribution or a distribution has been requested for a retirement account whose owner is deceased. If the owner of the retirement account is deceased and a valid death date is entered in the Death Date field (on the Deposits > Retirement > Retirement Plan screen), this transaction condition becomes active according to the assigned override level. This transaction condition is ignored if the retirement account owner is alive.

 

60. IRA OWNER AGE 70.5 IN CURRENT YEAR

This transaction condition stops contribution transactions for a retirement account in which the owner will be 70.5 years of age during the current calendar year, and for subsequent years. This condition is only used for IRA and SEP Retirement Plan Types (from the Deposits > Account Information > Additional Fields screen). This function is also retroactive, meaning if there was a prior year contribution and the owner was at least 70.5 in that year, the program will use this condition.

 

61. EXISTING CDT RECORD

This transaction condition stops closing transactions for retirement accounts that have existing CDT records. You can override the condition, or remove the CDT records from the account and then close the account.

 

62. TAKING ACCT NEG ON STMT CYCLE

This transaction condition is used to stop afterhours inclearing checks, ACH, and immediate-post ACH withdrawals from forcing deposit accounts negative on their cycle dates. If the Ignore Afterhours? field for the transaction is not checked, these withdrawal transactions are sent to GOLD ExceptionManager unposted and with an error message. The override level, ATM/GOLDPhone options, and teller transactions are not used for this transaction condition. We suggest you only use this condition if your institution allows accounts to go negative, and frequently reverses and returns transactions that take accounts negative. If Ignore Afterhours? is left blank, which is the default, all transactions that meet these conditions will be rejected. When Ignore Afterhours? is checked, transactions will force accounts negative even on their cycle nights. If the transactions are reversed and returned the following day, the transactions will appear on two separate statements.

 

63. PROCESSING FINAL TOTS CHKS-IN NOT 0

This transaction condition verifies whether the check-in totals in GOLDTeller are "0" at final sign-off. If they are not "0," an error message will display informing tellers to run either the Check to Bank transaction or the Bank Deposit transaction.

 

64. MONETARY HOLD AMT GREATER THAN BAL

This transaction condition allows a teller to add monetary holds greater than the current balance of an account.

 

65. G/L POSTING TO ANOTHER OFFICE

This transaction condition prevents a teller from running General Ledger debit or credit transactions (1800, G/L Debit or 1810, G/L Credit) to a G/L account in a different branch. It will not stop generated 1800 or 1810 transactions from processing for other transactions, such as loan payoffs.

 

66. BACKDATING NO-STMT CD BEYOND LST CYC

This transaction condition allows backdating transactions on certificate accounts with a Statement Cycle code of 000 (on the Deposits > Account Information > Additional Fields screen) and only up to the date of the last transaction instead of the beginning cycle date. This transaction only applies to accounts with a certificate feature set (on the Deposits > Account Information > Account Information screen).

 

67. ENFORCE UCF - CHECK IN/TOT UCF NOT EQ

This transaction condition appears if a teller attempts to process a check deposit transaction (1120/00) and the Check In field is not equal to the total of the Local Amount, Non-local Amount, and Unspecified Amount fields. Also, the Enforce Uncollected Fund Holds field on the Deposits > Account Information > Additional Fields screen must be selected in order for the condition to appear.

 

68. CHECK AMOUNT OVER LIMIT - MUST ADD UCF

This transaction condition is used in conjunction with Institution Option UCFF, which is an amount field that will be checked in the system whenever a transaction is run with a Check In amount in GOLDTeller. If the Check In amount is greater than or equal to the UCFF limit and uncollected funds holds are entered, the system will add an uncollected funds record to the account. If there are no uncollected funds amounts entered, this transaction condition will be invoked. The teller can then give the proper override or cancel and run the transaction with uncollected funds amounts. The default UCFF check limit is $9,999,999.99. The transaction condition will only be invoked when the Check In field on a GOLDTeller transaction equals or exceeds this limit.

 

69. # OF DEPOSIT ITEMS MUST BE ENTERED

This transaction condition will appear under the following conditions:

 

1.The Account Analysis field on the Deposits > Account Information > Additional Fields  screen is marked.

2.The transaction has a Check In amount entered.

3.The Number of Dep Items is not entered on the transaction. (The condition is not invoked if the Number of Dep Items is not a valid field for the transaction.)

 

70. Duplicate Check Number

This transaction condition appears when a teller is trying to cash a check that has already been posted to the account.

 

71. Check in Number 0

This transaction condition appears when a teller is trying to cash a check without entering a check number.

 

72. CLOSING TRAN HAS FUND HOLDS

This transaction condition is invoked only when the closing transaction (tran code 1190, deposit account close or tran code 1290, retirement account close) is processed. If there are monetary holds, uncollected funds, over-the-counter holds, or overdraft accounts using loans (Possible Reserves) and you have an override level, the closing transaction will not process until the override is entered or the funds and overdraft account are removed. If over-the-counter holds exist and the condition is overridden, the account will not close, and a hold code 13 will be placed on the account automatically. When the inclearing checks take the balance to zero, the account is closed. The closing inquiry shows these conditions, including open cards and billing accounts on safe deposit boxes. These two conditions cannot be overridden. You must close the cards and remove the billing account from the boxes so they will get billing notices for boxes once the account is closed.

 

This transaction condition was added to the Fee transaction (tran code 1750) to help your institution comply with requirements of Regulation E for more than six fees in the past 12 months. If a teller processes a non-sufficient fee and it is the seventh or greater fee for the year, this new tran condition becomes active. A decision can then be made regarding what to do with the fee. The negative/NSF descriptor used by your institution is the only fee that will invoke this condition; all others is ignored by this condition. The Ignore Afterhours, Ignore Wire Transfers, and Override ATM/Home Banking fields must all be checked.