9. Annexure A - Accounting Entries and Advices

This chapter contains the following sections:

• Section 9.1, "Events for the Payments and Collections Module"
• Section 9.2, "Accounting Roles"
• Section 9.3, "Product Type and Event Code and Accounting Entry Combinations"
• Section 9.4, "Event- Advices for PCs"
• Section 9.5, "Credit Acknowledgement Messages"

9.1 Events for the Payments and Collections Module

The following are the events defined for the PC module:

Event Code	Event Description	Remarks
BOOK	Transaction Booking	This event signifies the transaction’s entry into the system.
INIT	Transaction Initiation	Involves Product Resolution, Default of Product Parameters, Dates Resolution. BOOK and INIT are automatic events for transac­tions uploaded from Electronic Banking Auto authorization is done for uploaded contracts if the amount is within the limit defined for the upload source-product category. For the manual input transactions, BOOK is done on SAVE and INIT is automatic. INIT can also be done manually.
DRFX	Exchange Rate Popula­tion – Outgoing (Only Payments)	The events DRFX occur before the customer leg of accounting (provided the customer leg is the debit leg) The system triggers these events automatically if the amount is within the limit specified for the cus­tomer Agreement / Product / Currency. Else, you will have to trigger them manually.
DRLQ	Debit Entry Liquidation	The system triggers the event automatically and initiates the debit entry either to the customer account or to the clearing suspense account (based on the type of transaction).
DRCO	Debit Entry Consolida­tion	For debit transactions to the customer account that require consolidation this event is automatically triggered.
CRCO	Credit Entry Consolida­tion	This event is triggered automatically for all credit transactions to the customer account that require consolidation.
CRFX	Exchange Rate Popula­tion – Incoming (Only payments)	The events CRFX occur before the customer leg of accounting (provided the customer leg is the credit leg) The system triggers these events automatically if the amount is within the limit specified for the cus­tomer Agreement / Product / Currency. Else, you will have to trigger them manually.
CRLQ	Credit Entry Liquidation	The system triggers the event automatically and initiates the credit entry either to the customer account or to the clearing suspense account (based on the type of transaction)
RJBS	Reject prior to Inter bank settlement	In the case of Outgoing payment this event hap­pens prior to the interbank settlement of the outgo­ing payment. In the case of Outgoing Collection this event is pro­cessed before the due date of an outgoing collec­tion. In the case of Incoming Collection this event is pro­cessed before the due date of an incoming collec­tion.
REJT	Reject	In the case of outgoing payment this event is pro­cessed when a rejection message is received after the interbank settlement date of the outgoing pay­ment. In the case of incoming payment this event is trig­gered with in the payment rejection date.
REVP	Reverse	This event is triggered on receiving the reverse of Incoming collection transactions.
AMND	Amend	This event is triggered whenever an authorized contract, for which either DRLQ or CRLQ or DCLG events are not triggered, is modified.

9.2 Accounting Roles

The following list contains details of the accounting Roles that are applicable to the PCs you can process at your bank.

Accounting Role	Description	Role Type
INTSUSREC	Internal Suspense Receivable	Asset
CLGSUSREC	Clearing Suspense Receivable	Asset
INTSUSPAY	Internal Suspense Payable	Liability
CLGSUSPAY	Clearing Suspense Payable	Liability
CLGVOSTRO	Clearing VOSTRO (this could be used instead of using CLGSUSPAY and CLGSUSREC if a VOSTRO has been designated to be used and not a suspense GL)	Settlement
CHG1_INC	Charge 1 Income	Income
CHG2_INC	Charge 2 Income	Income
CHG3_INC	Charge 3 Income	Income
CHG4_INC	Charge 4 Income	Income
CHG5_INC	Charge 5 Income	Income
COMPACC	Compensation Account for Recall Transactions	X (User Defined)
CHARGEACC	Charge Account for Reject/Recall Transactions	X (User Defined)
P2PCUSTTFR	Customer Debit for P2P Payments	Liability
P2PTESTEX	Test transaction for P2P Payments	Expense

9.3 Product Type and Event Code and Accounting Entry Combinations

This section contains the following topics:

• Section 9.3.1, "Events for Payment and Collection Products"
• Section 9.3.2, "Accounting Entries"

