{"id":7486,"date":"2022-09-27T10:12:59","date_gmt":"2022-09-27T10:12:59","guid":{"rendered":"https:\/\/signdesk.com\/in\/?p=7486"},"modified":"2025-09-17T07:34:47","modified_gmt":"2025-09-17T13:04:47","slug":"utility-code-for-enach-mandates","status":"publish","type":"post","link":"https:\/\/melento.ai\/en-in\/blog\/utility-code-for-enach-mandates","title":{"rendered":"Utility Codes For eNACH Mandates – Explained"},"content":{"rendered":"

\"Utility<\/h2>\n

What is a NACH Utility Code?<\/b>\u00a0<\/span><\/i><\/span><\/h2>\n

A utility code is a unique user identification number assigned by NPCI to a corporate user of eNACH. Utility codes are also known as corporate user IDs and are crucial to track the mandates associated with a corporate account.<\/p>\n

To leverage eMandates<\/span><\/a>, corporate organizations must register for NACH services at NPCI (National Payments Corporation of India) Corporates can request NPCI via their sponsor Bank.\u00a0 NPCI will verify & scrutinize the submitted documents and issue a utility code to the corporate organization if everything is above board.\u00a0 <\/span>\u00a0<\/span><\/p>\n

It\u2019s important to note here that the utility code is mapped with the sponsor bank during the mandate registration process at NPCI.<\/p>\n

How Are Utility Codes Generated?<\/b><\/span><\/h2>\n

Utility codes are generated by NPCI after the sponsor bank lodges NACH payment<\/span><\/a> for the collection\/distribution of funds on behalf of its corporate client enrolled for NACH services.\u00a0<\/span><\/p>\n

NPCI also assists the destination bank in uploading the transaction file, which is then assigned to the appropriate destination bank for processing. The confirmation response is sent to the sponsor bank after completing the transaction.<\/p>\n

Differences Between Utility Codes and UMRN\u00a0 <\/b><\/span><\/h2>\n

A Unique Mandate Reference Number (UMRN) is assigned to each new mandate created in the system. This number is generated automatically by the NACH system during the eMandate workflow involving the customer\u2019s destination bank.\u00a0<\/b><\/p>\n

UMRN is mandatory for every transaction and is also required to amend or cancel NACH mandates<\/span><\/a>.\u00a0\u00a0<\/span><\/b><\/p>\n

In contrast, the utility code is a special user identification number provided by NPCI to corporate participants in the NACH system. Utility codes are issued after corporate organizations lodge a request via their sponsor bank. The request recommended by the sponsor bank is scrutinized, and a utility code is issued if the request is in order.\u00a0<\/b><\/p>\n

Every corporate participant in the NACH system receives a unique utility code, and customers can use this code to determine which organization is being paid via the registered eMandate.\u00a0\u00a0<\/b><\/p>\n

Apart from utility codes & UMRN, a merchant reference number is also generated. This is a one-of-a-kind payment code provided to merchants by their acquiring bank, also known as the payment processor. The merchant ID number is required for merchant identification in processing networks and routing transactions through the proper channels to ensure that funds reach their intended destination.<\/b><\/p>\n

How Are Utility Codes Used in NACH Debits?<\/strong><\/span><\/h2>\n

Utility codes are used to perform a number of important functions in the NACH mandate system<\/span><\/a>. Here are a few ways utility codes are used to streamline recurring payment transactions.\u00a0<\/span><\/p>\n

    \n
  1. Corporate number \/ Utility code validation:<\/b><\/span><\/b><\/li>\n<\/ol>\n

    The corporate number\/utility code provided in the transaction data will be checked against the corporate number\/utility code provided in the NACH system. The transaction will be refused if a mismatch occurs or the corporate number\/utility code does not exist.<\/span><\/p>\n

      \n
    1. Corporate number \/ Utility code linking with UMRN:\u00a0<\/b><\/span><\/li>\n<\/ol>\n

      When mandates are registered, the NACH system will link the corporate code and the UMRN assigned to the mandates presented with the code. The sponsor bank and the corporate should confirm that the transaction file contains the right corporate code linked to the relevant UMRN. If there is a discrepancy, the NACH system will reject the transaction.<\/span><\/p>\n

        \n
      1. Corporate registration with sponsor bank:<\/b><\/span><\/b><\/li>\n<\/ol>\n

        Any bank that wishes to operate as a sponsor bank for a corporate to process mandates must first register the corporate with NPCI. The bank must submit a user registration form with their utility code for such registration.<\/p>\n

          \n
        1. Corporate User Status:<\/b><\/span><\/li>\n<\/ol>\n

          If the corporate is new to the NACH system, NPCI will assign a new corporate code. In the case of an existing corporation, the corporate\/utility code must be quoted in the user registration form to be registered. If a corporation is assigned a new code, the corporate\/sponsor banks cannot utilize that code to conduct transactions relevant to mandates that have already been assigned a different utility code.<\/span><\/p>\n

            \n
          1. Corporate Portability:<\/b><\/span><\/li>\n<\/ol>\n

            The NACH utility code is indispensable when corporate entities move their mandates from one bank to another. The mandates operated by a corporate can be seamlessly transferred to another bank by using the utility code as a reference. <\/span><\/p>\n

            How eNach eMandates Work – Registration & Fund Transfer\u00a0<\/strong><\/span> <\/b><\/h2>\n

            Nach mandates automate recurring payments by digitizing Nach registration and the documentation process required to track and monitor multiple payments. This enables banks, NBFCs, and other financial institutions (FIs) to create friction-free payment cycles and enrich customer experience. Nach registration cycles typically take 2 days with Aadhaar mandates and occur in real-time with Nach APIs. The eNACH Mandate procedure<\/span><\/a> consists of two major steps:<\/span><\/p>\n

            Registration<\/strong><\/h5>\n

            eMandates<\/strong> are first registered at the destination bank (i.e., the bank where the customer has an account). Mandate registration is completed in real-time using APIs or via Aadhaar\/NetBanking credentials.<\/p>\n

            The mandate information is then forwarded to the sponsor bank, NPCI, and the numerous destination banks. The response is communicated with the eNACH<\/strong> provider once the destination bank confirms the eMandate.<\/p>\n

            Throughout this process, the utility code is used to track the mandates associated with the corporate.<\/p>\n

            Next, the balances in various customer accounts is checked at the respective destination banks and a response of the success rate of mandate registration is created. This response is communicated\u00a0 to the eNACH service provider.<\/p>\n

            Fund Transfer<\/strong><\/h5>\n

            Following this response, the assigned money is debited from the destination bank and sent to NPCI, which is then delivered to the sponsor bank and subsequently to the eNACH service provider’s nodal bank account.<\/span><\/p>\n

            Finally, the designated sum is deposited to a corporate account the next day.<\/span><\/p>\n

            Four Major eNACH Workflows Using Utility Code<\/b><\/span><\/h2>\n

            The NACH utility code<\/strong> is utilized in a number of ways by eNACH mandate service providers<\/span><\/a> to help streamline recurring payments.\u00a0<\/span><\/p>\n

            Here are four crucial NACH workflows that use utility codes.<\/p>\n

              \n
            1. If the corporate client wants to choose their own utility code along with the NACH provider\u2019s sponsor bank, the client can complete the mandate registration process using Aadhaar or API. The rest of the NACH process is handled by the sponsor bank.<\/li>\n
            2. The client can choose the sponsor bank\u2019s utility code. The service provider handles only API mandate registration and debit sheet presentation in such cases. The rest of the process is handled by the chosen sponsor bank.<\/li>\n
            3. The corporate client can choose not to use the NACH service provider\u2019s utility code, and instead utilize the XML eSign facility. In this situation, the NACH service provider gives the corporate access to the Aadhaar XML file. This is used by the customer to eSign for mandate registration. The rest of the NACH process is taken forward by a different sponsor bank.<\/li>\n
            4. For NACH credit, the corporate entity simply sends the utility code and transaction details to NPCI, after which the credit transactions are processed further.<\/li>\n<\/ol>\n

              Note:<\/i><\/b> Presently, Melento (Formerly SignDesk) may only use its utility code to onboard NBFCs. Banks and other FIs will be onboarded using their utility codes. Alternately, non-NBFCs can use <\/span><\/i>real-time API mandate registration<\/span><\/i><\/a> for their recurring payments.\u00a0 <\/span><\/i><\/span><\/p>\n

              Link.It: Melento (Formerly SignDesk)\u2019s eMandate Solution<\/b><\/span><\/h2>\n