The supplier of goods or services, the employee with unpaid wages, the government chasing statutory dues — these are the operational creditors of the Insolvency and Bankruptcy Code, 2016. Unlike a bank, an operational creditor cannot walk straight into the National Company Law Tribunal. The Code compels it to pause, to serve a statutory demand notice, and to wait ten days to see whether the corporate debtor pays up or, crucially, raises a dispute. Sections 8 and 9 together build this two-step gateway, and the Supreme Court has policed it strictly: the operational creditor's remedy is summary, swift and unforgiving of debtors who default — but it slams shut the moment a genuine, pre-existing dispute surfaces. This article maps the demand notice, the application, the documents, the threshold, the limitation clock and the decisive case law that every judiciary and CLAT-PG aspirant must command.

The Two-Step Scheme: Why Operational Creditors Are Treated Differently

The Code draws a sharp line between financial creditors and operational creditors, and the procedure for triggering a corporate insolvency resolution process (CIRP) reflects that distinction. A financial creditor under Section 7 may apply directly to the Adjudicating Authority on proof of default. An operational creditor cannot. Section 8 first obliges it to serve a demand notice and to wait; only if the corporate debtor fails to pay and fails to raise a dispute may the operational creditor proceed under Section 9. This is a deliberate filter. As the Bankruptcy Law Reforms Committee envisaged, operational debts — trade dues, employee wages, statutory liabilities — are frequently the subject of bona fide commercial disagreement, and the Code did not intend the insolvency machinery to become a debt-collection cudgel for contested claims.

The foundational architecture was explained by the Supreme Court in Innoventive Industries Ltd. v. ICICI Bank, (2018) 1 SCC 407, the first authoritative interpretation of the Code. While that case concerned a financial creditor under Section 7, the Court laid down the conceptual scaffolding for all CIRP triggers: a “default” means non-payment of a debt that has become due and payable in law and in fact, and once default is established the Adjudicating Authority's role is narrow. The operational creditor's route, however, carries the additional and decisive hurdle of the “existence of a dispute,” which has no counterpart in the financial creditor's path. For the contrasting mechanism, see our note on the initiation of CIRP by a financial creditor.

Who Is an Operational Creditor? Defining the Debt

Eligibility to invoke Sections 8 and 9 turns on two linked definitions. Section 5(20) defines an operational creditor as a person to whom an operational debt is owed, including any person to whom the debt has been legally assigned or transferred. Section 5(21) defines operational debt as a claim in respect of the provision of goods or services, including employment, or a debt in respect of the payment of dues arising under any law for the time being in force and payable to the Central Government, a State Government or a local authority.

The contours of these definitions were significantly widened by the Supreme Court in Consolidated Construction Consortium Ltd. v. Hitro Energy Solutions (P) Ltd., (2022) 7 SCC 164. The Court held that the phrase “in respect of” the provision of goods or services is expansive, and that operational creditors are not confined to those who supply goods or services to the corporate debtor; they include those who receive them. Consequently, a claim for refund of an advance payment made to a corporate debtor for the supply of goods or services is itself an operational debt. This reading rescued purchasers and customers who had paid in advance from being excluded from the operational-creditor category. For the full taxonomy of debts and creditors, consult the sibling note on key definitions under the Code.

The Court has also confirmed that statutory dues fall squarely within Section 5(21). Tax authorities and similar government bodies collecting dues under a statute qualify as operational creditors, a position later reinforced in Rainbow Papers and allied rulings on government claims. The breadth of “operational debt” therefore reaches trade creditors, employees, lessors of movable equipment in service contracts, and statutory authorities alike.

Section 8: The Mandatory Demand Notice

Section 8(1) is the indispensable first step. On the occurrence of a default, the operational creditor “may” deliver a demand notice of the unpaid operational debt, or a copy of an invoice demanding payment of the amount, to the corporate debtor. Although the verb is “may,” the courts treat service of a valid Section 8 notice as a condition precedent to a Section 9 application: an operational creditor that skips it has no cause of action before the Tribunal. The notice form is prescribed under the Insolvency and Bankruptcy (Application to Adjudicating Authority) Rules, 2016 — a demand notice in Form 3, or, where an invoice is the basis, an invoice attached to a notice in Form 4, served under Rule 5.

Section 8(2) then sets the clock running. Within ten days of receipt of the demand notice or invoice, the corporate debtor must do one of two things: (a) bring to the operational creditor's notice the existence of a dispute, if any, including the record of the pendency of a suit or arbitration proceeding filed before the receipt of the notice; or (b) pay the unpaid operational debt by sending proof of payment. The ten-day window is the corporate debtor's one opportunity to halt the insolvency machinery by demonstrating either payment or a genuine dispute. Default in both respects opens the gate to Section 9.

