How to get paid for mixing and mastering

Nobody becomes a mixing or mastering engineer because they enjoy accounts receivable. But if you freelance for long enough, the pattern finds you: the work is done, the client is thrilled, the files are delivered, and then the invoice ages. A week. A month. The follow-up emails get more awkward with each round, because you're no longer negotiating: you're begging for money you already earned, with nothing left to withhold.

That last clause is the entire problem. Once the files are delivered, you're not a vendor anymore, you're a creditor. Every bit of leverage you had lived in the deliverable, and you gave it away for free. So this guide isn't about writing sterner emails. It's about restructuring the handoff so the question "will they pay?" gets answered before the masters leave your hands, not after.

The moment of leverage (and when engineers give it away)

A music project has exactly one moment where the incentives are perfectly aligned: the client wants the files, and you have them. Before that moment, they're motivated to be responsive. After it, paying you is a chore with no upside: the record is already uploading to the distributor.

Most non-payment isn't malice. It's entropy. The artist got busy, the band's money guy went on tour, the label's accounting runs net-45 and nobody told you. But entropy is enough: industry surveys of freelancers consistently find that a large share of invoices are paid late and a meaningful chunk are never paid at all. The engineers who don't have this problem aren't luckier. They just never let the deliverable and the payment come apart.

The files are the invoice. Deliver them and the invoice loses its teeth.

Terms that actually hold up

You don't need a contract that reads like a lease. You need three sentences, agreed before you open the session:

• The price and what it includes. The rate, and the number of revision rounds inside it. (One or two is standard; the exact number matters less than saying it. More on that in the approval workflow guide.)
• A deposit for new clients. 30 to 50 percent up front. A client who balks at a deposit is telling you something useful early, while it's still cheap to hear it.
• Finals on payment. The client can review and approve everything, and the deliverable files are released when the balance clears. Said plainly up front, nobody ever finds this unreasonable. Said for the first time when the invoice is late, it sounds like a hostage note.

That third term is the one this guide is really about, because for most engineers it's the missing one, and the tooling to enforce it gracefully hasn't existed. Your options were watermarks, MP3 previews, or trust.

Why watermarks and preview bounces backfire

The classic self-defence moves all share a flaw: they degrade the thing the client is supposed to be judging.

• Watermark beeps sit right on top of the material. The client is trying to decide whether the vocal sits right, through a tone that's louder than the vocal.
• Low-quality previews mean the client approves an MP3 and receives a WAV: they signed off on audio that is not the deliverable. For mastering in particular this is self-sabotage; a lossy encode changes exactly the things you were hired for.
• Both still need a second delivery step. After payment you're back to WeTransfer links and "did you get it?" emails, which is where version confusion breeds. (That failure mode has a guide of its own.)

The clean version of "finals on payment" separates listening from possession: the client streams the real master, at full quality, as many times as they want, and the download is what waits for the money.

The payment-gated delivery workflow

Here's the whole loop, in four steps. It's the same review-and-approval flow you should be running anyway, with one added property: the delivery page knows about the balance.

1. Agree the terms in the first email

Price, deposit, included revisions, finals on payment. Two sentences. The point isn't legal armor, it's that no step later in this list should ever be a surprise.

2. Review and approve on a link, not attachments

Send a review link where the client streams the work losslessly and pins feedback to the waveform. They hear everything. They possess nothing. When they approve a specific version, you have a recorded sign-off, and the only thing left between them and their record is the balance.

3. Put the balance on the delivery itself

Create the delivery with the amount due attached, itemised: the base rate, the extra revision round they added in week two, the 96 kHz alternate masters, the stems. Line items matter, because scope creep is the other way engineers lose money: work that was clearly extra somehow ends up inside the original quote. When each extra is a visible line on the delivery, that conversation never has to happen.

The client opens the delivery page and sees their files, the balance, and how to pay. The downloads are locked. Not hidden, not watermarked: right there, with a lock on them.