9.3.1 Events for Payment and Collection Products

For your convenience we have listed the Events and Accounting Entries, which need to be defined for the various product types that can be maintained for this module. The Events that you need to set up for the various types of Payment and Collection products are as follows:

Outgoing Payment

You will need to define the following events while defining an Outgoing Payment product:

• BOOK
• INIT
• DRLQ
• CRLQ
• DCLG
• RJBS
• REJT
• CONS

Incoming Payment

You will need to define the following events while defining an Incoming Payment product:

• BOOK
• INIT
• DRLQ
• CRLQ
• CONS

Outgoing Direct Debit

You will need to define the following events while defining an Outgoing Direct Debit product:

• BOOK
• INIT
• DRLQ
• CRCO
• CRLQ
• DCLG
• RDSP
• APPR
• REJT
• CLOS
• RECL
• REVR
• CONS

Incoming Direct Debit

• BOOK
• INIT
• DRLQ
• CRLQ
• REJT
• RECL
• REVR
• CONS

Reject of Incoming Direct Debit

• BOOK
• INIT
• DRLQ
• CRLQ
• DCLG
• REVR

Reject of Outgoing Direct Debit

• BOOK
• INIT
• XREF
• DRLQ
• CRLQ
• REVR

Recall of Incoming Direct Debit

• BOOK
• INIT
• DRLQ
• CRLQ
• DCLG
• REVR

Recall of Outgoing Direct Debit

• BOOK
• INIT
• XREF
• DRLQ
• CRLQ
• REVR

Outgoing Request for Debit

• BOOK
• INIT
• DCLG
• RDSP
• APPR
• REJT
• CLOS
• REVR

Incoming Request for Debit

• BOOK
• INIT
• APPR
• REJT
• REVR

Approval of Incoming Request for Debit (Outgoing Payment)

• BOOK
• INIT
• DRFX
• DRCO
• DRLQ
• CRLQ
• DCLG
• REJT
• REVR

Approval of Outgoing Request for Debit (Incoming Payment)

• BOOK
• INIT
• XREF
• DRLQ
• CRCO
• CRFX
• CRLQ
• REVR

Reject of Incoming Request for Debit

• BOOK
• INIT
• XREF
• DCLG

Reject of Outgoing Request for Debit

• BOOK
• INIT
• XREF

Reject of Incoming Payments

• BOOK
• INIT
• DRLQ
• CRLQ
• DCLG
• MISC

Reject of Outgoing Payments

• BOOK
• INIT
• DRLQ
• CRLQ
• MISC

Reverse of Incoming Collection

• BOOK
• INIT
• DRLQ
• CRLQ
• DCLG
• MISC

Reverse of Outgoing Collection

• BOOK
• INIT
• DRLQ
• CRLQ
• MISC
• CONS

9.3.2 Accounting Entries

DRLQ: Debit Entry Liquidation for Payments

While triggering this event for Outgoing payment transactions the system posts a debit entry to the customer account. In the case of incoming transactions the debit entry will be posted to the Clearing Suspense account.

Those contracts satisfying the following parameters will be picked up for processing based on their priority.

• The contract is Active and Authorized
• The Debit entry date is prior to the current system date or is on the current system date.
• The Initiation event has been processed successfully
• For transactions involving the customer account having a foreign currency the exchange rate population event has been completed and authorized.
• For outgoing transactions the customer entry has been consolidated if the transaction has been marked for consolidation.

Entries posted for Outgoing transfers will be as follows:

Accounting Role	Dr./Cr. Indicator
Customer Account	Debit
Internal Suspense Payable –	Credit

Entries posted for Incoming transfers will be as follows:

Accounting Role	Dr./Cr. Indicator
Clearing Suspense Receivable (or Clearing Vostro)	Debit
Internal Suspense Receivable–	Credit

Note

If the entry dates of the debit and credit legs are the same, the system will not pass the entry to the Internal Suspense account. Also, for transactions marked for client entry con­solidation, a single debit entry to the customer’s account will be passed. The system gen­erates a new reference number for the consolidation and the accounting entries will be passed using this reference number.

Entries posted for Debit Notification will be as follows:

