Service contracts do not follow the same revenue recognition pattern as product sales or standard subscriptions.

Finance teams record revenue only as the organization delivers service. That means finance must spread revenue across the contract instead of booking it up front.

When revenue recognition timing shifts, so does when commissions can be earned, expensed, and reported.

Since sales commissions are treated as a cost of obtaining a contract, they need to be capitalized and amortized over the same period as the revenue. So, under service contracts, your rep commissions are calculated differently, and they get expensed differently, too.

This guide covers how the three main types of service contracts change revenue recognition under ASC 606 and what that means for sales compensation teams.

Key Takeaways

• Service contracts spread revenue across delivery, milestones, or time, instead of recognizing it all up front.
• Fixed-fee (milestone-based), time-and-materials, and recurring service contracts each change when revenue hits the books. Those differences affect how you need to handle commissions.
• Under ASC 606, commissions on longer-term contracts don’t get expensed immediately; they’re capitalized and amortized alongside the revenue.
• When revenue and commission timing fall out of sync, teams end up with distorted margin reporting, audit exposure from premature expense recognition, and ongoing reconciliation work to explain payouts to reps.

Why Service Contracts Are Different

Service contracts don’t provide finance teams a tidy moment where the deal is “done,” and they can put the revenue in the books. The work is delivered over time, and finance records revenue as that work happens, not when the contract is signed.

Service contracts also change when finance can recognize commission expenses, which forces comp models to adjust to align with service delivery.

Over-Time vs. Point-in-Time Recognition

ASC 606 splits revenue into two buckets: point-in-time and over-time.

Point-in-time is straightforward. A company ships a product. Once the customer receives it, the company records the revenue.

Service contracts almost always fall into the over-time category because the customer pays up front, and then the company provides service over time. The classic example is an annual subscription service.

The three ways revenue may qualify for over-time recognition are:

• The customer simultaneously receives and consumes benefits.
• The entity's performance creates or enhances an asset the customer controls.
• The entity's performance does not create an asset with alternative use and has an enforceable right to payment for performance to date. 

The Three Types of Service Contracts

Not all service contracts behave the same way, and the structure of the contract determines how revenue is recognized.

Most teams are dealing with some mix of three service models:

• Fixed-fee (milestone-based): Finance records revenue when the company completes defined milestones, and the customer accepts the work.
• Time-and-materials: Finance records revenue as staff completes work, or as the company incurs costs.
• Recurring or retainer: Revenue is spread evenly across the service period.

Each of these creates a different revenue timeline, which means commissions tied to those deals follow different earning and expense patterns.

The next section breaks down how each model works in practice and where teams tend to run into issues when they try to manage all three at once.

How Each Contract Type Changes Recognition

The structure of the service contract determines how revenue shows up and how commissions follow it. Milestone-based work ties revenue to deliverables, time-and-materials ties it to hours worked, and retainers spread it across the contract term.

Fixed-Fee and Milestone-Based Contracts

Revenue is tied to defined deliverables and recorded when each milestone is completed and accepted by the customer. This is an output-based approach under ASC 606.

Even if the customer has already paid, revenue doesn’t get recorded until that milestone is delivered. 

An example is a consulting engagement with three phases. Each phase has a defined deliverable, and revenue for that portion of the contract only gets recorded once the client signs off.

For comp teams, this creates step-function revenue. Nothing hits, then a milestone closes, and a chunk of revenue lands at once.

Time-and-Materials Contracts

Time-and-materials contracts tie revenue directly to the work performed. Teams record revenue as they log hours or incur costs.

For example, a consulting or implementation project is billed hourly. If a team logs 120 hours in a month at $200 per hour, they invoice $24,000 for that work.

For these contracts, revenue usually follows billing. If you bill based on hours worked, finance can record revenue using the invoice instead of calculating it separately.

That only works when billing matches the work completed. If the team does the work in January but invoices in March, or if the contract includes a fixed monthly minimum regardless of hours worked, the invoice no longer reflects what was delivered in that period.

In those cases, finance records revenue based on progress instead. They track how much work has been completed, such as hours worked to date relative to the total expected, and recognize revenue for that portion even if it hasn’t been invoiced yet.

Recurring and Retainer Service Contracts

Retainer contracts spread revenue evenly across the service period. If a customer signs a 12-month agreement for ongoing advisory services, finance records one-twelfth of the total contract value each month.

It gets more complicated when teams add variability. Overage hours, add-on work, and scope changes increase or decrease the total contract value over time. When that happens, finance can’t rely on a straight-line schedule. They adjust revenue as the contract changes, which shifts how much gets recorded in each period.

Measuring Progress: Input vs. Output Methods

ASC 606 requires teams to pick a method that accurately reflects how they deliver services.

That choice then determines how much revenue gets recorded in each period, which flows directly into commission expense.

