Mandate resubmission limits

NPCI MMS restricts the number of times you can resubmit the same mandate

This article is for physical variant and eSign eMandate variant only. For duplicate request validation in API eMandate, see API eMandate authorisation errors.

As published in Circular NPCI/2023-24/NACH/001 (dated 4 May 2023), NPCI NACH Mandate Management System (MMS) restricts the resubmission of mandates that were previously rejected for some reason codes.

The number of times that mandate can be resubmitted is linked to the reason for which it was previously rejected. The table below shows this.

Mandates that are resubmitted beyond the permissible number of times are ACK rejected (not acknowledged i.e. no UMRN) with reason:

"Mandate representation is not allowed! Max allowed limit exceeded. Limit is: 0"

(The zero can be two - see table below).

For the purpose of identifying a mandate attempt uniquely, NPCI MMS validates for resubmission based on these fields:

• Date of Mandate

• Debtor account number

• Debtor bank

• Creditor NACH utility code

• Amount

So if you submit any mandate request (LotusPay source) with the above details matching a previously rejected mandate (rejected by destination bank), this new attempt will be considered as a resubmission and will be subject to the limits in the table below.

In LotusPay, the source will return to pending submission status, and then will move to withdrawn status.

For example:

1 July 2023: You submit a mandate request (source). NPCI acknowledges it and forwards it to the destination bank.

10 July 2023: The destination bank rejects the mandate for M037 reason code.

11 July 2023: You submit a new mandate request (source) with the same values in the above five fields. NPCI MMS will not accept this input and will immediately ACK reject it. It will not even reach the destination bank.

These restrictions are effective 1 July 2023.