1. SEPA Direct Debits User Guide
  2. Collections Transactions
  3. Outbound Collections Transaction Input
  4. Saving of an Outgoing Collections Transaction

Saving of an Outgoing Collections Transaction

The system performs the following mandatory field checks and the referential checks during the enrich/ save of outgoing Collections transaction.
  • Bank Redirection
    • System validates if there are any redirection bank code maintained for the Debtor Bank Code, Indirect participant bank code and if there is, system replaces the original bank code with redirected bank code.
    • Any exception during this is logged into Transaction Repair Queue.
    • Applicable only for upload and web services.
  • Account Redirection
    • System validates if there is any redirection account maintained for the Creditor account specified for an Outgoing DD transaction initiated from current processing branch. If there is, system replaces the original creditor account with redirected account number.
    • Any exception during this is logged into Transaction Repair Queue.
    • Applicable only for upload and web services.
  • Verify On Us transfer (Y/N)
    • System defaults the On Us Transfer flagas ‘Yes’ if both the Creditor agent bank code and Debtor agent bank code are same as the current processing branch bank code (or) if both creditor account and debtor account are held with current processing branch bank code.
  • Transactional Validations
    • Verify if Instruction date/Collection date minus current system date is greater than or equal to First Collection receipt days (maintained in Network DD preferences) in case of FRST/OOFF & Recurrent collection receipt days in case of RCUR/FNAL. Else transaction is prompted with appropriate error message and is not booked.
    • For an outgoing DD transaction, the debit account currency and credit account currency is the same as Transfer currency.
    • Creditor account field is verified to check if it is valid and existing with appropriate status.
    • Debtor bank code, Creditor bank code, Direct Participant bank code fields are validated based on the Local bank code clearing maintenance.
    • Field Transfer Amount & Value Date should not be null and Field Transfer amount specified in the transaction should be within the limit amount provided in Network DD Preferences.
    • If the ‘Value Date’ falls on a Network Holiday, then Value date is moved to next working date and the date instructed in the Collections request is stored under ‘Original Value Date’.
  • Processing Dates Resolution
    • Activation date is derived based on the value date specified in the transaction. If Value date falls on a holiday, system derives the next network working day as the Activation date.
    • Dispatch date is derived based on the sequence type specified in the transaction
  • Debit/Credit Account Resolution
    • Debit account and Credit account details is derived based on the liquidation accounting codes maintained in Network DD Preferences.

If any of the below validation fails, then the transaction is rejected with an error code.

Following fields are mandatory for requesting Outgoing Collections transaction:
  • Host Code
  • Network Code
  • Creditor Bank Code
  • Creditor Account (or Creditor IBAN, if IBAN is mandatory for the Network)
  • Debtor Bank Code
  • Debtor Account (or Debtor IBAN, if IBAN is mandatory for the Network)
  • Debtor Name
  • Transfer Currency
  • Transfer Amount
  • Value Date
  • Mandate Id

If the source code is not MANL, then it is mandatory to specify the Source reference number.

System validates whether customer account is an open and authored record in External Account Maintenance. Holiday check for instruction date is done based on the local branch holidays maintained.

Any validation failure from user interface screen throws error on transaction saving. You can check the error details from the respective error message displayed and can take remedial action before re-submitting.

Parent topic: Outbound Collections Transaction Input