Accounting Role	Dr./Cr. Indicator
Interbank Receipt GL	Debit
Intermediary GL	Credit

Entries posted for Credit Notification will be as follows:

Accounting Role	Dr./Cr. Indicator
Network GL (NOSTRO)	Debit
Intermediary GL	Credit

If the contract is moved to release queue for ‘DRLQ’ event, then the following account entries are passed:

Event	Account	Debit/Credit	Amount
DRLQ	Customer Account	Debit	Transaction Amount
DRLQ	Intermediary GL	Credit	Transaction Amount

CRLQ: Credit Entry Liquidation for Payments

During this event a credit entry will be posted to the Internal/Clearing Suspense account for outgoing transactions. The entry will be posted to the customer account for incoming transactions.

Based on their priority, the system picks up all active and authorized contracts if:

• The credit entry date is prior to or is the current system date
• The DRLQ event has been processed successfully

Entries posted for Outgoing transfers will be as follows:

Accounting Role	Dr./Cr. Indicator
Internal Suspense Payable–	Debit
Clearing Suspense –Payable (or Clearing Vostro)	Credit

Entries posted for Incoming transfers will be as follows:

Accounting Role	Dr./Cr. Indicator
Internal Suspense –Receivable	Debit
Customer Account	Credit

Entries posted for Debit Notification will be as follows:

Accounting Role	Dr./Cr. Indicator
Intermediary GL	Debit
Network GL (NOSTRO)	Credit

Entries posted for Credit Notification will be as follows:

Accounting Role	Dr./Cr. Indicator
Intermediary GL	Debit
Interbank Receipt GL	Credit

If the contract is moved to release queue for ‘CRLQ’ event, then the following account entries are passed:

Event	Account	Debit/Credit	Amount
CRLQ	Intermediary GL	Debit	Transaction Amount
CRLQ	Outgoing Network GL (NOSTRO)	Credit	Transaction Amount

If the incoming payment or return of outgoing payment is suspended from the incoming authorization queue then system will process the ‘CRLQ’ event with following accounting entries:

Event	Account	Debit/Credit	Amount
CRLQ	Intermediary GL	Debit	Transaction Amount
CRLQ	Unsettle GL (will be picked up from Product Category)	Credit	Transaction Amount

If the incoming payment or return of outgoing payment is authorized from the repair queue then system will not post any accounting entries and the transaction will be moved into incoming authorization queue.

If the transaction is completely authorized from the incoming authorization queue, i.e., if the transaction does not fall on any exception queue, then system will process the ‘CRLQ’ event and pass the following accounting entries:

Event	Account	Debit/Credit	Amount
CRLQ	Intermediary GL	Debit	Transaction Amount
CRLQ	Customer Account	Credit	Transaction Amount

If the contract does not require any manual authorization or release action then both ‘DRLQ’ and ‘CRLQ’ event will be processed and following accounting entries are passed:

Event	Account	Debit/Credit	Amount
DRLQ	Customer Account	Debit	Transaction Amount
DRLQ	Intermediary GL	Credit	Transaction Amount
CRLQ	Intermediary GL	Debit	Transaction Amount
CRLQ	Outgoing Network GL (NOSTRO)	Credit	Transaction Amount

If the transaction does not fall in to any of the exception queues, then both ‘DRLQ’,’CRLQ’ will be processed and following accounting entries are passed:

Event	Account	Debit/Credit	Amount
DRLQ	Incoming Network GL (NOSTRO)	Debit	Transaction Amount
DRLQ	Intermediary GL	Credit	Transaction Amount
CRLQ	Intermediary GL	Debit	Transaction Amount
CRLQ	Customer Account	Credit	Transaction Amount

If the transaction falls on incoming authorization queue then ‘DRLQ’ event will be processed and following accounting entries are passed:

Event	Account	Debit/Credit	Amount
DRLQ	Incoming Network GL (NOSTRO)	Debit	Transaction Amount
DRLQ	Intermediary GL	Credit	Transaction Amount

If the transaction is moved from exception TA to exception T1 while authorizing the transaction from incoming authorization queue then system will not post any accounting entries.

The accounting entries posted for ‘Outgoing Payment’ for which the P2P payment type is ‘Customer Debit’ is as follows:

