View our How-to guide

Export Reports


When it comes to understanding your end users, Exports offers the data you need for reviewing enrollment and login behaviors, examining fraudulent activity, and evaluating employee permissions.

How does it work?

  • Exports
  • Requested

When you create an export, select from a list of default date ranges. For most reports, you can also create a custom date range spanning up to two years from the report’s start date1. After selecting the export(s) you want, click Create exports. You can wait around for exports to process, or work on another task because you’ll receive an email notifying you that the exports you requested are finished processing and available in Banno Reports. You can select the button or copy and paste the Enterprise link into your browser that takes you to the Requested exports window.

Requested exports

For managing and viewing reports, the Requested exports window tracks and stores requested reports in chronological order for 90 days. Each report downloads as a CSV file.

Report
Exported reports are labeled according to their type and display individually.
Date range
The time frame of an exported report’s generated data.
Requested by
An image of the enterprise user who created the export request displays. When you hover over the image, their name appears.
Requested on
The date and time an enterprise user created the export request.
Status
An export’s Status can be one of four possibilities—Pending, Processing, Complete, or Failed - Retry.
Pending
The status as a requested export awaits generating.
Processing
The status as a requested export generates the report. Depending on the number of exports and amount of data, it might take time for the export to complete.
Complete
The status when a requested export successfully generates the report and it’s ready to download. Selecting Complete downloads the CSV file. If, after a few minutes of generating, the status doesn’t change, refresh your browser to see if the status updated. You’ll also receive an email notifying you The exports you requested are finished processing and are available in Banno Reports. You can select the button or copy and paste the enterprise link into your browser taking you to the Requested exports window.
Failed - Retry
The status when a request export cannot generate the report. For a failed requested export, clicking the status restarts processing the data. If running the report continues to fail after repeated attempts, create a new request export for the failed report(s). If the export continues to fail, open a support case. As long as a failed report is part of a larger group of reports with a Complete status, a notification email notifying you The exports you requested are finished processing and are available in Banno Reports. sends. If only one requested report fails, or if all reports fail in a requested export, the notification email doesn’t send.
Delete
Selecting the trash icon removes a report from displaying. Once deleted, you’re unable to recover the report. If you need the report again, you’ll need to generate a new one.

Engagement

Engagement exports help you know who, when, and how often end users sign-in to your app or enroll in digital banking.

Active Users

Know the number of end users, when they use your app, and how often by downloading the Active users report. This report displays end users’ whose latest login to Banno Apps occurred during the report’s date range as shown in the Latest Mobile Use and Latest Online Use columns.

Signups

Know the number of end users and when they initially started using your app by downloading the Signups report. This report displays end users who logged into a Banno App for the first time during the reports’s date range as shown in the Activation column.

Login audit

Know whether or not (and when) end users successfully login to your app by downloading the Login audit report. The Login audit report offers up to six months of end user logins prior to the date the export is requested. This report displays end users who logged into a Banno App (or attempted to) during the report’s date range as shown in the When column. It also shows the status of each successful and attempted login in the Progress column.

Enrollments

Know when end users successfully enrolled or attempted enrollment in your app by downloading the Enrollments export. As an end user enrolls, they go through a series of steps that includes providing personal identification information in the New user enrollment window, verifying a 2FA code, and creating a username and password. They might successfully enroll, encounter an issue, or abandon the process, and this export shows the status of each enrollment in the Progress column.

What do the exported fields mean?

Based on the export selected and data available, several of the following fields are shown in the report. In alphabetical order, the possible fields for Engagement reports include:2

