The setup fee that can outlast its first contract.

One contract to work through.

An example SaaS company with a calendar year end signs a customer on 1 April 2026: a 60,000 dollar annual subscription and a 15,000 dollar implementation fee, both invoiced at signing and neither refundable. The team configures the tenant, loads the customer’s opening data and trains their users, and the customer goes live on 20 May. At renewal the customer pays the subscription only. New customers always pay the fee.

Search for how to recognize that fee and a common answer comes back. One April 2026 guide says implementation services are typically a separate performance obligation, recognized when delivered. That is right for some contracts. The standard itself starts from the other direction, and for many SaaS setups it ends somewhere else.

Two questions decide the period.

The first is whether the implementation is a service at all. We read ASU 2014-09 in the file. Paragraph 606-10-25-17 is direct about setup work:

“Therefore, those setup activities are not a performance obligation.”ASC 606-10-25-17

Implementation is a separate obligation only when it is distinct under 606-10-25-19: the customer can benefit from it on its own or with resources readily available to them, and it is separately identifiable from the subscription. Data migration that a consultant could do, or training that is useful beyond your product, can pass. Configuring a tenant so the customer can log in usually does not.

The second question applies when the answer is setup. Paragraph 606-10-55-51 says the fee is then an advance payment for the future services, and adds that the recognition period would extend beyond the initial contractual period if the renewal option gives the customer a material right. The standard’s own Example 53, a transaction processor charging a nominal setup fee, concludes there is no material right and spreads the fee over the services in the contract.

Four answers on the same 75,000 dollars.

We ran the contract through each outcome, plus the shortcut of booking the fee when it is invoiced. Nine months of the term fall in 2026.

The distinct case has a detail that surprises people. With standalone selling prices of 60,000 and 20,000, the 75,000 contract price is shared three quarters and one quarter, so the implementation earns 18,750 at go live and the subscription carries 56,250, less than its 60,000 invoice line. The material right case spreads 195,000 of expected consideration evenly over 36 months, so the first year recognizes 65,000 and 10,000 of the fee is still deferred when the customer renews. From 48,750 to 60,937.50 is 12,187.50 dollars, 25 percent, on a single contract.

Testing the renewal with your own prices.

The material right test compares what a renewing customer pays with what they would pay without the first contract. Deloitte’s revenue roadmap lists the renewal price compared with the price a new customer would pay among the factors, and works two membership examples to opposite conclusions on that basis. In our contract a new customer pays 75,000 for the first year and a renewing customer pays 60,000, a 20 percent difference. That points to a material right. A fee of 1,500 on the same subscription would be closer to Example 53.

For renewals, 606-10-55-45 offers a practical alternative to pricing the option: allocate the transaction price by reference to the services expected to be provided and the consideration expected for them. That is how the table reaches 65,000 a year. The expected renewals should come from your renewal history, and the estimate is reviewed as that history grows. If a customer leaves after the first term, 606-10-55-42 recognizes what is left when the option expires, so the balance clears on its own terms.

The cost side follows the same logic. Under 340-40-25-5, costs to fulfill a contract that relate directly to it, build resources used to satisfy future obligations and are expected to be recovered become an asset, and 340-40-35-1 amortizes that asset in line with the services it relates to, including specific anticipated contracts. Setup labor capitalized this way moves in step with the fee, which keeps margin steady through go live.

Setting up the same contract in Rivane.

In Rivane a revenue contract holds one or more performance obligations, each with a standalone selling price and a recognition pattern. The price is required: an obligation without one is rejected rather than given an even share. When the contract is activated, Rivane allocates the contract price across the obligations by relative standalone selling price, and the allocated amounts always sum exactly to the contract price. A contract with no obligations declared is treated as a single time based obligation, which is the setup only case.

There are two patterns. Time based spreads an obligation evenly by calendar month between its start and end dates, with the final month taking any rounding. At delivery recognizes the whole allocated amount in the month of the obligation’s start date, so for distinct implementation work that date should be go live, not signing. Recognition runs monthly, per obligation, and once anything has posted the allocation is locked, which is why the two questions above belong before the first month end.

# Case one in Rivane: implementation is distinct.
# Example company. Shape only.

contract:   60,000 subscription + 15,000 implementation
            2026-04-01 to 2027-03-31, total 75,000.00

obligation           pattern       dates                   SSP
Subscription         TIME_BASED    2026-04-01..2027-03-31  60,000.00
Implementation       AT_DELIVERY   2026-05-20 (go live)    20,000.00

activate -> allocated by relative SSP
Subscription         56,250.00     4,687.50 a month
Implementation       18,750.00     all in May 2026
allocated total      75,000.00     exact, no plug

