View Approval Queue

Introduction

The view approval queue lets the user to view the list of transactions that are in the queue or pending for relationship manager’s approval. The list displays all the type of transactions like payment, transfer, collections or loan redraw which are pending for approval. The user can fetch the list based on the selection criteria.

The retail user can:

Select any reference id to view the details of the corresponding transaction
Recall the transaction from Relationship manager (It should be noted that the user can recall only those transactions that are yet to be approved) using Recall option
The held transactions can be released manually using Manual Release Required option
View the history details of the selected transaction like when the transaction was initiated, was it recalled, was it sent back to the user by RM for repair along with the user and RM ID using View History option
Copy transaction using Copy Transaction option by selecting any transaction record in the list. Copied transaction will be similar to the transaction record selected.
The process for transactions to be approved, rejected or repaired are as given below:

The Approval Process:

For future dated transactions in the final approval stage and approval reason as ‘New’ and frequency type ‘Single’, once the user clicks Approve, the system executes validations for transaction status, transaction date, account access, approval limits and final approval. On successful validation, the system displays the Information like common details about the transaction and details about the entries.
If no further approval is required then only remarks field is displayed. Remarks are not mandatory in case of approvals.
For authentication, the system prompts the user to enter user credentials.
Once the user submits the details, the system performs following action:

Validates whether the remarks field doesn’t exceeds the maximum length (256 characters).
System validates the user information.
System validates approval limits.
User consumption limits is validated by the system and user’s limit is consumed.
System validates transaction workflow cycle and completes the cycle.
6System updates the status of the transaction as final approval done for the selected transaction.

Once approved, system displays the transaction details with confirmation message. A cyber receipt is displayed with the transaction details and the success message is displayed above the cyber receipt. The transaction becomes pending for processing and is available in 'View Scheduled Transaction'.
After the transaction is successfully approved, the system will capture the approval history of the transaction.

For approving a stop complete transaction (Frequency-Single) which is sent for approval, the process is:

Once the user clicks Approve, the system validates transaction status, account access and final approval.
Once the user submits the details, the system performs actions like:

Validates whether the remarks field doesn’t exceeds the maximum length (256 characters).
System validates the user information.
System validates transaction workflow cycle and completes the cycle.
Updates the status of the transaction and limit reversal happens.

Once approved, the system displays the transaction details with confirmation message with the reference ID. The transaction becomes canceled and is available in 'View Completed Transactions'.
After the transaction is successfully approved, the system will capture the approval history of the transaction.

Approving a stop transaction (Frequency-Single) which is sent for approval (for selected entries) can be done in the same way as stated above.

For approving a complete stop recurring transaction for next instance, the process is:

Once the user clicks Approve, the system validates transaction status, account access and final approval.
Once the user submits the details, the system performs actions like:

Validates whether the remarks field doesn’t exceeds the maximum length (256 characters).
System validates the user information.
System validates transaction workflow cycle and completes the cycle.
Updates the status of the transaction and limit reversal happens.

Once approved, the system displays the transaction details with confirmation message with the reference ID. The transaction becomes canceled and is available in 'View Completed Transactions'.
After the transaction is successfully approved, the system will capture the approval history of the transaction.

Approving a stop transaction (Frequency-Single) which is sent for approval (for selected entries) can be done in the same way as stated above.

For approving a complete stop recurring transaction for next instance, the process is:

Once the user clicks Approve, the system validates transaction status, account access and final approval.
Once the user submits the details, the system performs the following actions:

Validates whether the remarks field doesn’t exceed the maximum length (256 characters).
System validates the user information.
System validates transaction workflow cycle and completes the cycle.
Updates the status of the transaction. Limit reversal happens as per stop transaction use case. The complete recurring instruction is stopped.
Once approved, the system displays the transaction details with confirmation message and reference ID. The current instance of the transaction is updated as canceled and is available in 'View completed Transactions'.
After the transaction is successfully approved, the system captures the approval history of the transaction.

Approving a stop recurring transaction for next instance (for selected entries) is similar as above.

Approving a stop recurring transaction where all pending instances are sent for approval (for selected entries) can also be done as stated above.

Approving a stop recurring transaction where all pending instances are sent for approval can also be done as stated above.

Approving a transaction send for approval for stop action, with transaction date less than current date can also be done where past date transactions can be approved if the approval reason is ‘Stop’.

For Approving a Transaction with Approval Reason as ’Modify’:

This flow is for future dated transaction and is for final approval:

Once the user submits the details, the system performs the following actions:

Validates whether the remarks field doesn’t exceeds the maximum length (256 characters).
System validates the user information.
System validates approval limits.
The limit consumed earlier for the transaction will be reverted.
User consumption limits is validated by the system. And user’s limit is consumed.
System validates transaction workflow cycle and completes the cycle.
Updates the status of the transaction as pending for the selected transaction.

