The Client Has Stopped Paying. Here Is the Sequence, in Order.

dev.to

Don't chase harder. Not yet. The first thing is to figure out which of two completely different problems you're actually holding, because a client who cannot pay and a client who will not pay need opposite responses. Treat one as the other and a recoverable situation becomes a written-off invoice and a burned relationship on the same day.

Almost every guide on this topic hands you an escalation ladder. Polite reminder, firmer reminder, final notice, collections. That ladder is fine as far as it goes. What it skips is the diagnosis that decides whether to climb it at all. When to actually stop working. And, if you're in India, a statutory position that's a lot stronger than most freelancers and small agencies realise.

This is the sequence I'd follow, in order. It isn't legal advice. Where it touches law it points at the primary source so you can take it to someone qualified. Assume nothing here without checking your own facts against the current rules.

First: can't pay, or won't pay?

From your side they look identical. An unanswered invoice. They aren't the same event at all.

Can't pay is a cash-flow problem at their end. Intent is there. The money isn't, yet. Signals: they answer the phone. They give you a date, even a vague one. Other vendors are being paid late too. Someone in the business volunteers information before you ask.

Won't pay is a decision. Signals: silence. Replies that never contain a date. A sudden dispute about quality raised only after the invoice went out, about work that was signed off at the time. The person you dealt with stops being the person who answers. Requests for a "revised" invoice at a lower number.

Why does this matter? Because a client who cannot pay is a payment-plan conversation and often still a good client next year. A client who will not pay is a recovery process and never a client again. Spending three weeks being gently patient with the second kind costs you the window where your evidence is fresh and your leverage is highest.

There's a third category worth naming, honestly, because it's more common than either. Nobody knows. The invoice went to a person who left. Or into an accounts inbox that requires a PO number nobody gave you. Or it's sitting in an approval queue behind a signature. Someone was on leave, someone else assumed someone else had processed it, and now three weeks have passed. A surprising share of "the client has stopped paying" is administrative, not financial, and one phone call resolves it. Make that call before you draft anything stern. It's free. Being stern about a filing error is expensive to walk back, and the finance person on the other end will remember the tone longer than the amount.

Day zero: what makes this recoverable

Most of what determines your position was decided before the client went quiet. Reading this mid-crisis? Skip ahead. But come back, because the next one is coming.

Register under Udyam if you qualify. In India, the entire delayed-payment protection regime keys off this. The Samadhaan portal is explicit: "Any Micro or small enterprise having valid Udyam Registration can apply" (MSME Samadhaan). Unregistered, you're an ordinary creditor with an ordinary contract dispute. Registered, you're a protected supplier with statutory interest and a dedicated forum. It's free. It takes an afternoon. I've watched people discover this fact in the exact week it would have been useful and could no longer be applied retroactively.

Get the payment term in writing, and keep it at 45 days or under. More on why in a minute.

Create an acceptance trail. The clock in the statute runs from acceptance of the goods or services. So "delivered on the 3rd, approved on WhatsApp on the 4th" isn't pedantry. It's the start date of everything that follows. An email that says delivering X as agreed, please confirm receipt costs nothing and converts a memory into a record.

Bill in milestones, and bill early. The largest unpaid invoice I've seen anyone carry was large because it was three months of work invoiced at the end. The same work invoiced monthly would have failed after one month. That's a survivable failure. This is a cash-flow discipline more than a legal one, and it sits in the same bucket as understanding why profit and cash are not the same thing. The businesses that die are rarely the unprofitable ones.

Know what a client is worth before you price them. A client you priced too thin is a client you can't afford to stop working for. Which means you'll keep working unpaid, because the alternative feels worse. Pricing your services properly is a solvency question, not a confidence one.

The sequence, in order

When What you do What you must not do
Due date + 1 One friendly message. Assume administration, not malice. Confirm the invoice reached the right inbox and ask if anything is needed. PO number, vendor form, GST detail. Apologise for asking
+ 7 days Phone call, to a human. Ask one direct question: is there a date? Follow up in writing summarising what was said. Accept "soon" without writing down that they said "soon"
+ 14 days Escalate sideways, not upward in volume. Find finance if you have been talking to marketing; find your original sponsor if you have been talking to finance. State the amount, the date, and the consequence. Threaten anything you are not prepared to do
+ 21 days Stop new work. In writing, calmly, with a resumption condition. Stop silently, or keep going to "protect the relationship"
+ 30 days Written demand with the full record attached: contract, invoices, delivery and acceptance dates, communication log. Send it in anger, at night, without re-reading it
Past the statutory period Formal options: MSEFC reference via Samadhaan if you are an eligible Indian MSE, or legal advice on the contract. Assume this is expensive or slow before checking

The order does the work here. Each step should be a genuine escalation. Each one should make the next more credible. The failure mode I see most: people cycling between step one and step two for two months. Same friendly message, same non-answer, same friendly message again. That teaches the client nothing follows a reminder. If your reminders never turn into anything, they stop being reminders. They become part of the background noise the buyer already learned to ignore.

When to stop work, and how to say it

