Conversion does not clear the old liability ledger
Section 18(3) of the Companies Act, 2013 provides that registration under that section does not affect debts, liabilities, obligations or contracts incurred or entered into before conversion. They may be enforced as if the registration under section 18 had not been done; conversion itself is not a release of the company’s earlier obligations. A finance team should therefore carry forward the supported obligations rather than treating the conversion certificate as a debt-release document. This article concerns conversion of a company’s class under section 18, not conversion into an LLP, amalgamation, liquidation or strike-off.
Read the applicable text: Companies Act, 2013: section 18(1)–(3).
Verify the actual corporate event
Section 18(1) addresses conversion into another class through alteration of memorandum and articles in accordance with the Chapter. Under subsection (2), once satisfied that the applicable registration provisions have been complied with, the Registrar closes the former registration, registers the altered documents and issues a certificate of incorporation in the same manner as at first registration. The certificate and effective documents establish the event being reviewed; they do not replace class-specific approvals or procedures. This guide does not prescribe a single conversion form or approval route for every class pair. First establish that section 18 is in fact the governing transaction.
Freeze and reconcile the pre-conversion population
Prepare balances and supporting agreements for borrowings, suppliers, customer advances, guarantees, leases and other obligations as relevant. Separate amounts already settled from amounts still outstanding. Link each balance to a counterparty, contract, original date, payment history and current status. The corporate conversion alone does not prove that an accounting derecognition test has been met. Equally, section 18 does not determine every measurement question, tax treatment or contingent-liability classification; those require their own applicable requirements.
Distinguish administrative updates from release or novation
Update the company’s identifying particulars and communicate the change through appropriate authorised processes where needed. A revised invoice header, vendor master or bank mandate should not be confused with a creditor releasing a debt. If a genuine settlement, waiver, contract modification or novation occurs, retain its separate authority and evidence. Examine actual contractual notice, consent, status-change and covenant provisions rather than asserting either that conversion always requires every creditor’s consent or that no contract can have any relevant condition.
Continue the movement ledger after conversion
For each obligation, show the supported opening amount, post-event additions, settlements, genuine modifications and closing amount. Reconcile payments and receipts that straddle the conversion date without losing the original references. Preserve deposit and advance histories so previously received amounts are not recorded again as new receipts. Where two systems are used across the event, migrate balances once and retain an old-to-new account mapping, with unexplained differences visible.
Conclude on continuity, with exceptions stated
The final review should identify what continued under section 18, what changed under separate valid arrangements and what remains unresolved. Do not declare that all obligations disappeared because the earlier registration was closed in the administrative process. Conversely, do not use a continuity paragraph to ignore an actual negotiated settlement. Keep the certificate, constitutional changes, approvals, account mapping and exception file together so a reviewer can distinguish the legal conversion from independent commercial transactions.
Six worked illustrations
All facts and amounts are fictional. Calculations illustrate the stated assumptions, not a predetermined legal outcome.
Illustrative example 1: Supplier balance survives the event
Supported pre-conversion supplier dues are ₹12,00,000. There is no separate release or settlement. Opening post-conversion dues remain ₹12,00,000, not zero. If ₹3,00,000 is then paid, closing dues are ₹9,00,000.
Illustrative example 2: Borrowing with a genuine repayment
A borrowing balance is ₹50,00,000 at conversion. A supported post-conversion repayment is ₹8,00,000 and there are no other movements. Closing principal is ₹42,00,000. The reduction comes from repayment, not the conversion itself.
Illustrative example 3: Customer advances must not be received twice
A customer had paid ₹6,00,000 before conversion. The migrated ledger carries it once, and ₹2,50,000 is validly adjusted against later performance/invoicing. The remaining advance control is ₹3,50,000. Recording ₹6,00,000 again as a new receipt would overstate the control balance.
Illustrative example 4: Separate a negotiated release
An outstanding ₹10,00,000 obligation is independently settled under a valid agreement by payment of ₹8,00,000 and release of ₹2,00,000. The liability closes to zero through those two supported movements. Retain the settlement evidence; section 18 alone did not generate the ₹2,00,000 release or decide its tax treatment.
Illustrative example 5: Migration errors are not legal extinguishment
The old system supports ₹18,00,000 total obligations, while the new system contains ₹16,50,000. The unexplained migration difference is ₹1,50,000. Investigate account mapping and supporting records rather than treating that amount as automatically extinguished at conversion.
Illustrative example 6: Contract exposure and unpaid amounts differ
A continuing contract has total committed consideration ₹30,00,000. Supported payments already made are ₹18,00,000, leaving ₹12,00,000 unperformed/unsettled exposure on the assumed facts. Track the remaining commitment separately from any amount currently due; conversion does not itself turn all ₹30,00,000 into a new debt.
Ten-step verification table
| Step | Action | Evidence |
|---|---|---|
| 1 | Identify the event | Section 18 company-class conversion and effective documents. |
| 2 | Verify the procedural record | Approvals, constitutional alterations and certificate. |
| 3 | Freeze opening obligations | Counterparty and contract-linked balances. |
| 4 | Separate due amounts and commitments | Payment terms and remaining performance. |
| 5 | Review contractual conditions | Actual notice, consent and covenant wording. |
| 6 | Distinguish independent transactions | Settlement, waiver, repayment or modification evidence. |
| 7 | Migrate balances once | Old-to-new account mapping. |
| 8 | Reconcile straddling cash flows | Payment/receipt dates and original references. |
| 9 | Investigate differences | Unmapped balances and unresolved legal/accounting issues. |
| 10 | Approve the continuity file | Opening, movements, closing and exception conclusions. |
Sixteen practitioner FAQs
1. Does section 18 conversion erase pre-existing debts?
No. Subsection (3) preserves the stated debts, liabilities, obligations and contracts.
2. Is this the same as conversion into an LLP?
No. That is a different transaction with its own framework.
3. Does this article cover strike-off?
No. Do not apply this continuity workflow as a substitute for that separate analysis.
4. Does closure of the former registration prove all debts ended?
No. Read the registration process with subsection (3)’s express continuity rule.
5. Is one form prescribed here for all conversions?
No. Establish the class-specific procedural requirements separately.
6. Should unpaid supplier balances be carried forward?
Retain supported balances unless a separately evidenced transaction or applicable requirement changes them.
7. Does the certificate itself prove accounting derecognition?
No. Legal continuity and accounting measurement/derecognition require their appropriate analysis.
8. Can a debt be reduced by a valid separate settlement?
Yes, if established on the facts; preserve the separate agreement and authority.
9. Does section 18 decide tax on a waiver?
No. Tax consequences need separate examination.
10. Must every contract always obtain fresh creditor consent?
Do not make that universal assertion. Examine statutory and actual contractual requirements.
11. Can contractual notices still matter?
Yes. Review relevant change-of-status, notice and covenant terms.
12. Should customer advances be recorded again as new receipts?
No. Migrate the existing balance once and retain its original receipt history.
13. What if systems disagree?
Investigate mapping and movements; a migration variance is not proof of legal release.
14. Are total future commitments identical to current payables?
Not necessarily. Track the different populations and performance conditions.
15. What documents support continuity?
The corporate-event record, original contracts, balance evidence and post-event movement ledger.
16. What should the conclusion distinguish?
Obligations that continued, independently supported changes and unresolved exceptions.