Transaction History Settings

Purpose

Transaction History Settings define what transaction history is available and how it is played to callers. These settings control

  • How far back Teller searches for activity
  • How many transactions are returned
  • How playback behaves when history exists or does not exist

Key Rules (Important)

  • All numeric fields must be greater than or equal to 1
  • A value of 0 is not supported and results in no data being returned
  • A value of 99999 removes the limit (no restriction applied)

How Transaction Retrieval Works

Transaction retrieval is determined by two settings working together:

Lookback Period (Days)

Filters which transactions are eligible based on age

Maximum Number of Transactions

Limits how many of those eligible transactions are returned

Example: If 100 transactions exist in the last 90 days, and the maximum is 30 → only 30 are played.
Note: If no transactions meet both criteria, Teller plays a “no history available” message.

Configurations Supported

  • Whether history auto-advances or requires caller confirmation
  • Whether entity/account descriptions are spoken before history playback
  • Lookback periods (in days) for each transaction type
  • Maximum number of transactions returned for each type
  • Whether the number of lookback days is spoken when no history is found

Transaction Types Covered

  • General transactions
  • ACH
  • ATM
  • Credit Card payments
  • Credit Card transactions
  • Checks
  • Debit card
  • Deposits
  • Loan advances
  • Loan history
  • Point-of-sale (POS)
  • Purchases
  • Withdrawals

General vs Specific Transaction Types

  • General transactions include all transaction types (deposits, withdrawals, POS, payroll, etc.)
  • Specific transaction types (e.g., ACH, POS) filter only that category

General settings apply when a Teller feature returns a mixed result set.

Use Case

  • Lookback windows are tuned to balance usefulness and call length.
  • Maximum counts prevent excessively long Teller sessions.
  • “No history found” messaging is often simplified by not speaking the lookback period.

Lookback Periods (Days)

Applies to all “Retrieve ___ in the last X days” fields . Each field above pairs with the corresponding maximum field below.

  • Retrieve transactions in the last X days (Default: 90)
  • Retrieve ACH transactions in the last X days (Default: 365)
  • Retrieve ATM transactions in the last X days (Default: 365)
  • Retrieve credit card payments in the last X days (Default: 30)
  • Retrieve credit card transactions in the last X days (Default: 30)
  • Retrieve check transactions in the last X days (Default: 365)
  • Retrieve debit card transactions in the last X days (Default: 365)
  • Retrieve deposits in the last X days (Default: 365)
  • Retrieve loan advances in the last X days (Default: 365)
  • Retrieve loan history transactions in the last X days (Default: 365)
  • Retrieve point of sale transactions in the last X days (Default: 365)
  • Retrieve purchases in the last X days (Default: 90)
  • Retrieve withdrawals in the last X days (Default: 365)

Maximum Number of Transactions to Retrieve

Applies to all “Maximum number of ___ to retrieve” fields

  • Maximum number of transactions to retrieve (Default: 30)
  • Maximum number of ACH transactions to retrieve (Default: 50)
  • Maximum number of ATM transactions to retrieve (Default: 50)
  • Maximum number of credit card payments to retrieve (Default: 10)
  • Maximum number of credit card transactions to retrieve (Default: 10)
  • Maximum number of check transactions to retrieve (Default: 50)
  • Maximum number of debit card transactions to retrieve (Default: 50)
  • Maximum number of deposits to retrieve (Default: 50)
  • Maximum number of loan advances to retrieve (Default: 50)
  • Maximum number of loan history transactions to retrieve (Default: 50)
  • Maximum number of point of sale transactions to retrieve (Default: 50)
  • Maximum number of purchases to retrieve (Default: 30)
  • Maximum number of withdrawals to retrieve (Default: 50)
Note: Together, each lookback field and its matching maximum field determine exactly which and how many transactions callers hear in the Teller.

Field Reference

Type: Toggle/Boolean

Purpose: Controls whether transaction history automatically advances without requiring caller input.

Behavior: When enabled, Teller automatically plays the next transaction after finishing the current one. When disabled, Teller prompts the caller to continue before playing the next transaction.

Caller Impact: Callers either experience continuous playback of transactions or are prompted to control pacing between each transaction.

Default Value: Disabled

Type:Toggle/Boolean

