1. Generic Wires ISO User Guide
  2. Generic Wires ISO Interbank Direct Debit pacs.010
  3. Transaction Processing
  4. Credit Instruction Processing

Credit Instruction Processing

  • For each Credit Instruction (/Document/FIDrctDbt/CdtInstr) received in an incoming pacs.010 message, Sequence A transaction entry get created.
  • The source code for the incoming transaction is derived based on the Source code Maintenance (PMDSORCE). The source code for which the ‘Incoming SWIFT’ flag is checked is considered as the source code for the Incoming pacs.010 message.
  • The following processing is done for the Sequence A (Credit Instruction) records:
Duplicate Check Validation
  • Credit Identification (/Document/FIDrctDbt/CdtInstr/CdtId) is validated to check if another transaction with same Credit Identification is already present in the application.
  • In case if another transaction with same Credit Identification is already present in the application, then transaction is treated as duplicate transaction and moves to Business Override Queue.
Agreement Check Validation
  • Agreement validation at sequence A level is done for the Sender BIC (i.e., /AppHdr/ Fr/FIId/FinInstnId/BICFI).
  • The system verifies if an agreement is maintained for Sender BIC. First, the system checks the 11-character BIC. If BIC is not found, the system checks for 8-character BIC.
  • If the agreement is unavailable the transaction moves to the Business Override queue.

Parent topic: Transaction Processing