New 250GB Plans LIVE now. See plans →
All posts
August 31, 2026 · Operations

Payment Terms for Freelance Video Editors That Get You Paid on Approval

I once wrote net 30 from final delivery on a quote and waited close to three months. These are the deposit, milestone and net terms I use now, each one triggered by a named approved version.

SM
Saumyajit Maity
Co-founder, PlayPause

In the first year of my agency I copied the payment section of a free contract template onto a quote without a second read, and it said net 30 from final delivery, which I assumed was simply what payment terms for freelance video editors looked like, right, because everybody writes net 30. The job was a batch of short product explainers for a hardware company, and their marketing lead watched the first cut the afternoon I sent it and loved it.

The trouble was that nobody had ever defined final delivery. Every small tweak afterwards, a bigger logo, a caption spelling, a different end card and so on, meant a fresh export, and every fresh export quietly became the new final delivery in the client's head, so the thirty days kept restarting while the earlier exports were already live on their product pages. The first money landed close to three months after that happy call, and for most of that stretch I paid my editors out of my own savings.

The rate was fine and the client was happy, so what I got wrong was the trigger, right, because net 30 counted from an event nobody can point at is really an open-ended loan to your client. What I use now is a deposit up front, milestones that fire when a named version is marked Approved, and short net terms counted from that approval.

Why standard net 30 terms hurt freelance editors

Net 30 basically means the invoice is due thirty days after a start date, and most templates never say what that start date is. That's exactly where editors get hurt, right, because in our work there are three candidate dates, the day you send the cut, the day the client watches it and the day they approve it, and those can sit weeks apart.

Net 30 also grew up around suppliers selling to companies that pay in monthly batches, while someone working as a freelancer has no employer's payroll or credit line behind them. Say you finish four projects a month at $1,500 each, which is $6,000 a month or roughly $200 a day of finished work. On net 30 you're always carrying about $6,000 of watched and liked video that nobody has paid for, net 15 cuts that float to about $3,000, and net 7 brings it down to around $1,400, all before a single approval delay gets added on top.

$6,000
example float on net 30
$3,000
example float on net 15
$1,400
example float on net 7

Net 15 vs net 30 for freelance work

On net 15 vs net 30, I write net 7 for creators and small brands paying from their own account and net 15 for companies with an accounts team, and I'm pretty sure almost nobody has pushed back on either, because a short number reads as your normal policy. The catch here is that a shorter number does nothing if the clock still starts on a vague date, so the start date matters far more than the number of days.

The four video editing payment terms worth writing down

When I rewrote my quote, the single payment line at the bottom became four short terms, each answering a question the client would otherwise answer later to suit their own cash flow.

The first is the deposit, 50% for a new client and 30% for a repeat client who has paid on time, and it clears before I open the timeline. The reasoning is in how I set a deposit policy, and a plain deposit and final payment, half now and half later, is fine for small jobs, right, as long as the second half has a clear trigger.

The second term is that every milestone is named by an approved version, never by a date or a round number, and the third is that net terms count from that approval date, with the invoice leaving the same day. The fourth is that the full-resolution masters and project files go over when the final payment clears, and until then the client watches on a review link. The clause wording for all four sits in my video editing contract template.

Under those four I keep two smaller lines that most templates bury. One is a late fee, a small monthly percentage on anything past due, which I've almost never charged but which makes the due date read like a real date, so check what your country allows before you write a number. The other is cancellation, where a client who stops mid edit forfeits the deposit against the hours already spent, and one who stops after picture lock is approved owes the second milestone in full.

  • Deposit of 30 to 50 percent before the timeline opens
  • Every milestone named by an approved version, not a date
  • Net 7 or net 15 counted from the approval date
  • Masters and project files released on final payment
  • One named approver written into the quote

Tie payment milestones to an approved version, not a delivery date

Here's how milestone payments play out on a real video editing job, with illustrative numbers. Say a B2B software company books a six-minute customer story for $3,200, big enough to split into three payments. The deposit is 30%, so $960, and it clears before I touch the footage. The second milestone is 40%, so $1,280, due net 7 from the day the client approves picture lock, meaning the story and timing are locked and only the grade, mix, captions and graphics are left, the finishing stages of post-production. The last 30%, another $960, is due net 7 from approval of the finished version.

None of those says after round two or on the 15th, right, because a client can stretch a round forever with one more note, and both sides forget a date the moment the shoot moves. Most clients have never heard picture lock named, so new clients get my plain glossary of editing terms before the first cut, and I explain the gap between a provisional yes and a cut that's truly final before any money depends on it.

What makes this work in practice is naming the version. In PlayPause every new export goes onto the same card as a version stack (Creator plan and up), so the customer story card holds MV1, MV2, MV3 and so on, stacked in the one place the client already reviews from. It's the same idea as version control in software, where every change has a number and nobody debates which file shipped. So my invoice says picture lock approved on MV3 with the date, right, and their accounts team can match that line to the card without emailing me.

Terms tied to delivery

the clock starts when you send files, and every small tweak creates a new delivery date to argue about

Terms tied to approval

the clock starts once, when a named MV is approved, so the invoice and the cut point at the same thing

Review_Cut_v4.mp4In Review
212160p · ProRes
00:34 / 02:18
SR
Sarah 0:34

Frame-accurate note, everyone sees the exact same thing.

In PlayPause, every comment is pinned to the exact frame, no more “which part?” email threads.

Use approval statuses as your payment trigger

