Track each creator payment in a milestone ledger with separate fields for invoice receipt, milestone acceptance and money sent. Give every installment its own amount, due date, evidence and owner. This lets the team see whether a deposit needs processing, a draft needs review or an accepted deliverable has an overdue payment.
A single "approved" status cannot answer those questions. Modash's payment guide separates requesting an invoice, checking its details and passing it to finance. The ledger below adds a separate record for accepting the creator's work. It also records whether payment has completed.
Agree the payment trigger before work starts
For each installment, record what earns it and when the money is due. A deposit might follow signature. Another installment might follow acceptance of a named draft. Final payment might follow publication and delivery of the agreed files.
These are choices to negotiate. They are not standard percentages or platform rules. A publication payment should not acquire a sales target after the creator has already done the work.
Write down:
- The installment amount, currency and how it contributes to the total fee.
- The deliverable or event that triggers payment, with a version or evidence reference.
- Who reviews it, the review deadline and how the parties handle missed reviews.
- The invoice destination, required billing information and any purchase-order reference.
- The payment deadline, including whether the terms use calendar or business days.
- Who bears transfer charges, how taxes are handled and what happens after cancellation or a scope change.
Replace "payment after approval" with a defined review process and a due-date rule. If dates move, retain the original terms and attach the agreed change. An internal approval delay should never silently rewrite the creator's payment deadline.
Use the creator contract discussion guide to collect unresolved terms before sending them to a qualified adviser. This ledger is an operating template, not legal advice or a substitute for the contract.
Keep three records for each installment
UK government invoicing guidance distinguishes an invoice from a receipt acknowledging payment. Use the same distinction in your campaign records, while checking local invoice requirements with finance.
| Record | What to store | What it tells the team |
|---|---|---|
| Invoice | Invoice ID, amount, currency, receipt date, checked date, correction needed | Finance has received and checked the request |
| Milestone | Trigger, evidence link, reviewer, decision, decision date | The agreed event occurred or the reviewer accepted the named work |
| Payment | Due date, scheduled date, sent date, settled amount, transfer reference | How much money moved and what remains unpaid |
Keep a separate exception field for a dispute, missing invoice detail or failed transfer. An exception needs an owner and next action. It should not erase the other records.
For a deposit, milestone evidence can be the signed agreement. No content review is needed unless the parties agreed otherwise. For draft acceptance, save the approved file version and the reviewer's decision. The single-reviewer approval process helps define who can make that decision.
Keep payment credentials in the finance system. The campaign ledger needs a reference and status. For storage boundaries, use the guide to keeping payment details out of general campaign notes.
A worked milestone ledger
The following is a hypothetical fixed-fee arrangement for one video. The fee, percentages, invoice IDs and dates are illustrative, not market benchmarks. All amounts use USD; taxes and transfer charges are outside this example.
The parties have agreed the listed due dates. Reviewers met the acceptance dates shown. The ledger snapshot is October 16, 2026.
| Milestone | Fee share | Amount | Accepted evidence | Invoice received | Due | Payment state |
|---|---|---|---|---|---|---|
| Booking deposit | 30% | $600 | Signed agreement, September 30 | INV-01, October 1 | October 2 | Settled October 2 |
| Draft acceptance | 40% | $800 | Version 2 accepted, October 8 | INV-02, October 9 | October 15 | Scheduled October 18; overdue |
| Publication and file handover | 30% | $600 | Live link and files accepted, October 15 | INV-03, October 16 | October 23 | Checked; not scheduled |
The draft row requires action even though finance has scheduled it. Scheduling a transfer does not show that the creator received the money. Moving its due date to the scheduled date would conceal the delay.
| Hypothetical balance on October 16 | Amount |
|---|---|
| Total agreed fee | $2,000 |
| Settled payments | $600 |
| Unpaid balance | $1,400 |
| Overdue portion | $800 |
| Unpaid portion not yet due | $600 |
The deposit counts toward the agreed total. Do not pay the full fee again when the final invoice arrives. Reconcile each invoice to its milestone, then reconcile all installments to the contract total. Record partial payments against the same installment with their dates and references.
Resolve mismatches without losing the history
An invoice can arrive before the work reaches its milestone. Record its receipt immediately, then keep the milestone decision separate. Apply the agreed payment terms and any legal requirements; do not invent a new requirement to delay payment.
If the amount differs from the agreement, ask finance to identify the difference and request clarification. Keep the first receipt date, the correction request and the corrected document. Do not assume a correction restarts a legal payment clock.
If the reviewer requests more work, distinguish an agreed revision from an added deliverable. Record the requested change and resolve its fee and timing before treating it as a new payment condition. Keep any undisputed amount visible while finance and the responsible manager resolve the disputed portion under the contract.
A separate bonus also needs its own row. Give it the agreed measurement period, calculation and due-date rule. Do not hold a fixed production payment while waiting for bonus data unless the agreed terms require that dependency and it is lawful.
Late-payment escalation checklist
Use this checklist when an installment remains unpaid after its due date. The steps are an operational recommendation; legal remedies depend on the agreement and jurisdiction.
- Confirm the outstanding amount. Match the contract, invoice, acceptance record and payment history. Check for a partial payment or duplicate invoice.
- Name the blocker. Distinguish missing billing information, an unresolved review, an internal finance delay and a failed transfer. Assign one person to resolve it.
- Tell the creator what happens next. Confirm the amount owed, original due date, responsible contact and next update time. Give a payment date only after finance confirms it.
- Escalate internally. Send the evidence bundle to the finance lead and campaign owner. Request an authorized payment plan or a documented dispute response. A vague "processing" reply leaves the task open.
- Trace a sent payment. If the creator reports non-receipt, ask finance to investigate with the payment provider. Check the first transfer before authorizing another.
- Reconcile the result. Save the payment reference, settled amount and date. Keep failed or returned transfers visible until finance resolves them.
Payment law can apply independently of your ledger labels. For example, UK commercial-payment guidance says that without an agreed payment date, payment becomes late 30 days after invoice receipt or delivery of the goods or service, whichever is later. That is UK guidance, not a worldwide default.
For covered freelance work in New York City, DCWP identifies protections including a written contract and timely, full payment. Its hiring-party guidance page links a model contract. Ask a qualified local adviser about coverage, disputed work, interest or collection steps rather than deriving those decisions from a spreadsheet.
Before the next payment run, open every unpaid installment and give it a confirmed due date, an evidence reference and a named next-action owner.