Event	DR / CR	Accounting Role	Amount Tag
DRLQ	DR	CUSTOMER	TFR_AMT
DRLQ	CR	INTSUSPAY	TFR_AMT
CRLQ	DR	INTSUSPAY	TFR_AMT
CRLQ	CR	P2PCUSTTFR	TFR_AMT

The following accounting entries can be defined for Outgoing Payment for which the P2P payment type is test transaction:

Event	DR / CR	Accounting Role	Amount Tag
DRLQ	DR	P2PTESTEX	TFR_AMT
DRLQ	CR	INTSUSPAY	TFR_AMT
CRLQ	DR	INTSUSPAY	TFR_AMT
CRLQ	CR	CLGSUSPAY	TFR_AMT

The accounting entries posted for ‘Outgoing Payment’ for which the P2P payment type is ‘P2P Final Payment’ is as follows:

Event	DR / CR	Accounting Role	Amount Tag
DRLQ	DR	CUSTOMER	TFR_AMT
DRLQ	CR	INTSUSPAY	TFR_AMT
CRLQ	DR	INTSUSPAY	TFR_AMT
CRLQ	CR	CLGSUSPAY	TFR_AMT

The following accounting entries can be defined for Reject of Outgoing Payment for which the P2P payment type is P2P final payment:

Event	DR / CR	Accounting Role	Amount Tag
DRLQ	DR	CLGSUSREC	TFR_AMT
DRLQ	CR	INTSUSREC	TFR_AMT
CRLQ	DR	INTSUSREC	TFR_AMT
CRLQ	CR	CUSTOMER	TFR_AMT

The CRLQ event of the PC contracts where FATCA withholding has been determined will have the following entries

Event	DR / CR	Amount Type	Account
CRLQ	DR	Payment Amount (Consolidated)	Suspense GL
CRLQ	CR	Payment Amount (Consolidated)	Settlement Account/GL
CRLQ	DR	FATCA Tax	Settlement Account/GL
CRLQ	CR	FATCA Tax	Tax GL/Escrow GL

DRLQ: for Outgoing Collection, Reject of Outgoing Collection and Recall of Incoming Collection products

The following accounting entries can be defined for outgoing collection, reject of outgoing collection and recall of incoming collection products:

Event Code	Accounting Role	Amount Tag	Dr/Cr
DRLQ	CLGSUSREC	TFR_AMT	Debit
	INTSUSPAY	TFR_AMT	Credit
CRLQ	INTSUSPAY	TFR_AMT	Debit
	BENEFICIARY	TFR_AMT	Credit

DRLQ: for Incoming Collection, Reject of Incoming Collection and Recall of Outgoing Collection products

The following accounting entries can be defined for incoming collection, reject of incoming collection and recall of outgoing collection products:

Event Code	Accounting Role	Amount Tag	Dr/Cr
DRLQ	REMITTER	TFR_AMT	Dr
	INTSUSREC	TFR_AMT	Cr
CRLQ	INTSUSREC	TFR_AMT	Dr
	CLGSUSPAY	TFR_AMT	Cr

DRLQ: for Recall of Incoming Collection Products

The following accounting entries can be defined for recall of incoming collection products:

Event Code	Accounting Role	Amount Tag	Dr/Cr
DRLQ	CLGSUS­REC	INT_AMT	Debit
	COMPACC	INT_AMT	Credit

DRLQ: for Recall of Outgoing Collection Products

The following accounting entries can be defined for recall of outgoing collection products:

Event Code	Accounting Role	Amount Tag	Dr/Cr
CRLQ	COMPACC	INT_AMT	Debit
	CLGSUS­PAY	INT_AMT	Credit

Reject of Outgoing payments

The following entries can be defined for reject of outgoing payments:

Event Code	Accounting Role	Amount Tag	Dr/Cr
DRLQ	CLGSUSREC	TFR_AMT	Dr
	INTSUSREC	TFR_AMT	Cr
CRLQ	INTSUSREC	TFR_AMT	Dr
	CUSTOMER	TFR_AMT	Cr

Reject of Incoming payments

The following entries can be defined for reject of incoming payments:

Event Code	Accounting Role	Amount Tag	Dr/Cr
DRLQ	CUSTOMER	TFR_AMT	Dr
	INTSUSPAY	TFR_AMT	Cr
CRLQ	INTSUSPAY	TFR_AMT	Dr
	CLGSUSPAY	TFR_AMT	Cr

For reject of Incoming Payments (IN) contracts following accounting entries will be posted for DRLQ and CRLQ events:

Event	Account	Debit/Credit	Amount
DRLQ	Unsettle GL	Debit	Transaction Amount
DRLQ	Intermediary GL	Credit	Transaction Amount
CRLQ	Intermediary GL	Debit	Transaction Amount
CRLQ	Outgoing Network GL (NOSTRO)	Credit	Transaction Amount

Reverse of Outgoing collections

The following entries can be defined for reverse of outgoing collections:

Event Code	Accounting Role	Amount Tag	Dr/Cr
DRLQ	CUSTOMER	TFR_AMT	Dr
	INTSUSREC	TFR_AMT	Cr
CRLQ	INTSUSREC	TFR_AMT	Dr
	CLGSUSPAY	TFR_AMT	Cr

Reverse of Incoming collections

The following entries can be defined for reverse of incoming collections:

Event Code	Accounting Role	Amount Tag	Dr/Cr
DRLQ	CLGSUSREC	TFR_AMT	Dr
	INTSUSPAY	TFR_AMT	Cr
CRLQ	INTSUSPAY	TFR_AMT	Dr
	CUSTOMER	TFR_AMT	Cr

If the incoming payment is rejected from the incoming authorization queue then system will process ‘CRLQ’ event and pass the following accounting entries:

Event	Account	Debit/Credit	Amount
CRLQ	Intermediary GL	Debit	Transaction Amount
CRLQ	Unsettle GL(will be picked up from Product Category)	Credit	Transaction Amount

If the incoming payment is rejected from the repair queue then system will process ‘CRLQ’ event and pass the following accounting entries:

Event	Account	Debit/Credit	Amount
CRLQ	Intermediary GL	Debit	Transaction Amount
CRLQ	Suspense GL	Credit	Transaction Amount

If the contract is reversed from Release queue, then contract will be reversed and the following accounting entries are passed:

Event	Account	Debit/Credit	Amount
REVR	Customer Account	Debit	Negative transaction Amount
REVR	Intermediary GL	Credit	Negative transaction Amount

If the contract is reversed from Authorization (A1, A2) queues, then the system will not process any accounting entries.

The consolidated debit entry is posted to the customer account during the DRLQ event. The entries posted will be as follows:

Event	Debit/Credit	Amount Type	Account
DRLQ	Debit	Payment Amount (Consolidated)	Customer A/c
DRLQ	Credit	Payment Amount (Consolidated)	Suspense GL

Customer Consolidation Across Products

For transactions with ‘Customer Consolidation Across Products’ as checked, system triggers the DRLQ/CRLQ entries during file consolidation batch closure. A single debit entry is posted to the Customer account for the total file consolidation batch amount and individual credit entries are passed to the internal suspense account for each transaction amount.The Amount tag “FILE_AMT” is used for consolidation across products which denotes the total File amount or transaction amount that are considered for Consolidation.

During file level consolidation, for DRLQ event, the accounting entry reference no. for the debit leg will be based on the process code 'ZFCN' and the credit leg for the individual transfer amount will be based on the corresponding product code of the transaction.

The accounting entries for PC transactions with customer consolidation across products is as follows:

For Outgoing Payment

Event Code	Accounting Role	Amount Tag	Dr/Cr
DRLQ	CUSTOMER	FILE_AMT	Dr
DRLQ	INTSUSPAY	TFR_AMT	Cr

Event Code	Accounting Role	Amount Tag	Dr/Cr
CRLQ	INTSUSPAY	TFR_AMT	Dr
CRLQ	CLGSUSPAY	TFR_AMT	Cr

For Outgoing Collection

Event Code	Accounting Role	Amount Tag	Dr/Cr
DRLQ	CLGSUSREC	TFR_AMT	Dr
DRLQ	INTSUSPAY	TFR_AMT	Cr

