Receivables & Credit-Control Risk Audit in India: Customer Limits, Ageing, Collections, Write-Offs, Bad Debts & Recovery Controls 2026
A corporate-standard framework for preventing avoidable receivables loss through disciplined customer onboarding, credit approval, ageing, dispute resolution, collection and write-off governance.
Receivables risk is not merely an accounting issue. It begins when a customer is onboarded, credit is extended, contract terms are negotiated or sales teams override limits. By the time an invoice becomes severely overdue, the original control failure may be months old.
A structured audit therefore connects customer onboarding, contractual payment terms, credit limits, invoicing, proof of delivery or service, dispute management, collections, legal recovery, provisioning and write-off decisions.
1. Customer onboarding and credit risk
Review legal identity, ownership, billing entity, GST/tax information where relevant, credit history, references, financial capability, security, payment terms and concentration exposure. High-value or high-credit customers should have documented approval commensurate with risk.
Customer master changes should be controlled with the same discipline applied to vendor master changes.
2. Credit-limit governance
Test whether system limits match approved limits, expired exceptions remain active, sales teams can release blocked orders, and chronic overdue customers continue receiving credit without documented approval. Compare repeated overrides with the Management Override & Fraud-Control Review.
3. Ageing quality
Receivables ageing should distinguish current, 1–30, 31–60, 61–90, 91–180 and longer overdue buckets as appropriate to the business. Reconcile ageing to the general ledger and identify unapplied receipts, credit balances, old debit notes and invoices sitting in dispute without active ownership.
4. Documentation required for recovery
Each material receivable should be supported by contract or order, invoice, proof of supply or performance, customer acknowledgement where available, tax documentation, correspondence and any debit-note or dispute record. Weak documentation can convert a commercially valid claim into a difficult recovery.
5. Dispute and deduction management
Classify disputes by root cause: rate mismatch, quantity, service failure, tax, documentation, SLA penalty, return, claims, commercial concession or customer liquidity. Assign owners and closure deadlines. Repeated disputes of the same type indicate upstream contract, billing or operational weakness.
Where disputes arise from pricing or billing, cross-reference the Revenue Leakage Audit in India.
6. Collection discipline
Review reminder cadence, account-owner responsibility, escalation thresholds, stop-supply rules, senior-management intervention and legal referral. Collection promises should be documented rather than maintained only in individual email inboxes or messaging threads.
7. Security, deposits and set-off rights
Where the business uses security deposits, guarantees, retention, post-dated instruments, credit insurance or contractual set-off, maintain a register of validity, amount, expiry and invocation conditions. Security that has expired or cannot be located should not be assumed available.
8. Write-offs and provisioning
Bad-debt write-offs should record collection history, dispute status, legal assessment, authority and whether further recovery remains possible. Review write-offs concentrated around one customer, salesperson, branch or period, particularly where new sales continue after write-off.
9. Receivables analytics
- credit-limit overrides followed by overdue exposure;
- customers above approved limit;
- old invoices without active collection note;
- large unapplied receipts;
- repeated deductions by one customer;
- write-offs while new sales continue;
- customer concentration by salesperson or branch;
- negative balances or unusual credit notes;
- high dispute rates by product or service; and
- receivables transferred between customer codes.
10. Risk matrix
| Risk | Indicator | Action |
|---|---|---|
| Credit | Limit exceeded without approval | Block/review exception authority |
| Documentation | Invoice lacks proof of performance | Complete evidence and fix upstream process |
| Ageing | Long overdue with no escalation | Recovery owner and legal/commercial route |
| Write-off | Repeated unsupported write-off | Independent review and authority control |
11. Evidence required
Customer master, contracts, credit approvals, invoices, ageing, receipts, debit/credit notes, proof of delivery/service, collection notes, dispute registers, legal notices, security records, provisioning and write-off approvals form the core review set.
12. CFO and board deliverables
- customer credit-risk heat map;
- overdue ageing by root cause;
- top recoverability exceptions;
- credit-limit override report;
- dispute and deduction tracker;
- write-off governance review;
- security/guarantee register;
- recovery prioritisation matrix; and
- 30/60/90-day collection and control plan.
13. 30/60/90-day remediation
0–30 days: freeze material unsupported limit overrides, assign owners to old receivables, reconcile unapplied cash and preserve key recovery documents.
31–60 days: segment customers by risk, resolve recurring disputes, refresh credit approvals and formalise legal referral thresholds.
61–90 days: introduce recurring ageing dashboards, customer concentration monitoring, collection KPIs and independent write-off review.
14. Frequently asked questions
Should every overdue account go to legal recovery?
No. Route depends on evidence, value, dispute, customer viability, limitation, relationship and commercial strategy.
Can sales teams approve their own credit exceptions?
Material credit exceptions should have independent finance or authorised management oversight.
What is the biggest control failure?
Allowing new exposure to grow while old debt is unresolved without documented exception.
Is a write-off the same as abandoning recovery?
Not necessarily. Accounting treatment and legal recovery rights should be considered separately.
Authoritative references
Author: Adv. Govind Bali, Fastrack Legal Solutions LLP.