Purpose: Controls whether the entity/account description is spoken before transaction playback.

Behavior: When enabled, Teller omits entity identification messages. When disabled, Teller announces the entity description before playing history.

Caller Impact: Callers hear either streamlined transaction playback or additional account context before history begins.

Default Value: Disabled

Type: Toggle/Boolean

Purpose: Determines whether the configured lookback period is included in “no history found” messaging.

Behavior: When enabled, Teller includes the configured lookback period in the message (e.g., “No transactions found in the last 30 days”). When disabled, Teller simply states that no transactions were found without referencing the time period.

Caller Impact: Callers receive either more specific time-frame context or simplified messaging when no transactions exist

Default Value: Disabled

Type: Input/Integer

Purpose: Defines the number of days Teller searches for general transaction history.

Behavior: Teller retrieves general transactions that occurred within the configured number of days prior to the current date. Entering 99999 removes the date restriction. Unlike transaction-type-specific settings, this setting applies when a Teller feature can return a mix of transaction types in a single result set.

This setting works together with the Maximum number of transactions to retrieve.

Caller Impact: Callers hear only general transactions that fall within the defined time window.

Default Value: 90

Note: Applies to Teller features that return mixed transaction types (Recent Transactions, Transaction Search by Date and Amount, Mortgage History, Payroll History, Recent Mortgage Payments, Check Holds)

Type: Input/Integer

Purpose: Defines the number of days Teller searches for ACH transaction history.

Behavior: Teller retrieves ACH transactions that occurred within the configured number of days prior to the current date. Entering 99999 removes the date restriction. This setting works together with the Maximum number of ACH transactions to retrieve.

Caller Impact: Callers hear only ACH transactions that fall within the defined time window.

Default Value: 365

Type: Input/Integer

Purpose: Defines the number of days Teller searches for ATM transaction history.

Behavior: Teller retrieves ATM transactions that occurred within the configured number of days prior to the current date. Entering 99999 removes the date restriction. This setting works together with the Maximum number of ATM transactions to retrieve.

Caller Impact: Callers hear only ATM transactions that fall within the defined time window.

Default Value: 365

Type: Input/Integer

Purpose: Defines the number of days Teller searches for credit card payment history.

Behavior: Teller retrieves credit card payments that occurred within the configured number of days prior to the current date. Entering 99999 removes the date restriction. This setting works together with the Maximum number of credit card payments to retrieve.

Caller Impact: Callers hear only credit card payments that fall within the defined time window.

Default Value: 30

Note: The current Site Manager UI displays this field as "Retrieve card payments in the last X days" (without "credit"). A label update is pending. This setting applies exclusively to credit card accounts.

Type: Input/Integer

Purpose: Defines the number of days Teller searches for credit card transaction history.

Behavior: Teller retrieves credit card transactions that occurred within the configured number of days prior to the current date. Entering 99999 removes the date restriction. This setting works together with the Maximum number of credit card transactions to retrieve.

Caller Impact: Callers hear only credit card transactions that fall within the defined time window.

Default Value: 30

Note: The current Site Manager UI displays this field as "Retrieve card transactions in the last X days" (without "credit"). A label update is pending. This setting applies exclusively to credit card accounts.

Type: Input/Integer

Purpose: Defines the number of days Teller searches for check transaction history.

Behavior: Teller retrieves check transactions that occurred within the configured number of days prior to the current date. Entering 99999 removes the date restriction. This setting works together with the Maximum number of check transactions to retrieve.

Caller Impact: Callers hear only check transactions that fall within the defined time window.

Default Value: 365

Type: Input/Integer

Purpose: Defines the number of days Teller searches for debit card transaction history.

Behavior: Teller retrieves debit card transactions that occurred within the configured number of days prior to the current date. Entering 99999 removes the date restriction. This setting works together with the Maximum number of debit card transactions to retrieve.

Caller Impact: Callers hear only debit card transactions that fall within the defined time window.

Default Value: 365

Type: Input/Integer

Purpose: Defines the number of days Teller searches for deposit history.

Behavior: Teller retrieves deposit transactions that occurred within the configured number of days prior to the current date. Entering 99999 removes the date restriction. This setting works together with the Maximum number of deposits to retrieve.

Caller Impact: Callers hear only deposit transactions that fall within the defined time window.

