SaaS implementation projects: separate onboarding fees from delivery margin

The subscription is signed, the onboarding invoice is paid, and the customer is three weeks from launch. Then an unplanned data cleanup adds six consulting sessions. The finance team needs to see the additional delivery cost and unfinished work, even if the commercial fee remains unchanged and the subscription sale looks healthy.

Give each implementation a project record tied to the customer contract. Track the commercial fee, approved scope, actual effort, outside costs, expected remaining work, and changes. Keep this operating view alongside the revenue-recognition schedule. An invoice label and a project-cost report do not settle when the fee becomes accounting revenue.

Onboarding can involve guidance, configuration, migration, training, integration, or hands-on delivery. Those are different commitments. HubSpot, for example, describes technical and strategic guidance in its onboarding offering. That published scope illustrates why a buyer and provider need to distinguish advice about setup from an agreement to perform every implementation task.

Document who cleans source data, supplies credentials, builds integrations, tests outputs, approves acceptance, and trains end users. Define the included number or scope of sessions where applicable. If the sales proposal promises a working integration but the delivery plan includes only a configuration workshop, resolve the gap before it becomes recurring unpaid work.

Retain the approved scope version and change requests. A longer calendar duration may reflect customer delay without more consultant hours, while a short project may require intensive engineering. Report effort and elapsed time separately so the operational explanation remains visible.

The IFRS Interpretations Committee's January 2019 discussion of upfront fees explains that setup activity does not necessarily transfer a separate service. Its specific case concerns a stock exchange, so it does not determine a SaaS contract's result. The useful principle is to examine the goods and services promised and the actual transfer to the customer.

FASB's original Topic 606 amendments similarly discuss nonrefundable upfront fees and identifying performance obligations. The current applicable codification, later amendments, and the contract's facts govern a US GAAP assessment. Give the accountant the bundle, standalone service evidence, acceptance terms, and renewal rights rather than assuming every separately invoiced onboarding fee is immediately earned.

Maintain a bridge between the commercial project fee and any revenue allocated to the accounting performance obligation. They can differ. Label a fee-minus-delivery-cost report as an operating measure when it is not the financial-statement service margin, and explain the difference to management.

Assume a hypothetical implementation has a $6,000 commercial fee. The plan calls for 40 hours at an internal cost rate of $80 per hour plus $800 of outside services. Planned cost is $4,000, giving a $2,000 operating contribution before other overhead. The internal cost rate is an assumed management input, not a vendor price or universal labor benchmark.

At the review date, 35 hours have been used and the delivery lead expects 25 more. Forecast labor becomes 60 hours multiplied by $80, or $4,800. With the same $800 outside cost, expected total cost is $5,600 and operating contribution falls to $400. The unpaid or unperformed portion of the work cannot disappear from the estimate because the customer already paid.

If the customer approves a $1,000 scope addition that requires another five hours, the commercial fee becomes $7,000 and forecast cost becomes $6,000. The revised contribution is $1,000. Keep approval, incremental work, and the separate accounting assessment of the contract change together.

Classify extra work by cause: unclear scope, customer data condition, product defect, new requirement, consultant rework, or delayed decisions. Attach the explanation to recorded time or supplier cost. A single overrun total tells management little about which promise, process, or product needs attention.

Review shared implementation specialists as well as named consultants. An engineer who joins several difficult customer calls can become a material delivery cost even if their time never appears in the professional-services system. Use a practical consistent method to capture that effort and avoid counting it in two cost categories.

Record completed scope, acceptance evidence where relevant, open obligations, remaining costs, and the handover to support. Reconcile supplier invoices and accrued work to the project estimate. A launch date may be an operating milestone without proving that all contractual implementation work is complete.

Compare similar projects by scope and customer complexity, not only by fee. Decide whether to revise qualification questions, included services, change approval, or delivery pricing. The useful conclusion is a concrete change to how the next implementation is sold and delivered, supported by actual effort rather than a broad claim about customer value.