Once milestones are named by version, both sides need to see when a version is approved, and for me that's the card status. Custom statuses are on every PlayPause plan, so each client project gets the same six, In Edit, Client Review, Changes Requested, Approved, Invoiced and Paid. The status is basically the milestone marker, right, because the moment a card moves to Approved the invoice goes out that day, naming the MV and the date, and the card moves on to Invoiced.

Clients comment from the link without creating an account, so the approval is a written comment sitting on the exact version it refers to, and then my manager or I flip the status. With Slack connected (Creator and up) every comment posts into a channel, so the word approved lands in my channel and the invoice can go the same afternoon. You can see how this fits together on the approval tracking page and in the wider client approval workflow for video.

Payment fires on an event both sides can see, not on a date one person has to remember, and at the end of the day that's what gets you paid on approval instead of whenever finance gets round to you. The statuses slot into my wider freelance video editing workflow, and if a finance team ever questions a sign off, the paper trail is in documenting video sign off for billing.

One warning on Creator: share links and their files expire after 30 days (90 on Agency, never on Enterprise), so on net 30 the approved link could be gone by the time you chase, which is why the MV number, approval date and approver's name go on the invoice itself.

What to do when the client watched but will not approve

This is the situation that hurts the most, right, the client has clearly seen the cut, maybe even said on a call that they love it, and yet nothing gets approved, so your milestone never fires and the money sits behind a version everyone agrees is fine.

On Creator and up, PlayPause shows who watched a link, when and from which city, so before I send anything I check whether the named approver actually opened MV3. If they haven't, the problem is attention, and a short nudge with the link fixes it. If they have, they're usually waiting on someone else, a boss or a co-founder, and the only fix is getting that person to watch too.

I use the view record to decide which conversation to have, never as a gotcha, and trust me on any level, a message saying you can see they watched at 11:40 pm will cost you the client faster than any late invoice. What I send is warm and specific, that MV3 is ready, that if there are no changes I'll mark it Approved next Monday and send the picture lock invoice, and that anyone else who needs to see it can use the same link. Behind that sits a line on my quote saying that once the named approver has watched a version and five working days pass without notes, it counts as approved for billing.

1Check who watched the version and when
2Message the approver naming the MV and a date
3Allow five working days for notes
4Mark it Approved and send the milestone invoice

If notes arrive after that window, I don't argue about whether they're new, I treat them as the next round, and on Agency and up, side-by-side compare puts MV3 next to MV4 so the client can see what the extra round is for. If a client holds the unpaid milestone hostage for one more round, which I wrote about in the one more round payment stall, the next round starts once the owed milestone is paid. Does that make sense, right, the rule sits on a quote they already signed, so you point at a line instead of starting an awkward money conversation.

How to present payment terms without scaring a new client

Clients who push back on terms, in my experience, are almost always reacting to how they were presented, usually a wall of legal text at the bottom of a PDF, so I put mine in the body of the proposal, right under the timeline, in one plain paragraph.

I present the deposit as the thing that books their dates on my calendar, and the approval trigger as protection for them too, because they only pay a milestone on a cut they've personally approved. I also name the approver on the quote, for instance the head of marketing, because approval stalls when three people each assume someone else will sign off.

The wording I paste is close to this, and you're welcome to copy it: "A 50% deposit books your dates and is due before editing starts. The balance is due 7 days after your named approver signs off the finished version on your review link, and the invoice will name that version, for example MV3. Masters and project files are sent once the balance clears." That's really really all a small job needs, right, and on bigger jobs I just add the picture lock milestone in the middle.

Put the version on the invoice

When the invoice line reads picture lock approved on MV3 with the date, the client's accounts team can match it to the review card without having to email you.

On the kickoff call I say the terms out loud once, and to be very honest that one spoken sentence does more than any bolded clause. The PlayPause page for freelance editors shows how the review link, statuses and version stack look from the client's end, worth walking a new client through on that call. You see what I mean here, right, terms feel normal when the process around them already looks organised.

Frequently asked questions

What are standard payment terms for freelance video editors?

Most quotes I see say 50% deposit and 50% on completion, net 30, and I'd keep the first half and change the second. Tie the final payment to approval of a named version and count 7 or 15 days from that approval, because completion is a word the client gets to define, while approval of MV3 on a specific date is something both of you can check.

Is net 15 or net 30 better for a freelance video editor?

I'd write net 15 for most companies and net 7 for creators and small businesses paying from their own account. When a large company insists on net 30 or longer because their finance team runs a monthly cycle, I accept it but raise the deposit or add a picture lock milestone, so less of my money sits waiting. Either way, count the days from the approval date and send the invoice that same day.

What counts as approval if the client never clicks anything?

In PlayPause, clients comment from the link without an account, so my approval is a written comment on the exact version, for instance approved on MV3, after which my team moves the card to Approved. If the named approver has watched and stays silent, my quote says five working days without notes after a recorded view counts as approval for billing. I'm not a lawyer, so run your own version of that clause past one.

Custom statuses are on every plan, version stacks and who-watched analytics start on the Creator plan at $9 a month, and every plan comes with a 7-day free trial, so check the plans on our pricing page and run your next milestones through it.

So yeah. That's my way of saying it.

SM
Saumyajit Maity
Co-founder, PlayPause

Saumyajit co-founded PlayPause after years watching review and approval quietly eat creative teams' deadlines. He writes about the workflow side of video, feedback, versioning, and getting to a clean sign-off.

Related resources

Keep reading

Bring your team into one review space

Centralize feedback, lock approvals, and deliver faster, start free today.

Sign Up for Free