Account number
The account number for the account used to enroll in digital banking.
Activation
The date and time an end user successfully logged into your app for the first time.
Activity
The number of times an end user logged in to your app.
CIF
The Customer Information File (CIF) number assigned to end users whose banking institution uses Silverlake, CIF 20/20, or Core Director. For information on the CIF, check your core documentation. This field does not apply to credit union customers and displays as an empty value.
Email
The email address associated with the end user using your app.
Enrolled in App
The date and time the end user first logged on to Banno Mobile.
First name
The first name of the end user logged in to your app. For end users with Business as their User Type, the field is blank.3
IP Address/IP
A series of numbers identifying the device from which an end user logged in or enrolled in digital banking.
Last Approval Request
The date and time when the end user last enrolled in RDC.
Last name
The last name of the end user logged in to your app.[3] For end users with Business as their User Type, their first name also displays in the field. If a last name displays repeatedly, end users tied to the account have different usernames from one another.
Last Updated
The date and time when the last status (progress) update occurred for the end user in the digital banking enrollment process.
Latest Mobile Use
The most recent date and time an end user logged into Banno Mobile during the export’s date range. If this field is not applicable (empty) for all end users in the export, the column doesn’t display.
Latest Online Use
The most recent date and time an end user logged into Banno Online during the export’s date range. If this field is not applicable (empty) for all end users in the export, the column doesn’t display.
NetTeller ID
An end user’s assigned digital banking ID for NetTeller.3 The formatting of this field varies depending on the program used to view the CSV. If the field does not appear correctly, or if it shows the same NetTeller ID for each end user, try increasing the column width or changing the column format to number and making sure the number of decimal places is set to zero. Not every institution has NetTeller IDs assigned to end users, because some institutions migrated to Jack Henry without ever using NetTeller. Other institutions transitioned away from not using NetTeller, so end users may or may not have an ID. If this field is not applicable (empty) for all end users in the export, the column doesn’t display.
Phone
The phone number associated with the end user who logged in to your app.
Progress (Enrolled users export)
The recorded status of where the end user is in the digital banking enrollment process. Listed in alphabetical order, possible statuses include:
2FA failure
2FA authentication failed due to an issue with the third-party that provides the 2FA code.
2FA incorrect code
The end user submitted an incorrect 2FA code.
2FA success
The end user successfully verified a 2FA code, but they didn’t create their username and password credentials.
Enrolled
The end user successfully completed the enrollment process.
Episys failure
Enrollment was unsuccessful because of a call issue to core.
Failed to get if the CU is in memo mode
This status applies to credit unions only. The call to SymXchange failed, and it’s not determined if the institution was in memo mode or not.3
Institution not found
The institution ID doesn’t exist.
Invalid credentials
The end user successfully submitted personal identification credentials, verified a 2FA code, and had already submitted a username and password for registration in the core. However, the submitted username and/or password login credentials didn’t satisfy the institution’s rules for usernames and passwords. One rule example includes the password needing to be at least eight characters long for security purposes, but the end user submitted a password with five characters.3
Lookup authentication failure
The end user requested the 2FA code to resend, but the call to the third-party 2FA code provider failed.
Lookup success
The end user successfully provided matching personal identification information, but didn’t verify a 2FA code.
Netteller failure
Enrollment was unsuccessful because of an issue with NetTeller.
Not authenticated
Enrollment was unsuccessful due to an error in the authentication process. This can also occur when a step in the process is performed out of order.
Phone number doesn’t match
The end user attempted enrolling with a phone number that doesn’t match the phone number in core.
Server failure
Enrollment was unsuccessful as a result of an issue with the server.
The CU is in memo mode
This status applies to credit unions only. The end user attempted to enroll during memo mode, and they need to wait until the institution is out of memo mode to enroll.3
The user is too young
The end user’s age didn’t meet the minimum age as determined by the institution.3
The user’s age is not found
Core was unable to determine the end user’s age.
The user’s symx member number is invalid
The end user used an invalid member number, such as a wrong format.
Too many attempts
The report only shows this progress status for credit unions, because banks have a similar rate-limiting feature already implemented in the NetTeller-BSL. Over the 48-hour period preceding the attempt, there were too many attempts to initiate an enrollment. These may have been either too many attempts using the same Social Security Number (a.k.a. Tax Identification Number) or from the same IP Address. For security reasons, Banno Apps incorporate a rate-limiting feature, intended to prevent a malicious user who may get hold of the SSN from impersonating the end user and taking control of their account by enrolling.
Unknown error
A generic status for an unsuccessful enrollment we couldn’t identify.
User already enrolled
The end user is already enrolled, or they submitted a TIN/account number pair that’s already enrolled.
User is restricted from enrollment
The institution restricted the end user from enrolling.3
User not in core
The end user provided incorrect personal identification information that core didn’t recognize.
Progress (Login audit export)
The recorded status each time Banno authenticates an end user’s login or attempted login to Banno Apps. Except for Success, all statuses indicate the end user unable to login in. Listed in alphabetical order, possible statuses include:
Cash Management Access Denied
The Cash Management user attempted logging in with the incorrect username.
Cash Management Held
The Cash Management user was prevented from logging in because they’re in a held status.3
Cash Management Not Supported
An institution doesn’t support Cash Management and the CM user attempted logging in.
Customer Not Found
This status applies to banks only. The Business Services Layer didn’t recognize the end user’s ID.
Dormant
The end user’s account was dormant.3
Error
There was an authentication issue on the server.
Invalid Credentials
The end user provided an incorrect username or password.3
Locked
The end user’s account was locked.3
Member Number Changed
The end user’s account number (member number) and username no longer match. This can happen to credit union members who are registered in Banno—have used Banno at least once—with a given username and member number, or a member has had either their username or member number modified.3
No Valid Account
This status applies to banks only. The end user’s account status was inactive (not valid) in core.
Outside Allowable Time
A Cash Management user attempted logging in outside an allowable time. CM Users can have allowable times set to login to an account, so the CM user needs to talk with the account owner and have the allowable time adjusted.3
Service Unavailable
While this status is rare, the end user attempted logging in to their digital banking account for the first while core was unavailable or offline.
Success
The end user provided a valid username and password and successfully logged in to the Banno App.
Too Many Attempts
The end user attempted too many incorrect logins on the same day.
Unknown IP Address
When an institution has configured IP restrictions in NetTeller Back Office and the Cash Management user attempts logging in from an IP Address affected by the restrictions.3 It only applies to logins with a password (not mobile syncs). This status could also occur when the BSL doesn’t recognize the IP Address.
Started
The date and time when the end user started enrolling in digital banking.
TIN
The last four digits in the end user’s Taxpayer Identification Number (TIN).
Username
An end user’s digital banking username.
User type
Individual or Business differentiates between consumer and Cash Management users. Individual indicates consumers and Business indicates Cash Management users.
When
The date and time of every login and attempted login to Banno Apps during the export’s date range. Times are reported using the time zone set for your institution.

