by Katy Robinson | May 26, 2026 | SaaS
Why Your Hosting Arrangement Impacts Software Revenue Recognition
The Decision That Shapes Everything After It
A software company signs a three-year contract with a new customer. The platform is hosted on servers the company deploys and manages. The customer accesses the software though a SaaS arrangement. Thus, the customer never downloads the software, doesn’t install it, and has no contractual right to take possession of the underlying code.
Under ASC 606, the first question in any software revenue arrangement is not “what are we delivering?”, it’s “does the customer obtain a software license, or are we providing a service?” The answer determines which revenue recognition framework applies to the entire deal.
The Two-Part Test
Topic 606 applies the same framework that existed under legacy US GAAP to determine whether a cloud computing arrangement includes a software license. A license exists only when both conditions are met:
Condition 1: The customer has the contractual right to take possession of the software at any time during the hosting period without significant penalty.
Condition 2: It is feasible for the customer to run the software on their own infrastructure or through a third party, independent of the vendor.
If either condition fails, there is no software license. The arrangement is a SaaS arrangement.
Why Most Hosted Arrangements Are SaaS
In practice, many hosted software arrangements fail the first condition such as when the software vendor deploys and manages the hosting environment. The customer accesses the application through a web portal. There is no contractual provision allowing the customer to download the source code or run the software independently.
The result: upfront implementation fees are often deferred and recognized ratably over the service period, which starts when the customer can start using the software. There is no upfront license revenue event. The transaction price flows through the income statement on a time-based, straight-line basis.
The distinction is not about where the software runs. It is about whether the customer controls the right to run it elsewhere.
When a License Does Exist Inside a Hosting Arrangement
Some arrangements do include an embedded software license. This happens when the customer has a genuine contractual right to take possession, even if they never exercise it, and could feasibly operate the software independently.
When a license is present, the licensing implementation guidance applies. The software license is classified as functional intellectual property. If the license is distinct from other promised goods and services, revenue attributable to the license is recognized at the point in time when the customer obtains control.
This creates a fundamentally different revenue profile: upfront license revenue at delivery, with the hosting and support services recognized ratably over the remaining contract period.
The Hybrid Problem
Increasingly, software companies offer arrangements that combine both an on-premise element and a SaaS element, an on-premise application with cloud-based modules, or a SaaS application with an offline mode.
In many cases, these two elements will be distinct from each other. But when the on-premise software cannot function without the SaaS component, or only provides insignificant standalone value, the elements are not distinct. The combined item is generally accounted for as a service arrangement rather than a license.
The test here is whether the two elements are transformative to each other (combined into something new) or merely additive (each works independently). Transformative means single performance obligation. Additive means separate.
Real-World Application
Consider a software company that provides a proprietary platform to its customers. The platform is hosted on an environment the software company deploys and manages. The customer accesses it through a web portal and has no contractual right to take possession of the software at any time.
Because the customer cannot obtain the license, the entire arrangement is classified as SaaS. Fixed subscription fees are recognized ratably. Implementation services are evaluated separately under the complex versus non-complex framework discussed in Part 3 of this series: Your Implementation Services Aren’t All Created Equal
This classification drives every subsequent decision: how implementation fees are allocated, when contract costs are capitalized, and how the balance sheet reflects the economic substance of each software agreement.
The Bottom Line
The license vs. SaaS determination is not a secondary classification exercise. It is the foundational decision that shapes your entire revenue model. Get it wrong, and every downstream calculation, transaction price allocation, performance obligation timing, contract asset treatment, is built on the wrong premise.
If your software company hosts the product and the customer has no right to take possession, you are providing a service. Your revenue recognition framework needs to reflect that reality.
At Lavoie CPA, we work with software companies navigating complex hosting arrangements and SaaS revenue models.
Start the conversation today.
by Katy Robinson | May 26, 2026 | SaaS
Why the Complex vs. Non-Complex Distinction Is the Most Important Revenue Decision Your Software Company Will Make
The Setup That Catches Every Software CFO
You signed a $2 million SaaS contract with a marquee customer. The deal includes gap analysis, data conversion, training, system architecture, user acceptance testing, and a significant block of customer-specific configuration work that requires your engineering team to modify the platform’s source code.
Your controller books the implementation revenue as one line item and starts recognizing it over time as the team delivers milestones.
That decision just created a revenue recognition problem that could restate your financials.
Here’s why: under ASC 606, not all implementation services are treated the same. The distinction between “complex” and “non-complex” implementation services determines whether those services are a separate performance obligation or must be bundled with the SaaS subscription itself. The downstream effects touch everything, including revenue timing, contract asset balances, and the story your income statement tells investors.
The Two Groups: What ASC 606 Actually Requires
These are implementation activities where the customer consumes and receives the benefit as the work is performed. They don’t modify the software’s underlying code, and critically, another qualified provider could perform them. Typical examples include:
• Gap analysis and requirements gathering
• System design and architecture
• Data conversion and migration
• User acceptance testing
• Training
• Migration and installation
Revenue treatment: Recognized over time as a separate performance obligation. The customer is receiving value from these activities independently of whether the SaaS platform is live.
Group B: Complex (Non-Distinct) Services
These are the activities that change the software itself or require customer-specific preparation to use the SaaS. They may require modifying the source code to produce functionality that didn’t exist before. In a typical SaaS contract, these may include:
• Customer-specific rule configurations that modify the platform’s code
• Data mapping to accept information from the client’s existing systems
• Required reports and templates that demand new core development
Revenue treatment: These activities are not distinct from the SaaS. They are combined with the SaaS subscription as a single performance obligation, and revenue is deferred until the product go-live date, then recognized over the remaining contract term.
Why This Distinction Matters More Than You Think
The practical impact is significant. Consider a contract with $500,000 in total implementation fees. If your accounting team treats all implementation services as one bucket, you’re either recognizing too much revenue too early (if you book everything over time) or deferring too much revenue unnecessarily (if you defer everything to go-live).
The correct approach splits the implementation fees between the two groups based on their standalone selling prices. Non–complex revenue flows through the income statement as work is performed during the pre-go-live period. Complex revenue sits on the balance sheet as deferred revenue until launch, then amortizes over the contract life alongside the SaaS subscription.
The Test: How to Classify Your Services
The key analytical framework comes down to three questions:
1. Does the service modify or write additional software code? If yes, it’s likely complex and non-distinct from the SaaS.
2. Could another qualified provider perform the service? If yes, that’s strong evidence the service is distinct and should be a separate performance obligation.
3. Does the customer receive and consume benefits as the work is performed? If the customer can’t use the output until the entire platform goes live, the service is likely an input to the combined SaaS obligation.
Real-World Application: A Government SaaS Contract
Consider a software company that provides a proprietary platform to a customer. A typical contract includes both groups of services: non-complex deliverables like gap analysis, data conversion, and training (Group A), alongside customer-specific configuration and new core development that requires modifying the platform’s source code (Group B).
The company determined that the Group A services are more than mere setup costs, they provide standalone value and are recognized over time as separate deliverables. The Group B activities, however, are not distinct from the SaaS. They are combined with the SaaS subscription as a single performance obligation that begins recognition at the product go-live date.
This analysis also affects how subcontractor costs are allocated. Third-party development partners providing ongoing services (like security monitoring) have their costs bifurcated between the Group B pre-go-live period and the post-go-live SaaS period, ensuring cost recognition matches revenue recognition.
The Bottom Line
If your software company delivers implementation services alongside a SaaS product, you need to evaluate every deliverable individually, not as a single package.
The complex vs. non-complex distinction is the foundational decision that cascades through your entire revenue model: what gets deferred, what gets recognized, and when your income statement reflects the economic reality of the deal.
The implementation work feels operational, but the accounting treatment shapes how the entire contract shows up in your financials.
At Lavoie CPA, we work with software companies that need their revenue models to reflect how the business actually operates, not just how contracts are written.
Start the conversation today.
by Katy Robinson | May 26, 2026 | Sports
It’s the second week of the month. Your coaches are still submitting tournament receipts for the prior month. Last month’s bank reconciliations are half done. The board meeting is in five days, and the financials they’re about to see will be three weeks behind reality.
This is what an unstandardized close looks like.
Every staff member follows their own process. Spreadsheets vary from team to team. Critical transactions get posted late or missed entirely. And by the time the books are clean, the decisions they were supposed to inform have already been made without them.
The problem is that month-end close, one of the most repeatable processes in any organization, is being run as if it were a custom project every cycle. A standardized close workflow turns that chaos into rhythm. It defines clear steps, ownership, and automation triggers so your club moves from a reactive close to a consistent, reliable process that delivers accurate reports in days, not weeks.This is governance applied to the most recurring financial process you have. It’s the operational backbone of the third pillar of scalable club operations, and for most clubs, it’s the fastest place to see results.
1. Map Your Current Close Process
Before you can improve your close, you need to see it clearly. Most youth sports clubs run on a mix of accounting software, spreadsheets, and manual entries, and leaders have never actually traced the full path from transaction to financial statement.
Start by documenting the four basics:
- Who performs each step – recording deposits, reconciling credit cards, preparing reports.
- When those steps occur, and whether they follow a set calendar.
- Where data comes from, registration systems, facilities, sponsorships, point-of-sale tools.
- How communication flows between departments.
This exercise often exposes common patterns: duplicate entries, missing receipts, approvals delayed because they’re sent by email instead of through a shared checklist. The map itself is the diagnosis.
The benefit: transparency. Everyone sees how their role contributes to a faster, cleaner close, and where the friction actually lives.
2. Define a Repeatable Close Checklist
Once you’ve mapped the process, convert it into a standardized checklist that becomes your close playbook. Every task gets a clear description, an owner, and a due date.
A typical standardized close looks like this:
- Pre-month-end preparation: ensure routine transactions are recorded throughout the month, such as cash, credit cards, accounts payable, accounts receivable, payroll.
- Day 1: finalize all routine transactions through month end. Reconcile cash and credit card payable accounts.
- Day 1-2: Post all registration, merchandise, and event revenue.
- Day 3: Reconcile all other general ledger accounts.
- Day 4: Review expenses by program and vendor and flag anomalies.
- Day 5: Generate financial statements for leadership review.
Add automation wherever possible, scheduled reports, reconciliation reminders, task triggers, and make the checklist visible in a shared dashboard or project tool. The checklist is the rhythm. Automation is what keeps it running when life happens.
The benefit: consistency. No matter who’s out of office, the same process runs on time every month.
3. Standardize Data Sources and Dimensions
Even the cleanest checklist will falter if data lives in silos. True standardization requires aligning the inputs themselves, not just the steps that process them.
That means using uniform naming conventions for programs, departments, and cost centers. It means mapping revenue and expense accounts consistently across entities. And it means integrating your registration, payroll, and expense tools directly into your accounting platform so transactions don’t have to be retyped to be reported.
When every transaction flows through the same structure, reports reconcile automatically and the manual cleanup that consumes most close cycles disappears. This is exactly why automatic data feeds matter so much: they eliminate the gap between operational activity and financial reporting that forces finance teams into constant reconciliation mode.
The benefit: accuracy. Consistent data means fewer surprises at month-end.
4. Automate and Visualize the Close
Automation is what turns your standardized process from a checklist into a living system. The goal is to remove the parts of the close that don’t need humans and can be performed automatically.
Practical automation looks like:
- Importing transactions daily instead of monthly, using APIs instead of spreadsheet uploads.
- Triggering alerts when balances or journal entries fall outside expected ranges.
- Automatically assigning tasks once prior steps are complete.
Pair the automation with visual dashboards that track progress in real time, including what’s done, pending, and overdue. Finance leaders gain visibility. Team members know exactly what’s next.
The benefit: efficiency. A clear view of progress keeps everyone aligned and accountable, without the daily status emails.
5. Schedule Regular Close Reviews
Standardization should be a continuous improvement process. It’s a living framework, and the moment you stop refining it, it starts decaying.
Hold monthly close performance reviews. Look at cycle time, error rates, and bottlenecks. Ask the questions that matter:
- Which tasks consistently delay completion?
- Are new revenue streams, tournaments, camps, clinics, properly reflected in the workflow?
- Do team members have access to the reports and data they need?
Each review is a chance to learn and tighten the system. The clubs that close fastest continually refine the close process.
The benefit: continuous improvement. Each cycle gets faster and more reliable than the last.
What Changes for Your Club
When your close runs on a standardized workflow, four things shift at once. The rhythm becomes predictable and everyone knows when tasks start and finish. Manual touchpoints drop, which reduces risk and workload simultaneously. Reports are delivered days earlier, which means program-level financial insight becomes a planning tool instead of a postmortem. And coaches and program directors finally understand how their actions affect the bottom line, because they can see it in time to act on it.
When your process runs on autopilot, you reclaim the time that used to disappear into reconciliations and transaction overload. With better organization of your month-end close, management can redeploy time saved into growing the club, supporting your players, and funding your future.
Ready to Bring Order to Your Close?
A close that takes two weeks has structural issues that need to be resolved. And it’s almost always solvable with the same approach: map what you have, define what you want, and automate the path between them.
Start the conversation today.
by Katy Robinson | May 15, 2026 | Financial Operations
How improving transactional processes may not be capturing the data needed to make critical business decisions and how to fix those processes.
Most leadership teams operate with a version of their financials that is technically accurate and operationally misleading. The numbers tie. The reports get delivered. But the cost structure underneath those numbers was patched together with manual processes, spreadsheets, and disconnected systems. It evolved through workarounds, inherited processes, system migrations that were never fully completed, and manual steps that reluctantly became permanent fixtures.
The result is a business that makes decisions based on financial information that is late, blended, or structurally incomplete. Not wrong in a way that triggers an audit finding, but wrong in a way that makes it impossible to answer the questions that actually drive profitability: which customers are worth the resources they consume, which service lines earn their keep, and where the operating model is quietly subsidizing inefficiency.
The companies that consistently expand margins are the ones that fixed the processes generating their financial data, so leadership could finally see what was actually happening and act on it before the opportunity passed.
The Real Cost of Broken Processes
Broken accounting and transactional processes show up as symptoms that leadership learns to live with.
The monthly close takes longer than it should, but it gets done. Customer profitability is available at a blended level, but not at the granularity that would change a staffing decision. Vendor costs drift upward, but nobody catches it because the review process depends on someone remembering to check rather than a system surfacing the variance automatically.
Each of these symptoms has the same root cause: the processes that capture, classify, and deliver financial information were built for a smaller, simpler version of the business. They have not kept pace with the complexity of the current operation. And because the outputs still look reasonable at a summary level, leadership has no reason to question the infrastructure underneath.
This is how margin leaks become permanent – through a thousand small inaccuracies that compound into a cost structure no one would deliberately choose.
What Timely, Accurate Information Actually Changes
When financial processes are designed to produce timely, granular data, the decisions that follow are fundamentally different.
Customer-level margin visibility moves from a quarterly exercise to a continuous signal. Leadership can see which accounts consume disproportionate hours, which delivery models are quietly subsidized, and which relationships generate margin that justifies the investment.
Cost migration becomes visible in real time. When a vendor relationship creeps above its original scope, when overtime shifts from an exception to a pattern, when a software renewal happens without review — these movements surface as they happen, not months later when the institutional memory of what changed has already faded.
Service-line and product-line contribution becomes actionable. Instead of debating whether a particular offering is profitable based on estimates and allocations, leadership works from actual contribution data that reflects real resource consumption. The conversation shifts from opinion to evidence.
While some of these initiatives may require new technology or a transformation initiative, it often starts with fixing the transactional processes that feed the financial model so the data arriving in the general ledger is classified correctly, captured promptly, and structured for the analysis leadership actually needs.
Where the Process Gaps Live
The gaps that matter most are rarely where leadership expects them to be. They are in the transactional layer underneath the financial statements, specifically in the daily processes that determine whether the data arriving in the reporting system is useful or merely complete.
Revenue recognition and billing workflows. When billing does not reflect the actual delivery model, or when revenue recognition is handled through manual journal entries rather than systematic processes, the income statement becomes a lagging indicator rather than a management tool. Fixing this single process often changes how leadership understands which customers and service lines are actually performing.
Expense capture and classification. When costs are coded inconsistently, approved without standardized workflows, or classified based on convenience rather than economic substance, the cost structure becomes opaque. Leadership sees totals, but cannot trace those totals back to the activities, customers, or decisions that created them.
Vendor management and procurement. When vendor relationships are managed through informal renewals and undocumented scope changes, costs migrate quietly between categories without anyone making a deliberate decision. A vendor that was approved at one rate is now billing at another. A contract that covered one scope now covers three. Each drift is small. Collectively, they reshape the cost structure.Intercompany transactions and allocations. For multi-entity organizations, the allocation methodology determines which business units appear profitable and which appear burdened. When allocations are based on outdated assumptions or manual calculations, leadership makes investment decisions based on a margin picture that does not reflect operational reality.
The Compounding Value of Getting This Right
Fixing accounting and transactional processes is not glamorous work. It does not produce board-deck headlines or investor narratives. But it is the structural foundation that determines whether every other strategic initiative (pricing changes, market expansion, product launches, headcount decisions) is built on accurate information or informed guesswork.
Companies that invest in process quality compound the benefit over time. Each month produces cleaner data. Each quarter’s analysis builds on a more reliable foundation. Each year’s strategic planning starts from a position of genuine understanding rather than reconstructed approximation.
The companies that do not invest in process quality experience the opposite compounding effect. Manual workarounds multiply. The gap between what leadership believes about the cost structure and what the cost structure actually looks like widens. Decisions that seemed sound at the time turn out to have been based on incomplete information and the pattern repeats because the underlying processes never changed.
The difference between these two trajectories is not talent, technology, or market position. It is whether someone decided to fix the processes that generate the information the business runs on.
What We Help Leadership Teams Do
The work is structured, but not formulaic. We start by rebuilding the margin picture from the bottom up, by customer, by service line, by cost category, and then overlay the Q1 close period to identify exactly where the structural compromises happened. From there, the conversation moves to which compromises were worth it, which ones were accidental, and which ones are quietly becoming the new normal because nobody has formally examined them.
The output is not a report that sits on a shelf. It is a ranked list of decisions, organized by margin impact and ease of execution, that your leadership team can act on before Q2 closes. Some of the decisions are small, a vendor renegotiation, a delivery model adjustment, a customer segmentation change. Others are larger, sunsetting a service line that has quietly been losing money for three quarters, or restructuring how a specific account is staffed. What they have in common is that all of them are visible in May and invisible by July.
Q1 close tested your systems. May is when you get to test your assumptions about where the money actually comes from, and act on what you find before the data decays.
At Lavoie CPA, we work with finance leaders who treat the post-close window as the most valuable analytical period of the year.
Start the conversation today.
by Katy Robinson | May 15, 2026 | Financial Operations
Output is not the same as efficiency. Benchmarking your finance team’s performance is what determines whether your processes exhibit best-in-class performance.
There is a moment that happens in almost every finance organization after each month-end close. Leadership says some version of “great job, team,” and the conversation moves on to the next thing.
That moment is when the most important question goes unasked.
Was your team actually efficient, or did they just work hard?
Those are not the same thing. The fine line between efficiency and hard work is the difference between a finance function that can scale with the business and one that will quietly become the bottleneck when growth accelerates beyond what manual effort can absorb.
We see this distinction blur constantly, and the consequences are predictable.
A team that closes the books on time after working three weekends is not an efficient team. A team that produces the deliverables leadership asked for by routing everything through one senior accountant is not a scalable team. A team that hits its deadlines by absorbing pressure that should have been absorbed by systems is not a high-performing team.
They are a high-risk team performing well in spite of their structure, and the risk compounds every quarter that nobody formally examines it. The benchmarking work we run with clients is designed to make that distinction visible while the information is still fresh enough to support a real conversation.
The ratios nobody puts on the monthly report.
Most finance leaders are familiar with efficiency ratios at the company level, such as operating expenses to revenues, days sales outstanding, working capital turns. These are useful, but they are lagging indicators that tell leadership about the business, not about the function producing the numbers.
The ratios that matter for diagnosing your finance team are different, and almost none of them appear in standard reporting:
Hours-to-close ratio. Total team hours invested in monthly close, divided by the structural complexity of the close. Trending up over multiple months means structural drag is increasing even when the deliverables look identical from the outside.
Analysis-to-processing ratio. What percentage of your team’s time is spent producing insight versus moving data between systems. Below thirty percent and you do not have a finance team, you have a data entry operation with senior titles and senior salaries.
Single-point-of-failure index. How many critical processes depend on one specific person. Higher than two and you are one resignation away from a crisis that nobody on the leadership team is currently planning for.
Rework rate. Percentage of deliverables that require correction or revision after first delivery. Quietly the most expensive metric in any finance function, work paid for twice, trust that erodes a little with each instance.
Percentage of entries booked pre-month end. The percentage of journal entries and transactions that are recorded within the month versus those booked after month end. The sooner transactions are booked, the less effort there is during month-end close.
None of these show up in standard financial reporting. All of them determine whether your function is actually performing or just appearing to perform.
And all of them are easiest to measure in the immediate aftermath of a monthly close, when the data is concrete and the team can still remember exactly where the friction lived.
Where industry benchmarks help, and where they hurt.
The reflexive response to internal metrics is to compare them to industry averages. That is a useful starting point and a dangerous stopping point.
Industry benchmarks tell you where you sit in a distribution. They do not tell you whether the distribution itself is healthy.
We have worked with SaaS finance teams that benchmarked perfectly against their peer group and were still operating at forty percent of the efficiency they could realistically achieve.
Why? Because their entire peer group had absorbed the same structural inefficiencies and normalized them as “industry standard.” Comfort in that ranking became a reason to stop improving, when it should have been a reason to ask whether the comparison set was actually useful.
The right way to use benchmarks is as a calibration tool. Use them to understand whether your gaps are industry-wide or company-specific, then build the improvement plan around the company-specific ones first.
Those are the ones with the most leverage and the least competitive resistance, because closing them does not require an industry-wide shift, just a deliberate decision inside your own organization.
Industry-wide gaps are still worth understanding. They just belong on a longer time horizon. Company-specific gaps belong on the highest priority list.
What we help leadership teams do in May.
The diagnostic we run is structured around three questions:
- where is your team spending its time,
- where is that time creating value, and
- what improvements can we make this month without disrupting next month’s close?
We pull the actual data, close timelines across multiple periods, deliverable cycles, escalation patterns, rework instances, dependency maps, and compare it against your company’s goals.
The output is a clear picture of where your finance function has structural leverage available and where it is operating on borrowed time disguised as competence.
From there, the work is conversational. Which gaps are worth closing immediately. Which ones need a longer horizon. Which ones the leadership team was already aware of but had no formal mechanism to address.
The companies that maximize efficiency are the ones that measure honestly, benchmark intelligently, and act on the gap before it compounds into a crisis that demands a much more expensive response.
Your team just ran a marathon. Now is when you find out whether they were actually fast, or whether they just refused to stop running.
At Lavoie CPA, we work with finance leaders who want to convert post-close data into structural efficiency gains.
Start the conversation today.
