2.7.1 Breach Tracking at Main Line and Child Facility Level

This topic describes about the detailed information on breach tracking at main line and child facility level.

• In case a utilization transaction breaches the exception transaction, then the transaction goes for dual authorization. Likewise, because of the utilization transaction, if the total utilization breaches the exception breach percentage configured at facility level, then also the exception transaction goes for dual authorization.
• The dual authorization transaction is routed to appropriate role based on the queue maintenance.
• Dual authorization transaction is routed to appropriate queue considering the utilization transaction amount considering slabs configured for branch and category through ‘Exception Queue Slab Maintenance’ screen.
• Utilization transaction done at a facility level looks into exception transaction amount and exception breach percentage configured at that particular facility level for sending to dual authorization. For a child line having a main line attached, since the utilization transaction at child line level also updates the main line, utilization transaction goes for dual authorization if the transaction amount breaches the configurations at respective child and main line.
• Currency and amount of utilization transaction at line level is to be considered to decide the appropriate queue to which dual authorization transaction is to be sent for approval.
• Based on facility level configurations for exception transaction amount/percentage, if utilization transaction breaches the configured amount/percentage at both child and main line level, then multiple dual authorization transactions are triggered based on configuration.
• Both dual authorization transactions pertaining to child and main lines have to be authorized.
• For a facility where in facility transfer out has taken place because of which the available amount would have come down, utilization transaction will be sent to dual authorization if the overall utilization breaches the exception breach percentage configured considering this available balance after facility transfer.
• If multiple users are available in a particular role and if one of the users approves the transaction, transactions gets approved. Likewise, if one of the users rejects the transaction, same gets rejected.
• Both child and main line level dual authorization transactions are to be approved by the configured users for approval of the utilization transaction. If either of the child or main line dual authorization transaction is rejected, then the utilization transaction gets rejected.
• If the utilization currency is different from facility currency, then the utilization amount is converted to facility amount currency and validated with exception transaction amount and if the same is breaching, appropriate queue/slab applicable for the amount/currency is picked for routing the transaction.
• When different branches are involved in utilization transactions, that is main line in one branch and child line in a different branch, then appropriate branch/category combination configuration is considered.

Examples

When a single line configured with both breach transaction amount and breach exception percentage.

Scenario 1 - Utilization transaction resulting in breach of EITHER exception transaction amount or exception breach percentage – single transaction will go for dual authorization

• If one role is configured for a particular queue – all users in the role will get dual authorization transaction. If one of them approves, entire transaction gets approved. If one of them rejects, entire transaction gets rejected. No action required from other users.
• If multiple roles are configured for a particular queue – all users in all configured roles will get dual authorization transaction. If one of them approves, entire transaction gets approved. If one of them rejects, entire transaction gets rejected. No action required from other users.

Scenario 2 – Utilization transaction resulting in breach of BOTH exception transaction amount AND exception breach percentage – two transactions will go for dual authorization

• Since it is for the same facility both the transactions will go for the same queue considering the amount of utilization transaction considering the following.
• If one role is configured for a particular queue – all users in the role will get dual authorization transaction. If one of them approves, entire transaction gets approved. If one of them rejects, entire transaction gets rejected. No action required from other users.
• If multiple roles are configured for a particular queue – all users in all configured roles will get dual authorization transaction. If one of them approves, entire transaction gets approved. If one of them rejects, entire transaction gets rejected. No action required from other users.

When a child line having main line and both the lines configured with both breach transaction amount and breach exception percentage

Scenario 1 - Utilization transaction resulting in breach of EITHER exception transaction amount or exception breach percentage of both child and main lines - TWO transactions will go for dual authorization.

• If one role is configured for a particular queue – all users in the role will get dual authorization transaction. If one of them approves, entire transaction gets approved. If one of them rejects, entire transaction gets rejected. No action required from other users.
• If multiple roles are configured for a particular queue – all users in all configured roles will get dual authorization transaction. If one of them approves, entire transaction gets approved. If one of them rejects, entire transaction gets rejected. No action required from other users.
• Action to be taken on both the transactions for ensuring completion of the transaction. If both the transactions are approved, utilization transaction gets approved. If either of the transactions is rejected then utilization transaction gets rejected.

Since two different facilities are involved, considering queue configuration for different slabs for a combination of branch and category, appropriate queue is selected for routing dual authorization transaction for approval.

• If one role is configured for a particular queue – all users in the role will get dual authorization transaction. If one of them approves, entire transaction gets approved. If one of them rejects, entire transaction gets rejected. No action required from other users.
• If multiple roles are configured for a particular queue – all users in all configured roles will get dual authorization transaction. If one of them approves, entire transaction gets approved. If one of them rejects, entire transaction gets rejected. No action required from other users.
• Action to be taken on all the transactions for ensuring completion of the transaction. If all four the transactions are approved, utilization transaction gets approved. If any one of the transactions is rejected then utilization transaction gets rejected.