Default Value: 365

Type: Input/Integer

Purpose: Defines the number of days Teller searches for loan advance history.

Behavior: Teller retrieves loan advances that occurred within the configured number of days prior to the current date. Entering 99999 removes the date restriction. This setting works together with the Maximum number of loan advances to retrieve.

Caller Impact: Callers hear only loan advances that fall within the defined time window.

Default Value: 365

Type: Input/Integer

Purpose: Defines the number of days Teller searches for loan history transaction records.

Behavior: Teller retrieves loan history transactions that occurred within the configured number of days prior to the current date. Entering 99999 removes the date restriction. This setting works together with the Maximum number of loan history transactions to retrieve.

Caller Impact: Callers hear only loan history transactions that fall within the defined time window.

Default Value: 365

Type: Input/Integer

Purpose: Defines the number of days Teller searches for point-of-sale (POS) transaction history.

Behavior: Teller retrieves POS transactions that occurred within the configured number of days prior to the current date. Entering 99999 removes the date restriction. This setting works together with the Maximum number of point of sale transactions to retrieve.

Caller Impact: Callers hear only POS transactions that fall within the defined time window.

Default Value: 365

Type: Input/Integer

Purpose: Defines the number of days Teller searches for purchase transaction history.

Behavior: Teller retrieves purchase transactions that occurred within the configured number of days prior to the current date. Entering 99999 removes the date restriction. The transaction types included in "purchases" depend on the entity type being queried.

  • For checking and savings accounts, purchases combines point-of-sale and debit card transactions.
  • For credit card accounts, purchases refers to credit card purchase transactions.
  • This setting exists to give credit unions flexibility — some prefer to see point-of-sale and debit card transactions combined, while others configure them separately using the dedicated POS and debit card settings.
  • This setting works together with the Maximum number of purchases to retrieve.

Caller Impact: Callers hear only purchase transactions that fall within the defined time window.

Default Value: 90

Note: Purchases varies by entity type:

Checking/Savings: Point-of-sale and debit card transactions
Credit Card: Credit card purchase transactions

Type: Input/Integer

Purpose: Defines the number of days Teller searches for withdrawal transaction history.

Behavior: Teller retrieves withdrawal transactions that occurred within the configured number of days prior to the current date. Entering 99999 removes the date restriction. This setting works together with the Maximum number of withdrawals to retrieve.

Caller Impact: Callers hear only withdrawal transactions that fall within the defined time window.

Default Value: 365

Type: Input/Integer

Purpose: Defines the maximum number of general transactions Teller will play during a history request.

Behavior: Teller retrieves and announces up to the configured number of general transactions that meet the lookback criteria. Entering 99999 removes the count limit. Unlike transaction-type-specific settings, this setting applies when a Teller feature can return a mix of transaction types in a single result set.

This setting works together with the Retrieve transactions in the last X days.

Caller Impact: Limits how many general transactions are spoken during a single Teller session.

Default Value: 30

Note: Applies to Teller features that return mixed transaction types (e.g., Recent Transactions, Transaction Search by Date and Amount, Mortgage History, Payroll History, Recent Mortgage Payments, Check Holds)

Type: Input/Integer

Purpose: Defines the maximum number of ACH transactions Teller will play.

Behavior: Teller retrieves and announces up to the configured number of ACH transactions that meet the lookback criteria. Entering 99999 removes the count limit. This setting works together with the Retrieve ACH transactions in the last X days.

Caller Impact: Limits how many ACH transactions are spoken during playback.

Default Value: 50

Type: Input/Integer

Purpose: Defines the maximum number of ATM transactions Teller will play.

Behavior: Teller retrieves and announces up to the configured number of ATM transactions that meet the lookback criteria. Entering 99999 removes the count limit. This setting works together with the Retrieve ATM transactions in the last X days.

Caller Impact: Limits how many ATM transactions are spoken during playback.

Default Value: 50

Type: Input/Integer

Purpose: Defines the maximum number of credit card payment transactions Teller will play.

Behavior: Teller retrieves and announces up to the configured number of credit card payments that meet the lookback criteria. Entering 99999 removes the count limit. This setting works together with the Retrieve credit card payments in the last X days.

Caller Impact: Limits how many credit card payment transactions are spoken during playback.

