Milestone Revenue Recognition: 5 Steps, Example & Mistakes
Milestone revenue recognition counts each share of a fixed project fee as earned once the client approves that phase. When invoices and approvals fall in different months, your reported revenue stops matching the work you delivered.
You’ll see how the milestone method works under ASC 606 and IFRS 15, and how billing differs from recognition. A $60,000 website project shows each entry, including a late approval and a mid-project scope change.
Key Takeaways
- Book revenue on written sign-off. Each milestone’s share of the fee is earned when the client approves it, whatever the invoice date.
- Allocate the fee by standalone prices. Split the contract price in proportion to what each phase would cost if sold alone.
- Write an acceptance rule for every milestone. Name the deliverable, the client approver, and the proof of sign-off in the SOW.
- Connect project billing to accounting. An all-in-one tool like Productive sends each milestone invoice to the ledger without retyping.
- Match the method to the contract. Milestones fit phases that end in client approvals, and percentage of completion fits value that builds continuously.
What Is Milestone Revenue Recognition?
Milestone revenue recognition records part of a fixed project fee as earned each time the client approves a milestone. It’s also called milestone-based revenue recognition. Revenue recognition is the accounting rule for when income counts as earned. That date can differ from the invoice or payment date.
Professional services firms use it because they already plan work around project milestones the client approves. ASC 606 calls each promise to deliver goods or services a performance obligation. Each milestone stands for one such promise, and its share of the fee becomes revenue at sign-off.
USE PRODUCTIVE TO BREAK PROJECTS INTO CLEAR PHASES AND MILESTONES.
Example: A digital agency sells a $60,000 fixed-fee website project with three milestones: discovery and UX, build, and launch. It records $15,000 at discovery approval, $30,000 at build approval, and $15,000 when the client accepts the launch.
The method fits fixed-fee work with clear acceptance points. Hourly work billed as time and materials is different, because you recognize revenue as the approved hours add up.
How Does Revenue Recognition Work at Each Milestone?
Revenue recognition works at each milestone by booking that phase’s share of the fee on the client’s sign-off date. Under ASC 606 and IFRS 15, you recognize revenue when the client takes control of what you promised.
Written approval is the usual proof, so the invoice date doesn’t move the entry. Project managers record the approval date, and finance teams book the entry from it.
ASC 606 is the US GAAP (Generally Accepted Accounting Principles) revenue standard from the Financial Accounting Standards Board. IFRS 15, from the International Financial Reporting Standards, is its international counterpart.
The Five Steps of Revenue Recognition Under ASC 606 and IFRS 15
ASC 606 and IFRS 15 share a five-step model that every milestone passes before you book revenue. Here are the steps, applied to the $60,000 website project.
1. Identify the contract. Your signed SOW (the scope agreement) names the fee, the phases, and who approves each one.
2. Identify the performance obligations. A phase is its own performance obligation when the client can use its deliverable without the later phases.
3. Determine the transaction price. On this project, it’s the $60,000 fixed fee. A bonus or penalty clause (variable consideration) would change it.
4. Allocate the transaction price. Split it by standalone selling price, which is what you’d charge for each phase alone. The table shows the split.
5. Recognize revenue when each performance obligation is satisfied. For a milestone, that’s the point in time when the client accepts the phase in writing.
Example: allocating the $60,000 fee by standalone price
| Phase | Price if sold alone | Share of total | Allocated fee |
|---|---|---|---|
| Discovery and UX | $18,000 | 25% | $15,000 |
| Build | $36,000 | 50% | $30,000 |
| Launch | $18,000 | 25% | $15,000 |
| Total | $72,000 | 100% | $60,000 |
Your accountant makes the final call on which phases count as separate performance obligations.
Milestone Billing vs Revenue Recognition
Milestone billing and revenue recognition answer different questions: when you ask for payment, and when you’ve earned it. Billing follows your payment terms and drives cash flow. Recognition follows delivery and client sign-off.
| Dimension | Milestone billing | Revenue recognition |
|---|---|---|
| Purpose | Request payment from the client | Record when the fee is earned |
| Trigger | A planned checkpoint on the billing schedule | Client acceptance of the milestone |
| Timing | Can come before or after acceptance | Only once the client accepts the work |
Most milestone billing revenue recognition errors come from treating the invoice as the revenue entry. An invoice the client pays before sign-off is deferred revenue (cash received for work not yet accepted). Work the client accepted but you haven’t invoiced yet is unbilled revenue.
In Productive’s Billing and invoicing, you schedule draft invoices with future dates on a single budget. Or you create one budget per milestone and invoice each one separately.
Now, when we deliver a project, we just create an invoice in the app, send it, and then close the project. No extra time needed.
Read how ENKI simplified its invoicing with Productive.
Keep an Unapproved Phase Out of This Month’s Revenue
A phase the client hasn’t approved shouldn’t count as revenue, even when its invoice already went out.
In Productive, fixed-price revenue follows one setting, under Revenue Recognition in Settings. Choose recognition on a single date. Set open budgets to recognize nothing, and delivered budgets to use the delivery date. Then give each milestone its own budget. After client sign-off, mark that budget as Delivered. Productive then recognizes revenue for the phase on its delivery date.
CHOOSE WHEN FIXED-PRICE REVENUE IS RECOGNIZED IN PRODUCTIVE.
In the bulk Deliver action, you pick the delivered date, so it can match the sign-off date. A late approval keeps the budget open, so the fee stays out of that month’s recognized revenue.
The setting applies to every fixed-price budget in your organization. Changing it recalculates past periods too, so agree the change with finance first. The Financial Items report shows when each budget’s revenue is recognized.
On the Ultimate plan, custom revenue recognition spreads one budget’s fee across periods you define. Time and materials services recognize revenue from approved time entries and expenses.
Recognize Milestone Revenue on the Day the Client Signs Off.
Give each milestone its own budget in Productive, and fixed-price revenue is recognized on the budget’s delivery date.
How Do Milestones Compare to Other Revenue Recognition Methods?
Milestones differ from other revenue recognition methods in their trigger: client acceptance of a finished phase. The percentage of completion method recognizes revenue gradually, in step with project progress. The completed contract method recognizes revenue once, when the whole project is delivered.
ASC 606 no longer uses those names. It asks whether a performance obligation is satisfied over time or at a point in time. Hours or costs spent are an input method of measuring project progress. Milestones achieved are an output method.
How each recognition method records the $60,000 website project
| Method | When revenue is recorded | On the $60,000 project | Fits when |
|---|---|---|---|
| Milestone | At each client acceptance, an output method | $15,000, $30,000, and $15,000 at the three sign-offs | Phases end in client approvals |
| Percentage of completion | Each month, by share of budgeted hours worked, an input method | $21,000, $27,000, and $12,000 for 35%, 45%, and 20% of the hours | Value builds continuously |
| Completed contract | Once, at final acceptance | $60,000 after the launch sign-off | Earlier phases give the client nothing usable |
The milestone method fits when your contract defines acceptance points and each phase gives the client something usable. Progress-based recognition fits ongoing work, such as a long implementation.
Your contract terms decide which one applies, so write the recognition method into your accounting policy.
How Do You Handle Late Approvals and Scope Changes?
You handle late approvals by holding the fee until sign-off, and scope changes by testing the added work.
Example: Discovery was approved in March, and launch is due in May. Build approval is planned for April 30, and the $30,000 invoice goes out that day. The client asks for fixes and approves on May 6. A spreadsheet that books on planned dates shows $30,000 of April revenue that wasn’t earned.
Example: revenue by month when build approval slips from April 30 to May 6
| Month | Booked on planned dates | Booked on sign-off dates |
|---|---|---|
| March | $15,000 | $15,000 |
| April | $30,000 | $0 |
| May | $15,000 | $45,000 |
Keep two date columns for each fixed-fee milestone in your revenue recognition schedule: planned sign-off and actual sign-off. Recognize a row only when the actual date is filled. Before month-end close, match every recognized entry to a dated approval.
ASC 606 calls a scope change a contract modification. The test is whether the added goods or services are distinct. If the client can use them alone and you charge your standalone price, treat them as a new milestone.
If they only extend a phase, the change order raises the transaction price and that phase’s fee.
Example: Mid-build, the client adds a $6,000 blog migration it could buy separately, so it becomes a fourth milestone. Two extra page templates for $4,000 only extend the build, which becomes a $34,000 milestone.
What Are the Best Practices for Milestone Billing?
The best practices for milestone billing are acceptance rules, automated invoice drafts, and a synced accounting system. Together they tie every revenue entry, and the invoice behind it, to one dated client approval.
Best Practice 1: Write Specific Acceptance Rules
Write an acceptance rule into the SOW for every milestone before the phase starts. Each rule names the deliverable, the acceptance criteria, the client approver, the proof of sign-off, and the fee. Write criteria the client can check, such as a passed QA checklist, never “upon client satisfaction”.
Example: Discovery passes when the client’s marketing lead approves the sitemap and wireframes by email.
Store those client acceptance records in your project management tool, where finance and auditors can find them. Change orders rewrite the affected rule and its fee. The rules hold when your receivables report shows no invoice on hold over a scope question.
Best Practice 2: Automate Invoice Draft Creation
Automate invoice draft creation so a finished phase can’t go unbilled because someone forgot it. You set this up with Productive’s Automations for invoice drafts. When a milestone budget is marked Delivered, the automation creates the invoice draft and sends finance a Slack message.
USE PRODUCTIVE TO CUT MANUAL ADMIN WITH AUTOMATIONS.
Finance teams check each draft against the client approval and the milestone’s fee before sending it. It’s working when the month-end draft list equals the list of approved milestones.
Set up AI agents to help you out with invoicing.
Best Practice 3: Integrate Milestone Billing With Your Accounting System
Integrate milestone billing with your accounting system so each invoice is entered once. Productive integrates with Xero and QuickBooks on its Professional and Ultimate plans. You copy a finalized invoice to your accounting tool from the invoice screen, one by one or in bulk.
Payments recorded there can sync back, so finance teams and project managers see the same paid status. To compare tools for this setup, see our project accounting software list. At month-end, invoice totals should match in both systems, with no manual journal entries.
What Are the Common Mistakes in Milestone Accounting?
Common mistakes in milestone accounting are payment-based fee splits, phases with no standalone use, and milestones spaced months apart. Each one books revenue in the wrong period.
Splitting the Fee by the Payment Schedule
Splitting the fee by the payment schedule books revenue the way you get paid. ASC 606 allocates it by standalone prices instead. Example: A 50% deposit on the website project would book $30,000 at discovery, double its $15,000 share. Keep the milestone payment terms in the billing schedule, and base revenue on the allocated fees.
Counting a Phase the Client Can’t Use Alone
Counting a phase the client can’t use alone creates a milestone that isn’t a real performance obligation. Example: An internal QA pass or a first draft only feeds the next phase. Merge it into the phase it feeds, and recognize revenue when the client accepts that phase.
Spacing Milestones Months Apart
Spacing milestones months apart leaves whole months with costs and no revenue, then one large spike. Your financial statements then show losses in months when the team worked at full capacity. If you bill at the same milestones, cash flow dips in those months too. Add interim deliverables the client accepts, or ask your accountant whether the work qualifies for recognition over time.
Final Thoughts: Let the Sign-Off Date Set the Revenue Date
Milestone revenue recognition works when every revenue entry traces back to one dated client approval. If the entry follows an invoice or a planned date instead, your monthly financial reports reflect paperwork, not delivery.
Start with one live project: list each milestone’s approval date beside its revenue entry, and fix any mismatch. If you want milestone budgets, invoice automation, and accounting sync in one tool, book a demo with Productive.
FAQ
What Do Milestone Contracts Need to Define?
Milestone contracts need to define each deliverable, its acceptance criteria, the approver, the proof of sign-off, and the fee. Add a review window, such as ten business days, after which the phase counts as accepted.
What Counts as Proof of Sign-Off?
Proof of sign-off is a dated, written approval from the approver named in the contract. An approval email, a signed acceptance form, or an approval logged in your project management tool all count. A verbal okay on a call doesn’t, so follow it up in writing.
Does ASC 606 Allow Booking Revenue by Milestone?
ASC 606 allows booking revenue by milestone when each milestone is a separate performance obligation the client accepts. Milestones can also measure progress on one larger performance obligation, as an output method. Hours worked against budget would be an input method instead. The older milestone method of revenue recognition, built for research and development deals, was replaced by ASC 606.
What Are the 4 Criteria for Revenue Recognition?
The 4 criteria for revenue recognition are an agreed arrangement, delivery, a fixed or determinable price, and collectibility. They come from older US guidance, SEC Staff Accounting Bulletins 101 and 104. ASC 606 replaced them with its five-step process, starting in 2018 for public companies.
Can You Recognize Revenue When the Client Pays?
You can recognize revenue when the client pays only if the work is already delivered and accepted. Under accrual accounting, a payment received earlier stays a liability until then. The installment method and the cost recovery method tie revenue to cash collected. ASC 606 ties it to delivery.
Run Milestone Billing Without Juggling Spreadsheets.
Schedule milestone invoices in Productive, automate the drafts, and copy them to Xero or QuickBooks.