A SaaS setup fee is nonrefundable: what evidence does accounting need?

A contract can call an upfront charge a setup fee without explaining the service it buys. Ask the delivery owner to describe the actual work: creating an account, importing records, configuring a customer's workflow, training staff or providing a usable deliverable. Separate internal preparation from work the customer receives and can evaluate. The fee's name is a starting point for investigation, not the accounting conclusion.

The IFRS Interpretations Committee's 2019 discussion of upfront fees emphasizes assessing whether activities transfer a promised service. Its specific decision concerned a stock exchange, not a SaaS company. Use the principle to frame questions for your accountant, who should apply your reporting framework to the particular subscription and implementation arrangement.

Retain the signed order, statement of work, sales promises and completion records. For each setup activity, identify who performs it, what output exists and whether the customer can use that output apart from the continuing subscription. Include dependencies: a configuration file that works only within the hosted application presents a different fact pattern from a separately usable training program.

Ask what would happen if the customer stopped after setup. Would it keep a useful deliverable, owe further amounts or lose access to everything? Record the contractual answer and the operational reality. If the team has never sold the activity separately, say so. A hypothetical standalone price created for a sales proposal is weaker evidence than an actual comparable transaction.

Nonrefundable describes one term governing the customer's payment. Finance still needs an approved conclusion about the promise being delivered and the relevant period. Give the reviewer any cancellation, termination or service-failure clauses that qualify the headline wording. A side agreement offering a refund if implementation fails belongs in the same review packet.

For illustration, two vendors could each collect a $2,000 onboarding charge. One provides a separately usable training course; the other creates internal account settings needed to deliver its hosted service. The identical amount and fee label do not establish identical treatment. The example is a prompt to compare evidence, not a conclusion that either fee should be recognized immediately.

Ask accounting to document its conclusion, applicable policy, allocation method where relevant and required delivery evidence. The revenue schedule should refer to the contract and fee line so someone can move from the balance back to the underlying agreement. Keep the invoice date, payment date and service evidence distinct even if they happen to fall in the same month.

If the conclusion depends on a later milestone, assign an owner to confirm that milestone and state the evidence expected. A project manager's general note that onboarding is done may omit an undelivered training session or outstanding customer acceptance. Resolve those facts before the schedule is approved, and preserve the decision made at the time.

Review new setup packages when the product or delivery model changes. A prior conclusion for automated account activation may not fit a new paid migration service with separate deliverables. Add a short question to deal intake asking whether the charge buys anything beyond the standard subscription and who can substantiate the answer.

When engaging an outside accountant, supply a redacted contract and completed delivery record before requesting a policy recommendation. A useful response explains the evidence that matters and any missing facts. It should leave your team with a repeatable review for genuinely similar arrangements and a clear route for escalating exceptions.