1. Bulk File Handling User Guide
  2. Bulk File Processing
  3. pain.001 File Processing
  4. Batch Processing of transactions
  5. Batch processing of Successful transactions

Batch processing of Successful transactions

  • If all transactions shows ‘Success’ status, Network cutoff is checked for the batch based on the time maintained in Network maintenance (PMDNWMNT).
  • If cutoff time is over, the payment is moved to Network Cutoff Queue. Force release, Cancel & carry forward actions is possible from Network Cutoff queue.
  • If a batch is cancelled from Network Cutoff queue, unwind requests for FX and ECA are sent.
  • Debit accounting is applicable for successfully completed transactions only. Consolidated/Itemsised entries are posted based on Batch booking tag value or NonUrgent preferences maintained.
The debit amount and entries posted will be consolidated if
  • Batch Booking tag value in the incoming file for the Batch ID is ‘True’

    OR

  • If Batch Booking tag is not available for the Batch ID, in the Non urgent payment preferences, ’Batch debit accounting’ field value set as ‘Consolidated’.
The debit amount and entries posted will be Itemised if
  • Individual debit entries are posted if Batch Booking tag in the file for the Batch ID is set as ‘False’ or if the tag is not available for the Batch ID, then in the Non urgent payment preferences, ’Batch debit accounting’ field value set as ‘Itemized’.
  • Credit amount is always be passed for accounting as consolidated batch amount irrespective of the debit accounting preference.
  • ECA reference is mentioned for the consolidated debit amount / transaction debit amount only. Charges are sent with Force Post flag as ‘Yes’.
  • On completion of accounting the transactions are released from batch for messaging and dispatch file generation.

Parent topic: Batch Processing of transactions