Direct Answer For Founders

Indian startups should write customer payment terms in a way that makes the cash event clear: what is billable, when the invoice can be raised, when GST applies, what TDS may be deducted, what counts as acceptance, when payment is due, what happens if payment is delayed and how disputes are handled.

This sounds operational, but it quickly becomes legal, tax and diligence work. A startup can show impressive revenue and still have weak cash collection because the contract says “payment after completion” without defining completion. Enterprise customers may withhold payment because the purchase order is missing, the GSTIN is wrong, acceptance is open, the milestone is disputed, TDS is not reconciled or change requests were never priced.

A founder should treat payment terms as part of the product’s commercial architecture. The best contract is not the longest contract. It is the one that lets the company deliver, invoice, collect, reconcile and prove revenue quality without a monthly firefight.

Why Payment Terms Matter More Than Founders Think

Customer Payment Terms Checklist

1. Define the invoice trigger

Tie invoicing to objective events: signing date, purchase order receipt, subscription start, monthly billing period, sprint completion, delivery of agreed reports, go-live date, shipment dispatch, user activation, milestone certificate or written acceptance. Avoid vague triggers such as “after satisfactory completion” unless the acceptance process is equally clear.

2. Write the due date in calendar terms

“Payable within 15 calendar days from invoice date” is clearer than “payable soon” or “as mutually agreed”. If a large enterprise insists on 45, 60 or 90 days, model the working-capital impact before signing. A long payment cycle is a financing decision, not just a customer-success compromise.

3. Separate base fee, GST and reimbursables

State whether fees are exclusive of applicable taxes. Mention that GST invoices will be issued as per law and that the customer must provide correct GSTIN, legal name, billing address, place-of-supply information, purchase order and finance contact before invoicing. Reimbursables should be pre-approved, evidenced and billed with supporting documents.

4. Handle TDS without monthly arguments

If the customer deducts TDS, the contract should say that payment net of legally applicable TDS will not be treated as short payment if the customer provides the required TDS certificate or tax-credit trail. If the customer deducts TDS at a disputed rate, the parties should have a reconciliation process rather than letting the invoice sit open forever.

5. Add an acceptance clock

For services, software implementation, design, custom development or consulting work, use a review window. Example: the customer must either accept deliverables or give specific written objections within seven business days; otherwise the deliverable is deemed accepted for invoicing. The objection must identify the missed requirement, not simply say “not satisfactory”.

6. Protect against full invoice holdbacks

If only part of an invoice is disputed, the undisputed amount should still be paid on time. Without this, one small disagreement can block the entire receivable. This clause is especially important for implementation projects, retainers and enterprise subscriptions with add-on services.

7. Price change requests

Any work outside the agreed scope should require written change approval. The approval should mention the added fee, timeline impact and payment milestone. If change requests are free by habit, the startup’s margin will quietly move from the contract to the customer.

8. Link suspension rights to overdue invoices

A startup should decide whether it can suspend access, pause work, stop new deliverables or move the account to advance billing if invoices are overdue. The clause should be commercially sensible. Suspension rights are useful only when the team can enforce them without harming customer relationships or regulatory obligations.

9. Keep collection records like a diligence file

Store signed contracts, purchase orders, invoices, delivery proof, acceptance emails, GST returns, TDS certificates, credit notes and follow-up records together. Investors often review receivables quality before trusting revenue.

GST Invoice Readiness

GST mistakes often delay otherwise valid payments. Under GST invoice rules, tax invoices have prescribed particulars and timing requirements. For services, CBIC’s invoice rules state that an invoice is generally issued within thirty days from the date of supply of service, with specific exceptions for certain financial, insurance, banking and telecom cases. Founders should confirm exact applicability with their tax advisor, especially for mixed supply, exports, recurring services and milestone contracts.

Do not let the sales team promise “invoice later” without finance review. GST timing, revenue recognition, customer ITC and collection planning should be aligned before the deal is signed.

TDS Reconciliation: Prevent Short-Payment Confusion

Many startups waste time chasing a “short payment” that is actually TDS deducted by the customer. The contract should require the customer to deduct only legally applicable TDS, deposit it correctly and provide the TDS certificate or Form 26AS/AIS trail within the applicable timeline. The startup’s finance records should separate invoice value, GST, TDS, net amount received and balance actually overdue.

MSME Payment Angle: If The Startup Is A Micro Or Small Enterprise

If the startup qualifies as a micro or small enterprise and has Udyam registration, delayed-payment rules under the MSMED Act may become relevant. Section 15 of the MSMED Act provides that payment should be made by the agreed written date, and the agreed period cannot exceed forty-five days from the day of acceptance or deemed acceptance. Section 16 deals with interest for delayed payment.

This does not mean founders should rely on legal escalation as a sales strategy. It means payment terms should be drafted with awareness of the MSME framework, especially where enterprise customers push long cycles. The purchase order, work order, acceptance record, invoice and Udyam details should be preserved if the startup may later need to demonstrate the payment timeline.

For buyers, the MSME angle also matters because delayed payments to micro and small enterprises can have tax and reporting consequences. For founders selling to larger businesses, a clear MSME status disclosure and clean acceptance trail can reduce back-and-forth with the buyer’s finance team.

Payment Models By Startup Type

Clause Bank: Founder-Friendly Concepts To Discuss With Counsel

These are not copy-paste legal clauses. They are drafting concepts founders can take to counsel and commercial teams.

Investor Diligence: How Receivables Are Reviewed

Investors do not only ask how much revenue was booked. They ask whether it can be collected and whether future revenue will behave the same way. A revenue line backed by signed contracts, clean invoices and timely collections is stronger than a revenue line backed by verbal work orders and overdue invoices.

A Simple Collections Operating Rhythm

• Before signing: confirm buyer entity, GSTIN, PO process, payment cycle, finance contact and required invoice format.
• Before delivery: confirm scope, acceptance criteria, customer dependencies and milestone evidence.
• On invoice date: send invoice, PO reference, delivery proof and payment instructions in one email.
• Seven days before due date: confirm invoice is accepted and scheduled for payment.
• On due date: escalate politely with finance and business owner if payment is not received.
• After overdue: track reason codes: PO issue, GST issue, TDS issue, acceptance issue, cash issue or dispute.
• Monthly: review ageing, disputed invoices, top customer exposure, credit notes and collections forecast with founders.

Seven-Day Cleanup Plan

Mistakes To Avoid

• Starting work before purchase order, statement of work or email approval is in place.
• Accepting long payment cycles without checking runway impact.
• Using “payment after completion” without defining completion and acceptance.
• Treating TDS deduction as default when valid tax credit proof is available.
• Raising invoices with wrong GSTIN, address, place of supply or tax treatment.
• Allowing indefinite customer acceptance timelines.
• Letting customers hold the full invoice for a small disputed item.
• Not charging for change requests outside scope.
• Keeping receivables follow-ups only in WhatsApp or phone calls.
• Showing revenue to investors without receivables ageing and collection context.

Sources

• Income Tax Department TDS overview: Tax Deduction at Source
• GST portal: GST official portal
• CBIC GST invoice rules: Tax Invoice, Credit and Debit Notes
• CBIC GST Act Section 31, tax invoice: Section 31
• GST e-invoice system: e-Invoice portal
• India Code, MSMED Act, 2006: Micro, Small and Medium Enterprises Development Act, 2006
• Goods and Services Tax Council: GST Council

FAQ Section

Founder / Business Takeaway

Revenue is not real operating strength until the startup can invoice it, collect it and explain it during diligence. The Best CS Firm In India mindset is to make payment terms boringly clear before cash gets stuck.