Default Value: 10

Note: The current Site Manager UI displays this field as " Maximum number of card payments to retrieve" (without "credit"). A label update is pending. This setting applies exclusively to credit card accounts.

Type: Input/Integer

Purpose: Defines the maximum number of credit card transactions Teller will play.

Behavior: Teller retrieves and announces up to the configured number of credit card transactions that meet the lookback criteria. Entering 99999 removes the count limit. This setting works together with the Retrieve credit card transactions in the last X days.

Caller Impact: Limits how many credit card transactions are spoken during playback.

Default Value: 10

Note: The current Site Manager UI displays this field as " Maximum number of card transactions to retrieve" (without "credit"). A label update is pending. This setting applies exclusively to credit card accounts.

Type: Input/Integer

Purpose: Defines the maximum number of check transactions Teller will play.

Behavior: Teller retrieves and announces up to the configured number of check transactions that meet the lookback criteria. Entering 99999 removes the count limit. This setting works together with the Retrieve check transactions in the last X days.

Caller Impact: Limits how many check transactions are spoken during playback.

Default Value: 50

Type: Input/Integer

Purpose: Defines the maximum number of debit card transactions Teller will play.

Behavior: Teller retrieves and announces up to the configured number of debit card transactions that meet the lookback criteria. Entering 99999 removes the count limit. This setting works together with the Retrieve debit card transactions in the last X days.

Caller Impact: Limits how many debit card transactions are spoken during playback.

Default Value: 50

Type: Input/Integer

Purpose: Defines the maximum number of deposit transactions Teller will play.

Behavior: Teller retrieves and announces up to the configured number of deposit transactions that meet the lookback criteria. Entering 99999 removes the count limit. This setting works together with the Retrieve deposits in the last X days.

Caller Impact: Limits how many deposit transactions are spoken during playback.

Default Value: 50

Type: Input/Integer

Purpose: Defines the maximum number of loan advance transactions Teller will play.

Behavior: Teller retrieves and announces up to the configured number of loan advances that meet the lookback criteria. Entering 99999 removes the count limit. This setting works together with the Retrieve loan advances in the last X days.

Caller Impact: Limits how many loan advance transactions are spoken during playback.

Default Value: 50

Type: Input/Integer

Purpose: Defines the maximum number of loan history transactions Teller will play.

Behavior: Teller retrieves and announces up to the configured number of loan history transactions that meet the lookback criteria. Entering 99999 removes the count limit. This setting works together with the Retrieve loan history transactions in the last X days.

Caller Impact: Limits how many loan history transactions are spoken during playback.

Default Value: 50

Type:Input/Integer

Purpose: Defines the maximum number of point-of-sale (POS) transactions Teller will play.

Behavior: Teller retrieves and announces up to the configured number of POS transactions that meet the lookback criteria. Entering 99999 removes the count limit. This setting works together with the Retrieve point of sale transactions in the last X days.

Caller Impact: Limits how many POS transactions are spoken during playback.

Default Value: 50

Type: Input/Integer

Purpose: Defines the maximum number of purchase transactions Teller will play.

Behavior: Teller retrieves and announces up to the configured number of purchase transactions that meet the lookback criteria. Entering 99999 removes the count limit. The transaction types included in "purchases" depend on the entity type being queried.

  • For checking and savings accounts, purchases combines point-of-sale and debit card transactions.
  • For credit card accounts, purchases refers to credit card purchase transactions.
  • This setting exists to give credit unions flexibility — some prefer to see point-of-sale and debit card transactions combined, while others configure them separately using the dedicated POS and debit card settings.
  • This setting works together with the Retrieve purchases in the last X days.

Caller Impact: Limits how many purchase transactions are spoken during playback.

Default Value: 30

    Note: Purchases varies by entity type:

    Checking/Savings: Point-of-sale and debit card transactions
    Credit Card: Credit card purchase transactions

Type: Input/Integer

Purpose: Defines the maximum number of withdrawal transactions Teller will play.

Behavior: Teller retrieves and announces up to the configured number of withdrawal transactions that meet the lookback criteria. Entering 99999 removes the count limit. This setting works together with the Retrieve withdrawals in the last X days.

Caller Impact: Limits how many withdrawal transactions are spoken during playback.

Default Value: 50