The linked Direct Participant has to be stored in dispatch details as Instructed agent if the creditor agent is an indirect BIC for each payment, Batch processing is applicable for each payment record for dispatch, if the Instructed agent is enabled for Batch processing.

• If Creditor Agent is a direct participant, then the same bank will be the Instructed agent and batch processing preference can be fetched for that bank.
• All payment records for which batch processing is enabled is processed separately while generating the dispatch file.
• Records with same instructed agent creates a batch per settlement date and message type.
• A new batch is created, if the number of messages exceed the maximum number allowed for a batch.
• A new file is created for the rest of the batches, if the number of batches for a single file is exceeding the maximum allowed number of batches.
• Messages with Instructed Agents for which Batch Processing is not applicable creates a separate dispatch file in bulk mode in the existing way.
• Batch level validations:
  • Batches can contain only a single type of message
  • Batches always have a unique identifier (Message ID)
  • Each batch has the same Interbank Settlement Date and Instructed Agent for all the transactions included in the Batch since these parameters are at XML Group Header level
  • Multiple batches with same Settlement Date can be present in a single file
  • Within a file containing different types of messages, batches follow a specific order.

The following messages types are exchanged using the Batch Processing Option:

• pacs.008: Credit transfer message
• camt.056: Recall message
• pacs.004: Return message
• camt.029: Negative answer to a Recall

Additional validations on Dispatch Processing

• For a transaction, tracking is based on both Dispatch Reference and File Reference so that when a file re-generation is triggered only the transactions which were part of the original file only should be picked up.
• Dispatch file generation is based on the activation date. If the activation date is a network holiday, dispatch will be scheduled for first cycle of next network business day.
• Settlement date population for the bulks is based on the instruction date of the transaction. The dispatch file has separate bulks based on settlement date if future dated transactions are part of the file.
• If any transaction is with back value instruction date, the settlement date is populated as current date provided, it is not a Network holiday or next network business day.
• On force release from Network Cutoff queue, if no dispatch cycle available for current date, a new dispatch schedule is created without populating the time. This transaction can be either manually dispatched on the same day or the next day’s first dispatch cycle will pick up the transaction.
• Dispatch accounting consolidation has to be based on settlement date, transaction branch and message type.