Billing AMCs on Cards: Recurring Mandates for Service Centres

Published: 24 October 2026

Category: how-to-guides | cardbuzz

Tags: AMC billing, recurring mandates, e-mandate, UPI Autopay, service centre

Annual maintenance contracts are the steadiest revenue a service centre can own: a housing society's fifty ACs, an office's water coolers and pantry appliances, a PG's room coolers and geysers — contracted for the year, serviced on schedule, billed on terms. The operational headache has always been collection: cheques that arrive late, transfers that need chasing, cash that needs a visit. Recurring card mandates solve the collection problem mechanically — the customer's card is debited automatically on the billing date — but they come with a regulatory framework, failure modes and customer-communication duties that a service centre must set up correctly from day one. This guide covers the mechanics of putting AMC billing on recurring mandates.

Why AMCs and Mandates Fit Each Other

An AMC is a fixed-amount, fixed-schedule obligation — the ideal shape for a recurring mandate. Unlike per-visit billing, the amount is known in advance (the annual contract value, possibly split quarterly or monthly), the dates are known (contract start and billing milestones), and the customer relationship is long-term. This predictability is exactly what mandate systems are designed for, and it is why mandate-based AMC billing outperforms every manual collection method on two metrics: on-time collection rate and administrative cost per invoice.

The economics are straightforward. Manual collection of a quarterly AMC instalment typically costs a phone call, a follow-up, sometimes a visit, and an average delay measured in weeks. A mandate debit costs the MDR on the transaction (typically around 1-2% for credit cards) plus near-zero staff time, and lands on the scheduled date. For a centre running dozens of AMCs, the staff-hours recovered alone justify the MDR many times over.

The Mandate Framework: What the Rules Require

Recurring payments on cards in India operate under the RBI's e-mandate framework, and the service centre — as the merchant — needs to understand its obligations, not just its payment gateway's marketing.

Registration: the customer registers a mandate (a standing instruction) on their card for the AMC billing, specifying the maximum amount per debit and the frequency. Registration requires additional factor authentication — the customer approves it with an OTP or equivalent — and this is a one-time step.

Pre-debit notification: the framework requires the customer to be notified at least 24 hours before each debit, with the amount and date. In practice the payment gateway or the issuing bank sends this; the centre's duty is to ensure its gateway is configured to trigger it and to keep its own billing schedule aligned so the notification matches reality.

Per-debit limits: mandates carry a maximum amount per transaction as registered. If an AMC instalment ever exceeds the registered maximum — say, a quarterly bill inflated by extra spare-parts charges — the debit will fail. The discipline this imposes is healthy: keep the mandate strictly for the contracted AMC amount, and bill variable extras (parts, out-of-scope visits) as separate one-time transactions with the customer's explicit approval.

Cancellation rights: the customer can cancel the mandate at any time through their bank, and the centre must honour that by reverting to manual billing without penalty or pressure. Any AMC agreement should state the billing consequence of mandate cancellation plainly.

Setting Up Mandate Billing: The Practical Sequence

For a service centre moving its AMC book onto mandates, the setup sequence runs like this.

First, choose the rail. Card-based e-mandates (credit or debit cards) and UPI Autopay are the two rails. UPI Autopay debits the customer's bank account directly with zero MDR to the merchant; card mandates carry the card MDR but work for customers who prefer card billing and let corporate customers route AMC spend through company cards. Many centres offer both and let the customer choose — the collection automation is identical, only the cost differs.

Second, integrate through the payment gateway or aggregator the centre already uses for payment links. Mandate management — registration links, pre-debit notifications, retry logic, cancellation handling — is gateway functionality; building it in-house is not a sensible use of a service business's time. Evaluate gateways on mandate-specific features: how registration links are delivered (SMS, WhatsApp, email), whether retries on failure are automatic and configurable, and what dashboard visibility exists per customer.

Third, rewrite the AMC agreement template. The agreement needs four mandate clauses: the billing schedule and amounts under the mandate, the customer's right to cancel the mandate and the fallback billing mode, the treatment of variable extras outside the mandate, and the notice period for amount changes. Get this signed (physical or digital) before the first registration — a mandate without a matching signed agreement is a dispute waiting for a failed debit.

Fourth, run registration as part of onboarding, not as an afterthought. The moment the AMC is signed is the moment of maximum customer cooperation; sending the mandate registration link that same day, with a two-line explanation of what it does, gets completion rates that follow-up calls never achieve.

The Failure Modes and How to Handle Them

Mandate debits fail, and each failure mode has a standard response.

Insufficient funds or expired card: the most common failures. The gateway should retry automatically after a configurable interval — one retry after two to three days catches most temporary shortfalls. After two failed attempts, the process must become human: a polite call or message, not a third silent retry that trains the customer to ignore the notifications.

Card replaced or reissued: when a customer gets a new card (expiry, loss, upgrade), the old mandate typically breaks. Some issuers and networks support automatic mandate migration to the new card; many do not. The centre's system needs a flag for "mandate broken — re-register", triggered by the failure code, with a fresh registration link sent proactively. This is the single largest source of silent AMC revenue leakage in mandate systems — the debit fails, nobody notices for a quarter, and the service visits continue unbilled.

Pre-debit notification ignored: customers sometimes miss or disregard the 24-hour notice and then query the debit. The defence is the signed agreement plus the notification record; the prevention is keeping the debit amount exactly as agreed so there is never a surprise to query.

Customer disputes the debit: treat it as a service issue first and a payments issue second. Pause the next scheduled debit while investigating, resolve the underlying complaint (a missed service visit is the usual cause), and only then resume. A mandate is a convenience, not a collections weapon — using it aggressively against a disputing customer converts a service complaint into a bank complaint.

Dunning Without Damaging the Relationship

"Dunning" — the process of recovering failed recurring payments — needs a lighter touch in a service business than in a subscription software company, because the customer is a neighbour, a society committee or a local office, and the technician will be at their premises next month regardless.

The effective pattern is graduated and personal: an automated message on the day of failure stating the amount and a payment link; a personal call after the first retry fails, framed as a service check ("the quarterly debit didn't go through — is the card still the same one?"); and only after two human touchpoints, a written notice linking continued scheduled servicing to the cleared instalment. At no point should servicing already performed be held hostage — the leverage of an AMC is future service, and threatening past work destroys the trust the contract is built on.

Reconciliation and Accounting

Mandate billing changes the bookkeeping rhythm. Instead of reconciling sporadic receipts, the centre reconciles a predictable debit schedule: for each billing date, the expected debits per the AMC register, the successful debits per the gateway report, and the exceptions. This is a cleaner control than cash-book chasing, and it produces a genuinely useful management report — the "AMC collection health" view showing on-time rate, failure rate by cause, and ageing of failed debits.

For GST, each debit needs its invoice: raise the tax invoice for the instalment on or before the debit date, with the mandate reference noted. The invoice, not the debit, is the taxable event; the debit is the collection. Keeping the two linked per customer per period makes both GST filing and customer queries trivial.

The Rollout Plan

A centre with an existing AMC book should not flip every contract to mandates at once. Pilot with five to ten cooperative customers — ideally the societies and offices with the most professional billing contacts — and run one full billing cycle. Measure the on-time collection rate, the failure rate by cause, and the staff time per contract versus manual collection. Fix the agreement wording, the notification copy and the retry settings based on what the pilot teaches. Then roll out at each contract renewal, when the customer is already signing paperwork and the mandate registration is one more initial on the page. Within two renewal cycles the book is converted, the collection calls stop, and the AMC revenue the centre thought it had becomes the AMC revenue it actually collects.