This project will add a feature to the new Xpress Teller platform to allow CUs to define posting limits for individual tellers.  This will control the maximum amount of incoming funds (cash/checks in and other deposits) and the maximum amount of outgoing funds (cash/checks/money orders out and other withdrawals) that a teller can post during a single teller transaction via the new Xpress Teller posting tool.

• A new activation flag will be added to Express Teller Workflow Controls so that a CU can choose whether or not to activate transaction limits. (NOTE: These controls are stored by branch, but the limits are stored by employee ID. Therefore, a teller’s limits would apply only to branches at which limits have been activated.)
• Limits are entered via CU*BASE Employee Security and can be entered only for employee IDs that are authorized for teller posting in the employee profile.
• Limits need to be entered only for tellers who need them; if no limits are entered, tellers can post any amounts, just like now.
• If an employee ID is deleted or archived, limits will be deleted (there is no archive for limits on previous employees). Likewise, if an ID is changed so that it is no longer allowed to do teller posting, any limits under that ID will be cleared.
• Two limits can be set:
  • Maximum incoming/deposited funds (includes audit keys 5, 6, 7, and 9)
  • Maximum outgoing/withdrawn funds (includes audit keys 3, 4, B, and C)
• These are per-transaction limits, not daily accumulated limits. Whenever a teller uses one of the “post” buttons within Xpress Teller, the system will simply count up all of the amounts being posted, by audit key type, and if the total amount for either incoming or outgoing funds goes over the limit, a message will appear stopping the entire transaction from being posted. That warning message will have two options:
  • Backup (to make a correction, such as if there was simply a fat-finger error), OR
  • Secondary Approval (to allow a head teller/supervisor to authorize the transaction). Once a second employee ID (can’t be the same person) and password has been entered, the transaction will post as usual.
• The authority to provide secondary approval will be based on the existing “Teller override” flag in employee Special Security.
  (NOTE: This is not considered the same as other overrides and there will be no special tracking. CUs using limits should give this authority only to trusted supervisors, and auditors can use Tool #1700 Teller Audit Analysis Dashboard to monitor activity for tellers who are subject to limits.)

Status as of May 2021:  Specifications have been submitted and Project #56445 is currently awaiting approval in the project queue.

Your chef for this recipe:  Dawn Moore