Once approved , system displays the transaction details with confirmation message and reference ID . The transaction becomes pending for processing and is available in 'View Scheduled Transaction'.
After the transaction is successfully approved, the system captures the approval history of the transaction.

To Approve a Transaction with Approval Reason as ‘Repair’:

This flow is for future dated transaction and is for final approval:

Once the user submits the details, the system performs following actions:

Validates whether the remarks field doesn’t exceeds the maximum length (256 characters).
System validates the user information.
System validates approval limits.
User consumption limit is validated by the system. And user’s limit is consumed.
System validates transaction workflow cycle and completes the cycle. .
Update the status of the transaction as 'Pending' for the selected transaction.

Once approved , system displays the transaction details with confirmation message and reference ID. The transaction becomes pending for processing and is available in 'View Scheduled Transaction'.

Intermediate Approval is required where final Approval Check Fails.

User selects the next approver, either by entering the user or role directly in the text box or by looking up using the 'Look up' option.
Once the user submits the details, the system performs following actions:

Validates whether the remarks field doesn’t exceeds the maximum length (256 characters).
System validates the user information.
System validates approval limits.
System validates the next authorizer chosen and sends the transaction for next approval.
User consumption limits is validated by the system. And user’s limit is consumed.
System updates the workflow details of the transaction.
Updates the status of the transaction as 'Approved' and 'More Approval Required', for the selected transaction.

Once approved , system displays the transaction details with confirmation message and reference ID. The transaction becomes pending for approval and is available in 'View Approval Transaction'.
After the transaction is successfully approved, the system will capture the approval history of the transaction.

Final Approval of an Immediate, Online or Hot Transaction:

If the transaction date is current date (while approving), system checks if the final approval is done and bank approval is not required.
System checks that the transaction does not require 'Manual Release'.
After successful validation, the transaction gets submitted to the host for processing by host.
After the transaction is successfully approved, the system will capture the approval history of the transaction.

Where Final Approval is done and RM Approval is Pending:

Once approved, system displays the transaction details with confirmation message and reference ID. The transaction status becomes pending for bank approval and is available in 'View Approval Queue' with transaction status as ‘Pending For Bank Approval’.
After the transaction is successfully approved, the system will capture the approval history of the transaction.

Where the Final Approval is done and Transaction is on Hold:

Once approved, the system displays the transaction details with confirmation message and reference ID.
The transaction status becomes pending for release and is available in 'View Approval Queue' which would require a manual release.
This is similar if the transaction is a hot payment too.

Cases where Error Messages will be Displayed:

Where the user does not select a transaction and performs ‘Approve’ action, an error message is displayed.
Where the user selects a transaction to approve which is waiting for bank approval and performs ‘Approve’ action, an error message is displayed as ‘[TRAN00060] [100919] Transaction is not waiting for your approval’ .
The user selects a transaction to approve which is waiting for retail approval and performs ‘Approve’ action, an error message is displayed.
If the user tries to approve a transaction initiated by him, that is, if he chooses a transaction where the value of 'My Role' column is 'Initiator', then the system throws an exception.
If approval limit validation is failed, then the user will not be allowed to approve the transaction and the system will throw an exception.
If the confirmation credentials entered by the user are invalid, then the system will throw an error message.
If the user tries to approve the transaction whose transaction date is less than current date and approval reason is not ‘Stop’, an error message is displayed to the user.
Invalid next authorizer error will be displayed when the user enters any of the following invalid next approver in the next authorizer field:

User is not applicable in the workflow rule for that transaction.
User is applicable in the workflow rule but already approved that particular transaction.
If the workflow rule is hierarchical and User applicable in the workflow rule but not following next highest hierarchy for that transaction.

If the transaction date is current date and if approval reason is ‘New’, ’Modify’ or ‘Repair’ and if the current date validation fails (as per transaction date) , an error is displayed.
Where ever there is an error condition during limits consumption or reversal, approval action will not be processed and error message will be displayed.
When the user enters the remark which exceeds the maximum length of 256 characters, then the system will throw an error message 'Your remarks exceeded the maximum length'.

Duplicate Transaction Check

Whenever a user initiates a transaction, Finacle e-Banking will do a check to see whether the entered transaction is a duplication of the previously entered transaction during day. For performing this check, the inputs taken are:

Counterparty
Transaction Date
Transaction Amount

If a transaction entered by the user matches with another transaction on a particular day with respect to the above listed three parameters, then a warning message will be displayed to the user. The warning message displayed will be “Entry with same Transaction Date, Counter Party and Transaction Amount Already Exists”. However user can still continue with the transaction.

For Example:

If User U1 transfers Rs.10,000 to one of the counterparties C1 on 1st January 2012 and later on the same day, if he tries to transfer another Rs. 10,000 to the same counterparty C1 then, e-Banking application displays the warning message

This check is performed upon Copying a transaction. While checking for duplicate transaction Finacle e-Banking will also check the transactions which are Scheduled and Waiting for approval.

Note:

Transaction with the below mentioned status will not be considered for duplicate transaction check.
- Repaired
- Expired
- Failed
- Pending For My Approval
- Recalled
- Rejected
- Saved

Navigation

Click View Approval Queue in the Transaction Management menu option
The Approval Queue screen is displayed.

What you can do

The table below provides a brief description of the data that should be entered on the screen and the functions you can perform:

Field

Description

SEARCH CRITERIA

Saved Criteria Templates

From the drop-down list, select the saved template for the new search criteria.

Note:

Click OK after selecting the appropriate value from the drop-down list. The fields get defaulted with the saved values as per template.
If no template is selected as default template then the first value in the drop-down list is <SELECT>.

Transaction Type

Mandatory

From the drop-down list, select the transaction type to be retrieved.

Valid values:

All

Fund Transfer

Payment

Collection

Loan Redraw

Bill Presentment

Shopping Mall Payment

Note:

The default value is All.

Frequency Type

The listing can be done on the basis of the frequency of the transactions.

Valid Values:

Single

Recurring

All

Transaction Date Range

Type the from date and to date range for which the list needs to be fetched.

No. of Rows

Optional

Drop-down

Select the number of records to be viewed in the listing. The values for this drop-down are defined in common code type NOLR.

Note:

If no value is entered rows will be fetched as per PRPM set at bank level

Transaction Status

Optional

Drop-down

Select one of the transaction statuses for displaying the transactions which need approval.

Valid Values:

All
Pending for My Approval
Pending for Other Joint Account Holder’s Approval
Pending for Bank Approval

Template Actions

From the drop-down list, select the template action.

Valid Values:

Save Template

Delete Template

Note:

Click OK after selecting the appropriate value from the drop-down list.

Transaction Reference Name

Type the reference name for the transaction, which can be used for retrieval of the transaction details in the future.

Note:

This is a text field and there will not be any validations on this field.

ADVANCED SEARCH CRITERIA

Reference ID Range

Type the range of transaction reference ID (from and to) to retrieve the list.

Initiator’s Account

Select the account of the initiator from the list of accounts.

Counter Party Type

Select the counter party type based on which the records are retrieved.

Counter Party Nickname

Use Look Up to retrieve the list of counter party,select the appropriate counter party nick name and to fetch the transaction records.

Total Amount Range

Type the total amount range based on which the search happens.

Network

Select the network based on which the search happens.

Manual Release Required

Type the appropriate option to fetch the transaction records, that require manual release or does not require manual release. Selecting ‘All’ option fetches transactions that require manual release and the transactions that does not require manual release.

Click

List the transactions pending for approval, based on the search criteria.

Note:

The details of this screen are given in the table below.

Clear

Refresh the screen without the specified query criteria (where results have not been displayed) or to reload the screen with the latest results for the criteria specified.

Field

Description

APPROVAL QUEUE

Select

Select the transaction record from the list .

Note:

Select option will be a check box.

This is for facilitating the approver to select multiple records while approving / rejecting the transactions in one go. Apart from approve/reject, approver can also recall, send transactions for repair and update next approver in one go, by selecting multiple records.
If the approver selects multiple records and tries to copy a transaction, view history or Manual release, then appropriate error message will be displayed as below.
- Multiple transactions cannot be copied at a time, Please select only one record.
- Multiple transaction history cannot be viewed at a time, Please select only one record.
- Multiple transactions cannot be released at a time. Please select only one record.

Reference ID

The reference ID of the transaction is shown. Click the link to view the details of the transaction.

Transaction Type

The transaction type is displayed. It can be wither funds transfer, payment or collection.

Frequency Type

This indicates if the transaction is one time or recurring.

Transaction Date

The transaction date of the transaction is displayed.

Manual Release

Indicates if the transaction records require manual release or not.

Total Entries

The total number of entries in the transaction.

Currency

The transaction currency of the transaction.

Total Amount

The total amount of the transaction.

Transaction Status

The status of the transaction.

Click	To
	Go to the previous list page.
	Go to the next list page.
Go to Page	Type the list page number and click Go to fetch the corresponding list page.
Recall	The selected transactions can be recalled by the user after authorizing using valid credentials.
Manual Release Required	Mark the transaction for manual release required. Note: In case of joint holding pattern any user can hold or release a transaction.
View History	View the transaction history details.
More Actions	Additional functions can be performed on the transactions, which are: Copy Transaction - Copy the selected transaction to a new transaction Save As Template- Save the information as a template for future reference Note: At the time of copying a transaction, if the duplicate transactions are found the appropriate warning will be displayed.
Download Detail As	The details of the cart can be downloaded in the following formats by selecting an entry from the list box and click OK. HTML CSV XML DAT XLS PDF RTF TXT
Approve	Approve the transaction.
Reject	Reject the transaction.
Note: If the mode of operation for joint accounting pattern is other than Jointly by All and Minimum N Number then the Approve or the Reject buttons will be disabled and also transactions will be displayed in the queue, only if the RM approval is required.