How to monitor mandate registration using the mandate MIS?

How to monitor mandate registration using the mandate MIS?

First let’s understand mandate lifecycle and states 

                                                            All Mandates (These Can be classified into 3 Authentication States) 

Partial

AuthFail

Signed (Represents all authenticated mandates irrespective to further lifecycle status. These can be further classified into below 6 states) 




              ACK lifecycle states (For API mandate - only Awaiting RES)

Awaiting UMRN



Filter* : 

UMRN Overdue

 

Bank/NPCI reject

Transfer Failed


(Not in use) 

Awaiting RES

(ACK received)


Filter* : 

Registration Overdue


                                                                                       


         Res lifecycle states (Final registration status)

    Register Failed

  Register Success



     Filter* : Filters are not actual lifecycle states, these are conditional filters to classify overdue mandates (TAT breach)


The Mandate MIS report contains consolidated information of all Mandates including live statuses, for a selected period of time. It can be generated using the ‘Download’ button (beside ‘Filters’) on the Mandate Book toolbar and then clicking ‘Download MIS Report’.

Select a status to filter by and a date range. Click ‘Download’ and the csv with all the selected information is downloaded.

The report has the following fields:



Field

Example Value

Description

1


utility_code

NACH00000000000357

The corporate’s utility code as defined in the corporate config profile.

2

corporate_name

Test Business

The name of the corporate as per Digio’s records.

3

sub_user

subuser@corporate.com

The email address of a sub-user defined by the admin user.

4

nach_id

ENA200821143400755DDXL65IPCK56ES

Digio’s internal identifier used to refer to a mandate once created

5

mandate_request_id

MMI200821143400756UHM5FQN7NPM3JF


6

file_name

MMS-CREATE-YESB-ADSF123-24032017-ESIGN000001-INP.xml

The name of the file shared with Sponsor Bank

7

mode

esign

'esign’, ‘api’ or ‘physical’. Denotes the authorization method.

8

sponsor_bank

Yes Bank Ltd

Name of the Sponsor Bank

9

sponsor_bank_ifsc_or_micr

YESB0000001

IFSC Code of the Sponsor Bank

10

mandate_type

CREATE

One of ‘CREATE’, ‘AMEND’ or ‘CANCEL’. Denotes the action that the mandate performs.

11

customer_reference

CUST0000108

The customer identifier as passed by corporate during mandate creation

12

scheme_reference

PP198IKO4FGIP

The scheme reference as passed by the corporate

13

customer_name

Rishabh

The name of the customer

14

customer_bank

Federal Bank

The name of the customer’s bank (Destination Bank)

15

customer_bank_account

12345673456

The account number of the customer’s bank from which funds are to be debited

16

customer_account_type

savings

The type of the customer’s account

17

customer_bank_ifsc_or_micr

FDRL0001542

The IFSC code of the customer’s account

18

customer_identifier

9587774749

The email address or mobile phone number to which the authentication request is sent.

19

customer_mobile

9535536823

The mobile number of the customer as entered.

20

customer_email

upmanrishabh1@gmail.com

The email address of a customer as entered.

21

customer_other_id


Any other identifier of the customer as entered by the corporate

22

recurring

true

Whether the mandate is recurring or one-time

23

frequency

MONTHLY

The maximum frequency at which the mandate can be presented. e.g a weekly mandate may be presented monthly, but not vice versa.

24

mgmt_category

L001

The management category of the mandate as allotted by NPCI

25

start_date

2016-12-15 12:00:00

The start date of the mandate

26

end_date

2017-12-15 12:00:00

The end date of the mandate

27

amount

22000

The amount of the debit

28

amount_type

fixed

The type of the amount. If maximum, any amount below that may be debited. If fixed, the exact amount may be debited.

29

authenticated_at

2020-08-21 02:36:30

The time at which the mandate was authenticated

30

transferred_to_bank_at


The time at which the mandate file was shared with the bank

31

current_or_last_status

AUTH_SUCCESS

The status of the mandate at the time of generating the report

32

sponsor_bank_status

accepted/rejected

The status of the mandate as shared by sponsored bank

33

sponsor_bank_timestamp

YYYY-MM-DD HH:MM:SS

The timestamp of acceptance/rejection as processed by sponsor bank

34

sponsor_bank_reject_reason

“Duplicate instrument!”

The reason for rejection by sponsor bank

35

ack_status

Awaited/accepted/rejected

The status of ACK returned by sponsor bank

36

ack_timestamp

YYYY-MM-DD HH:MM:SS

The timestamp of receiving the ACK

37

nack_reason_code

 


Only present if rejected at ACK level. Provided page 12 onwards on this document

38

nack_reason


Only present if rejected at ACK level. Provided page 12 onwards on this document

39

umrn

HDFC701210820000XXXX

Unique Mandate Resource Number. An identifier assigned to the mandate by NPCI that identifies it globally.

40

registration_status


The status of the mandate (Registered/unregistered)

41

registration_timestamp


Time at which the Mandate is officially registered as per NPCI

42

reject_code


The code given for rejection

43

reject_reason


The reason given for the mandate’s rejection

44

expire_on

2020-08-31 11:59:59

The expiry date of the mandate

45

overdue_status


Whether the mandate is overdue or not.

46

overdue_by


The no. of days the mandate is overdue by.

47

npci_txn_id


The transaction ID of the mandate as per NPCI

48

auth_sub_mode

debit, net_banking

The authorization mode for Net Banking/Debit card auth.

49

auth_failed_reason_code


Code denoting the reason for auth failure

50

auth_failed_reason_desc


Description of the reason behind auth failure

51

time_taken_for_registration_status


The time taken to register the mandate

52

time_taken_for_umrn_status


The no. of days from date of authentication to date of UMRN receipt. Calculated based on dates.

    • Related Articles

    • How to monitor mandate registration using mandate analytics feature?

      Below tables can be found under Analytics section of Mandate Book: To generate a report, a Bank and date range (automatically set to 7 days) has to be selected and the ‘Generate’ button clicked. If any data is present, upto two tables are shown which ...

    • How can I monitor my mandate registration & debit status?

      Three ways mandate registration & debit status can be monitored - a - Webhooks. (Data proactively updated at your end) b - Digio Dashboards (Individual entity level real time status can be seen) c - Digio MIS (Separate MIS can be downloaded upto 30 ...

    • How does user authentication happen using API mandate?

      An authentication is triggered via Digio link sent over SMS/Email or SDK trigger using eNACH id and identifier provided by Digio. In both cases below screens open - NPCI then redirects the Customer to the Destination Bank’s NetBanking or to a Debit ...

    • How do I know if my mandate registration is successful?

      RES is confirmation that the mandate has been registered successfully and is ready for making debits. API Mandate Physical eSign Mandate TAT T+1 T+7 T+7 Channel Received via H2H server sponsor bank channel in XML or CSV Format Received via H2H server ...

    • How does the mandate registration process happen?

      Steps 3 Mandate Variants API eNACH (Debit Card & Net Banking) PHYSICAL NACH eSIGN eNACH 1 - Sponsor bank profile creation Via Digio Dashboard (One time activity) Via Digio Dashboard (One time activity) Via Digio Dashboard (One time activity) 2 - ...