Transactions

Your end users want to know where their money is going. It’s common sense, and Banno’s robust transaction features help ensure those end users have the best view possible. Whether they’re looking for a specific transaction or trying to remember why they spent four hundred dollars on shoes last month, Banno apps will be their best ally in keeping a grip on their finances.

Banno Apps pull 500 transactions at a time per account. Mobile caches the transactions retrieved the last time the end user used the app, allowing for quicker access to transactions as far back as the end user has used Banno Apps.

End users can click the See more button to incrementally pull seven days worth of transactions into Banno Apps. If transactions reach 180 consecutive days of inactivity, End of available activity displays in Banno Online while Banno Mobile end users reach the end of their transaction history.

Provided an end user has 20 or fewer accounts, Banno Apps function exactly how you’d expect—down to displaying a bird’s-eye view of all transactions for all accounts, grouped in a single, comprehensive transactions card. Once an end user has 21 or more accounts, viewing all transactions for all accounts is disabled to ensure the speed and stability of the app. End users must view transactions for each account individually, and transaction searches must be performed on a single account at a time.

Note that this limitation only affects visible accounts—that is, those accounts that have the Account Setting Show balance and activity (Mobile) or Display activity and transactions (Online/People) enabled. Hidden accounts do not apply toward the 20 account threshold, and hiding accounts can bring an end user back below this threshold.

At the top of the Transactions list on an account’s dashboard, end users can click to print the Transactions list or to download transaction activity. When an end user downloads transaction activity, they’ll select a date range and file type to export. For a file type, end users can choose to export a CSV spreadsheet, a text file, or an Open Financial Exchange file.

There are two experiences for transaction enrichment in Banno: Native Banno Enrichments and OFM Enrichments, both of which are described below.

Our loan payment breakdown functionality makes loan payment transactions simpler for Symitar and SilverLake customers. It consolidates all information about the payment to a single transaction while providing additional information about the payment, putting your end users’ most important information at their fingertips. To get started, simply open a support case!

In the past, banks would sometimes see multiple transactions related to a single loan payment. This new ability condenses those transactions into a single, detailed transaction, providing clearer information for both banks and credit unions as outlined in the sections below.

The loan payment does not need to be made in Banno for the Loan Payment Breakdown feature to work.

A new breakdown is shown for all loan payment transactions, except those going entirely toward the principal amount. The following fields appear, if applicable to the given payment:

  • Principal
  • Interest
  • Escrow
  • Late Charge
  • Unapplied Funds
  • Other Charges/Fees

Please note that the loan payment breakdown may have interactions with any transaction filtering your bank has configured. Most importantly, if your bank is configured to filter out the primary loan payment transaction, this transaction will not show in your end users’ apps. Transaction filtering will still apply at the transaction level, but will not be accounted for at the payment breakdown level.

A new breakdown is shown for all loan payment transactions, except those going entirely toward the principal amount. The following fields appear, if applicable to the given payment:

  • Principal
  • Interest
  • Escrow
  • Fee
  • Billed Fee Amount
  • Sales Tax Amount
  • Late charge waived

Credit unions have the option to display up to four of the last digits of a debit or credit card number within transaction details on Banno Online, Banno Mobile, and Banno People. This enhancement improves verification, security, and card identification for all business and retail users by allowing them to match a transaction to the correct physical card.

Credit unions can configure the display of these digits via their core system in two formats:

  • If the configuration is set to display more than four digits, the maximum number of digits shown will still be four (eg. x1234).
  • If the configuration is set to display fewer than four digits, the maximum number of digits shown will match the number of digits selected (eg. x45).

The feature is enabled for all credit unions as of January 2026. Note that certain parameters need to be set in Episys for this feature to work:

  • Online Card Parameters: * Set Card Number in Tran History to Yes.
  • Online Main Parameters: * Set Card in History Digit Count to 4 (or your preferred number of digits).

After updating the parameters, a refresh is required for the changes to take effect. To do this, go to Device Control > ATM Network and click the Refresh Parameter icon (represented by the two green arrows).

EDI is the standard for inter-company communication of business documents. This is especially important for Banno Business users, who often require this format for purchase orders, invoices, and more. Banno apps provide available EDI data for posted transactions on CIF 20/20 and SilverLake, once configured and activated.

Transactions with available EDI data show EDI Transaction beneath the memo in the transaction list. These transactions are identified at login and added to the eligible transactions when the transaction list is updated. Once a transaction with EDI data is identified, navigating to the Transaction details screen shows a Download EDI information option. This initiates a download of a detailed file with all EDI data for the selected transaction, and is available for both pending and posted transactions.


Related