1.4 Salient Features

Learn about the salient features of the Oracle Banking Branch application.

The salient features are as follows:

Table 1-8 Salient Features

Feature	Description
Generation of Teller Sequence Number	The system generates a unique Teller Sequence Number and displays an information message Teller Sequence Number nnn indicating the generated number after submission of each teller transaction. The generated sequence number is also displayed at the following levels: Completion Authorization Submission Re-submission Reversal Rejection
Advice Generation for Teller Transactions	The system generates the transaction advice if it is enabled in the definition of function code. The advice includes the currency and amount values involved in the transaction.
Transaction Approval	When you perform a transaction for an amount greater than the allowed limit, it needs approval from the Supervisor. Based on the Assignment Mode in Function Code Preferences screen, the following conditions apply: Manual – The system will show a list of approval if the request status is Approval. Auto – The transaction is automatically assigned to the default authorizer if the request status is Approval. The transaction approval flow consists of the following steps: Initiation Pending Approval Approved (Sent Back) Completed For more information on transaction approval flow, refer to Table 1-9.
Transaction Reversal with Approval	A transaction can be reversed with auto-approval or approval from the Supervisor. Based on the Assignment Mode in Function Code Preferences screen, the following conditions apply: Manual – The system will show a list of approval if the request status is Approval. Auto – The transaction is automatically assigned to the default authorizer if the request status is Approval. The transaction approval flow consists of the following steps: Completed Pending Approval Approved (Sent Back) Completed Reversed For more information on transaction flow for reversal with approval, refer to Table 1-10.
Transaction Reversal	A transaction can be manually reversed only when it is authorized and completed from the Journal Log. When you reverse a transaction, the data remains in the system with the status Reversed and the accounting entries are reversed. Also, this will update the Till Balance for the currencies (for cash transactions), wherever applicable. You can select the transaction to be reversed from the transaction screen. If the reversal is applicable for the function code, the Reversal icon will be enabled. When you click this icon, the reversal request will be initiated. If cash transactions are reversed, the system validates the following: the Till used for the reversal is the same as that used in the original transaction the denominations are input a batch is open
Transaction Rejection	You can manually reject the authorized customer transactions from the Teller Journal Log. Note: When you reject a transaction, the data remains in the system with the contract status Discarded and no further action is allowed on the transaction.
External API	External APIs will be processed only if called by an external system, which is maintained in Oracle Banking Branch. The external system can be maintained using the External System Maintenance screen. For more information on the External System Maintenance screen, refer to External System Maintenance. External APIs are supported for the following transactions: Cash Deposit Cash Withdrawal Account Balance Inquiry Account Transfer Note: These transactions will work only if OAuth is enabled.
Machine Learning	For information on machine learning, refer to About Machine Learning.
Oracle Digital Assistant (ODA)	For information on ODA, refer to About Oracle Digital Assistant.
Virtual Identifier	For information on the virtual identifier, refer to About Virtual Identifier.
Amount-Based Signature Verification	For information on amount-based signature verification, refer to About Amount-Based Signature Verification.

Table 1-9 Transaction Approval Flow

Stage	Description
Initiation to Pending Approval	If the transaction amount exceeds the limit defined in Branch User Limits and on click of Submit, the system shows a popup message Amount exceeds limit for this transaction, and request status is shown as Approval. If assignment mode is manual and on click of Confirm, the system shows a list of approval based on branch code, transaction amount, currency, and function code. The user can give a narrative and click Submit for Approval button.
Pending Approval to Sent Back	The Approver needs to log in and fetch the transaction from Journal Log with transaction status as Pending Approval. The Supervisor can approve the pending transaction by clicking Approve with the supervisor comment. Note: The approver remarks are mandatory during the rejection of a transaction.
Sent Back to Completed	The user needs to fetch the transaction from Journal Log with transaction status as Sent Back and click Submit.
Override Flow (Initiation to Completed)	Based on the branch maintenance setup at certain levels like Function Code, Function Code Preferences, Branch User Limits, and Branch role limits, if the transaction is validated with any warning override, the system shows a pop-up message with request status as Warning. Once the user confirms, the transaction status will be shown as Completed.

Table 1-10 Transaction Reversal with Approval Flow

Stage	Description
Completed to Pending Approval	The completed transaction can be selected from the Journal Log screen. Once you click Reverse, the system shows a pop-up message Authorization required for Reversal and requests for a confirmation. If assignment mode is manual and on click of Confirm, the system shows a list of approvers based on branch code, transaction amount, currency, and function code. The user can give a narrative and click Submit for Approval button.
Pending Approval to Sent Back	The Approver needs to log in and fetch the transaction from Journal Log with transaction status as Pending Approval. The Supervisor can approve the pending transaction by clicking Approve with the supervisor comment. Note: The approver remarks are mandatory during the rejection of a transaction and the transaction will be restored to the Completed status.
Sent Back to Reversed	The user needs to fetch the transaction from Journal Log with transaction status as Sent Back and click Submit.
Override Flow (Sent Back to Reversed)	The user needs to select the completed transaction in the Electronic Journal screen and click Reverse. If the Reversal Requires Authorization is enabled in the Function Code Definition screen, the system displays an information message to select the Approver based on Manual or Auto assignment mode. After selecting the approver internally, reversal override will be called and request status will be updated as Approval.

This topic contains the following subtopics:

• About Machine Learning
  Oracle Banking Branch uses machine learning to process an email request from a customer automatically.
• About Oracle Digital Assistant
  The Oracle Digital Assistant (ODA) helps the Teller to reduce the time taken to access the transaction screens through automatic text/voice processing.
• About Virtual Identifier
  The virtual identifier is used to validate the specified account number of the customer.
• About Amount-Based Signature Verification
  The Teller can use the "Amount-Based Signature Verification" feature to verify the signature displayed in the Customer Information widget while performing the transactions.