Input Methods

Input methods track revenue based on the effort required to deliver the work. Teams record revenue as they log hours, incur costs, or use resources relative to the total expected. This is common in time-and-materials and cost-plus contracts, where tracking effort is straightforward and closely tied to how the work gets done.

The tradeoff is that effort doesn’t always equal value. If a project runs inefficiently and requires more hours than expected, teams may record more revenue even though the customer isn’t receiving additional value. That can distort both revenue reporting and the commission expense tied to it. You end up in a situation where revenue looks higher in-period, and commission expense increases alongside it. However, under the hood, actual profitability has declined.

Output Methods

Output methods track revenue based on what the customer receives. Revenue is recorded when teams complete milestones, deliver defined outputs, or get customer acceptance.

Teams use this approach in fixed-fee and milestone-based contracts, where the contract spells out specific deliverables and when the customer accepts them.

This keeps revenue tied directly to value. Once a team completes a milestone and the customer signs off, finance records that portion of the contract as revenue.

But the issue shows up in timing. Milestones rarely land evenly, so revenue comes in large increments instead of a steady flow. Those spikes and dips in revenue make it difficult to measure performance, and it can muddy your forecast. A single delayed milestone can shift both revenue and commissions into a different period, exacerbating revenue variability from period to period.

What This Means for Sales Commissions

When revenue shifts from upfront to over time, commissions become harder to track, expense, and reconcile because payout timing and expense recognition no longer align.

Sales teams still earn and get paid commissions at close, but finance has to recognize that cost over the life of the contract. That creates a split between cash paid and expense recognized, which complicates cost of sales, margin reporting, and audit support. Finance teams need to track each commission across its full amortization schedule, tie it back to the underlying contract, and ensure it stays aligned with revenue recognition.

As contract structures become more complex with multi-year terms, usage-based pricing, and mid-contract changes, that tracking burden increases quickly. What looks like a single payout to a rep becomes a multi-period accounting schedule that finance has to maintain and defend.

That’s where systems matter. Once revenue recognition sets the schedule, companies need a way to apply that same logic to commissions without managing it manually.

Commission Timing Follows Revenue Timing

When a rep closes a $500K milestone-based consulting contract, the deal is done from a bookings perspective. But that doesn’t mean the commission or the revenue hits the P&L all at once.

Say the rep earns a 10% commission, or $50K, and the company pays that amount right after the deal closes. From a cash flow perspective, the transaction is complete, and the rep has been paid.

Finance handles it differently.

If the contract recognizes $200K, $150K, and $150K of revenue across three milestones over 18 months, finance spreads the $50K commission expense across those same milestones. When the company records the first $200K of revenue, it records $20K of commission expense. As it records each $150K milestone, it records $15K of commission expense alongside it. So even though the company pays $50K up front, the expense shows up gradually as the work is delivered.

That’s the split finance teams have to manage. Cash goes out up front when the company pays the commission, but the expense hits the P&L over time in line with revenue.

That mismatch affects how companies measure margin, cost of sales, and profitability in any given period. A large deal can create a significant cash outflow in one quarter while only a portion of the expense shows up in the same period, which makes performance harder to interpret and forecast.

It also creates an operational burden. Finance has to track each commission across its full amortization schedule, tie it back to the underlying contract, and ensure it stays aligned with revenue recognition for audit purposes. As deal structures get more complex, that tracking becomes harder to manage manually and easier to get wrong.

ASC 606 Commission Capitalization Requirements

ASC 606 treats commissions as a cost of obtaining a contract. Instead of expensing that cost immediately, finance capitalizes it and amortizes it over the period the company delivers the service. For service contracts, that period often spans the full contract term or expected customer relationship, which can run multiple years.

There’s a narrow exception. If the amortization period is one year or less, finance can expense commissions immediately. Once contracts extend beyond that, the law requires capitalization.

For comp teams, this means every deal carries a multi-period expense schedule that has to stay aligned with how revenue is recorded.

If those schedules fall out of sync, finance can misstate cost of sales and margin in a given period, which creates problems for forecasting, board reporting, and audits. Comp teams also have to maintain that alignment over time as contracts change, which turns what looks like a single commission payout into an ongoing accounting process that needs to be accurate and defensible.

The Operational Complexity Problem

Most teams aren’t managing a single contract type or a single commission plan. They’re managing a mix of milestone-based deals, time-and-materials work, and retainers, each with different revenue timelines.

Each combination of contract and comp plan creates its own capitalization and amortization schedule. Over time, that turns into dozens or hundreds of overlapping schedules that finance has to track and reconcile.

In spreadsheets, this quickly becomes difficult to maintain. Small errors in timing or allocation can cascade into reporting issues, audit exposure, and constant back-and-forth between finance and RevOps.