A recurring procedural question is who may issue the demand notice. The Supreme Court settled it in Macquarie Bank Ltd. v. Shilpi Cable Technologies Ltd., (2018) 2 SCC 674, holding that a lawyer or authorised agent acting under the instructions of the operational creditor can validly issue the Section 8 notice. Reading Sections 8 and 9 conjointly with Section 30 of the Advocates Act, 1961, the Court refused to confine the power to the creditor personally, provided the agent holds an authority and discloses a position in relation to the creditor. The notice cannot, however, be issued by a stranger with no authority.

The Heart of the Matter: “Existence of a Dispute”

No proposition is more frequently tested than the meaning of “dispute” in Section 8(2)(a). The governing authority is Mobilox Innovations (P) Ltd. v. Kirusa Software (P) Ltd., (2018) 1 SCC 353, the Supreme Court's definitive interpretation of the operational-creditor route. Section 5(6) defines “dispute” to include a dispute relating to (i) the existence of the amount of debt, (ii) the quality of goods or service, or (iii) the breach of a representation or warranty. The word “includes” signalled to the Court that the definition is illustrative, not exhaustive.

The Court laid down the test that the Adjudicating Authority must apply at the threshold: all it has to examine is whether there is a plausible contention requiring further investigation, such that the dispute is not a patently feeble legal argument or an assertion of fact unsupported by evidence. So long as a dispute truly exists in fact and is not spurious, hypothetical or illusory, the Authority must reject the Section 9 application. The Tribunal is emphatically not to decide the merits of the dispute or assess its likelihood of success; it is enough that a real dispute exists.

Mobilox also resolved a textual puzzle. Section 8(2)(a) requires the corporate debtor to bring to notice the existence of a dispute “and” the record of pendency of a suit or arbitration. Read literally, this would demand a pre-existing suit or arbitration in every case. The Court held that “and” must be read as “or” — a dispute may be evidenced either by a pending proceeding or by other material showing that a real dispute had arisen before the demand notice. This purposive reading prevents the bar from being defeated merely because litigation had not yet been formally commenced.

The Dispute Must Be Pre-Existing

A critical refinement is the timing of the dispute. The dispute that defeats a Section 9 application must pre-date the Section 8 demand notice; a debtor cannot manufacture a dispute for the first time in its reply to the notice. Mobilox itself anchored the inquiry to disputes raised “before the receipt” of the demand notice, and subsequent benches have hardened this into a settled rule: the dispute must have been in existence prior to the service of the Section 8 notice, even if it was reduced to a reply only after the notice.

The point was sharply illustrated in K. Kishan v. Vijay Nirman Co. (P) Ltd., (2018) 17 SCC 662. There, an arbitral award had been passed in favour of the operational creditor, but the corporate debtor had challenged it under Section 34 of the Arbitration and Conciliation Act, 1996. The Supreme Court held that the pendency of a Section 34 challenge to an arbitral award constitutes a pre-existing dispute that bars a Section 9 application. An operational creditor cannot use the IBC as a substitute for execution of a contested award; until the arbitral proceedings attain finality, the underlying claim remains genuinely disputed. The decision is a powerful guard against the abuse of insolvency proceedings as a recovery mechanism for unsettled claims.

The Supreme Court applied the same discipline in Kay Bouvet Engineering Ltd. v. Overseas Infrastructure Alliance (India) (P) Ltd., (2021) SCC OnLine SC 581, where it upheld the rejection of a Section 9 petition on finding a plausible, pre-existing dispute on the record. The consistent theme across Mobilox, K. Kishan and Kay Bouvet is that the Adjudicating Authority's task is to satisfy itself that a real dispute existed before the notice — nothing more, nothing less.

Section 9: Filing the Application

If, after the expiry of ten days from delivery of the demand notice or invoice, the operational creditor does not receive payment or a notice of dispute under Section 8(2), it may file an application before the Adjudicating Authority under Section 9(1). The application is made in Form 5 under Rule 6 of the 2016 Adjudicating Authority Rules, accompanied by the prescribed fee. Where the operational creditor has received a reply that fails to disclose a genuine dispute, it may still proceed; the existence of a dispute is then tested by the Tribunal under the Mobilox standard.

