It’s the nightmare scenario: You deliver a project that meets all the requirements, and the client says: "I just don't like it. I’m not going to pay the final invoice."
Is this legal? Can they do that?
1. The "Satisfaction Clause" Trap
The answer depends entirely on your contract. If your contract has a clause that says "Payment is subject to client satisfaction," you have accidentally given the client a "Get Out of Jail Free" card.
Before you sign your next agreement, use our AI Contract Scanner to spot "Subjective Acceptance" language. You want to replace it with "Objective Acceptance" (e.g., "Payment is due upon delivery of the requirements listed in Section 1").
2. Revisions vs. Rejection
Most disputes happen because a client confuses "I want a change" with "This is unusable." Your invoice line items should clearly state how many revisions are included. If they want to go in a completely different direction, that is a new project, not a reason to withhold payment for the work already done.
3. Your Leverage
If the client hasn't paid, they do not own the copyright. Legally, they cannot use the work. If you see them using your designs or code on their live site while the invoice remains unpaid, you can issue a DMCA Takedown notice.
Frequently Asked Questions (FAQ)
What is a 'Reasonable' rejection?
In court, "reasonable" usually means: did the freelancer follow the brief? If you were hired to build a blue website and you built a red one, the rejection is reasonable. If you built a blue one and they changed their mind, it is not.
Should I offer a partial refund to end the dispute?
Only as a last resort. If you offer a refund, make the client sign a "Settlement and Release" agreement stating they will not leave a bad review and they surrender all rights to the work.
How do I prevent this in the future?
Break the project into milestones. If the client "dislikes" Phase 1, you stop work before wasting 40 hours on Phase 2. This keeps your financial risk low.