Event Code	Accounting Role	Amount Tag	Dr/Cr
CRLQ	INTSUSPAY	TFR_AMT	Dr
CRLQ	CUSTOMER	FILE_AMT	Cr

For Reversal of Outgoing Collection

Event Code	Accounting Role	Amount Tag	Dr/Cr
DRLQ	CUSTOMER	FILE_AMT	Dr
DRLQ	INTSUSPAY	TFR_AMT	Cr

Event Code	Accounting Role	Amount Tag	Dr/Cr
CRLQ	INTSUSPAY	TFR_AMT	Dr
CRLQ	CLGSUSREC	TFR_AMT	Cr

Incoming Payment to the Loan Account

Incoming payment to the loan account will be manual payment in CL module

Event	Accounting Role	Amount Tag	Dr/Cr
DRLQ	CLGSUSREC	TFR_AMT	DR
DRLQ	INTSUSREC	TFR_AMT	CR
CRLQ	INTSUSREC	TFR_AMT	DR
CRLQ	CUSTOMER	TFR_AMT	CR

If the customer account is of loan type then system will replace the CUSTOMER accounting role with the Credit Settlement Bridge maintained in the CL module.

Reject of Incoming Payment to the Loan Account

If the transaction is rejected for a manual payment which is already done in CL, then the manual payment where the original payment contract reference number is linked in CL also will be reversed.

Event	Accounting Role	Amount Tag	Dr/Cr
DRLQ	CUSTOMER	TFR_AMT	DR
DRLQ	INTSUSREC	TFR_AMT	CR
CRLQ	INTSUSREC	TFR_AMT	DR
CRLQ	CLGSUSREC	TFR_AMT	CR

If the manual payment is reversed, the CUSTOMER accounting role will be replaced with the Debit Settlement Bridge in CL.

Outgoing Collection for the Loan Account

The outgoing direct debit collection for the loan account can be initiated through Periodic Instruction and Manual Input.

Event	Accounting Role	Amount Tag	Dr/Cr
DRLQ	CLGSUSREC	TFR_AMT	DR
DRLQ	INTSUSREC	TFR_AMT	CR
CRLQ	INTSUSREC	TFR_AMT	DR
CRLQ	CUSTOMER	TFR_AMT	CR

On the due date of the transaction, when the customer account is of loan type then system will replace the CUSTOMER accounting role with the Credit Settlement Bridge that is maintained in the CL module and manual payment in CL will be processed.

Reject of Outgoing Collection for the Loan Account

You can reject an operation on outgoing collection for a loan account. If the rejection is before the due date then only the PC transaction is rejected. If rejection is after the due date then system will try to reverse out the manual payment created as part of original direct debit collection transaction.

Event	Accounting Role	Amount Tag	Dr/Cr
DRLQ	CUSTOMER	TFR_AMT	DR
DRLQ	INTSUSREC	TFR_AMT	CR
CRLQ	INTSUSREC	TFR_AMT	DR
CRLQ	CLGSUSPAY	TFR_AMT	CR

If the manual payment is reversed, the CUSTOMER accounting role will be replaced with the Debit Settlement Bridge in CL.

Recall of Outgoing Collection for the Loan Account

Recalling outgoing collection for the loan account is initiated by the debtor bank and is allowed on outgoing direct debit collection.

Event	Accounting Role	Amount Tag	Dr/Cr
DRLQ	CUSTOMER	TFR_AMT	DR
DRLQ	INTSUSREC	TFR_AMT	CR
CRLQ	INTSUSREC	TFR_AMT	DR
CRLQ	CLGSUSPAY	TFR_AMT	CR

If the manual payment is reversed, the CUSTOMER accounting role will be replaced with the Debit Settlement Bridge in CL.

Reversal of Outgoing Collection for the Loan Account

You can reverse an original outgoing collection for the loan account.

Event	Accounting Role	Amount Tag	Dr/Cr
DRLQ	CUSTOMER	TFR_AMT	DR
DRLQ	INTSUSREC	TFR_AMT	CR
CRLQ	INTSUSREC	TFR_AMT	DR
CRLQ	CLGSUSREC	TFR_AMT	CR

