Short answer: In most SaaS contracts, an implementation or onboarding fee is not a separate performance obligation, so it is not recognized when the setup work is done. It is combined with the subscription and recognized over the contract term or, if paying it once gives the customer a material right to renew without paying it again, over the longer period the customer is expected to stay.
This applies to any SaaS company that charges an upfront setup, onboarding or implementation fee alongside a subscription. Recognizing the fee in the month it is invoiced, when the setup is not a separate obligation, overstates revenue in the months a company signs large deals.
Why the setup fee is not revenue on day one
Revenue is recognized when the company satisfies a performance obligation by transferring control of a promised good or service, as the IFRS Foundation summary of IFRS 15 sets out in its five-step model. ASC 606 uses the same model. An upfront fee is therefore revenue only if it pays for something the customer receives.
Much SaaS setup work does not transfer anything to the customer on its own. Creating the tenant, loading the customer's data, configuring standard settings and running a kickoff call are activities the company performs so that it can deliver the subscription. The standards treat activities like these as part of fulfilling the main promise, not as a separate service. The fee is then an advance payment for the subscription and is recorded as deferred revenue until it is earned.
How to test whether implementation is distinct
An implementation service is a separate performance obligation only if it is distinct. That requires two conditions to be met.
- Capable of being distinct. The customer can benefit from the service on its own or together with resources that are readily available, such as a service other providers sell.
- Distinct in the context of the contract. The service is separately identifiable from the subscription. It does not significantly modify or customize the software, and it is not highly interdependent with it.
Indicators that implementation is distinct include: other firms, such as consultants or partners, offer the same service; the customer could use the software without it; and the company sells the service separately. Indicators that it is not distinct include setup work only the company can perform, configuration the customer cannot use without the subscription, and work that significantly customizes the platform. Our guide to revenue recognition types covers how point-in-time and over-time obligations differ.
When implementation is distinct, part of the transaction price is allocated to it based on standalone selling prices, and that part is recognized as the work is delivered.
Contract term or expected customer period
When the fee is not distinct, the next question is how long to spread it over. The answer depends on whether the fee creates a material right.
A material right is an option that gives the customer something it would not receive without entering the contract. In SaaS, the usual example is renewal: a new customer pays a $12,000 setup fee, but an existing customer renews without paying it again. That renewal price is lower than a new customer would pay, so the right to renew at that price may be a material right.
- No material right. Renewing customers pay a fee that reflects the value delivered, or the fee is small relative to the contract. The setup fee is recognized over the contract term.
- Material right. The renewal discount is significant. Part of the fee relates to future renewals, so it is recognized over the period the customer is expected to stay, which is often longer than the initial term.
The standards allow a practical alternative for renewal options of this kind: the company can estimate the goods or services it expects to provide, and the consideration it expects to receive, across the expected renewals. In practice, this is why many SaaS companies recognize a material upfront fee over an expected customer period based on their own retention history. That estimate should be documented and revisited as retention data changes.
Illustrative recognition schedule
Illustrative example: on January 1, 2026, a customer signs a 12-month subscription for $60,000 and pays a $12,000 onboarding fee upfront. The onboarding is not distinct. Renewing customers do not pay the fee again, and the company's retention data supports an expected customer period of 36 months. The table below compares the two outcomes.
| Line | Over the 12-month term | Over a 36-month expected period |
|---|
| Onboarding fee recognized each month | $1,000 | $333 |
| Onboarding fee recognized in 2026 | $12,000 | $4,000 |
| Subscription revenue recognized in 2026 | $60,000 | $60,000 |
| Deferred onboarding fee at December 31, 2026 | $0 | $8,000 |
Source: illustrative figures, not customer data.
If the fee were recognized in January when invoiced, January revenue would be overstated by $11,000 under the contract-term approach and by $11,667 under the expected-period approach. If the customer leaves at the end of the first year, the remaining deferred balance is recognized at that point, because no further service is owed.
Costs to set up a customer are a separate question
The fee the customer pays and the costs the company incurs are accounted for separately. Costs incurred to fulfill a contract, such as the salaries of an onboarding team, are capitalized as an asset if they relate directly to the contract, generate or enhance resources the company will use to deliver the service, and are expected to be recovered. Otherwise they are expensed as incurred.
Capitalized fulfillment costs are amortized on a systematic basis consistent with the transfer of the related services, which is often the same expected period used for the fee. Sales commissions are a different category, costs to obtain a contract, with their own capitalization rules. Many finance teams keep both in a schedule alongside their prepayments so that amortization is reviewed at each close.
Common mistakes with onboarding fees
- Recognizing the fee on invoice. Unless implementation is distinct and complete, the fee belongs in deferred revenue.
- Treating every implementation as distinct. Calling setup a separate service because it appears as a separate line on the order form does not meet the test.
- Ignoring the renewal price. If renewals skip the fee, the material right question needs an answer on file.
- Using a customer period without evidence. The expected period should come from the company's retention data, not a round number.
- Netting costs against the fee. Fulfillment costs and the onboarding fee are measured and presented separately.
How ScaleXP supports onboarding fee schedules
Once finance has decided the recognition period for a fee, the work is keeping a schedule for each customer and releasing the right amount every month. ScaleXP builds revenue schedules from your invoice data in Xero or QuickBooks, with contract details from HubSpot, Salesforce or Pipedrive, and prepares the revenue journals. The journals are posted once finance approves them, so the judgment on distinctness and the recognition period stays with the finance team.
See how the schedules and journals work on the revenue recognition automation for Xero and QuickBooks page, and how deferred balances are tracked on the deferred revenue automation page.
Conclusion
Implementation and onboarding fees in SaaS are usually not revenue when invoiced. Test whether the implementation is distinct; if it is not, recognize the fee with the subscription over the contract term, or over the expected customer period when renewals without the fee create a material right. Account for the setup costs separately, and document the judgments so they can be explained at audit.
Frequently asked questions
Are SaaS implementation fees recognized upfront?
Usually not. An implementation fee is recognized upfront only when the implementation is a distinct performance obligation and the work has been delivered. Most SaaS setup work is not distinct, because the customer cannot benefit from it without the subscription. In that case, the fee is deferred and recognized with the subscription over the contract term or the expected customer period.
What makes an implementation service distinct?
An implementation service is distinct when the customer can benefit from it on its own or with readily available resources, and it is separately identifiable from the software. Signs include other providers offering the same service and the customer being able to use the software without it. Significant customization of the platform usually means the service is not distinct.
What is a material right in a SaaS setup fee?
A material right is an option the customer would not receive without entering the contract. If new customers pay a setup fee but renewing customers do not, the right to renew without the fee may be a material right. When it is, part of the fee relates to future renewals and is recognized over the expected customer period rather than the initial term.
How do you estimate the expected customer period?
The expected customer period is based on the company's own retention history for similar customers, such as average customer lifetime by segment or plan. It should be supported by data, documented in the revenue policy and reviewed when retention changes. A round number without evidence is difficult to defend at audit, and changes to the estimate are applied going forward.
Can onboarding costs be capitalized?
Onboarding costs can be capitalized when they relate directly to a contract, generate or enhance resources used to deliver the service, and are expected to be recovered. Capitalized costs are amortized in line with the transfer of the related service, often over the same expected period as the fee. Costs that do not meet these conditions are expensed as incurred.
Sources (checked October 2026): IFRS Foundation, IFRS 15 Revenue from Contracts with Customers.
