Software product start-ups tend to approach the MSME Samadhaan filing process with three assumptions, and each one causes trouble later. The first is that recognition as a start-up by DPIIT is enough to qualify. The second is that once the form is submitted, the buyer must pay within 45 days. The third is that the dispute clause in the customer's master services agreement has to be exhausted first. None of these is right, and correcting them early saves months.
Myth one: start-up recognition is the same as MSME status
DPIIT recognition and Udyam registration are separate. Only Udyam registration as a micro or small enterprise opens the delayed-payment chapter of the MSMED Act, 2006, and only for supplies made after the registration date. A recognised start-up without Udyam cannot file, however young or small it is.
Myth two: filing makes payment due within 45 days
The 45-day figure in Section 15 is the maximum credit period a buyer may take after accepting the supply. It is the reason interest is due, not a deadline for the council process. Once a reference is filed, the process moves through scrutiny, notice, conciliation and possibly arbitration, and that takes considerably longer.
Myth three: the contract's dispute clause must be used first
Many enterprise contracts provide for escalation meetings and private arbitration. Section 24 of the Act gives Sections 15 to 23 overriding effect, and Section 18 lets an eligible supplier approach the council directly. Escalation is still worth trying for commercial reasons, but it is not a legal precondition. When you want the process planned and run properly, you can hire Advocate BK Singh for MSME, recovery, commercial or arbitration cases.
Key facts at a glance
- The process has six phases: checks, submission, scrutiny and notice, conciliation, arbitration, and award.
- Udyam registration must predate the supplies claimed (Silpi Industries, 2021).
- The council of the supplier's State hears the case under Section 18(4).
- Conciliation comes first under Section 18(2); arbitration follows under Section 18(3) if it fails.
- Interest under Section 16 runs at 17.25% a year, compounded monthly, based on the Bank Rate of 5.75% from 7 October 2026.
- A buyer must deposit 75% of the award to challenge it (Section 19).
What Does the MSME Samadhaan Filing Process Involve From Start to Finish?
The MSME Samadhaan filing process has six phases: pre-filing checks, online submission, council scrutiny and notice to the buyer, conciliation, arbitration if conciliation fails, and the award followed by any challenge and enforcement. Most of the supplier's effort goes into the first phase and into preparing for conciliation and arbitration, not into the online form itself.
It helps to think of the process as a pipeline. What goes in at the start, in the form of eligible invoices, clear evidence and a correct computation, determines what comes out at the end. A supplier that rushes the first phase to get the form submitted often spends the later phases repairing the damage.
Each phase also has a decision built into it. After the checks: file or not, and which invoices. After the buyer's reply: how to answer. At conciliation: settle or press on. After the award: accept, challenge or enforce. A process that is planned around these decisions moves faster and produces better results than one that simply reacts.
The phases below describe the process in general terms. The portal's screens change from time to time, and councils differ in their practice, so check the official sources for the current details. What does not change is the statutory structure in Sections 15 to 19 of the MSMED Act, 2006.
Phase One: What Must Be Checked Before You File?
Before filing, check that your Udyam registration shows micro or small status and predates every invoice you plan to claim, that your activity is a service or manufacture, that each invoice is for an accepted supply now overdue, that it falls within limitation, and that you have the buyer's correct legal name and address. This phase decides the rest.
For a software start-up, the Udyam certificate deserves a careful look. Check the registration date, the classification and the NIC activity codes. Software development, publishing and related services sit within the service codes. If the registration lists only an unrelated activity, the buyer may question whether the supplies fall within it. Udyam details can be updated on the official portal without charge.
Next, check each invoice. List them with dates, amounts, payments received, TDS deducted and the outstanding balance. Mark the date the customer accepted the supply, whether through a go-live sign-off, a UAT completion email or simply by using the software without objection. Calculate the due date under Section 15, which is the end of the agreed credit period, capped at 45 days from acceptance.
Then check limitation. The Supreme Court held in Silpi Industries (2021) that limitation applies to council arbitration. Invoices that fell due more than three years before filing may be barred unless the customer acknowledged the debt in writing in the meantime.
Finally, check the buyer. Enterprise customers often contract through one entity and pay through another. File against the entity that signed the order form and received your invoices.
Is Software Supplied by a Start-up Covered by the MSMED Act?
Software development, licensing, SaaS subscriptions, implementation and support supplied by a micro or small enterprise are generally treated as services under the MSMED Act, 2006, so they can be claimed through Samadhaan. The supplier must hold Udyam registration from before the supply. Pure resale of third-party software licences may be challenged as trading.
The Act covers enterprises engaged in providing or rendering services. A start-up that builds and hosts its own product, licenses it to customers, implements it and supports it is plainly a service provider. Its invoices for subscriptions, implementation fees, customisation and support are invoices for services.
The grey area is resale. Some start-ups bundle third-party licences, such as cloud credits or another vendor's software, into their invoices. If those items are simply bought and resold at a margin, the buyer may argue they are trading supplies outside the chapter. Where they form part of an integrated solution that the start-up designs and delivers, the service character is stronger. The invoice description matters, and so does the order form.
Another grey area is advance billing. SaaS subscriptions are often invoiced annually in advance. A buyer may argue that nothing is due for the months of service not yet delivered. The cleaner claim is for the service period already rendered, with interest from the due date for that period. Claiming the full year before the service has been provided invites an argument the supplier may not win.
Phase Two: How Does the Online Submission Proceed?
In general terms, the supplier identifies its enterprise through its Udyam details, verifies through the registered mobile number, enters the buyer's particulars, lists each unpaid invoice with dates and outstanding amounts, attaches supporting documents and submits. The portal then provides an application reference for tracking. The submission itself usually takes far less time than the preparation.
- Prepare the invoice schedule. Finalise the list of invoices with dates, amounts, payments, TDS and balances before logging in. Do not work out figures on the portal.
- Organise the attachments. Convert order forms, invoices, sign-off emails, usage reports and correspondence into clear PDF files with descriptive names.
- Log in with Udyam details. Make sure the mobile number linked to the Udyam registration is active, as verification usually depends on it.
- Enter the buyer's details. Use the buyer's exact legal name and registered address, taken from its order form, GST registration or company records.
- Enter each invoice. Record the invoice number, date, value and outstanding amount, matching the schedule exactly.
- Attach and submit. Upload the documents, review every entry once more and submit. Save the reference and a full copy of what was filed.
A short written statement explaining the facts is useful where the customer is likely to contest. It can go with the filing or be kept ready for the council. For an overview of the documents and stages from the filing side, see our page on MSME Samadhaan filing.
Which Records Prove a SaaS or Software Supply Was Accepted?
Acceptance of software is proved by go-live or UAT sign-off emails, milestone completion certificates, the customer's usage data such as active users and logins, support tickets raised and resolved, renewal or expansion orders, and the absence of any written objection within fifteen days of delivery. Usage logs are often the strongest evidence a software supplier has.
Software supplies do not produce delivery challans or goods receipt notes. The proof lies elsewhere. A UAT sign-off email from the customer's project lead is the clearest evidence for an implementation milestone. For a subscription, the customer's own usage, visible in the admin dashboard or server logs, shows the service was delivered and used.
Support tickets help too. A customer that raised fifty tickets about how to use a feature, and had them resolved, was using the product. A customer that asked for additional user licences mid-term can hardly claim the product was rejected. Export these records with dates and keep them as PDFs or spreadsheets with an explanation of what each field means.
Deemed acceptance under the Act applies where the customer did not object in writing within fifteen days of the supply. A complaint that the product never went live, first raised six months later in response to a payment reminder, will not displace acceptance if the usage logs show hundreds of logins in the meantime. Our page on MSME Samadhaan filing and representation describes how such evidence is presented to the council.
Practical tip: Export and save usage logs for disputed customers now, before access is revoked or data retention policies delete them. Months later, when the council asks, they may no longer exist.
Phase Three: What Happens During Scrutiny and Notice?
After submission, the council scrutinises the application for completeness and jurisdiction, may ask the supplier for clarification or documents, and then issues notice to the buyer. The buyer is given time to respond. This phase is often where the first delay occurs, usually because of incomplete details or a buyer that does not respond.
During scrutiny, the council checks that the supplier is eligible, that the application concerns amounts due under the Act and that it falls within the council's jurisdiction under Section 18(4). If anything is unclear, the council may ask questions. A prompt, complete answer keeps the application moving.
Notice to the buyer follows. For enterprise customers, notice may land with a legal or procurement team that has never heard of the dispute, because the relationship was managed by a business unit. That sometimes produces a quick settlement once someone senior sees the claim. Other times it produces a long reply drafted by lawyers.
The supplier should keep an eye on the portal and any communication from the council during this phase. If nothing happens for a long time, a polite written follow-up is appropriate. It is also worth checking that the buyer's address used for notice was correct.
Phase Four: How Does Conciliation Work in Practice?
Conciliation under Section 18(2) is a council-led negotiation. The council member, acting as conciliator, meets both parties, hears their positions and helps them find agreement. Admissions made there cannot be used later. A signed settlement binds both sides like an arbitral award. If no agreement is reached, the council ends conciliation and moves to arbitration.
The conciliation provisions of the Arbitration and Conciliation Act, 1996 apply. That brings a useful protection: what a party says or offers during conciliation cannot be relied on in later proceedings. The supplier can negotiate openly without worrying that a concession will be used against it in arbitration.
Preparation matters more than people expect. Before the first meeting, the supplier should know its walk-away figure, the strongest and weakest parts of its claim, and the buyer's likely arguments. For a software start-up, the weakest parts are often disputed change requests and advance-billed subscription periods. The strongest are usually signed-off milestones and periods of proven usage.
Conciliation can take one meeting or several. If the buyer is engaging seriously, extra meetings are worth it. If the buyer is using the meetings to delay, the supplier can ask the council to record that conciliation has failed and move to arbitration. Our page on MSEFC arbitration and conciliation cases covers both stages in more depth.
Phase Five: What Does the Arbitration Phase Involve?
When conciliation fails, the council arbitrates itself or refers the dispute to an institution under Section 18(3). The supplier files a detailed statement of claim, the buyer files its defence and any counterclaim, documents and evidence are exchanged, the parties argue, and the council passes a reasoned award with interest under Section 16.
The arbitration phase is formal. The 1996 Act applies as if there were an arbitration agreement between the parties. Pleadings set out each side's case. Evidence is usually given by affidavit, with cross-examination where the council allows it. Final arguments, often in writing as well as orally, close the hearing.
For software disputes, technical issues sometimes arise. A customer may claim the product failed its performance requirements, or that the start-up breached service levels. The supplier answers with uptime reports, ticket histories and usage data. Where the technical dispute is central, a party may consider an independent technical opinion.
Counterclaims are allowed before the council, as Silpi Industries (2021) confirmed. A customer may claim refund of fees paid, service credits under the SLA, or the cost of migrating to another vendor. The supplier must answer these on the facts and on limitation. At this phase many start-ups decide to hire Advocate BK Singh for MSME, recovery, commercial or arbitration cases, because arbitration needs pleadings, evidence and legal argument rather than negotiation alone.
How Much Interest Builds Up During the Process?
On an outstanding principal of ₹43,50,500, Section 16 interest at 17.25% a year with monthly compounding is ₹3,88,977 after six months and ₹8,12,732 after twelve. At twenty-four months, the interest is ₹17,77,293 and the total due is ₹61,27,793. Interest runs from each invoice's due date until the buyer pays.
The rate is three times the RBI Bank Rate, compounded monthly. The Bank Rate is 5.75% from 7 October 2026, so the annual rate is 17.25%, or 1.4375% per month. The table below works through the illustrative principal.
| Period after the due date | Growth factor | Interest (₹) | Total due (₹) |
|---|---|---|---|
| 6 months | 1.0894 | ₹3,88,977 | ₹47,39,477 |
| 12 months | 1.1868 | ₹8,12,732 | ₹51,63,232 |
| 18 months | 1.2929 | ₹12,74,375 | ₹56,24,875 |
| 24 months | 1.4085 | ₹17,77,293 | ₹61,27,793 |
Principal ₹43,50,500. Interest compounded monthly at three times the RBI Bank Rate (5.75% from 7 October 2026), that is 17.25% a year or 1.4375% a month. Check the Bank Rate in force for your period.
Because the process takes time, interest is a large part of the final figure. A claim filed a year after the invoices fell due, and decided a year after filing, carries roughly two years of interest. For the customer, that is a significant extra cost, made worse by Section 23, which prevents the buyer from deducting it for tax, and by Section 43B(h) of the Income-tax Act, which delays the deduction for the principal until payment.
For SaaS invoices, each billing period has its own due date. Monthly or quarterly invoices produce many due dates, each starting its own interest clock. A computation that applies a single date to the whole balance will be wrong. Our page on MSME delayed payment interest explains how invoice-wise computations are done.
Phase Six: What Comes After the Award?
After the award, the buyer may apply under Section 34 of the Arbitration and Conciliation Act, 1996 to set it aside within three months, extendable by thirty days, but must first deposit 75% of the awarded amount under Section 19. If no challenge is filed or it fails, the supplier enforces the award as a decree under Section 36.
A Section 34 challenge is not an appeal. Courts do not reassess the evidence or substitute their own conclusions. The grounds are limited to matters such as lack of jurisdiction, inability to present a case and conflict with the public policy of India in its narrow sense. A well-reasoned award on a clean record is difficult to set aside.
The 75% deposit gives the supplier real protection. The court may release part of it to the supplier while the challenge is pending. For a start-up waiting on cash, that interim release can matter as much as the final result.
If the buyer does not challenge, or loses, enforcement follows. The supplier files an execution petition, and the court can attach the buyer's bank accounts, receivables or property. Large enterprise customers usually pay once an award becomes enforceable, because the alternative is disruption to their own operations.
Where Does the Process Usually Get Stuck, and What Can You Do?
The process usually gets stuck at scrutiny, because of incomplete details; at notice, because of a wrong buyer address; at conciliation, because the buyer delays; and at arbitration, because of adjournments or preliminary objections. Each hold-up has a practical fix, and a supplier who acts on it promptly saves months.
| Hold-up | Usual cause | What the supplier can do |
|---|---|---|
| No movement after submission | Council docket; query not answered | Check for queries; send a polite written follow-up |
| Notice not served | Wrong or old buyer address | Provide the registered office address from company records |
| Repeated conciliation adjournments | Buyer stalling | Ask the council to record failure and move to arbitration |
| Preliminary objection on eligibility | Invoices before Udyam date; trading items | Concede ineligible invoices; press the rest |
| Limitation objection | Old invoices | Produce written acknowledgments or part-payment records |
| Counterclaim filed | Buyer seeking set-off | Answer on facts, limitation and proof of loss |
Most of these hold-ups trace back to Phase One. An application with correct buyer details, only eligible invoices and documented acknowledgments for older ones avoids four of the six problems in the table.
How Does the Samadhaan Process Compare With Other Routes?
The Samadhaan process gives eligible micro and small suppliers statutory interest and a strong deposit rule on challenge. A commercial suit suits claims of ₹3 lakh or more outside the Act. A summary suit is faster on clean documents. Section 138 applies to bounced cheques, and IBC Section 9 needs a default of at least ₹1 crore.
| Route | Process in brief | Best suited to |
|---|---|---|
| MSME Samadhaan and MSEFC | Online filing, conciliation, arbitration, award | Eligible micro and small suppliers with post-registration invoices |
| Commercial suit | Section 12A mediation, then suit, trial and decree | Ineligible invoices or larger contractual disputes |
| Summary suit | Suit under Order XXXVII; buyer must seek leave to defend | Clear invoices with no real defence |
| Section 138 complaint | Notice within 30 days of dishonour, complaint, trial | Customers who paid by cheque that bounced |
| IBC Section 9 | Demand notice, application to NCLT | Undisputed defaults of ₹1 crore or more |
Software start-ups selling to large enterprises often face customers that dispute something, even if only a change request. That makes the IBC route risky and summary suits less certain. The council route is usually the strongest for post-registration invoices. For the wider recovery picture, see our guide to MSME delayed payment recovery.
Which Software Buyer Excuses Should You Answer Before Filing?
Answer the usual software excuses in writing before filing: that the product never went live, that users did not adopt it, that budgets were frozen, that the customer is moving to another vendor, or that the invoice was not uploaded on its vendor portal. Most are not legal defences, and a written reply now becomes evidence later.
Enterprise customers use a familiar set. The product never went live, when the usage logs say otherwise. Adoption was poor, which is the customer's own change management issue. Budgets are frozen for the quarter, which is internal. The company is migrating to another platform, which does not cancel invoices for service already delivered. The invoice was not uploaded on the vendor portal, which is a procedural point the customer controls.
The vendor portal excuse deserves a word. Large customers require invoices to be uploaded on their procurement systems, often with a purchase order number. If the start-up did not upload an invoice, the customer may claim it never received it. The fix is simple: upload it now, or send it by email to the accounts team and keep the acknowledgment. The underlying duty to pay arises from supply and acceptance, but there is no reason to leave the customer an easy excuse.
Each written reply should be short and factual. It should state the invoice, the service period, the evidence of use and the due date. If the customer raises a genuine performance issue promptly, take it seriously and fix it, but do not let a late, general complaint go unanswered.
Honest limit: If the customer is outside India, a council award may be difficult to enforce abroad. The process can still be useful as pressure, but a supplier should weigh whether the customer has assets or operations in India before investing in it.
Why Hire Advocate BK Singh for the MSME Samadhaan Filing Process?
Because each phase of the process has its own decision, and he advises on every one while also representing suppliers when the buyer contests.
- Process knowledge across all phases. Advocate BK Singh handles Samadhaan references from pre-filing checks to execution. Clients get one adviser for the whole pipeline.
- Careful pre-filing checks. Udyam dates, NIC codes, invoice eligibility and limitation are checked before filing. That prevents most of the hold-ups that slow cases later.
- Experience with services claims. Software and services disputes depend on emails, logs and sign-offs rather than delivery challans. His MCA background helps in reading and presenting technical and digital evidence.
- Representation at conciliation and arbitration. When the customer contests, he appears before the council. Pleadings, evidence and arguments are prepared with the later court review in mind.
- Court follow-through. Section 34 challenges and Section 36 execution are handled in court. He appears before the Supreme Court, High Courts, DRT/DRAT, NCLT and commercial courts.
- Alternative routes covered. Ineligible invoices can go to commercial or summary suits. Recovery and commercial litigation are part of the same practice.
- A team for continuity. The Legals365 team of 50+ advocates supports drafting and appearances. Dates are covered without delay.
- Qualified and candid. He holds MCA, LLB and LLM degrees and gives straightforward advice on weak points, such as advance-billed subscriptions. That keeps expectations realistic.
No outcome can be promised in any legal matter. You can read more on the Advocate BK Singh profile page.
How Can You Begin the MSME Samadhaan Filing Process With Us?
Begin with a pre-filing review. Send your Udyam certificate, the customer's order forms or master agreement, unpaid invoices, sign-off emails, usage reports, support ticket history and correspondence. We check eligibility and limitation, build the invoice schedule, compute interest and plan the MSME Samadhaan filing process with you, phase by phase.
A software start-up with a large enterprise customer that has stopped paying does not need to choose between silence and a costly lawsuit. The council process exists for exactly this situation, provided it is run with care from the first phase. When you are ready to start, you can hire Advocate BK Singh for MSME, recovery, commercial or arbitration cases and have the process planned before the form is ever opened.
Official sources: references are filed on the MSME Samadhaan portal, Udyam details are managed on the Udyam Registration portal, and the MSMED Act, 2006 is on India Code.
Speak to Advocate BK Singh
Share your invoices, purchase orders, delivery records and correspondence for an initial review of your matter.
Advocate BK Singh | Legals365 | Phone/WhatsApp: +91 98115 61566 | Offices: Vaishali (Ghaziabad) and Dwarka (New Delhi)
Frequently Asked Questions
Who is the best lawyer for MSME Samadhaan filing process?
The best lawyer for the MSME Samadhaan filing process guides you through every phase, from pre-filing checks to enforcing the award, and can represent you when the buyer contests. Advocate BK Singh of Legals365 checks eligibility and limitation, prepares the invoice schedule, files the reference and appears at conciliation and arbitration. Ask how a lawyer would handle the hold-ups typical of your buyer.
Why should I hire Advocate BK Singh for MSME Samadhaan filing process?
Because each phase of the process has a decision that affects the result, and he advises on every one. Advocate BK Singh runs the pre-filing checks that prevent common hold-ups, prepares the claim, represents you at conciliation and arbitration, and handles any Section 34 challenge or execution. The Legals365 team of 50+ advocates supports the matter throughout.
Can Advocate BK Singh handle MSME, recovery, commercial and arbitration cases together?
Yes. Advocate BK Singh and the Legals365 team handle Samadhaan references, council arbitration, commercial suits, summary suits and Section 138 complaints together. That matters when some invoices qualify for the council and others do not, or when a customer's cheque bounces. One team keeps the invoice schedule, the evidence and the strategy consistent across every forum.
What are the steps in the MSME Samadhaan filing process?
There are six phases: pre-filing checks on Udyam status, invoices and limitation; online submission on the portal; council scrutiny and notice to the buyer; conciliation under Section 18(2); arbitration under Section 18(3) if conciliation fails; and the award, followed by any Section 34 challenge and enforcement under Section 36 of the Arbitration and Conciliation Act, 1996.
Can a DPIIT-recognised start-up file on MSME Samadhaan without Udyam?
No. DPIIT start-up recognition and Udyam registration are separate. Only Udyam registration as a micro or small enterprise gives access to the delayed-payment chapter of the MSMED Act, 2006, and only for supplies made after the registration date. A recognised start-up should register on Udyam, which is free on the official portal, before relying on this route.
Are SaaS subscription invoices covered by MSME Samadhaan?
Generally yes. SaaS subscriptions, licensing, implementation and support supplied by a micro or small enterprise are services under the MSMED Act, 2006. The supplier must be registered on Udyam before the supply. For annual subscriptions billed in advance, the safer claim is for the service period already delivered, because buyers often dispute amounts for future months not yet rendered.
How do software companies prove acceptance in a Samadhaan claim?
Through go-live or UAT sign-off emails, milestone certificates, usage data such as logins and active users, support tickets raised and resolved, renewal or expansion orders, and the absence of a written objection within fifteen days. Usage logs are often the strongest proof. Export and save them early, before the customer's access ends or data retention removes them.
Does filing on Samadhaan mean the buyer must pay within 45 days?
No. The 45-day figure in Section 15 is the maximum credit period the buyer may take after accepting the supply, and it is why interest is owed. It is not a deadline for the council process. After filing, the case passes through scrutiny, notice, conciliation and possibly arbitration, which usually takes considerably longer than 45 days.
Must I use the contract's dispute resolution clause before filing on Samadhaan?
No. Section 18 of the MSMED Act, 2006 lets an eligible supplier approach the council directly, and Section 24 gives Sections 15 to 23 overriding effect over contrary contract terms. Escalation meetings under the contract may still be worth trying for commercial reasons, but they are not a legal precondition. Buyers sometimes raise the clause as an objection, which should be answered.
What causes delays in the Samadhaan filing process?
Common causes are incomplete details at scrutiny, a wrong buyer address that delays notice, buyers seeking repeated adjournments at conciliation, and preliminary objections on eligibility or limitation in arbitration. Most can be prevented or reduced by careful pre-filing checks, correct buyer details from company records, and asking the council to record failure of conciliation when the buyer is stalling.
What happens during conciliation in the Samadhaan process?
The council member acts as conciliator, meets both parties and helps them reach agreement. Under the conciliation provisions of the 1996 Act, admissions and offers made during conciliation cannot be relied on later. A signed settlement binds both sides like an arbitral award. If no agreement is reached, the council ends conciliation and moves the dispute to arbitration.
Can a customer file a counterclaim during the Samadhaan arbitration phase?
Yes. The Supreme Court confirmed in Silpi Industries (2021) that a buyer may raise a counterclaim before the council. Software customers may claim refunds, SLA service credits or migration costs. The supplier should answer with uptime reports, ticket histories, usage data and the contract terms, and should check whether the counterclaim itself falls within limitation.
How much interest builds up during the Samadhaan process?
Interest under Section 16 is compound with monthly rests at three times the RBI Bank Rate, which is 17.25% a year with the Bank Rate at 5.75% from 7 October 2026. It runs from each invoice's due date until payment, including while the case is pending. Over a two-year period, it adds roughly forty per cent to the principal.
What if my software customer says the invoice was not uploaded on its vendor portal?
Upload it now, or email it to the customer's accounts team and keep the acknowledgment. The duty to pay arises from supply and acceptance under the MSMED Act, 2006, not from the customer's internal procurement procedure, but there is no reason to leave an easy excuse. Record the date of upload or email, because it may be relevant to the due date.
Can I file a Samadhaan claim against a foreign customer?
Technically, the council of your State can receive a claim, but enforcing an award against a customer with no assets or operations in India is difficult. The process may still create pressure if the customer values its Indian relationships. Before investing time, consider whether the customer has an Indian entity, assets or receivables that an award could reach.
How long does each phase of the Samadhaan process take?
There are no fixed periods for each phase in practice. The Act says a reference should be decided within ninety days, but councils often take longer. Scrutiny and notice can take weeks or months, conciliation may need one meeting or several, and contested arbitration takes longer still. A court challenge and execution add further time after the award.
What happens after the council passes an award?
The buyer has three months, extendable by thirty days, to apply under Section 34 to set the award aside, but must first deposit 75% of the awarded amount under Section 19. The court may release part of the deposit to the supplier during the challenge. If no challenge succeeds, the supplier enforces the award as a decree under Section 36.
Should I update my Udyam NIC codes before filing on Samadhaan?
If your Udyam registration does not reflect the software or service activity your invoices describe, updating it is sensible, and the official portal does not charge for updates. A mismatch can give the buyer an argument that the supplies fall outside your registered activity. The update does not change the original registration date, which is what decides eligibility for earlier supplies.
Can I claim for change requests in the Samadhaan process?
Yes, if the change requests were approved in writing, delivered and invoiced. Keep the approval emails, the delivery or deployment record and any acceptance by the customer. Change requests done on oral instructions, or disputed as part of the original scope, are weaker. Include them where you have evidence, but expect the customer to contest them more strongly than signed-off milestones.
Which documents should a software start-up gather before starting the process?
Gather the Udyam certificate, the order form or master services agreement, statements of work, invoices, UAT and go-live sign-offs, usage reports and logs, support ticket histories, change request approvals, payment records and all correspondence about payment or performance. Organise them by invoice. A complete set makes pre-filing checks quick and gives the council a clear picture of the claim.
Disclaimer: This page gives general information in line with the Bar Council of India Rules. It is not legal advice or a solicitation, and the outcome of any matter depends on its own facts and evidence.
MSME Msme Samadhaan Filing Process Lawyers?
Get strategic legal guidance from experienced consumer dispute lawyers who help individuals and businesses in Msme Samadhaan Filing Process Lawyers resolve MSME matters, insurance disputes, real estate conflicts, and defective service claims with confidence and clarity.
Chat on WhatsApp +91-9811561566Schedule Your Consultation