Section 9(4) permits the operational creditor to propose a resolution professional to act as the interim resolution professional, a notable difference from the financial creditor's route, where naming an IRP is optional but commonly exercised. Where no resolution professional is proposed, the Adjudicating Authority makes a reference to the Insolvency and Bankruptcy Board of India for a recommendation. The contrast with the corporate debtor's own filing is covered in our note on initiation of CIRP by the corporate debtor.

Documents to Accompany the Application: Section 9(3)

Section 9(3) prescribes the documentary record the operational creditor must furnish: (a) a copy of the invoice demanding payment or the demand notice delivered by the operational creditor to the corporate debtor; (b) an affidavit to the effect that there is no notice given by the corporate debtor relating to a dispute of the unpaid operational debt; (c) a copy of the certificate from the financial institution maintaining accounts of the operational creditor confirming that there is no payment of the unpaid operational debt by the corporate debtor, if available; and (d) such other information as may be specified.

The mandatory character of clause (c) — the financial-institution certificate — was the central issue in Macquarie Bank Ltd. v. Shilpi Cable Technologies Ltd., (2018) 2 SCC 674. The Supreme Court held that Section 9(3)(c) is directory and not mandatory. The words “if available” and “as may be specified” showed that the certificate is only one mode of proving non-payment; a foreign operational creditor who banks abroad, or any creditor unable to obtain such a certificate, may establish default through other documents. A creative, purposive interpretation was preferred over a literal one that would have produced unworkable and discriminatory results. The ruling is frequently paired with the holding on lawyer-issued notices, both flowing from the same judgment.

Admission or Rejection: The Section 9(5) Decision

Section 9(5) requires the Adjudicating Authority, within fourteen days of receipt of the application, either to admit or to reject it. The Authority shall admit the application if it is satisfied that: (i) the application is complete; (ii) there is no payment of the unpaid operational debt; (iii) the invoice or notice for payment was delivered; (iv) no notice of dispute has been received by the operational creditor, or there is no record of dispute in an information utility; and (v) no disciplinary proceeding is pending against the proposed resolution professional.

Conversely, the Authority shall reject the application if: (i) the application is incomplete; (ii) the unpaid operational debt has been paid; (iii) the creditor has not delivered the invoice or notice; (iv) a notice of dispute has been received or there is a record of dispute in an information utility; or (v) a disciplinary proceeding is pending against the proposed professional. Before rejecting an incomplete application, the Authority must give the applicant a notice to rectify the defect within seven days of receipt of such notice — a proviso that prevents purely technical dismissals.

The fourteen-day timeline is directory rather than mandatory; like the corresponding period under Section 7, it is a guideline whose breach does not invalidate a subsequent admission. The interplay of these timelines with the overall outer limit is examined in our note on the time limit for completing CIRP.

The Minimum Threshold of Default: Section 4

Section 4 fixes the financial gateway. The Code applies to a default in relation to a corporate debtor where the minimum amount of the default is one lakh rupees, with a proviso empowering the Central Government to notify a higher minimum not exceeding one crore rupees. By Notification S.O. 1205(E) dated 24 March 2020, issued in the wake of the COVID-19 disruption, the Central Government raised the threshold to one crore rupees. The increase was intended to insulate micro, small and medium enterprises from insolvency over modest defaults and to de-clog the Tribunals.

The threshold change is prospective: it applies to applications under Section 7 or Section 9 filed on or after 24 March 2020. An operational creditor whose claim falls below one crore rupees cannot maintain a Section 9 application, however clear the default — it must pursue ordinary civil remedies. The threshold operates on the amount of default, not the total ledger between the parties, so an operational creditor may aggregate unpaid invoices to cross the bar, provided each represents a genuine, undisputed operational debt.

Limitation: The Three-Year Clock

A Section 9 application is governed by the Limitation Act, 1963. Following B.K. Educational Services (P) Ltd. v. Parag Gupta & Associates, (2019) 11 SCC 633, it is settled that Article 137 of the Limitation Act applies to applications under the Code, prescribing a limitation period of three years that runs from the date on which the right to apply accrues — that is, from the date of default. An application filed beyond three years from default is time-barred unless the delay is saved by an acknowledgement of debt under Section 18 or condoned under Section 5 of the Limitation Act.

The Supreme Court applied these principles to the operational-creditor route in Sabarmati Gas Ltd. v. Shah Alloys Ltd., 2023 INSC 10. The Court reaffirmed that limitation for a Section 9 application runs from the date of default and is, in principle, extendable only through Section 5 condonation on sufficient cause. On the facts, it allowed exclusion of the period during which the operational creditor's right to sue stood suspended under the erstwhile Sick Industrial Companies (Special Provisions) Act, 1985, while underscoring that the three-year Article 137 period otherwise governs. Aspirants should note that the demand notice does not by itself extend limitation; the clock runs from default, and only a valid acknowledgement or condonation can save a stale claim. The wider doctrine of triggering events is covered in our note on insolvency triggering events.