Stop when the unpaid amount reaches the point where losing it would hurt but not end you. Or at the 21-day mark. Whichever is sooner. Not later. Every day you keep delivering after that, you're lending money to someone who's demonstrated they don't repay on schedule, at zero interest, without having agreed to.

Wording matters more than timing here, because the goal is a pause that can be reversed, not a rupture. What works:

Hi [name], I'm pausing work on [X] from today until invoice [number] is settled. Nothing is deleted and nothing is lost; everything picks up exactly where it stopped as soon as payment clears. Happy to get on a call today if it's useful.

Three things that sentence does. It's specific. A named invoice and a named date, not a mood. It's reversible. You've described a condition, not a punishment. And it's calm, which is the part people find hardest and the part that most affects whether you get paid, because the person reading it usually isn't the person who decided not to pay you. You want them on your side inside their own organisation.

What doesn't work: continuing to deliver while sending reminders. It reads, accurately, as the invoices are optional. Nobody prioritises a supplier whose service continues regardless. If nothing changes when the invoice goes unpaid, nothing has to change on their side either. That's the whole game.

The leverage Indian MSMEs actually have

Page one of the search results does not cover this, because most of what ranks is written for a US freelancer and stops at "consider a collections agency."

If you're a micro or small enterprise in India with valid Udyam registration, the Micro, Small and Medium Enterprises Development Act, 2006 gives you three things an ordinary creditor does not have.

A statutory payment ceiling. A written agreement can set a payment period, but it cannot exceed 45 days from acceptance or deemed acceptance. With no written agreement, the period is 15 days. This is a cap, not a default. A contract clause saying "payment within 90 days" does not override it for a protected supplier.

Compound interest, at a punitive rate. In the government's own words: "The buyer is liable to pay compound interest with the monthly rests to the supplier on the amount at the three times of the bank rate notified by RBI in case he does not make payment to the supplier for his supplies of goods or services within 45 days of the acceptance of the goods/service rendered" (MSME Samadhaan). Three times the RBI bank rate, compounded monthly, is not a token late fee. Look up the current bank rate on the RBI site rather than trusting any figure quoted in an article, including a recent one. It moves.

A forum with a deadline. References go to the Micro and Small Enterprise Facilitation Council through the Samadhaan portal, and "every reference made to MSEFC shall be decided within a period of ninety days from the date of making such a reference." A ninety-day statutory clock is a materially different proposition from ordinary civil litigation. The filing is online.

There's a fourth lever. It's the one that actually moves money, because it costs the buyer something on a timeline they care about. Section 43B(h) of the Income-tax Act, inserted by the Finance Act 2023 and applicable from assessment year 2024-25, provides that any sum payable to a micro or small enterprise beyond the time limit in Section 15 of the MSMED Act is deductible only in the year it is actually paid (Taxmann: FAQs on Section 43B(h)). Plain terms: if they don't pay you inside the window, they cannot claim your invoice as an expense in that year, and their taxable profit goes up.

Two constraints on all of this. Both are absolute:

  • Micro and small only. Medium enterprises aren't covered. As the same source puts it, "only micro and small enterprises are considered suppliers for the purpose of Section 43B(h). Medium enterprises are not regarded as suppliers."
  • Registration is the gate. "Supplier" is defined by reference to having filed the memorandum. That's Udyam Registration. Unregistered, none of the above is available to you. Which is the whole argument for doing it on a quiet afternoon rather than an urgent one.

Used well, this is a sentence in an email, not a lawsuit: as a Udyam-registered micro enterprise, this invoice falls under the MSMED Act's 45-day provision, and I'd rather resolve it directly than through a Samadhaan reference. Most finance teams know exactly what that means. Many of them would rather pay you than explain a 43B(h) disallowance to their auditor.

I'm not a lawyer and this isn't legal advice. Read the primary sources, then talk to your CA. Who, if you're Udyam-registered, has almost certainly already had this conversation with a client on the other side of it.

The line you should not cross

You'll often be holding something. Their ad accounts. Their analytics. Their domain. Their dashboards. A database. The credentials to systems their business runs on.

Withhold your labour. Do not withhold their assets.

The distinction isn't squeamishness. It's self-interest layered on top of the ethics. Refusing to do further work is a contractual position that any council, court or reasonable observer will understand instantly. Locking a client out of their own advertising account, deleting a live campaign, holding customer data hostage. Avoid all of that. Doing any of it converts you from the wronged party into the party with a problem. It can expose you to claims that dwarf the invoice you were owed. The one situation where you have unambiguous moral high ground is the one you forfeit by doing this.

This cuts both ways. It's worth knowing which assets you're actually holding before the argument starts, not during it. The access audit every founder should run once a year is the same inventory taken from the other side of the table.

Adjacent things to also not do. Publicly naming them while the matter is live. Invoicing a surprise late fee that was never in the contract. Accepting a "settlement" at 60% purely to end the discomfort. That last one feels like closure. It's the most expensive option on the list. It prices your work for every future client who hears about it, and clients talk to each other more than you think. The discount you took to end one bad month becomes the anchor number the next buyer starts negotiating from.

