Business FAQ
Banno Business FAQ
- Create the new business and business users in NetTeller. When this is complete, ensure autoseeding is enabled. This will ensure that the new organization and users are synced automatically. Once the process is finished, business Admins can invite business users to complete their account and log into Banno. If autoseeding is not enabled, contact your Banno support representative.
- Yes, you can!
- Yes! Banno Buisness features can be enabled in Banno for the tester and the CM SSO will still be available to them.
- Admin users at businesses can enroll in these.
- Yes! These are specific to the user.
- Yes, it does!
- Account recovery is available to cash management users.
- The effective dates available in Banno match those available in NetTeller, and these dates vary based on each institution’s configurations.
- We will use the default that the customer has set up on the host. If you have the default set to held status, all new users will be held upon creation.
- Currently when a retail ID is converted to a cash management ID in Banno People the old retail profile will still display in Banno People. It is recommended that devices are removed from the old retail profile by navigating to “Security” and choosing the option for “Remove all Devices”.
- Yes! See the account renaming doc for more details.
- There are several different ways to get a list of all business users/customers, each with its own conditions. Please see our Knowledge Base article on how to pull a list of business users.
Banno Business Authentication and Security FAQ
- The Passkey replaces the user’s password, and the FIDO token is a 2FA method.
- For security purposes, this is not allowed.
- No, they are not. Banno product takes a secure by default approach and has preset risk points. Users are always challenged at these points.
- They cannot. Wire pins have been replaced by high risk authentication due to modern security needs.
- No, the dashboard card framework is unaffected by this process. However, passkey and FIDO will disrupt aggregators.
- There is no fee or service charge associated with the Banno platform, but there is a cost to purchase from vendors. This key is not specific to your bank and can be used across applications.
- You’re not charged a fee for FIDO tokens. We don’t believe in charging more for more security unless we absolutely have to.
- No, FIDO supports many users on a single token.
- Yes, they can.
- No, it does not, so long as you check the “remember my device” setting. They protect the device on initial login. If you’re using the FIDO key as a passkey, however, it would need to stay.
- There is a toggle in the Security submenu of the Settings section.
Banno Business Alerts FAQ
- There is no additional contract involved for Banno Business banks, as both NetTeller and Banno send alerts over Enterprise Notification System (ENS). However, with this migration to Banno Business alerts, we will enable Text, Email, and Phone delivery options for all alerts, which may differ from the global settings your finanicial institution had established in NetTeller.
If your financial institution wants to disable Banno Business alerts at the global level, please submit a support ticket via the For Clients Portal.
- No, the user must enroll themselves. We are looking to introduce controls that would address this into People in the near future, but cannot give an ETA at this time.
- Yes. During the migration to Banno alerts Jack Henry automatically ported user’s preferences over from NetTeller. Early in the migration process, this was not the case, but we recognized the impact this would have on our customers and your users and built a tool to facilitate that migration.
- Business users will be the most impacted by this change. Once the migration is complete, business users will have new alert options available to them in the Settings > Alerts menu. This is where they will need to manage their alert preferences going forward. They should also notice that the content of the alerts themselves has changed.
Retail users will be minimally impacted by this change as well. Users will notice a new General section within Settings > Alerts in Online. As these alerts were not previously available to them, the impact should small.
- In total we are adding 31 new alerts for SilverLake customers and 24 new alerts for 20/20 customers. You can see more details about all available alerts in the associated Knowledge Base article.
- Alert configuration work is currently in progress and not widely available. All alerts are available to users but off by default for for all institutions - with the exception of Banno alert early adopters who were given the option to specify how they want alerts configured.
In the meantime, please submit a support ticket to either see or change how alerts are configured and our team will be able to assist you. When requesting a change, institutions should include which alert and delivery method they wish to change and what new value they would like to use. The available options are:
- Available but off by default. Users will need to opt-in to receive the alert via this delivery method.
- Available but on by default. Users will automatically receive the alert once they have the appropriate permissions but can opt-out.
- Forced. All users with the appropriate permissions will receive this alert. Users cannot opt-out.
- Unavailable. The delivery method or alert is completely unavailable to users.
- No. The NETPAR > Option 30 options for the system watches no longer control which alerts are active for an institution, and these settings were not migrated over to Banno. All alerts are available to users but turned off by default for for all instituions - with the exception of Banno alert early adopters who were given the option to specify how they want alerts configured. See the previous question for instructions on how to change how alerts are configured for your institution.
- Alerts in Banno are grouped by feature and are controlled by specific alerts permissions related to that feature, but not by the specific features themselves. Users must have the specific alert permission in order to receive those types of alerts. When an alert is forced, it will go out to any user with permissions to receive that type of alert.
For example, Positive Pay exception alerts that are forced will go to any user who has the
Positive Pay alertspermission, regardless of if they have access to Positive Pay. If the user does not have that permission, they will not receive the alert. Similarly, if the user has that permission but does not have Positive Pay, they will receive any forced Positive Pay alerts. - Alerts in Banno are grouped by feature and are controlled by specific permissions related to that feature, but not by the specific features themselves. Users must have the specific alert permission in order to receive those types of alert.
For example, if a user has the
Positive Pay alertspermission and is subscribed to the Positive Pay exception alert but the user does not have access to Positive Pay, the user will receive the Positive Pay exception alert. - Since the beginning of Banno business we have sent out a security related notification to users when they perform certain high-risk actions, such as initiating ACH batches or sending a wire. This is a security feature to ensure users know what activity is happening on their account and only goes out the person who performed the action. It cannot be turned off.
With the release of Banno alerts, we send alerts to anyone subscribed to that alert when the associated action is performed by anyone at the business. So, for example, when an ACH batch is initiated, the user that performed the action will receive two alerts if they are subscribed to the ACH batch initiated alert: one security alert and one Banno alert. The user can unsubscribe from Banno alerts, which will stop the duplicate alerts, but it’s important to understand that this will also stop all alerts when anyone else at the business performs that action.
- This will depend on how the bank has Positive Pay configured under NETPAR > Option 1 > Sub-option 8 > Generate Pos Pay Exception Alert once per day. If this is set to N then Positive Pay exception alerts would be generated during the day as new exceptions are found. If this is set to Y then Positive Pay exception alerts will generate during EOD. This is identical to how NetTeller handled Positive Pay alerts.
- Yes, the NETPAR settings for Generate PosPay Exceptions Alert once per day and Send alert no. of hours prior to NT ARP/Pos Pay end time are respected.
- No. Users will only receive alerts if they have outstanding exceptions to review.
- Reports are unavailable at this time. A financial institution can see what alerts a user has set up by going to that user’s Activity feed in People and filtering to Alert settings. All alerts that the user has manually opted into are recorded here. We have plans to follow up later in 2025 with additional functionality to add visibility into institution and user alert preferences.
- Templates for Banno alerts are not customizable per institution at this time. Every institution uses the same template and wording.
- Yes. In NetTeller, alerts only go out to users who performed the action. When a user is held, they cannot log in and as a result cannot perform any actions that would trigger alerts.
In Banno, when an action is taken within a business, any user with appropriate permissions and who has opted into an alert will receive the alert. While held users wouldn’t receive alerts for their own actions, they would receive alerts for actions taken by other users of the business.
- Yes, alerts do not consider the hidden status of the account.
- No. Once the migration is complete, alerts will stop being sent through NetTeller and only be sent through Banno. Users do not receive duplicate alerts.
- No. Alerts can currently only be set to be forced for the entire institution and cannot be customized per user.
- Institution employees can see which alerts have been sent to users by going to the user’s profile in People and navigating to the Messages tab.
- At this time turning off the specific feature alert permission is not possible. This willl be addressed in the near future.
- This is a known issue that will be addressed in the near future.
- At present, custom alerts will continue to be sent through NetTeller. Institutions with custom alerts must leave the CM SSO enabled for users to subscribe to those alerts.
- This is a known issue that will be resolved in a future update. The alerts impacted are:
- ACH batch about to expire
- ACH batch has expired
- ACH batch about to be initiated
- Incoming ACH EDI
- Incoming ACH credit
- Incoming ACH debit