Security

Engagement exports help you know who, when, and how often end users sign-in to your app or enroll in digital banking.

Potentially compromised

Know when an end user’s account might have been compromised by downloading the Potentially compromised report. If credential stuffing was detected, this report displays end user information where a username and password were successfully entered, but completing 2FA to log in was unsuccessful—likely due to inaccessibility to the end user’s device that received the 2FA code.

Unverified 2FA

Know when an end user’s account might have been compromised by downloading the Unverified 2FA report. If an institution requires end users to enroll in 2FA using a phone number matching core, this reports displays end user information when they submit a phone number that doesn’t match core. When an end user hasn’t enrolled in 2FA before and is prompted to, entering a mismatched phone number to receive a 2FA code can occur in one of the following scenarios:


  • Account enrollment
  • Account login
  • Account recovery

What do the exported fields mean?

Based on the export selected and data available, several of the following fields are shown in the report. In alphabetical order, the possible fields for Security reports include:2

Auth Method
This field is no longer used and will be removed from the report with the next release.
Challenge type
After the end user successfully entered their username and password, they were prompted to complete one of the following challenges before logging in to the app: verify 2FA (most common challenge type), set up security questions, change username, change password, or no challenge was given and the user was allowed to login.
CIF #
The Customer Information File (CIF) number, Epysis account number, or Epysis member number displays. This field does not apply to credit union customers and displays as an empty value.3
Default Delivery Method
This field is no longer used and will be removed from the report with the next release.
Device ID
An identification number generated by Banno to tag the device used for login.
E-mail
The email address associated with the username and password used for attempting login(s).
Enrollment Email
This field is no longer used and will be removed from the report with the next release.
Enrollment Phone
The phone number the end user used to enroll for 2FA.
IP
A series of numbers identifying the network IP address of the end user or attacker that attempted logging in.
Login timestamp
The date and time in which the username and password were successfully entered.
Netteller ID
An end user’s assigned digital banking ID for NetTeller associated with the username and password used for attempting login(s). 3 The formatting of this field varies depending on the program used to view the CSV. If the field does not appear correctly, or if it shows the same NetTeller ID for each end user, try increasing the column width or changing the column format to number and making sure the number of decimal places is set to zero. Not every institution has NetTeller IDs assigned to end users, because some institutions migrated to Jack Henry without ever using NetTeller. Other institutions transitioned away from not using NetTeller, so end users may or may not have an ID. If this field is not applicable (empty) for all end users in the export, the column doesn’t display.
Phone
The phone number in the core associated with the username used for attempting login(s).
Rate limited count
The number of times an end user attempted to login with the username and password from the IP address. The higher the number, the more likely credential stuffing occurred.
Timestamp
The time and date the username and password were successfully entered.
User ID
The Banno ID associated with the end user’s username and password used for attempted login(s).
Username
An end user’s digital banking username used for attempted login(s).

Banno Activity

When an enterprise user successfully creates an export request, Banno Activity records the following:

  • Date and time when the export request was created
  • First and last name of the enterprise user
  • Report type
  • Report date range
  • IP address of the device used by the enterprise user

If multiple reports are selected within a single export request, separate records with each report type display.

FAQ


How do I view fields that display incorrectly or the same for each end user?
We suggest changing the column format to what it should be (ex. number, text, etc.). If you’re changing the format to a number, make sure the number of decimal places is set to zero.

  1. The Login audit report offers up to six months of end user logins prior to the date the export is requested. ↩︎

  2. As we continue adding Exports documentation, eventually exported field descriptions for all reports will be listed. ↩︎

  3. For additional information regarding account information, configurations, etc., refer to your core and/or NetTeller documentation. ↩︎