missing SSP          -> rejected, SSP_UNRESOLVED
after first posting  -> allocation locked

Two limits are worth knowing. Implementation recognized over time by progress, such as percentage of completion, is not supported today; at delivery is a single point. And an obligation’s dates must sit inside the contract, so the material right case, which runs past the first term, cannot be held as an obligation yet. For that case, recognize the year one amount on the contract and carry the 10,000 into a separate material right liability account by journal, released as each renewal is served.

A short checklist for implementation fees.

• For each contract type, write down whether the implementation work transfers a service the customer could use without your platform, and why.
• If it does, set a standalone selling price for it from what you charge when it is sold alone, or from cost plus a margin, and allocate the whole contract price on those prices.
• If it does not, compare the renewal price with what a new customer pays in year one, fee included, and record the conclusion on the material right.
• If the renewal is a material right, base the expected renewals on your own renewal history, and review the estimate at least once a year.
• Date the recognition from go live for distinct implementation work, and from the subscription start for everything else.
• Settle the split before the first month is recognized, so the schedule never has to be rebuilt after revenue has posted.

Where this usually goes wrong.

• Treating every implementation fee as a separate obligation because a guide said it usually is. Configuration that only gets the customer onto your platform is the setup case the standard describes.
• Allocating by the invoice. When implementation is distinct, the contract price is shared by standalone selling price, so the subscription can carry less revenue than the subscription line on the invoice.
• Stopping at the end of the first term. A fee that customers never pay again on renewal can belong to the renewal years too.
• Forgetting the cost side. Setup labor that meets 340-40-25-5 is an asset amortized with the services it relates to, which keeps margin from swinging in the month of go live.
• Changing the answer from deal to deal. Similar contracts with different treatments are the first thing an auditor will sample.

What the audit evidence looks like.

• A memo per contract type that answers the distinct question and the material right question, with the paragraphs relied on.
• The standalone selling price support for each obligation, and the allocation it produced.
• Renewal history behind the expected renewal period, and the date it was last reviewed.
• The schedule per contract, tied to the deferred revenue and material right balances in the trial balance.
• The go live evidence for any implementation recognized at a point in time.

Answer the two questions once per contract type.

Is the implementation a service the customer could use on its own, and does renewing without the fee give a material discount? Written down for each kind of contract you sell, those two answers set the period for every fee, and the revenue schedule follows from them. An auditor then tests one documented judgement instead of a pile of individual ones.

To see the year one schedule for your own figures, put the amount allocated to the first term into the Rivane revenue recognition calculator. For the material right case above, 65,000 over 12 months gives 5,416.67 a month and 48,750.03 by December.

Sources

• FASB Accounting Standards Update 2014-09, Revenue from Contracts with Customers (Topic 606), Section A, May 2014. Downloaded and read in the file for paragraphs 606-10-25-17 (setup activities), 606-10-25-19 (distinct), 606-10-55-41 to 55-45 (customer options and material rights, including the renewal practical alternative), 606-10-55-50 to 55-53 (nonrefundable upfront fees), Example 53 at 606-10-55-358 to 55-360, and 340-40-25-5 and 340-40-35-1 (costs to fulfill a contract). Later Updates amended parts of Topic 606, so check the current Codification for final wording.
• Deloitte, Roadmap: Revenue Recognition, section 5.6 Nonrefundable Up-Front Fees. Read in the page for its factors in the material right test, including the renewal price compared with the price a new customer would pay, and its two membership examples that reach opposite conclusions.
• Livmo, SaaS Revenue Recognition: ASC 606 Mistakes That Kill Deals (27 April 2026). Read as an example of what a search currently returns. It says implementation services are typically a separate performance obligation recognized when delivered.
• Rivane revenue recognition calculator, used to check the year one schedule in the worked example: 65,000 dollars over 12 months gives 5,416.67 a month, 48,750.03 after nine months, and a final month of 5,416.63.

A note on how this was researched. The Topic 606 and Subtopic 340-40 paragraphs were read in the ASU 2014-09 file, and paragraph numbers come only from text we read. IFRS 15 carries matching guidance on non-refundable upfront fees, but the consolidated EU text could not be reached on the day we wrote this, so no IFRS paragraph is quoted. The company and contract are an example, and every figure was calculated in a script, which you can repeat with a spreadsheet. The Rivane section describes revenue contracts as the product is built today, checked against the code rather than marketing copy. Confirm the treatment of your own contracts with your auditor.

On embedded social posts: we looked for public posts from standard setters or practitioners on SaaS implementation fees and material rights and found none we could verify as current, relevant and authentic, so this article uses ordinary citations instead.