Business & Compliance
Software Project Completed But Client Won't Pay: What Can You Do?
If you completed a software project and the client doesn't want to pay, the first step is to gather proof of agreement, project delivery, client approvals, and invoices raised but not paid. You can then try to recover the amount through a formal payment demand, legal notice, mediation, arbitration, or even a recovery suit, depending on the contract and nature of the dispute.
Do not just delete client data, block access, or disable the software without checking your contractual and legal rights, as it can lead to further liabilities
What to Do If Client Doesn't Pay After Software Delivery?
If your client doesn't want to pay after delivery of software, here are the things you need to do immediately:
- Go through the contract, SOW, or project agreement to understand payment terms, acceptance criteria, and the dispute-resolution clause
- Confirm what amount is still due, invoices raised, and any adjustment proposed
- Confirm that you indeed delivered what was agreed with the client
- Keep proof of project delivery, like deployment records, repository, and handover documents
- Keep proof of client approvals and communication, like emails, UAT confirmation, or meeting records
- Ask for the reason for non-payment from the client and get their response on what they think is wrong
- Send a reminder to pay with the details of the invoice and due date
- Review the dispute-resolution clause before going for arbitration, litigation, or other remedies
Can a client refuse to pay after software delivery?
A client may withhold payment on valid contractual grounds but cannot refuse payment merely because they dislike the developed software. The dispute resolution clause determines how disagreements are addressed and whether payment can be withheld or adjusted until resolution. Changes beyond the agreed scope may require a formal change request under the contract.
Under Sections 37 and 73 of the Indian Contract Act, 1872, parties must fulfil their contractual obligations, while compensation may be claimed for losses caused by a breach. A client's continued use of delivered software does not automatically exempt them from making the agreed payment.
What proof do I have that I completed the software project?
The developer should keep all the proof to show that they delivered the software project. This includes:
- Signed contract or SOW
- Project scope and requirements documents
- Milestones approvals
- Git commits or Repository
- Deployment records
- Emails confirming delivery
- Client acceptance messages
- UAT approvals
- Handover documents
- Invoices and payments
- Demo recordings
- Project management records
What if my client says that the software has a lot of bugs or is incomplete?
The developer should compare the software with the agreed scope of work and request a written list of defects. Genuine bugs should be distinguished from requests for additional features. The developer should review warranty terms, document reported issues, and offer necessary fixes under the contract.
Can I stop the client from using the software until they pay me?
It depends on the contract, licence terms, and applicable law. The developer should check whether usage rights depend on payment. Avoid disabling systems or deleting client data without assessing the legal consequences.
Should I send a legal notice to the client?
Yes, a legal notice can formally demand outstanding payment and specify a reasonable deadline. It should include project details, invoices, the amount due, and applicable interest, if justified. It gives the client an opportunity to settle the dispute before further legal action.
Can You Use Arbitration for an Unpaid Software Project?
Yes, if a valid arbitration clause applies. The developer can initiate proceedings under the Arbitration and Conciliation Act, 1996, to claim unpaid fees and legally recoverable losses. Both parties can present contracts, invoices, communications, and technical evidence.
Can You File a Recovery Suit Against the Client?
Yes, the developer can file a recovery suit for unpaid fees. Depending on the dispute's nature and specified value, the Commercial Courts Act, 2015, may apply. Contracts, invoices, delivery records, and client communications can support the claim.
Can You File a Summary Suit for an Unpaid Software Project?
Yes, a summary suit under Order XXXVII of the Code of Civil Procedure, 1908, may be available if the claim meets its legal requirements. The developer should verify the written agreement, payment obligation, and eligibility before choosing this procedure.
Can You Claim Interest and Compensation for Delayed Payment?
Yes, interest and compensation may be claimed where legally justified and supported by evidence. Sections 73 and 74 of the Indian Contract Act, 1872, address compensation for contractual breaches and stipulated sums. Recovery depends on the contract and applicable law.
What If the Client Is Using the Software but Still Hasn't Paid?
The developer should preserve evidence of software delivery, deployment, and usage. They should review the contract's payment, ownership, and licensing terms before pursuing recovery or other remedies. Avoid disabling systems or deleting data without legal assessment.
How Long Do You Have to Take Legal Action for Unpaid Software Development Fees?
Many money recovery claims have a three-year limitation period under the Limitation Act, 1963, but the starting date depends on the claim. Invoice due dates, payment milestones, acknowledgments, and part payments should be examined to determine the applicable deadline.
How Can Software Developers Prevent Payment Disputes in Future Projects?
Developers should use a written agreement defining the project scope, deliverables, payment milestones, acceptance criteria, and change-request process. The contract should also cover intellectual property, warranties, delayed payments, and dispute resolution. Maintaining invoices, approvals, and delivery records helps prevent disputes.
Software Project Payment Dispute: Legal Options Compared
Option | When It May Be Suitable |
|---|---|
Payment reminder | Initial payment delay |
Formal demand | Clear outstanding amount |
Legal notice | Client continues to avoid payment |
Mediation | Both parties are willing to settle |
Arbitration | Contract contains a valid arbitration clause |
Qualifying written payment claim | |
Payment dispute requires court resolution | |
Eligible Micro/Small Enterprise claims |
Legal Articles You May Like
- Software Development Agreement Checklist: 15 Essential Clauses to Include
- Client Agreements That Protect Your Business
- How Can Indian Businesses Recover Unpaid Payments From Foreign Clients?
Conclusion
An unpaid software project can lead to cash-flow and contractual issues, especially if the client receives the software. Developers should protect evidence of the deliverables, invoices and communications and firstly consider the payment and dispute clauses in the contract. Possible remedies include a demand, legal notice, mediation, arbitration, summary proceedings, recovery proceedings, or MSME remedies depending on the case.
Prompt action while safeguarding intellectual property rights and preventing unauthorised measures can enable developers to take legal action against unpaid amounts.
Disclaimer: This blog is for informational and educational purposes only and should not be construed as legal or professional advice. Laws are subject to change, and therefore, it is recommended to consult an experienced Corporate Lawyer before taking any action or entering into any agreements.
Frequently Asked Questions
Q1. What Can I Do If a Client Does Not Pay After Software Delivery?
Review the contract, retain delivery evidence, and request payment. If unresolved, consider a legal notice, mediation, arbitration, or recovery proceedings.
Q2. Can a Client Refuse Payment Because of Software Bugs?
A client’s right to withhold payment depends on the contract, the nature of the bugs, and the agreed acceptance criteria.
Q3. Can I Sue a Client for an Unpaid Software Project?
Yes, a developer may pursue recovery proceedings for unpaid fees, subject to the contract, evidence, and applicable law.
Q4. What Evidence Proves That I Completed a Software Project?
Relevant evidence includes contracts, invoices, source-code records, delivery documents, UAT approvals, emails, and client acceptance records.
Q5. What If There Was No Signed Software Development Contract?
Emails, messages, quotations, invoices, purchase orders, payment records, and approvals may help establish the agreement and its terms.