Getting paid is part of the job

There is a particular quiet that arrives about five weeks after a post goes live. The work was delivered, the brand said it looked great, the invoice went somewhere, and nothing has landed. Most creators respond to this by concluding they are bad at the business side.

They are usually not. What happened is that the deal was agreed in one place, the terms were written down in another, the invoice went to somebody who does not pay invoices, and nobody had a date in a calendar for chasing it. Those are process breaks, and process breaks are fixable in an afternoon by somebody who has never enjoyed admin in their life.

This is the boring half of the job, and it decides whether the work you already finished turns into money this quarter or next.

The deal is in a DM and the money is somewhere else

Trace an unpaid invoice backwards and the same four breaks turn up, in the same order, nearly every time.

1. It was agreed in a DM. A price and a rough scope, in a chat window that scrolls, with nothing written about when the money arrives.
2. The terms came later by email, as one clause inside a longer paragraph, and the payment term was the least prominent thing in it.
3. The invoice went to the person you had been talking to. They are a marketing manager and they cannot pay you. It needed to reach accounts payable, usually carrying a reference number nobody mentioned to you.
4. Nobody was chasing. Not the brand, for obvious reasons, and not you, because chasing has no trigger unless you built one.

None of the four involves anybody behaving badly. A company with every intention of paying you still takes sixty days if its process takes sixty days, and that process does not begin until a correctly addressed invoice with the right reference on it reaches the right inbox. Until then you are not late in their system. You are not in their system.

The QuickBooks figures come from a January 2025 survey of 2,487 US small businesses, and 47% of them said some of those invoices were already more than thirty days past due. You have not been singled out. This is the ordinary condition of everybody who invoices for a living, including the agency that hired you.

What actually has to be on the invoice

An invoice is a document that has to survive being forwarded to somebody who has never heard of you and has no idea what a reel is. That is the entire design brief, and most creator invoices fail it because they were written for the person who commissioned the work.

On the next deal, before you send anything, ask the person who hired you one question: who should this invoice go to, and is there a purchase order number I should put on it. It is an ordinary question, it costs you nothing socially, and in any company above about fifty people the answer is almost never them. Asking it once removes the single most common reason a creator invoice goes quiet.

Net 30 and net 60, in cash flow terms

Net 30 means the invoice is due thirty days after it is issued. Net 60 means sixty. That is the whole definition, and the part that costs creators money is not the number. It is the word after it.

Thirty days from what. From issue, from delivery, from the day the post goes live, from the end of the month in which the invoice was received, or from the end of the month after that. All of those are real terms in ordinary use. Net 30 from the end of the month following receipt can work out at fifty-nine days on an invoice you sent on the second. The fix is one line: put the due date on the invoice as a date.

For a creator, the cost of net 60 is not the waiting. It is that you did the work, paid for whatever the shoot cost, and then financed a company much larger than you for two months at no charge. Two deals on net 60 overlapping is a quarter's income sitting on somebody else's balance sheet while you cover your own rent from the one before.

There is a defensible reason companies run long terms, which is that their own money arrives on similar schedules. There is also a lazier reason, which is that nobody negotiated. Terms move more often than creators expect, and the moment to move them is before the work starts, while you still have something they want.

A chasing schedule you can follow without dreading it

Chasing feels awful because it usually happens when you are already annoyed, which makes the message hard to write and easy for the recipient to ignore. Set the dates in advance and your feelings stop being part of the system. Everything below counts from the due date on the invoice, not from the day you sent it.

1. 01Three days before it is due. One line, no pressure, on the original thread: just checking this is sitting with the right person for the 14th, and tell me if you need anything else from me. This is the highest value message in the list, because it catches the wrong-inbox failure while there is still time to fix it quietly.
2. 02Day one after the due date. Reply on the same email, so the invoice is still attached. Say it was due yesterday and you are resending in case it needs a nudge. No apology and no explanation of why you are asking. It was due yesterday.
3. 03Day seven. Add the person who actually pays, and change the question. Stop asking for the invoice to be paid and start asking for the date it is scheduled for. A date is something you can hold somebody to. Soon is not.
4. 04Day fourteen. Ask for the reason, in writing. Something is blocking it and it is nearly always one of three things: no purchase order, the wrong legal entity, or an approval nobody chased internally. Naming all three in your email usually gets an answer, because picking one is easier than composing an explanation.
5. 05Day thirty. Move out of email. Phone accounts payable, or go back to the person who hired you and tell them you need their help internally. By day thirty the polite channel has been tried and, more importantly, documented.

