Payment workflow
Creator Payment Milestones: From Booking to Final Delivery
Build a clear payment workflow around booking, production, approval, invoices, expenses, and delivery without hiding important triggers in email threads.
A payment term is only operational when each amount has a trigger, owner, document, and due date. “50/50” does not say what books the work, when the second invoice is issued, or whether a delayed launch postpones payment.
Build the milestone ledger
| Milestone | Trigger | Evidence | Next action |
|---|---|---|---|
| Booking | Signed agreement and deposit received | Agreement, invoice, payment record | Reserve production window |
| Production | Concept or script approval | Dated approval message | Begin filming |
| Final delivery | Approved export ready | Approval and file list | Issue balance invoice or release files per agreement |
| Closeout | Balance and expenses reconciled | Receipts and payment confirmation | Archive and set license reminders |
Name the invoice clock
Write “net 15 from receipt of a valid invoice” or the actual agreed trigger. Do not attach the entire payment clock to campaign launch when launch is controlled by the brand. Confirm billing entity, address, tax information, purchase-order number, vendor portal, and finance contact before the invoice is due.
Separate expenses
List travel, props, shipping, locations, specialist support, and taxes as included, capped, pre-approved, or reimbursed. Unknown expenses need an approval route. Save receipts and the message approving the cost.
Record change and cancellation
If a project pauses or changes, update the ledger with work completed, approved expenses, delivered assets, invoice status, and the contractual next step. Do not invent cancellation or late-payment language after production starts.
Handoff checklist
- Correct legal and billing entity confirmed.
- PO or vendor setup complete.
- Approved files and delivery method listed.
- Outstanding amount and due date visible.
- Usage start and expiry tracked separately from payment.
Work a hypothetical delay
A fictional brand approves the final export on June 10 but postpones campaign launch until July. If the agreement makes final approval the invoice trigger, the creator issues the invoice on June 10 and the launch delay does not restart the clock. If payment was written as “after launch,” the creator has accepted a dependency controlled by the buyer. The lesson is not that one trigger is universal; it is that the trigger must be chosen and visible before booking.
Monthly reconciliation
Review the ledger on a fixed date. Match invoices to payments, attach approved expense receipts, flag missing purchase-order details, and identify the next responsible person. Keep payment status separate from content approval and license expiry so one delayed process does not obscure the other two.
Source and verification note
The milestone ledger is original Ratefolio operational material. It is not accounting, tax, or legal advice. Invoice requirements, taxes, deposits, and collection rights vary by business and jurisdiction.
Put this guide to work
Take the section checks into your next conversation.
Copy a checklist built from this guide’s review points, or print the full page for a project file.