After it resolves, one decision remains

If they pay: decide, deliberately and while the memory is fresh, whether you want them back.

The useful test isn't whether they eventually paid. It's what they did while not paying. A client who called, explained, and proposed a schedule under real cash pressure has told you something good about themselves. That's often a relationship worth keeping, on tighter terms. Advance payment. Smaller milestones. A shorter leash. A client who went silent, disputed quality retroactively, or made you chase to the point of a formal notice has also told you something. It will be true again. Revenue from that client isn't revenue. It's a loan you keep issuing.

Then change the contract. One clause, in every agreement from now on: payment terms stated in days, a defined right to suspend services on non-payment after a stated period, and (if you qualify) your Udyam registration number on every invoice. That last detail is not decorative. It puts the buyer's finance team on notice of exactly which regime the invoice sits under, before anything goes wrong. Which is when notice is worth something.

One unglamorous point to finish. The reason a late invoice becomes an emergency is almost never the invoice. It's that there was no buffer behind it. A business with three months of costs in the bank negotiates from a completely different position than one that needs this payment to make salary on the 30th. It also makes better decisions as a result, because it can afford to stop work at day 21 instead of day 60. That buffer is the cheapest leverage available to you. The only one that works with every client, in every jurisdiction, without filing anything. The emergency fund argument applies to businesses at least as much as to people. If you're not sure what your real monthly cost base is, reading your own P&L is the place to start.

FAQs

What should I do first when a client stops paying?

Find out whether they cannot pay or will not pay. Rule out administration before either. A large share of unpaid invoices are stuck behind a missing PO number, a departed contact, or an approval queue. One phone call resolves those. A client who cannot pay is a payment-plan conversation. A client who will not pay is a recovery process. The responses are opposite. Diagnose before you escalate.

When should I stop working for a non-paying client?

Around 21 days past due, or when the unpaid amount reaches a level that would hurt to lose. Whichever comes first. Say it in writing. Name the specific invoice. Make it reversible: work resumes when payment clears. Continuing to deliver while sending reminders teaches the client that your invoices are optional.

Can I hold a client's ad accounts or data until they pay?

Withhold your labour, not their assets. Pausing work is a contractual position anyone will understand. Locking a client out of their own accounts, deleting live campaigns or holding customer data can expose you to claims larger than the invoice. It also turns you from the wronged party into the party with a problem. It's the fastest way to lose an argument you were winning.

What is the 45-day MSME payment rule in India?

Under the MSMED Act, 2006, a written agreement may set a payment period but it cannot exceed 45 days from acceptance or deemed acceptance of the goods or services. With no written agreement, the period is 15 days. Beyond that, the buyer is liable for compound interest with monthly rests at three times the RBI bank rate. It applies to micro and small enterprises with valid Udyam registration.

Do I need Udyam registration to use the MSME delayed-payment provisions?

Yes. "Supplier" under the Act is defined by reference to having filed the memorandum. That's Udyam Registration. An unregistered business is an ordinary creditor with an ordinary contract dispute. Registration is free and quick. It cannot be applied retroactively to help with an invoice that has already gone bad. Do it before you need it.

What is Section 43B(h) and why does it make clients pay faster?

It provides that a sum payable to a micro or small enterprise beyond the MSMED Act time limit is deductible only in the year it is actually paid. In practice, a buyer who holds your invoice past the window cannot claim it as an expense that year, so their taxable profit rises. It applies from assessment year 2024-25 and covers micro and small enterprises only. Not medium. That tax consequence often moves money faster than any reminder does.

Should I take a partial settlement to close it out?

Rarely. Almost never purely to end the discomfort. A discount accepted under pressure prices your work for every future negotiation, and word travels between clients. If a genuine cash-flow problem is behind it, a payment schedule at the full amount is a better instrument than a haircut. It keeps the number intact and gives them a way to honour it.

Does the relationship survive this?

Sometimes. The test is what they did while not paying, rather than whether they eventually paid. Someone who called, explained and proposed a schedule under real pressure is often worth keeping on tighter terms. Someone who went silent or retroactively disputed quality has shown you a pattern that will repeat.

Key takeaways

  • Diagnose first: can't pay, won't pay, or nobody knows. The third is more common than you think.
  • Udyam registration is the gate to every statutory protection. Do it on a quiet afternoon.
  • Escalate in a real sequence. Each step must make the next one credible.
  • Stop work at around day 21, in writing, with a resumption condition.
  • Withhold your labour, never their assets.
  • In India, the 45-day rule, compound interest at three times the RBI bank rate, the 90-day MSEFC clock and Section 43B(h) are all real leverage. None of it is available unregistered.
  • A cash buffer is what lets you stop at day 21 instead of day 60.

A client who has stopped paying is the obvious case for ending a relationship. The visible one. The one nobody has to argue about, because the ledger already made the argument for you. The much more common case, and the one this post is not about, is the client who keeps paying and should still be fired, because the account is quietly costing you more than the invoice is worth. The behavioural signals to watch for are in when to fire a client: the four signals, and why revenue is never one of them.

Source: dev.to

arrow_back Back to News