Why are payments grouped through NACH?
An organisation may need to pay many recipients or collect recurring payments from many customers. NACH provides an electronic arrangement for those activities, rather than treating each interaction as a customer manually making a separate bill payment at a counter.
RBI’s Payment System Report, section 2.25 explains the credit and debit sides. Its examples include salaries, pensions and dividends on the credit side, and utility bills, loan instalments and insurance premiums on the debit side.
These are examples of system uses. They do not mean every salary, pension or bill payment in India necessarily uses NACH.
NACH Credit and NACH Debit
| Type | Direction from the customer’s perspective |
|---|---|
| NACH Credit | Money is credited through an organisation’s disbursement arrangement |
| NACH Debit | Money is collected from an account through the applicable authorised arrangement |
The distinction helps a customer interpret a statement entry. A NACH-related credit and a recurring collection are not the same event, even if both contain the same system name.
Identify the organisation, amount and date associated with the entry. The acronym alone does not establish which bill, instalment or benefit the customer is looking at.
What is the role of a mandate?
A mandate records an authorisation within the applicable collection process. It should be understood separately from the collection instruction and from the resulting account debit.
For example, a customer may have authorised a recurring collection, but a particular presentation can still need checking. Conversely, cancelling a future arrangement and investigating an earlier debit are different tasks.
Use the bank’s and collecting organisation’s current instructions for mandate creation, changes, cancellation and disputes. A retailer should not promise that paying a bill once through a counter automatically changes an existing recurring mandate.
The Canara Bank NACH FAQ is an example of bank guidance for the service. Details from one bank’s process should not be presented as universal app instructions.
How does NACH differ from BBPS?
NACH describes a payment and collection system. BBPS, now associated with the Bharat Connect ecosystem, provides a bill-payment arrangement involving billers, operating units and customer interfaces.
The fact that both can relate to an electricity bill does not make them interchangeable. One customer might pay a bill through a counter; another may have a recurring bank collection arrangement. The payment record and complaint route need to match the actual transaction.
Our BBPS explanation covers that ecosystem. Avoid replacing its bill-payment workflow with a general NACH explanation.
An example involving a recurring bill
Illustrative example: A customer normally has a bill collected automatically but visits a retailer because they cannot see the expected debit. They ask the retailer to pay the bill immediately.
The retailer first asks them to check the current bill and collection status with the responsible provider. If an automatic instruction is still pending, a separate manual payment could create an additional payment rather than repair the original process.
The retailer does not infer that the mandate has ended simply because the customer cannot see a debit. The bank and biller’s records establish what happened and what action is appropriate.
Questions about NACH
Does a registered mandate prove every debit succeeded?
No. Authorisation and transaction outcome are separate. Inspect the specific payment record.
Is NACH only used for loan instalments?
No. RBI describes both disbursement and collection uses, including salaries, pensions, bills and premiums.
Can a retailer cancel a customer’s mandate?
Only use a process for which the retailer is actually authorised. Otherwise, direct the customer to the bank or collecting organisation’s official cancellation route; do not promise an account change outside the shop’s control.