4. They pay, the files unlock

Two paths, and you should offer both:

• Card, instantly. If you connect a Stripe account, the delivery page gets a Pay button. The client pays at 2 a.m. on a Sunday, the downloads unlock on the spot, and the money goes straight to you. No waiting for you to wake up and confirm.
• Their way, with one click from you. Bank transfer, PayPal, Wise, a check if you must. Your payment instructions sit on the delivery page, the client taps a button saying the payment is sent, you get notified, and confirming it unlocks their files. The gate doesn't force anyone to change how they pay; it only changes when the files move.

In Soneam this is built into every plan, Free included, and the platform fee on your money is zero percent. Some competing tools run the same gate but take a cut of each transaction or paywall the feature; if you're comparing, the Soneam vs Filepass page covers the differences honestly.

"Can you just send them? I'll pay Friday."

You'll hear it, usually from someone you like. Here's the thing the lock changes: you don't have to say no. The delivery is already in their inbox. They can stream the approved masters right now, today, as much as they want. The only thing waiting for Friday is the download, which is exactly when they said the money would arrive. "It's all there waiting for you, it unlocks the moment the payment lands" is a complete answer, and it doesn't spend a drop of goodwill, because you're not withholding anything they need before release day.

And if Friday comes and goes? Nothing rots. The link keeps working, the files stay ready, and the reminder writes itself: the delivery page is the reminder.

When the files are already gone

If you're reading this with an unpaid invoice and delivered files, the honest answer is that your options are the slow ones: a polite dated reminder, then a firmer note (with the late fee, if your terms included one), then small claims court or a collections letter if the amount justifies it. Sometimes a phone call outperforms all of it, since most late payment is disorganisation rather than theft.

But do the forensic thing too: trace how the files left before the money arrived, and close that path. Usually the answer is "I always send finals when the client approves, because that's what I've always done." That habit is the leak. Next project, run the gate.

The short version

State the terms up front: price, deposit for new clients, revisions included, finals on payment. Run review and approval on a streaming link so approval never requires possession. Put the balance, itemised, on the delivery itself, and let the downloads unlock on payment: instantly by card, or with one click from you for everything else. You'll send exactly zero awkward chasing emails, because the workflow asks for the money at the only moment the incentives are on your side.

Frequently asked questions

How do I make sure a client pays before I send the final files?

Separate listening from possession. Let the client stream and approve the work on a review link, then deliver through a page that shows the balance due and keeps the downloads locked until it is paid. The client can hear everything and owns nothing until the money lands, which removes the need to chase an invoice after the fact.

Should I ask for a deposit for mixing or mastering work?

For new clients, yes. A 30 to 50 percent deposit filters out the people who were never going to pay and covers your time if the project dies midway. For repeat clients who have always paid, many engineers drop the deposit and rely on releasing final files on payment, which keeps the relationship light while still protecting the deliverable.

What should I do when a client will not pay for a mix or master?

If the files have not been delivered, you hold the leverage: the work stays locked until payment, and most stalls resolve themselves. If the files are already gone, escalate in order: a polite dated reminder, a firmer note with a late fee if your terms include one, then small claims or a collections letter for real money. And change the workflow so the next project cannot end up here, by never releasing finals before payment.

Are watermarks a good way to protect unpaid mixes?

Watermarks protect you, but they cost you too: the client approves audio that is not the real deliverable, beeps mask the exact things they are paying you to judge, and the final still has to be sent separately afterwards. Locking the download instead lets the client approve the actual master at full quality while the files stay in your control, which protects the work without degrading the review.

What payment methods should I accept as a freelance engineer?

Whatever your clients already use: bank transfer, PayPal, Wise, and card. The method matters less than the moment, which should be before the final files are released. If you take card through Stripe, the payment can unlock the delivery instantly with no waiting on you to confirm, and the money goes straight to your account.