The Micro, Small and Medium Enterprises Development Act, 2006 was drafted around a simple commercial picture: an enterprise supplies goods or renders services, the buyer sits on the invoice, and Sections 15 to 18 supply the remedy. Real contracts are rarely so tidy. An electrical contractor supplies material and installs it; a fabricator designs, manufactures and erects; an IT vendor licenses, customises and maintains. Whether such composite engagements are "supply of goods or rendering of services" under the Act is a threshold fight in many Facilitation Council references, and it deserves more careful pleading than it usually gets.
Why the characterisation fight matters
Everything the MSMED Act gives a claimant hangs on the word "supplier". Section 15 obliges the buyer to pay before the appointed day (or agreed period capped at forty-five days) for goods supplied or services rendered. Section 16 attaches compound interest at three times the bank rate to the delayed amount. Section 17 makes the buyer liable for the amount with interest, and Section 18 opens the Facilitation Council's doors. A respondent who persuades the Council that the engagement was neither a supply of goods nor a rendering of services — but something else, most commonly a works contract creating immovable property — aims to cut the claim off at the root, statutory interest and all.
The anatomy of a composite engagement
Pure supply
Manufacture and delivery of goods against purchase orders — the Act's core case; characterisation is uncontested.
Supply and installation
Goods manufactured, delivered and installed or commissioned. Ordinarily divisible into supply plus service elements; squarely arguable within the Act.
Service engagements
Testing, maintenance, IT development, professional and support services — covered as rendering of services by a registered service enterprise.
Construction-dominant works
Civil construction of immovable property with incidental material — the contested frontier where buyers press the "not a supply" objection hardest.
Building the claimant's characterisation
Three practical rules assist enterprises whose work sits in the middle of that spectrum. First, invoice architecture is destiny. Contracts and bills that separately identify supplied goods and rendered services — quantities, rates, service milestones — make the statutory characterisation almost self-executing, while a single lump-sum "for the works" figure invites the objection. Second, registration should mirror reality. The Udyam certificate's activity classification (manufacturing or service, with the relevant codes) should cover the activity that produced the claim; enterprises that diversify should update their registration before, not after, the dispute. Third, the acceptance trail fixes more than the appointed day. Delivery challans, installation reports, and the buyer's acceptance or deemed acceptance under Section 2(b) both start the payment clock and evidence that what happened was, in fact, supply.
The respondent's perspective
Buyers objecting to characterisation should do so with equal discipline: the objection is about the substance of the engagement, not its label. A genuine construction contract for immovable works, a pure lease, or an engagement predating the claimant's registration in the relevant category present arguable defences. But Councils are alive to objections raised only after years of accepting invoices that describe goods and services — conduct evidence cuts across characterisation arguments, and a buyer's own GST treatment of the transaction (goods, services, or works-contract service) is quotable material on both sides.
| Document | What it proves in the characterisation fight |
|---|---|
| Contract / purchase orders | The engagement's substance: scope, deliverables, milestones. |
| Udyam certificate | MSME status and the registered activity at the time of supply. |
| Invoices and challans | The goods-services break-up; the payment clock under Section 15. |
| GST invoices / returns | Contemporaneous classification of the transaction by both sides. |
| Acceptance / commissioning records | Deemed acceptance, the appointed day, and the fact of supply itself. |
Practice note: Where characterisation is genuinely doubtful, claimants should weigh pleading in the alternative — the Council reference asserting supply of goods and rendering of services, with a commercial suit preserved for the balance of the engagement. What should be avoided is silence: references that never address the issue hand the first word, and often the framing, to the objecting buyer.
Frequently Asked Questions
Does the MSMED Act define "goods" and "services"?
Sparsely. Section 2(n) defines "supplier" by reference to micro and small enterprises which supply goods or render services; the Act leans on the classification framework of Section 7, under which enterprises are classified whether engaged in manufacture or production of goods or in providing or rendering of services. The absence of a works-contract definition is what generates the disputes.
Are works contracts covered?
There is no blanket exclusion in the statute. A works contract is, in substance, a composite of goods and services, and enterprises executing them have maintained references where their engagement is fairly characterised as supplying goods and rendering services within their registered activity. Buyers resist by painting the contract as an immovable-property construction engagement outside "supply". The characterisation battle is fact-specific: scope of work, invoicing structure and the enterprise's registration all matter.
Does Udyam registration for one activity cover claims from another?
The safest position is alignment: the activity generating the claim should correspond to the activity for which the enterprise is registered and classified. Councils and courts examine whether the claimant was an MSME engaged in the relevant activity when the supply was made — mismatches between registration and the contract's substance invite maintainability objections.
What should the reference plead on this issue?
The contract documents; the Udyam certificate and activity classification; a break-up showing the goods supplied and services rendered with invoices; and the acceptance trail fixing the appointed day. Where the buyer will argue "works contract, not supply", the reference should pre-emptively characterise the engagement clause by clause rather than leave the label to the objector.