Enforcing payment means picking a lever: a late-fee clause, a freelance-payment law like New York's or Illinois's, a commercial collections agency, or small claims. Each one depends on someone else acting — a collector, a court, a client's willingness. None of them touch the invoice already lost. The one lever that doesn't need anyone's cooperation is built into the code itself, before it ships.
You've sent the invoice. You've sent the follow-up. Now you're typing how to enforce payment as a freelancer into a search bar at 11 p.m., because asking nicely already failed.
TL;DR
Enforcing payment means picking a lever: a late-fee clause, a freelance-payment law like New York's or Illinois's, a commercial collections agency, or small claims. Each one depends on someone else acting — a collector, a court, a client's willingness. None of them touch the invoice already lost. The one lever that doesn't need anyone's cooperation is built into the code itself, before it ships.
You Did Everything Right, and You're Still Not Paid
You delivered on time. You sent the invoice with clear terms. The first follow-up was polite. The second got a "sending this week." The third got nothing.
That's not a sign you handled this badly. It's what happens once working code has already changed hands — the client has what they need, and every tool you reach for next (a firmer email, a legal threat, a lawyer) costs you time and money before it gets you a cent back. If this is the first time a client's gone quiet on you entirely, start with the immediate playbook before coming back here for the enforcement mechanics.
There's a piece of that third email you haven't sent yet, and it isn't a nicer version of the first two.
How to Enforce Payment as a Freelancer: The Four Real Levers
Past the follow-up email, four things actually exist:
A demand letter, written the right way.
A freelance-payment statute, if one happens to cover your client.
A commercial collections agency.
Small claims court.
One of the four costs you money up front before it earns you any back — we'll get to which one, and how much.
Does the FDCPA Protect Freelancers From Non-Paying Clients?
No. The Fair Debt Collection Practices Act defines "debt" as an obligation arising from a transaction for "personal, family, or household purposes" — consumer debt, full stop (FTC). A client's invoice for freelance work is a commercial debt. That cuts both ways: no federal rulebook restricts how a collections agency can pursue your client on your behalf, but there's also no federal law that makes a non-paying business answer to you the way the FDCPA can make a collector answer to a consumer. You're on your own, for better and worse.
Freelance-payment laws, where they exist
New York City's Freelance Isn't Free Act requires a written contract on any deal worth $800 or more, sets payment due within 30 days if the contract doesn't name a date, and allows double damages plus attorney's fees in individual cases — with civil penalties up to $25,000 for hiring parties who do this repeatedly (nyc.gov).
Illinois passed its own version in 2024: a written contract required once work crosses $500 in a 120-day period, payment due within 30 days by default (Illinois Department of Labor). California has a comparable law on the books too. None of them help you if your client sits outside their jurisdiction — these statutes protect freelancers doing business under that state or city's law, not freelancers everywhere.
The demand letter that isn't a fourth follow-up
Here's the piece the first three emails were missing: a dollar figure, a deadline measured in business days (ten to fifteen is standard), the contract clause or statute you're invoking, and a named next step if the deadline passes — collections, small claims, or (where a freelance-payment law applies) the fact that pattern nonpayment can trigger regulatory penalties, not just a lawsuit from you. A demand letter that skips any of those four reads exactly like the emails that already got ignored.
Commercial collections agencies
This is the lever that costs money before it makes you any. Commercial collection agencies typically work on contingency — 10% to 25% of whatever they recover on larger accounts, climbing to 35% or higher on debts under roughly $3,000 or older than six months, since older and smaller accounts are harder to collect (Southwest Recovery Services). Run the math before you sign anything: a $2,000 invoice at a 35% contingency nets you $1,300 if — and only if — the agency actually collects, which isn't guaranteed.
Small claims and beyond
For local clients, small claims is often the cheapest formal option, though caps and timelines vary by state and cross-border cases run into their own wall. We've broken down the full escalation path — demand letter to small claims to arbitration, and what each stage actually costs — in a separate post.
The same week, two versions
Every One of These Levers Needs Someone Else to Move First
Line them up and the pattern is obvious. A demand letter works if the client fears the consequence enough to act. A freelance-payment law works if your client happens to sit inside its jurisdiction. A collections agency works if a stranger decides your file is worth their time. Small claims works if a court has an open date and the client actually pays the judgment once you win. All four activate after delivery, and all four hand the decision to somebody who isn't you.
That's the real problem, and it isn't the client. It's that finished, working software changed hands before the invoice cleared. Once that happens, every lever you have left runs through someone else's calendar, budget, or goodwill.
There's a category of lever none of the four above belong to, and it's the only one that doesn't wait on anyone else's schedule.
The One Lever That Doesn't Need Anyone's Cooperation
DevAegis builds that lever into the delivery itself. You build normally — no change to how you write code. Before you ship, the DevAegis CLI encrypts the compiled build output with AES-256-GCM; the decryption key stays with you, not embedded in what you hand over. It works with Next.js, Vite, Create React App, Express/Fastify, and generic Node projects. Full setup details live in how to protect your code as a freelancer.
The client deploys on their own infrastructure. A small DevAegis runtime checks in with the DevAegis API. In good standing, it decrypts in memory and the app boots like normal software, because that's what it is.
Mark the project unpaid, and you flip one toggle in the dashboard. The runtime stops decrypting. The client's build stops booting — they get a payment screen where their site used to be. Mark it paid, and access restores automatically. No demand letter, no collector, no court date.
This has to be disclosed in the client agreement as a condition of delivery before you ship — you're not hiding anything in their codebase. You're licensing software, and the license is conditional on payment, the same way every SaaS company already operates. We've written up the legal shape of that disclosure in detail. Set it up at devaegis.com/signup before your next delivery goes out.
Be clear about what this doesn't do: it won't get you the $2,000 you're chasing right now if that project already shipped unprotected. Nothing retroactively encrypts code a client already holds in readable form — the lever only exists if it's built in before delivery. What it changes is every invoice after this one.
Two Versions of the Same 90 Days
Same delivery date. Same invoice. Same silence through day 45. Here's where the two paths split, and what each one costs by day 90.
The One Next Action
Before you deliver your next project, run the DevAegis CLI as the final step of your build and add the license condition to your contract. That's the one change that makes every invoice after this one enforceable without a single follow-up email. Start at devaegis.com/signup.
FAQ
Can I charge interest or late fees on an unpaid freelance invoice? Yes, if your contract says so. Most states allow a stated late-fee or interest clause, and freelance-payment laws like Illinois's and New York's require a written payment due date you can point to. Without a contract clause or statute behind it, adding a fee after the fact has no legal weight — the client can simply refuse it, and you're back to the same enforcement problem, now with an extra line item.
Does the Fair Debt Collection Practices Act protect me if a client stops paying? No. The FDCPA covers debts for personal, family, or household purposes. A client's invoice for freelance work is a commercial debt, so neither you nor a collections agency working your case is bound by — or protected by — its rules.
Is it worth hiring a collections agency for a $2,000 invoice? Usually not on its own. A typical contingency fee of 25% or more on a smaller or older account means you'd net under $1,500 even on a full recovery, with no guarantee of success. It can be one part of a broader push alongside a demand letter and, for local clients, small claims — but it isn't a fast or cheap lever by itself.
What's the fastest way to enforce payment on a project I've already delivered unprotected? There isn't a fast one. A demand letter, a collections referral, and a small-claims filing all take weeks to months and depend on someone else acting. If the code shipped without a payment-dependent kill switch already built in, that leverage can't be added retroactively — what's left are the reactive options above.
Does a freelance-payment law like the Freelance Isn't Free Act apply if my client is out of state? No. These laws are jurisdictional. New York City's, New York State's, and Illinois's freelance-payment protections apply based on where the work is performed or the hiring party is located under each specific statute — not where you live — so a client outside those jurisdictions won't be covered by them.
Key takeaways
- The Fair Debt Collection Practices Act only covers consumer debt — a freelance invoice for client work is a commercial debt, so neither you nor a collector working it is bound by (or protected by) the FDCPA.
- New York City, New York State, and Illinois all now require written contracts and set default 30-day payment deadlines for freelance work, with real penalties for violations — but coverage stops at their borders.
- Commercial collection agencies typically take 10% to 25% of what they recover on larger accounts, climbing to 35% or more on debts under about $3,000 or older than six months.
- Every enforcement tool available today — demand letters, collections agencies, freelance-payment statutes, small claims — activates after the client already has the finished work and depends on someone else choosing to act.
- A kill switch built into the delivery itself is the one enforcement mechanism that needs no cooperation from a collector, a court, or the client — but it only works if it's installed before the code ships.
Frequently asked questions
Straight answers to what people ask about how to enforce payment as a freelancer.
You probably cannot fix this one. You can make sure it is the last.
The reason this invoice is hard to recover is that the code was working on their server before the money arrived. DevAegis moves payment in front of that moment, so the next client never gets the same position.
Protect your next delivery