Direct answer — How are game publishing advances paid out, and what happens when a milestone slips? A game publishing advance is almost never wired in one payment: it is split into instalments, each released when the publisher accepts a milestone deliverable such as a vertical slice, alpha, beta or gold master. Voyer Law’s 2026 market report found that 84% of agreements tie the advance to specific development milestones. When a milestone slips or is rejected, the payment attached to it waits, and depending on the contract the studio can also be in breach, lose funding or, in the worst drafting, hand over development. Acceptance criteria, review deadlines and a cure period are what keep a slip from becoming a cash crisis.
The headline number in a publishing offer is the advance. The number that decides whether your studio makes payroll is the payment schedule behind it: how many instalments, what each one requires, who decides it has been delivered, and how fast the money follows. Two offers with the same advance can carry very different risk.
I have spent more than 20 years on the commercial side of games, including 17 at Gameloft and a period running the mobile games unit at SFR, and I have negotiated with developers on the other side of the table. This guide covers how publisher funding milestones work, what acceptance criteria to ask for, and what a slip triggers. It assumes you already have an offer, or are close to one.
Key Takeaways
- Milestone payments are the norm. In the 2026 Voyer Law sample of over 130 agreements, 84% tie the advance to development milestones; Strebeck says the rest generally pay monthly or quarterly instead.
- Approval is the payment trigger. Without a review deadline and deemed acceptance, a publisher’s silence delays your money as effectively as a rejection.
- A slip is a contract event, not just a schedule problem: breach, termination for cause and step-in rights all hang off the milestone clause.
- Every instalment is recoupable, so read the payment schedule and the recoup clause as one mechanism.
How a game publishing advance is split into milestones
An advance is development funding that the publisher pays before launch and recovers from the game’s revenue. Strebeck, summarising Voyer Law’s 2026 Video Game Publishing Agreement Market Report, puts the median advance at $270,000 and the average at $602,818, and notes that 62% of the agreements in the sample included an advance at all.
The money then arrives in instalments. Tom Buscaglia described the logic in Game Developer as early as 2005: instead of a single cheque, the funds are delivered over time, and the publisher’s approval of each milestone deliverable triggers the payment of the matching advance. The share of milestone-based deals has stayed high across Voyer’s reports: 79.7% in the 2025 report (over 100 agreements) and 84% in 2026. The samples overlap, so read this as a stable market practice rather than a trend.
A typical schedule follows the production plan:
| Milestone | What the publisher usually reviews | Risk for the studio |
|---|---|---|
| Signature | The signed contract | Low: the first instalment pays for ramp-up |
| Vertical slice or first playable | A final-quality section of the game | Medium: subjective “fun” judgements |
| Alpha | All features in, content incomplete | High: scope disputes on what “feature complete” means |
| Beta | Content complete, bug fixing | High: performance and bug thresholds |
| Gold master / launch | The release build, platform certification | Medium: certification delays outside your control |
| Post-launch | Updates, ports or DLC, when the deal includes them | Variable |
The alternative to milestones is time-based instalments. Monthly payments are easier on cash flow because they do not stop for a review, but publishers using them usually keep the right to suspend payment if the project drifts. Monthly builds are also common inside milestone deals: Tim Repa Davies describes contracts where the studio delivers a build each month and can only invoice once the publisher approves it.
If you are still building the plan behind your pitch, the milestones you propose become the ones you are paid against; my guide on what publishers look for in a vertical slice covers how to cost them. And when an offer arrives, negotiating publisher milestone payments is part of the deal work, alongside the advance, recoupment and rights.
Milestone acceptance criteria and what a slip triggers
Repa Davies sums up the core problem: “the developer only receives front end payments where the publisher has given its approval.” Acceptance is therefore a cash-flow clause, and vague acceptance is the most common way a payment gets delayed. Buscaglia’s warning still holds two decades later: “the advances tied to those deliverables could mean life or death to your company.”
The milestone acceptance criteria worth fighting for:
- Written deliverables per milestone. Features, content counts, target platforms and performance thresholds, drawn from the production plan, not “alpha quality”.
- A fixed review period. Repa Davies notes that publishers are generally amenable to a reasonable review time, “say, 10 working days”.
- Deemed acceptance. If no written rejection with reasons arrives within the review period, the milestone counts as approved for payment.
- Resubmission and cure. A defined number of resubmissions, each with its own deadline, before any breach can be declared.
- Partial acceptance. A rule for paying the delivered share when one item is missing.
- A change process. When the publisher asks for new scope, the schedule and the payments move with it. Buscaglia argued for exactly this: make the deliverables in the contract match the deliverables in practice.
What a slip triggers depends entirely on the drafting. At the mild end, the payment simply waits for the resubmission. In many contracts, a missed milestone also puts the studio in breach, and Repa Davies warns that this can allow the publisher “to walk away without penalty”. Buscaglia draws the distinction worth knowing: termination for cause after a missed milestone, against termination “for convenience”, which often requires the publisher to pay out part of the remaining advances.
The extreme end is step-in rights. In Secret Mode v Victura, reported by Lewis Silkin in 2026, the publisher was to fund up to $8 million in development costs, released milestone by milestone. It rejected a milestone and two resubmissions; the step-in clause let it take over development, “with the publisher’s revenue share increasing to 75%”, and required the source code to be handed over. The High Court granted interim relief to neither side, and the case shows how much rides on one acceptance decision. The full list of clauses to check, from vague milestones to one-sided termination, is in my game publisher deal red flags guide.
Cash flow and recoupment: what the payment schedule really costs
For a small team, the risk is not the size of the advance but the gap between instalments. Salaries and contractors are paid monthly; milestone payments arrive after delivery, review, any resubmission and the invoice term. A single disputed milestone can leave a studio paying a full team for weeks with nothing coming in.
Three habits reduce that risk:
- Model runway on payment dates, not the headline advance. Take each milestone date, add the review period, one resubmission cycle and your invoice term, and check payroll still clears.
- Front-load the schedule where you can. A larger signature payment, or more and smaller milestones, keeps the gap between instalments short.
- Keep a buffer outside the deal. A studio with no reserve has little leverage in a dispute; in the Victura case, the developer’s request was refused largely because the court was not satisfied it had the resources to finish and market the game.
The schedule also feeds recoupment. Every instalment you receive is recoupable, so ask whether recoupment counts what was actually paid or the full committed advance, whether extra funding to cover a slip carries the same markup, and whether an unrecouped balance is written off at the end of the term. Recoup structures are shifting toward studios (full-stop recoupment fell from 48.4% to 37% of deals between the last two Voyer reports), but the clause still decides when you see revenue. The math is in my recoup clause guide.
What we could not verify
We looked for public data on how advances are typically split across milestones (for example the share paid at signature), on how often milestones are rejected or paid late, and on the review periods and payment terms that publishers actually sign. No source we could read publishes these with a method we could check; the 10 working days figure is a practitioner’s example, not a market average. The Voyer Law figures come from Strebeck’s and GameDev Reports’ summaries, not the full reports, and neither summary says how mobile deals are represented.
Before you sign the payment schedule
Read the schedule as the deal’s real cash plan: count the instalments, write down what each one requires, cap the review period, secure deemed acceptance and a cure period, and model payroll against realistic payment dates. Then read the recoup clause against the same schedule. If you do not have an offer yet, shortlisting and approaching publishers is covered in my guide on how to find a game publisher.
Publisher search fees are published on the offer page: EUR 2,000 for preparation, EUR 1,500 per month over an initial 3-month mandate, and a 5% success fee on funding attributable to the mandate and actually received by the studio, with the retainers credited once against it across all funding instalments. Game Growth Advisor takes no fees from publishers and no share of your game’s revenue.
Have a publisher offer with a milestone schedule in it? Book a free 30-min call and bring the term sheet, your production plan and your monthly burn.