That’s why most teams that arrive at this level of operational complexity choose an Incentive Compensation Management (ICM) platform like CaptivateIQ. An ICM platform can automate commission capitalization and amortization, align commission expenses with revenue recognition schedules, and generate audit-ready reports.

Common Revenue Recognition Pitfalls in SaaS Contracts

Mistiming revenue and commission accounting distorts your P&L statement and increases the organization’s audit risk.

In practice, these problems arise when teams recognize commission expense too early, treat different contract types the same, or fail to adjust for mid-contract changes.

Recognizing Commission Expense Before Revenue

If teams expense commissions early, they record the cost before the related revenue. That makes early periods look less profitable and later periods look more profitable than they actually are, which distorts margin, skews performance trends, and makes it harder to understand how the business is actually performing.

It also puts the company out of compliance with ASC 606’s requirement to align commission expenses with revenue, which increases audit risk and can lead to restatements or scrutiny during financial reviews.

Treating All Service Contracts the Same

Different contract types create different revenue timelines, and commission accounting needs to follow those timelines.

A milestone-based consulting project recognizes revenue in chunks tied to delivery. A monthly retainer recognizes revenue evenly over time. If both run through the same commission recognition logic, one of them will be wrong.

Comp plans don’t need to change for every deal, but the way commission expense is recognized needs to map to how the contract delivers value.

Revenue defines when the company actually earns value from the contract, and commission expense is supposed to follow that same pattern.

If commission expense doesn’t map to how the contract delivers value, finance ends up recognizing costs in a different period than the revenue they relate to. That breaks margin accuracy, since cost of sales no longer reflects the revenue in the same period, and it makes performance harder to interpret.

It also creates compliance risk. ASC 340-40 requires companies to align commission expense with the period of benefit, which in SaaS typically mirrors revenue recognition. If those don’t line up, finance has to justify the mismatch or correct it.

Ignoring Mid-Contract Changes

Service contracts morph as the work evolves. Teams add scope, extend deadlines, and tweak milestones all the time.

When that happens, finance has to update how it recognizes revenue. That change flows directly into how commission expense gets recognized as well.

If the comp process doesn’t adjust alongside those changes, teams end up manually correcting revenue and commission timing, adding reconciliation work and increasing audit exposure.

It’s better to build flexibility into commission plans so they can handle contract changes without manual rework. That means tying commissions to contract terms, defining how upgrades and downgrades are treated, and using systems that can automatically update both payouts and amortization schedules when a deal changes.

FAQ

What is revenue recognition for service contracts?

Revenue recognition for service contracts means recording revenue as the work is delivered, not when the deal closes or the invoice is sent.

For most service contracts, that happens over time, tied to milestones, hours worked, or the length of the agreement.

How does ASC 606 apply to professional services?

ASC 606 requires companies to record revenue when the customer receives value.

For professional services, that usually means recognizing revenue as the work is performed. It also requires teams to align related costs, including commissions, with that same timeline.

When are commissions recognized on service contracts?

Companies can pay commissions when a deal closes, but finance recognizes the expense over time as revenue is recorded.

If a contract delivers revenue across multiple periods, the commission expense follows that same pattern, even if the cash payment happens up front.

What is the difference between input and output methods for measuring progress?

Input methods track revenue based on effort, such as hours worked or costs incurred.

Output methods track revenue based on results, such as completed milestones or delivered work.

The method you choose determines whether revenue flows steadily with activity or shows up in larger increments tied to delivery.

Do I need to capitalize commissions on service contracts?

If the contract term is longer than one year, ASC 606 requires companies to capitalize commissions and amortize them over the period the service is delivered.

If the contract term is one year or less, companies can expense commissions immediately.

How do contract modifications affect revenue recognition and commissions?

When teams change scope, pricing, or timelines, they change the underlying economics of the contract, so finance has to update the revenue schedule to reflect what the company now expects to deliver and earn.

Those changes also affect how commission expense is recognized. If teams don’t update both together, revenue and commission timing fall out of sync, which leads to reporting issues and manual reconciliation work.

Align Commission Recognition With Revenue Recognition

Service contracts alter revenue recognition, and commission accounting has to follow that same timeline.

Once revenue shifts to milestones, hours worked, or contract duration, commission expense can’t stay tied to bookings alone because bookings no longer reflect when the company actually earns the revenue.

Instead, finance needs to recognize it alongside revenue, and comp teams need to manage that alignment across different contract types.

That becomes difficult to maintain manually. Milestone-based deals, time-and-materials work, and retainers all follow different revenue schedules, and each one creates its own commission expense timeline.

CaptivateIQ handles that complexity by connecting commission logic directly to revenue data. Teams can automate commission calculations, align expense recognition with ASC 606 requirements, and manage multiple contract structures without relying on spreadsheets.

Request a demo to see how CaptivateIQ supports commission accounting across service contracts.