Payment Terms in MSME Service Agreements in India

Why MSME payment terms need careful drafting

Small service providers often work with larger clients that have stronger bargaining power and slower payment cycles. The client may insist on 60-day, 90-day, or "after internal approval" payment terms. The service provider may accept because it needs the business. But if the provider is a micro or small enterprise registered under the MSME framework, Indian law provides specific delayed payment protections. The Micro, Small and Medium Enterprises Development Act, 2006 includes provisions requiring buyers to make payment to micro and small enterprises within the agreed period, with an outer limit of 45 days from the day of acceptance or deemed acceptance. Delayed payments may attract interest consequences, and disputes may be referred through the statutory mechanism under the Act. These protections are important, but contracts should still be drafted clearly. A statutory right is stronger when the invoice, delivery, acceptance, and payment timeline are well documented. The payment clause should therefore be designed not only for legal recovery but also for day-to-day billing clarity.

Fee structure: fixed fee, retainer, milestone, or hourly

The agreement should clearly state how the fee is calculated. Fixed-fee arrangements work well when scope is clear. Retainers work for ongoing monthly services. Milestone payments work for projects with defined phases. Hourly or daily rates work where effort is uncertain, but they require time records and approval processes. For a fixed-fee project, the contract should state whether the fee includes all deliverables, how many revisions are included, whether taxes are extra, and what work is excluded. For a monthly retainer, the contract should state what services are included each month and whether unused service hours carry forward. For milestone projects, the agreement should identify what event triggers each payment: signing, submission, approval, completion of design, delivery of beta version, go-live, report submission, or handover. A payment clause should never depend only on vague "client satisfaction". Satisfaction can be subjective. It is better to define measurable acceptance criteria.

Advance payments and milestone payments

Advance payments protect service providers from starting work with no financial commitment from the client. For many MSMEs, an advance also covers initial time, resource blocking, vendor costs, and opportunity cost. The agreement should state whether the advance is refundable, adjustable, or non-refundable after work begins. Milestone payments are useful because they divide risk. The service provider receives payment as work progresses, and the client can review defined stages before releasing the next amount. This is particularly useful for website development, software projects, branding, content projects, consulting assignments, training programs, and marketing campaigns. For high-value or long-duration projects, the agreement may state that work on the next milestone will begin only after payment for the previous milestone is received. This prevents the common situation where the service provider completes the entire project but remains unpaid for earlier stages.

Invoice process and due date

The contract should define when invoices may be raised and when payment becomes due. It should state whether invoices are due within 7, 15, 30, or another number of days from invoice date or receipt. If the supplier is an MSME, the clause should be aligned with the MSMED Act and should not casually accept terms beyond the statutory outer limit where the Act applies. The invoice clause should also include GST, TDS, purchase order numbers, billing addresses, supporting documents, and email addresses for submission. Many payment delays happen because the client later says the invoice was not submitted to the correct department or did not include the right internal reference. A practical contract reduces these excuses. The agreement should also state that payment will be made to the bank account mentioned in the invoice or agreement and that changes to bank details must be confirmed through authorized communication.

Acceptance and deemed acceptance

Acceptance is critical. If payment depends on acceptance but the contract does not define the acceptance process, the client may delay payment by simply not responding. The agreement should state how deliverables are submitted, how long the client has to review, what counts as rejection, and what happens if the client remains silent. A deemed acceptance clause protects the service provider. It may say that deliverables will be deemed accepted if the client does not raise specific written objections within a defined review period, such as 5, 7, or 10 business days. The objection should identify specific defects against the agreed scope. General dissatisfaction or new requirements should not delay payment for completed work. Deemed acceptance is especially useful for creative and digital work where clients may delay approvals indefinitely. It does not prevent genuine quality review. It simply requires timely and specific feedback.

Late payment consequences

The payment clause should state what happens if payment is delayed. Possible consequences include interest, suspension of services, withholding of further deliverables, pause on timelines, recovery costs, legal notice, and termination for non-payment after notice. For MSME suppliers covered by the MSMED Act, delayed payment may attract statutory consequences. The contract should not undermine these rights. It may expressly state that the supplier reserves rights under the MSMED Act where applicable. Suspension rights are often more practical than immediate litigation. The clause may say that if payment remains overdue after a notice period, the service provider may suspend work until payment is received, and timelines will be extended accordingly. This prevents the client from receiving ongoing service while ignoring invoices.

GST, TDS, and tax clarity

The agreement should state whether fees are inclusive or exclusive of GST. If GST is applicable, the service provider should issue a tax invoice. If the client is required to deduct TDS, the agreement should state that TDS will be deducted in accordance with applicable law and that the client will provide the TDS certificate within the prescribed timeline. Tax clauses should be drafted carefully because service providers often calculate fees based on expected net receipts. If GST, TDS, reimbursements, withholding, and deductions are not clarified, payment disputes arise even when the base fee is agreed. For reimbursable expenses, the agreement should state whether prior approval is needed, what documentation is required, and whether reimbursements are at actual cost.

Disputed invoices

A fair payment clause should include a disputed invoice process. The client should raise disputes within a defined period and identify the specific portion disputed. The undisputed portion should still be paid on time. This prevents a client from holding back the entire invoice because of a small disagreement. The agreement may also require senior-level discussion before escalation. For ongoing business relationships, this can resolve payment issues without immediately sending legal notices.

MSMED Act protection

The MSMED Act provides important support for micro and small enterprises supplying goods or services. The buyer must make payment on or before the date agreed in writing, but the agreed period cannot exceed 45 days from the day of acceptance or deemed acceptance. If payment is delayed, interest consequences may apply, and the supplier may approach the Micro and Small Enterprises Facilitation Council for resolution. However, service providers should not rely only on statutory language. They should maintain clean documentation: Udyam registration details, signed contract, accepted proposal, purchase order, delivery proof, invoice, email submission, reminders, approval messages, and proof of work. Strong paperwork improves leverage.

Common drafting mistakes

Common mistakes include no advance payment, vague milestone triggers, payment after "complete satisfaction", no deemed acceptance, no late payment consequences, no GST clarity, no TDS clause, no suspension right, no MSME reference, no dispute process, and no record of approved changes. Another mistake is starting work based only on verbal approval. Even an email confirmation is better than no record, but a proper agreement is stronger.

How Inamdar Legal can assist

Inamdar Legal assists with drafting and reviewing payment clauses in service agreements, MSME vendor agreements, agency retainers, consulting agreements, software development contracts, SOWs, purchase order terms, and freelancer agreements. We help align payment triggers, acceptance, MSME protections, GST, TDS, and late payment remedies.

When to Review This

• Fee structure, advances, and milestones
• Invoices, GST, TDS, and reimbursements
• Acceptance, deemed acceptance, and due dates
• MSME delayed payment protections