Disputes need facts: agreement excerpts, delivery proof, and approval records.
8 min readInvoice dispute paths
| Dispute claim | Your evidence | Response path |
|---|---|---|
| "I never approved this" | Approval message or signed scope | Point to written acceptance |
| "Quality is wrong" | Brief + delivery checklist | Fix only what the brief required |
| "Too expensive" | Quote and rate agreement | Restate the agreed fee; no silent discount |
| "Pay later / partial" | Payment schedule | Offer a written revised schedule once |
Why disputes happen
Common triggers:
- Client forgot what was in scope
- Approver changed mid-project
- Work finished but approval never formalized
- Currency or fee surprise on their side
Filipino VAs lose disputes when records live only in chat apps with no export.
Step-by-step response
- Pause new work until core facts are clear (if amount is large).
- Open your agreement and the recap emails.
- List deliverables with dates and approval quotes.
- Send one calm email with attachments or links.
- Propose resolution: partial pay, split invoice, or call with agenda.
Sample dispute reply
Hi [Name], I want to resolve this cleanly. Invoice [#] covers [items] per our agreement dated [X] and your approval on [date] ("approved"). Attached are [files/screenshots]. I am open to a 15-minute call to walk through line items. Please suggest times.
What to save before disputes
- Signed or confirmed scope
- Milestone approval emails
- Time logs if hourly
- Version history for deliverables
- Payment terms they accepted
Common mistakes
- Long WhatsApp arguments with no summary email after.
- Deleting messages out of frustration.
- Accepting "we will pay later" with no new date in writing.
- Threatening actions you do not plan to take.
Final thoughts
Most invoice disputes are memory problems. Documentation turns them into solvable math. Stay professional. Many good clients pay once they see the trail.
How Salag helps
- Freelance Readiness Checker. Strengthen records before disputes arise.
- Late Fee Calculator. Show how delays compound when disputes drag on.
- Scam Pattern Detector. Spot bad-faith dispute patterns early.
Move safer. Not faster.
In short
When an invoice dispute freelance situation hits, gather three things: what the agreement said, what you delivered, and what they approved in writing. Respond with facts and a short timeline. Avoid long emotional threads.
Common questions
When an invoice dispute freelance situation hits, gather three things: what the agreement said, what you delivered, and what they approved in writing. Respond with facts and a short timeline. Avoid long emotional threads.
Write down what you agreed on and what changed. Do not start new work on vague terms.
Use plain English, confirm in writing, and set clear hours. Clients hire you for reliability, not cheap labor.
Put the basics in your agreement or a recap email before billable work starts. Bigger projects need fuller terms.
Stay warm but firm. Offer options inside a clear process, like a change order or a short written recap.
ALIGN means: capture facts, compare to your agreement, name tradeoffs, confirm in writing, and save the decision for next time.
Escalate when the same problem repeats: unpaid extras, late approvals plus new asks, or refusal to confirm in writing.
Yes. A clear email with tasks, dates, price, and limits beats a verbal yes every time.
Salag gives you tools and templates so you can set boundaries before small problems grow.
Use written recaps, scope trackers, and Salag tools like agreement builders and scope detectors.
Most recaps take five minutes after a call. That small step saves hours of arguing later.
Yes. Retainers need weekly change logs. Projects need milestone gates. Always compare new asks to written terms.
Pause billable work on unclear items. Send a narrow summary of what you will do. Save their reply either way.