NACH
Important Definitions
| Topic | Definition |
|---|---|
| NACH | National Automated Clearing House (NACH) is a centralised system, which can be used for making bulk transactions towards distribution of subsidies, dividends, interest, salary, pension etc. and also for bulk transactions towards collection of payments pertaining to telephone, electricity, water, loans, investments in mutual funds, insurance premium etc. Click here for more info |
| Mandate | A document issued by a bank to another bank requesting that the second bank allow a customer to open account, conduct transactions and generally receive privileges as if he/she were an existing account holder. Click here for more info |
NACH is a new feature where the User should be facilitated to create mandate, upload mandate request and mandate response.
NACH MANDATE Actions and Status Description
| Action | Scenario | Status | Status Code | Description |
|---|---|---|---|---|
| CREATE | The User want to create a new mandate for debitting the EMI amount from his customers bank account. | Requested | 100 | Once the mandate is created/drafted freshly for new mandate request, then the status of the mandate changes to CREATE_REQUESTED |
| In Process | 101 | When the new mandate create request file is generated the status of the mandate chnages to CREATE_INPROCESS | ||
| Rejected | 102 | When the NPCI rejects the mandate i.e., the response file will have the status as rejected then the status of the mandate will be updated as CREATE_REJECTED | ||
| Active | 400 | Once the NPCI Approve mandate the response file will be sent with status as Active. The same get updated in the Finflux application once response file is uploaded | ||
| UPDATE/MODIFY | The User have already create a mandate, for some reason the mandate got rejected or the customers bank account number got chnages etc. In such cases the user have to request for change request. | Requested | 200 | When the mandate is drafted for change request the status of the mandate changes to UPDATE_REQUESTED |
| In Process | 201 | Once the request file is processed for update and downloaded from Finflux the status changes to UPDATE_INPROCESS | ||
| Rejected | 202 | If the mandate get rejected by NPCI i.e., the response with status as rejected will change the status of the mandate in Finflux as UPDATE_REQUESTED | ||
| Active | 400 | Once the NPCI Approve mandate for update request, the response file will be sent with status as Active. The same get updated in the Finflux application once response file is uploaded | ||
| CANCEL | Now the user have collected all the repayments or due to some reason customer don't want to continue with the NACH process like the customer might come and preclose the loan using any other source like cash, check etc. In such cases the user don't want to collect any more repayments hence he will request for cancel to make the mandate as inactive. | Requested | 300 | When the mandate is drafted for cancel request, the status of the mandate changes to CANCEL_REQUESTED |
| In Process | 301 | Once the mandate cancel request file is generated from Finflux, the status of the mandate changes to CANCEL_INPROCESS | ||
| Rejected | 302 | If the NPCI rejects the mandate cancel request status in the response file will be updated as Rejected. When the same response file is uploaded to Finflux the status of the mandate changes to CANCEL_REJECTED | ||
| Inactive | 500 | If the NPCI approves the mandate cancel request, then the status will be updated as "Inactive" | ||
| Invalid | Any other codes | If any other status code is tried with mandate, then the status will be updated as Invalid. |
Step 1: Configuration for NACH processing
Navigate to Admin>>System>>External Service will land on the page as shown in the fig 1.1. Clicking on this link will land on the configuration screen as shown in the fig 1.2
fig 1.1: Entry point for NACH external service configuration
The below screen (fig 1.2) shows the configuration screen for NACH. Here you should click on the Edit button to set configurations.
fig 1.2: View external service configuration for NACH
The below screen (fig 1.3) is the edit screen for NACH external service configuration. Field description is as listed below
| # | Field | Description |
|---|---|---|
| 1. | CORPORATE_UTILITY_CODE | This field describes the corporate utility code which will be defined by the User (client specific) |
| 2. | CORPORATE_UTILITY_NAME | This field describes the corporate utility name which will be defined by the User (client specific) |
| 3. | PROCESSOR_QUALIFIER | This field describes the processor qualifier which will be defined by the Conflux (client specific) |
| 4. | SPONSOR_BANK | This field describes the sponsor bank which will be defined by the User (client specific) |
| 5. | SPONSOR_BANK_CODE | This field describes the sponsor bank code which will be defined by the User (client specific) |
Fill the NACH configuration fields with valid data and click on submit.
fig 1.3: Edit external service configuration for NACH
Step 2: Upload mandate document and create mandate
To upload documents go to client screen>>create new loan>>Approve. Once loan is approved click on "Loan Documents" tab where the mandate document should be uploaded. For uploading the doc click on upload button as shown in fig 2.1 and this will land on the document upload screen fig 2.2 where you need to provide name and description to the mandate doc and click on choose file button to upload the doc and click on submit.
fig 2.1: Loan Document
Upload Document Details
| # | Field | Description |
|---|---|---|
| 1. | Name | This is the field to define the name for mandate |
| 2. | Description | Here you can provide the description for the mandate you are uploading. |
| 3. | select file | You should choose the mandate file and should upload here |
fig 2.2: Upload Loan Document
Once the loan is approved and mandate doc is uploaded, click on mandate tab. This will take you to the below screen as shown in the fig 2.3. click on create button to create mandate which will land on create mandate screen as shown in fig 2.4.
fig 2.3: Mandate
To create mandate select the scanned copy that is attached in loan document. The user can view the document on the left side of the page and it helps the user to fill the mandate details in the field. Fill all the required details and click on submit which will create mandate.
| # | Field | Description |
|---|---|---|
| 1. | Scanned Document | This is a drop down filed where all the document uploaded will be populated. |
| 2. | Requested Date | Provide the requested date as per the attached document. |
| 3. | Bank Account Holder's Name | Provide the bank account holder's name as per the attached document. |
| 4. | Bank Name | Provide the bank name as per the attached document. |
| 5. | Branch Name | Provide the branch name of bank as per the attached document. |
| 6. | Bank Account Number | Provide the bank account number as per the attached document. |
| 7. | MICR | Provide the MICR as per the attached document. |
| 8. | IFSC | Provide the IFSC as per the attached document. |
| 9. | Account Type | Select the account type here. |
| 10. | From Date | Here you need to select the start date for mandate |
| 11. | To Date | Here you need to select the expiry date for mandate |
| 12. | Until Cancelled | The mandate will be valid till the mandate is canceled if the check box is tick marked. |
| 13. | Debit Type | Select debit type here |
| 14. | Amount | provide the loan amount |
| 15. | Debit Frequency | Select the debit frequency here |
fig2.4: Create mandate-1
fig 2.5: Create mandate-2
Once the mandate is created, the mandate status will changes to CREATE_REQUESTED as shown in the fig 2.6. Here the user can edit the mandate if required.
fig 2.6: Mandate after creation
Step 3: Create mandate request
Navigating to Admin>>Organization>>ACH>>Create ACH Mandate Request will land on the page as shown in the fig 3.1. Here the user have to select the office requested for and should tick child offices? and mandate scans? check and should click on submit. This will result in the list of requested mandates as shown in the fig 3.2
fig 3.1: Search mandate request
Initially the newly requested mandates will be in the "REQUESTED" state as shown in fig 3.2 and clicking on refresh status the status changes to processed or failed as shown in fig 3.3.
| # | Field | Description |
|---|---|---|
| 1. | Request Type | This field has four options
If the request type is selected, based on the request type the ACH files will be filtered and displayed on the screen else all the details irrespective of requested type will be displayed. |
| 2. | Request Office | Here the user can change the office, that he/she requesting for. Hence the ACH file under the selected office will be displayed on the screen. |
fig 3.2: Mandate requested list
fig 3.3: Processed mandate
The user can download the mandate by clicking on the mandate file which will result in pop up for authentication where the user need to provide valid user name and password for downloading the file as shown in the fig 3.4.
fig 3.4: Download mandate file
Once mandate is requested the status of the mandate will change to CREATE_INPROCESS as shown in the fig 3.5.
fig 3.5:Mandate status after requesting for mandate
Step 4: Upload mandate response
Once the mandate request is done, the user receives mandate response from NACH which should be uploaded to the system as shown in fig 4.1. Here the user should upload the response file received from NACH and click on submit button to upload the file.
NOTE: The request file which was downloaded (fig 3.4) should be sent to ACH/NACH via any media and should receive response via any media. It is not automated in the system.
fig 4.1: Upload response from NACH
Once the file gets uploaded the view screen will be as shown in the fig 4.2.
| # | Field | Description |
|---|---|---|
| 1. | Request Type | This field has four options
If the request type is selected, based on the request type the ACH files will be filtered and displayed on the screen else all the details irrespective of requested type will be displayed. |
| 2. | Request Office | Here the user can change the office, he/she requesting for. Hence the ACH file under the selected office will be displayed on the screen. |
fig 4.2: View uploaded response
Once the file get uploaded successfully the mandate status will changes to ACTIVE as shown in the fig 4.3
fig 4.3: Updated mandate status in loan account page
Step 5: Create mandate transaction request
To do repayment via ACH, the user have to create mandate request by providing the following criteria and should click on submit (fig 5.1) which will show the view screen of downloaded/uploaded ACH file as shown in the fig 5.2.
| # | Field | Description |
|---|---|---|
| 1. | Request Office | Select the office for which the ACH transaction need to be requested. |
| 2. | Child office? | Tick mark this check box if ACH transaction need to requested for the child office also. |
| 3. | Payment Due Start Date | Pick the date from when you need to create transaction request |
| 4. | Payment Due End Date | Pick the date till where you need to create transaction request |
Precondition: The Loan should be disbursed before performing this action.
fig 5.1: Create ACH Transaction request file
The user should download the request file and should be sent to the NACH.
| # | Field | Description |
|---|---|---|
| 1. | Request Type | This field has four options
If the request type is selected, based on the request type the ACH files will be filtered and displayed on the screen else all the details irrespective of requested type will be displayed. |
| 2. | Request Office | Here the user can change the office, he/she requesting for. Hence the ACH file under the selected office will be displayed on the screen. |
fig 5.2: view Downloaded/uploaded ACH file history
Step 6: Upload mandate transaction response
Once the NACH sends response to the user, he/she should upload the file and should click on submit.
fig 6.1: upload mandate transaction response
Once the user uploads the response file, View Download/Upload ACH file history screen will be shown (fig 6.2) where the user can see all the required details of downloaded and uploaded files.
| # | Field | Description |
|---|---|---|
| 1. | Request Type | This field has four options
If the request type is selected, based on the request type the ACH files will be filtered and displayed on the screen else all the details irrespective of requested type will be displayed. |
| 2. | Request Office | Here the user can change the office, he/she requesting for. Hence the ACH file under the selected office will be displayed on the screen. |
fig 6.2: View uploaded mandate transaction response
Step 7: View mandate request and response
Here the user is facilitated to search the request and response mandate file which are uploaded/downloaded as shown in fig 5.1.
| # | Field | Description |
|---|---|---|
| 1. | Request Type | This field has four options
If the request type is selected, based on the request type the ACH files will be filtered and displayed on the screen else all the details irrespective of requested type will be displayed. |
| 2. | Request Office | Here the user can change the office, he/she requesting for. Hence the ACH file under the selected office will be displayed on the screen. |
fig7.1: View mandate request and response screen
Step 8: View mandate transaction request and response Summary
Here the user should provide the following criteria for filtering the mandate transaction request and response.
| # | Field | Description |
|---|---|---|
| 1. | Request Type | The request type have two options
|
| 2. | Request office | Select the office for which you need summary for. |
| 3. | Child office? | Select the child office to fetch the summary of the child office additional to main office. |
| 4. | Request Start Date | Filter the summary by selecting requested start date from when you need to fetch the summary |
| 5. | Request End Date | Filter the summary by selecting requested end date till where you need to fetch the summary |
fig 8.1: Search ACH mandate/transaction summary
The results for the submitted searching criteria will be as shown in the fig 6.2
fig 8.2: View ACH mandate/transaction summary