Most producers who move into sonic branding discover the same thing in the same order. The craft is the easy part. The sound logo lands, the client says the right words in the review call, everyone is happy. Then the files go out, and the money takes eleven weeks to arrive.
That gap is not a client problem. It is a structure problem. An invoice that arrives at the end of a project is a request. An invoice that was designed at the start of the project is a schedule. The difference between the two is decided months before you send anything.
Here is how we structure payment on a sonic branding engagement, and where the terms come from.
The invoice is written during scoping, not after delivery
The single most useful habit: when you write the scope, write the payment schedule in the same document, in the same sitting.
Scoping tells you what you will make and when the client will see it. That is already a payment schedule. You just have to name it. If your scope has three moments where the client receives something and reacts to it, you have three invoices. If your scope is one long silence followed by a zip file, you have one invoice and no leverage.
We covered the scoping side in How to Scope Your First Sonic Branding Client. The payment structure below is the second half of that document.
Three moments, not one
A single invoice at delivery puts the entire commercial risk on you. You have already spent the studio hours. The client has already heard the work. Nothing on your side is still owed, which means nothing on your side still creates urgency.
Split it.
Deposit at signature. Between 30% and 50%. This is not a gesture of good faith, it is the thing that converts a conversation into a project. Nothing starts before it clears. Not the audit, not the moodboard, not a single session. The deposit is also your filter: a client who hesitates for three weeks on a 40% deposit will hesitate for three months on the balance.
Milestone at first presentation. Typically 20% to 30%, due when you present the direction. Not when the client approves it, when you present it. Approval is a subjective event and you do not control it. Presentation is an observable event and you do.
Balance at delivery. The remainder, invoiced the day the deliverables are ready, paid before the files transfer.
For a retainer the shape is simpler: a fixed monthly amount, invoiced on the first, covering a defined block of work. We wrote about that transition in How Music Producers Turn a Sound Pack Into a Sonic Branding Retainer.
Make every trigger observable
This is the part that quietly decides whether you get paid on time.
A payment trigger must be an event that either happened or did not, with no room for interpretation. "On approval of the sound logo" is not a trigger. It is a permission slip the client can decline to sign, for months, without ever saying no.
Compare:
Weak trigger / Strong trigger
On client approval → On presentation of three directions
On completion of revisions → On delivery of revision round one
On project completion → On delivery of the master files
When the campaign launches → Thirty days after final delivery, launch or no launch
The last row matters more than it looks. Campaigns slip. Rebrands get paused. If your final payment is tied to a launch date, your cash flow is tied to a decision made in a room you are not in.
The same logic protects the revision phase, which is where most sonic branding engagements lose their margin. If revisions are unbounded, so is the delay before your last invoice. We broke that down in How to Run a Sound Logo Revision Round Without Losing the Brief: a defined number of rounds, a defined window to use them, and a stated consequence when the window closes. That consequence is usually the balance becoming due regardless.
The licence is a line item
The most common underpricing mistake in sonic branding is burying usage rights inside a single number.
A sound logo used on one product page and a sound logo used across broadcast, retail, and in-app onboarding are the same file and a completely different commercial object. If your invoice says "Sound logo design: 4,000" and nothing else, you have sold the second one at the price of the first, and you have no basis to revisit it when the client expands usage next year.
Break it out:
Creation covers the work: research, direction, production, revisions, delivery.
Licence covers the use: which media, which territories, how long, exclusive or not.
Two lines. The client sees what they are buying. You get a natural conversation next year when the licence term ends and the sound is now genuinely part of how the brand is recognised. That renewal conversation is worth more than the original project, and it does not exist if you sold everything once, forever, in a single line.
State the licence scope on the invoice itself, not only in the contract. Invoices get forwarded to finance teams and pasted into procurement systems. Contracts get filed and forgotten.
Transfer of rights on final payment
Write this clause, and write it in plain language.
The principle: the client receives the rights described in the licence when the final invoice is settled, not when the files are sent. Until then, the delivered material is provided for review.
In France this is standard and enforceable, and it is the single most effective late payment deterrent we have used. A client who has already deployed a sound they do not yet own has a strong reason to close the invoice. A client who owns it on receipt has none.
Two caveats worth knowing. First, in French law moral rights stay with the author and cannot be transferred, whatever the contract says. Authorship is yours permanently. What you transfer are the economic rights of exploitation. Second, this framing is specific to French and broadly European practice. If you are working under US or UK law, or your client is, get the equivalent clause checked locally rather than translating this one.
What the invoice document actually has to carry
Boring, and worth getting right the first time, because a non-compliant invoice is a legitimate reason for a finance department to send it back and restart the clock.
For a French sole trader, the minimum set:
Your legal name, address, and SIRET
The client's full legal name and address, plus their VAT number for cross-border work
A unique sequential invoice number, with no gaps in the sequence
Issue date and due date, as a date and not a delay
A clear description of the service, one line per element
Amounts, and the VAT position
Payment terms and late payment penalties
Bank details
If you are on the French micro regime under the VAT franchise, the invoice must carry the exact wording "TVA non applicable, art. 293 B du CGI". If you are selling to a business in another EU country, the reverse charge mention applies instead and the client's VAT number becomes mandatory.
Two details that save real time. Put the due date as an actual date, because "net 30" gets interpreted from whenever the invoice was opened rather than issued. And name a person, not a department. An invoice sent to accounts@ with no internal owner sits until someone adopts it.
Late payment terms are written before you need them
Nobody enjoys this clause. Write it anyway, at signature, when the relationship is warm and nobody is negotiating it line by line.
In France, late payment on a B2B invoice carries interest plus a fixed recovery indemnity of forty euros, set by law and due without prior notice. The EU late payment directive sets a comparable floor across member states. You do not have to enforce it, and most of the time you will not. But a stated penalty changes how an invoice is prioritised when a finance team is sorting a stack of them, and it is impossible to introduce after the fact.
Set your own terms deliberately rather than defaulting. Thirty days is common in agency work. Fifteen is reasonable for a solo studio. Payment on receipt is fair for a final invoice on a project the client has already heard and approved.
Delivery and payment are the same moment
The cleanest handoff we have found: the final invoice and the delivery notice go out together, and the files follow the payment.
The email is short. Here is what was produced, here is the licence you now hold, here is the invoice, here is the link that opens when it clears. No apology, no hedging, no long preamble. You are not asking for a favour. You are completing a transaction that was agreed in writing at the start.
That email is much easier to write when the delivery itself is organised, documented, and obviously finished. A folder with clear naming, a short guidelines document, and every variant the client will need is worth more at invoice time than any amount of chasing. We laid out that structure in How to Document a Sonic Starter Kit for a Client.
When it still goes quiet
Sometimes it does. A short sequence that works without damaging the relationship:
Day 1 after due date. A one line reply on the original email thread. No new subject, no escalation, just visibility.
Day 7. Same thread, plus the specific consequence in one sentence. Usage rights not yet transferred, or the recovery indemnity now applying.
Day 15. A separate email, addressed to a named person, restating the amount, the invoice number, and the contract clause.
Day 30. Formal notice. In France, a lettre de mise en demeure sent by registered post.
Almost everything resolves at step one or two. What makes steps three and four available at all is the fact that the terms were written down before the work began.
The pattern underneath
Every one of these mechanisms does the same thing. It moves a decision from the end of the project, where you have no leverage, to the start, where you have all of it.
The scope, the payment schedule, the revision count, the licence scope, the transfer clause, the penalty terms. Six paragraphs, written once, reused on every engagement. They are not the interesting part of sonic branding. They are the part that determines whether you get to keep doing the interesting part.
If you are still building the front end of that document, start with How to Write a Sonic Branding Brief. The brief and the payment schedule are the same conversation, held on the same day.
This article describes practice, not legal advice. Contract and invoicing requirements vary by country and by client. Have your standard terms reviewed once by a professional in your jurisdiction, then reuse them.