Summary Jurisdiction and the Limits of Adjudication

The unifying thread of the case law is that Section 9 confers a summary jurisdiction. The Adjudicating Authority does not conduct a trial. Following Mobilox, it asks only whether the operational debt is due, whether default has occurred above the threshold, whether the application is within limitation, and whether a plausible pre-existing dispute exists. If a genuine dispute is shown, the application must be rejected at the threshold and the parties relegated to the appropriate civil or arbitral forum; the merits are not for the Tribunal to decide.

This restraint protects solvent but contesting companies from the draconian consequences of admission, while preserving the Code's speed for clear, undisputed defaults. The Code is, as the Supreme Court has repeatedly stressed, a beneficial legislation for resolution and not a recovery statute. An operational creditor who treats Section 9 as a pressure tactic to extract payment of a contested claim courts dismissal and, potentially, costs. Conversely, a corporate debtor that has genuinely defaulted on an undisputed operational debt above one crore rupees has no defence to admission.

The operational-creditor route must be read against the Code's overarching purpose: time-bound resolution of insolvency to maximise the value of assets and balance the interests of all stakeholders. The structured pause built into Section 8 — demand, wait, dispute or pay — is the Code's way of reconciling speed with fairness for the operational class. For the policy backdrop and the legislative scheme, see the foundational note on the introduction, object and scheme of the IBC, and return to the full syllabus map on the IBC notes hub.

For the examination, three holdings are non-negotiable: Mobilox on the meaning and threshold test of a dispute; Macquarie Bank on the directory nature of Section 9(3)(c) and lawyer-issued notices; and K. Kishan on a challenged arbitral award as a pre-existing dispute. Layered with the Section 4 one-crore threshold, the Article 137 limitation rule from B.K. Educational Services and Sabarmati Gas, and the expansive definition of operational debt in Consolidated Construction Consortium, these authorities furnish a complete and defensible account of how an operational creditor initiates CIRP.

Frequently asked questions

Is a Section 8 demand notice mandatory before filing under Section 9?

Yes in substance. Although Section 8(1) uses “may,” the Tribunals treat service of a valid Section 8 demand notice as a condition precedent to a Section 9 application. Without it the operational creditor has no cause of action, because the corporate debtor must first be given the ten-day window to pay or to raise a dispute.

What did Mobilox v Kirusa decide about the “existence of a dispute”?

In Mobilox Innovations (P) Ltd. v. Kirusa Software (P) Ltd., (2018) 1 SCC 353, the Supreme Court held that the Adjudicating Authority must reject a Section 9 application so long as a dispute truly exists in fact and is not spurious, hypothetical or illusory. It need only find a plausible contention requiring investigation; it does not decide the merits. The Court also read “and” in Section 8(2)(a) as “or.”

Must the dispute pre-date the demand notice?

Yes. The dispute that bars a Section 9 application must be a pre-existing one that arose before the Section 8 notice; a debtor cannot fabricate a dispute for the first time in reply. In K. Kishan v. Vijay Nirman Co. (P) Ltd., (2018) 17 SCC 662, a pending Section 34 challenge to an arbitral award was held to be such a pre-existing dispute, barring CIRP.

Can a lawyer issue the Section 8 demand notice?

Yes. In Macquarie Bank Ltd. v. Shilpi Cable Technologies Ltd., (2018) 2 SCC 674, the Supreme Court held that a lawyer or authorised agent acting on the instructions of the operational creditor may validly issue the demand notice, reading Sections 8 and 9 with Section 30 of the Advocates Act, 1961. The agent must, however, hold authority from the creditor.

Is the financial-institution certificate under Section 9(3)(c) compulsory?

No. Macquarie Bank Ltd. v. Shilpi Cable Technologies Ltd., (2018) 2 SCC 674, held Section 9(3)(c) to be directory, not mandatory. The certificate is one means of proving non-payment; a creditor who cannot obtain it — for instance, one banking abroad — may establish default through other documents.

What is the minimum default amount for an operational creditor's application?

Under Section 4, the threshold is one crore rupees for applications filed on or after 24 March 2020, raised from one lakh rupees by Notification S.O. 1205(E). A Section 9 application for a default below one crore is not maintainable, and the operational creditor must pursue ordinary civil remedies instead.