2.4.1 Batch Cancellation Checks
The related processing of cancellation is explained in the below table depending on the processing stage at which the request is received:
| Batch Cancellation Check | Resultant system action |
| On successfully completing debit account validations which are not overridable.
OR On releasing the batch from PE queue |
Check whether batch is marked for cancellation. If yes, mark the batch as cancelled. |
| After successfully completing overridable exceptions
OR On releasing the batch from BO |
Check whether batch is marked for cancellation. If yes, mark the batch as cancelled. |
| On completion of network resolution
OR On releasing the batch from |
Check whether batch is marked for cancellation. If yes, mark each transaction record as cancelled. |
| On segregating urgent and nonurgent payments, the non-urgent payment batches will be checked for batch cancellation | Check whether batch is marked for cancellation. If yes, mark the Consol batch as cancelled. Note: Consol batch is the batch created after regrouping |
| After holiday check & processing date derivation of non-urgent batches | Check whether batch is marked for cancellation. If yes, mark the Consol batch as cancelled. Note: Consol batch is the batch created after regrouping |
| On completion of FX rate fetch for non-urgent batches
OR On release of batch from FX |
Check whether batch is marked for cancellation. If yes, mark the Consol batch as cancelled. Request for FX unwind will be sent. |
| On completion of amount block for debit amount for non-urgent batches
OR On release of the batch from ECA |
Check whether batch cancellation request received. If yes, mark the Consol batch as cancelled. Requests for FX & ECA unwind will be sent. |
| Individual payment processing of Non urgent transactions completed last stage of individual payment processing | Check whether batch cancellation request received. If yes, mark each transaction record as cancelled. Requests for FX & ECA unwind will be sent transactionwise, if already done |
| Before Network cutoff check of a success batch | Check whether batch cancellation request received. If yes, mark the Consol batch as cancelled. Requests for FX & ECA unwind will be sent. Transaction records of the Consol Batch will be marked as cancelled. |
| On completion of network cutoff check | Check whether batch cancellation request received. If yes, mark the Consol batch as cancelled. Requests for FX & ECA unwind will be sent. Transaction records of the Consol Batch will be marked as cancelled. |
| Before doing accounting handoff | Check whether batch cancellation request received. If yes, mark the Consol batch as cancelled. Requests for FX & ECA unwind will be sent. Transaction records of the Consol Batch will be marked as cancelled. |
| Before doing dispatch | Check whether batch cancellation request received. If yes, mark each transaction record as cancelled. Requests for FX & ECA unwind will be sent transactionwise .Accounting entries will be reversed. |
| When successful transactions of a future dated batch is sent for value date processing | Check whether batch cancellation request received. If yes, mark the batch and the related payment records as cancelled. |
| When successful transactions of a carried forward batch is sent for value date processing | Check whether batch cancellation request received. If yes, mark the batch and related payment records as cancelled. Requests for FX & ECA unwind will be sent. |
| When Urgent payment processing (individual)completed each stage or is released from an exception queue | Check whether batch cancellation request received. If yes, mark each transaction record as cancelled. Requests for FX & ECA unwind will be sent transactionwise, if already done |
| Transaction processing is completed with dispatch for a batch/consol batch | Cancellation will not be applicable |
Parent topic: Batch Cancellation