Five messages over five weeks, none of them angry, all of them written before you needed them. Write the first two on the same day you send the invoice and schedule them then, while you still feel neutral about these people.

At sixty days, and at ninety

Past sixty days you are no longer chasing an oversight, and the messages should stop sounding like you are. Four things happen at sixty.

• Send a formal notice. Invoice number, amount, due date, days elapsed, and what you will do next and on what date. Attach the invoice again. Keep every sentence factual, because this is the document that gets read by somebody else if it goes further.
• Stop new work for that client. Delivering while unpaid teaches their process that not paying you has no consequence, and it is the single most common way a two month delay becomes a six month one.
• State interest, if your terms or your country's law allow it. You do not have to enforce it to state it, and stating it moves an invoice up a queue that is otherwise ordered by who is loudest.
• Tell somebody senior at the brand, once, without drama. The person who hired you very often does not know, and being told is usually enough for them to walk down the corridor.

At ninety days you pick one of three routes, once: a letter before action, a small claims process, or writing it off and never working with them again. All three are legitimate endings. The expensive one is the fourth nobody chooses on purpose, which is chasing quietly for another six months while it stops feeling like real money.

Making the next deal not need any of this

Everything above is repair work. Two changes made before the work starts reduce how often you need it, and both of them are ordinary commercial practice that creators talk themselves out of asking for.

The first is a deposit. Half up front on a first deal with a brand you have not worked with, less once there is a history. It covers your costs, and it does something more useful: it tests whether their payment process works at all while the amount at stake is small. A brand that cannot get a deposit through in two weeks has told you exactly what the final invoice is going to do.

The second is staged payment. On anything longer than a single post, split the fee: something on signature, something on delivery, the rest on publication. Each stage carries its own date and its own small invoice, so a failure surfaces at the first stage instead of at the end, and one missed payment never takes the whole fee down with it.

Both are easier to ask for than creators assume, because the person on the other side has almost certainly paid a deposit to a photographer or a venue this year without thinking about it. It only feels awkward the first time you say it out loud.

Where we come in, and where we do not

This is the product section, and it is one section because the schedule above works whether or not you ever open our software.

Synclify keeps the invoice attached to the deal it came from. Take Maya's Amber Home deal in our demo account: 48,000 rupees for one reel, three stories and one carousel, with three things the brief never said (how long they can use the video, whether she can work with similar brands, and when they actually pay). Those answers, the deliverables and the invoice are one record, so chasing never means reconstructing what was agreed out of an email thread from six weeks ago.

proof: an invoice row carries the collaboration id of the deal it belongs to, so the two cannot drift apart (shared/schema/content.ts, invoices.collaborationId)

A job runs once a day and handles the invoice side: raising the ones that recur and sending the payment link out. A separate job runs hourly and derives reminders from dates rather than from anybody remembering, so an invoice due in three days produces a notice before it is late instead of after.

proof: the invoices cron runs once a day and reminders hourly (the scheduled jobs file), and generateInvoiceReminders fires three days ahead of a due date (server/reminder-scheduler.ts)

The assistant will also raise a late invoice without being asked. It is one of five things it is allowed to speak first about, and it has to clear four gates before it reaches you: unprompted messages switched on, not the middle of your night in your own timezone, the same subject not already raised recently, and under the daily cap. The bar for late is properly late rather than merely due, which in the code means more than seven days past the due date.

proof: an invoice more than seven days past its due date is one of five proactive signals, behind four gates (server/agent/proactive.ts)

Questions creators ask about getting paid