SilverLake Exceptions
Jack Henry Exception Manager’s integration with SilverLake allows financial institution staff to decision exception items generated from the core within Jack Henry Exception Manager and have those results passed back to SilverLake.
Decisioning a SilverLake Exception
To resolve an exception item, select a decision from the dropdown menu, and select Resolve. To update a decision, select a decision from the dropdown menu and select Update.
If applicable, staff can also choose to waive the fee and/or print a notice when resolving or updating an exception by using the respective toggle buttons.
For SilverLake exceptions, staff will have the following decision options available:
- No Action
- This decision leaves the exception in its current state without taking any immediate action. It is used when additional information is needed, when waiting for account conditions to change, or when the exception will be handled through alternative means outside the system. The exception remains in the queue and can be revisited at any time.
- Retry
- This decision attempts to process the original transaction again using the current account conditions. It is commonly used when the initial reason for posting failure has been resolved.
- Return
- This decision returns the original transaction amount to the sender. It is commonly used in account not found, closed account, NSF, or stop payment scenarios. It will not be available for exceptions that have a transaction type of ATM, AFT, or Unspecified. If Unspecified is changed to a different transaction type value (other than ATM or AFT), then the Return option will become available.
- Manual Post
- This decision should not be used for SilverLake exceptions.
- Force Post
- This decision attempts to process the original transaction again using the current account conditions. It is commonly used when the initial reason for posting failure has been resolved.
NSF Decisioning
For Non Sufficient Funds exception types, there are additional fields that can be entered.
- Return Reason
- When selecting the return decision, a user will see a dropdown list of return reason codes/descriptions which will be tied to the transaction type (ACH, Checks only). Underneath this dropdown is a checkbox for On us return. If that checkbox is selected, this indicates that the exception is an on-us exception and sends the appropriate return code to SilverLake.
- Fee Decisioning
- The charge fee toggle determines the fee decision that is sent to SilverLake. If it is set to
Yes, charge fee, the user can choose to apply the displayed Calculated fee or select Fee limit reached if the customer has already been charged the maximum daily NSF fees. If the toggle is set toWaive, the user can select a fee waive reason and no fee will be charged. - Print Notice
- The
Yes, print noticeorNo print noticetoggle tells SilverLake whether to print or not print the notice.
Viewing SilverLake Exception Details
The following fields and their definitions are applicable to SilverLake exceptions.
Read-Only Information
The exception type, state, amount, transaction type, created date, and ID are displayed in the middle panel of the screen along with a timestamp and name of the user who last edited or resolved the exception, if applicable.
The following read-only fields are visible in the left-hand side panel.
Entity Details
- Phone Number
- Phone number(s) associated with the entity (i.e. customer).
- Email address associated with the entity (i.e. customer).
- Entity Creation Date
- The date the CIF record was created.
Account Details
Account balance details can be refreshed at any time by selecting the Refresh balances button.
- Status
- The account’s status (active, closed, charged-off, etc.).
- Account Number
- The account number associated with the exception.
- Account Type
- The type of account (i.e. checking, savings, etc.) that generated the exception.
- Name on Account
- Accountholder name.
- Entity Number
- CIF number.
- Account Open Date
- The date the account was opened.
- Available Balance
- The amount of funds available after accounting for pending debit and/or credit transactions and holds.
- Current Balance
- The total posted balance in the account before pending transactions and holds are applied.
- Overdraft Limit
- Overdraft protection limit if applicable.
Account Exception History
- Exception Activity
- Link to view any exceptions from the previous day associated with the account.
- Exception History
- Link to view all exceptions on the account from the previous 365 days.
The following read-only fields are visible in the right-hand side panel.
General Details
- Account Messages
- Messages/notes associated with either the account or customer.
- Branch
- The branch where the exception originated.
- Officer
- The officer code associated with the account.
Transaction Details
- Transaction Type
- Classification of the original transaction (i.e. ACH, check, etc.). Note: ACH transactions will also include the name of the company that originated the transaction.
- Transaction Date
- The transaction date.
- Source
- Where the exception was generated from, such as
SilverLake Non-PostorSilverLake NSF. - Exception Type
- Type of exception, such as
Non Sufficient Funds (NSF),Closed Account,No Account Found, etc. - Source Tracer Number
- Original transaction tracking number. This is the same as the trace number for an ACH exception.
NSF Details
- Service Charge Code
- Two character code defined in SilverLake and assigned to the account.
- Available Balance at Post
- Available funds at the time the transaction was posted or posting was attempted.
- Fee Waived Within Tolerance
- Yes/no on whether fees can be waived based on tolerance settings in SilverLake.
ACH Details
This section only appears for exceptions related to an ACH transaction.
- Company
- Company that initiated the ACH transaction.
- Company ID
- The identifier assigned to the originating company.
- Originating Routing Number
- Routing number of the financial institution that submitted the ACH transaction.
- ACH Sequence
- The sequence number used to identify the ACH entry within its batch.
- ACH Batch
- The batch number associated with the ACH entry.
- ACH File Key
- A unique identifier used to associate the transaction with the ACH file in which it was transmitted.
- Standard Entry Class Code
- Identifies the type of ACH transaction. Examples include
PPD(consumer payments),CCD(corporate payments), andWEB(internet-authorized payments). - ACH Transaction Code
- Indicates the specific type of transaction processed by specifying whether the transaction is a debit or credit and the account type (i.e. checking, savings, etc.).
- Individual Name
- Name of the individual receiving the ACH transaction as entered by the originating financial institution.
- Company Discretionary Data
- An optional field in an ACH file used by the originating company or originating financial institution to include custom internal codes for specialized handling or identification.
- Company Entry Description
- Description provided by the originating company to explain the purpose of the transaction to the receiver.
Editable Fields
The following fields can be edited by staff when reviewing and resolving an exception.
- Exception Status
- Update the workflow status (
New,In Progress,On Hold,Pending Approval,Done). - Effective Date
- Allows the user to modify the effective date in order to post the transaction to a different date. This will only apply to SilverLake Non-Post exceptions.
- Transaction Code
- Allows the user to update the transaction code that was applied to the exception. This will only apply to SilverLake Non-Post exceptions.
- Transaction Type
- Classification of the original transaction (i.e. ACH, check, etc.). Allows the user to update the transaction type if it’s set to
Unspecified. - Account Number
- Allows the user to update the account number associated with the exception in order to successfully post the transaction or post it to a different account. This will only apply to SilverLake Non-Post exceptions.
- Account Type
- Allows the user to update the account type associated with the transaction exception in order to successfully post the transaction. This will only apply to SilverLake Non-Post exceptions.
- View check
- When viewing SilverLake exception items, there may be some items that have an option to view the check image. These images are pulled from 4|sight and can be found by selecting an exception item and clicking on the View check button, which is displayed in the Exception details section in the center panel. From there, staff can edit the Check number, Account number, Account type, Effective date, and Transaction code.
- Description
- Not applicable for SilverLake exceptions.
GL Details
- Branch ID
- Allows the user to update the branch ID associated with the General Ledger transaction exception.
- Cost Center
- Allows the user to update the cost center associated with the GL transaction exception.
- Product Code
- Allows the user to update the product code associated with the GL transaction exception.
- Transaction reference
- Allows the user to update the transaction reference associated with the GL transaction exception.
- Description
- Allows the user to update the transaction description associated with the GL transaction exception.