If the manual payment is reversed, the CUSTOMER accounting role will be replaced with the Debit Settlement Bridge in CL.

 

9.4 Event- Advices for PCs

The following list of advices can be generated for the various events that get triggered during the life cycle of a PC transaction.

Event code	Advice
INIT	REMIT_SLIP
CRLQ	CREDIT_ADVICE
APPR	APPROVAL_ADVICE
REJT	REJECTION_ADVICE
CLOS	CLOSURE_ADVICE
RECL	RECALL_ADVICE
DRLQ	DEBIT_ADVICE
APPR	APPROVAL_ADVICE
REJT	REJECT_ADVICE
RECL	RECALL_ADVICE

The following advices will be generated for collection transactions

• Remit Slip: Based on the product advice definition, this advice is generated when a contract is saved. It is automatically printed and cannot be viewed/regenerated subsequently.
• Debit Advice: Based on the product advice setup, this advice is generated while processing the Debit Entry Liquidation (DRLQ) event for the following type of transactions
  • Incoming Direct Debit
  • Reject of Incoming Direct Debit
  • Recall of Outgoing Direct Debit
  • Approval of Incoming Direct Debit (Outgoing Payment)

• Credit Advice: Based on the product advice setup, this advice is generated while processing the Credit Entry Consolidation (CRLQ) event for the following type of transactions:
  • Outgoing Direct Debit
  • Reject of Outgoing Direct Debit
  • Recall of Incoming Direct Debit
  • Approval of Outgoing Request for Debit (Incoming Payment).

• Approval Advice: Based on the product setup, this advice is generated for the following type of transaction while processing Collection of Approvals (APPR).
  • Outgoing Collection
  • Incoming Collection

• Reject Advice: This would is generated for the following type of transactions:
  • Rejected Outgoing Collections: If the advice basis date is the Event Date, the advice is generated while processing the Collection of Rejection (REJT) event for the transaction. If you have identified the Response Date as the advice basis date, the advice is generated on the response date of the transaction.
  • Rejected Incoming Collections: The advice is generated while processing Collection of Rejection (REJT) event for the transaction.
  • Rejected Approval of Incoming Request for Debit (Outgoing Payment): The advice is generated while processing Collection of Rejection (REJT) event for the transaction.

• Closure Advice: This advice is generated for following type of transactions:
  • Outgoing Request for Debits without Re-dispatch - generated while processing the Collection Closure (CLOS) event of the transaction.
  • Outgoing Request for Debits with Re-dispatch - generated during contract re-dispatch (RDSP).

• Recall Advice: Based on the product advice setup, this is generated for the following type of transactions while processing the Contract Recall (RECL) event
  • Outgoing Direct Debit
  • Incoming Direct Debit

9.5 Credit Acknowledgement Messages

For Outgoing Payments

If we receive the Credit Acknowledgement message for our outgoing payment contracts then system will update the message status of the corresponding outgoing payment contract as ‘CD’ (Credit Done).

For Incoming Payments

The system will generate the outgoing Credit Acknowledgment (N10) message for incoming payment contract. After processing the CRLQ event, system will generate the ‘Credit Acknowledgement Message’ for the incoming payment contract. This process will group the number of incoming payment contracts and generates the single ‘Credit Acknowledgement Message’ for those contracts (Number of contracts for group will be parameterized in product maintenance).

Message Format

The system will support the following credit acknowledgement messages:

M/O	Field No	Field Name	Contents / Options	Description
M	2020	Transaction Refer­ence Number	16x	Uniquely identifies the mes­sage.
Repeating Group Begins
M	2020	Transaction Refer­ence Number	16x	Uniquely identifies the trans­action. (loop)
M	5518	IFSC of Originator of Remittance	4!a4!c[3!c]	IFSC of Debit Originator
M	2006	Related Reference	16x	For inward N10 message (received for our outgoing pay­ment), Transaction reference number of the original N06 message For outward N10 message (generated for the incoming payment which we received), we need to populate the Transaction reference num­ber of the incoming payment message (N02)
M	3501	Amt Credited Time	8!n 6!n	Date and Time when the amount is credited to the cus­tomer 8!n is the credited date YYYYMMDD 6!n is the credited time HHMISS
Repeating Group Ends