by Katy Robinson | Jun 2, 2026 | FQHCs
For most Federally Qualified Health Centers, the annual cost report is a project. It shows up on the calendar, consumes weeks of staff time, and gets filed under pressure. Then everyone moves on until next year.
That cycle is the problem. The CMS-224-14 isn’t a standalone compliance task, it’s the final output of every financial decision your organization made over the previous twelve months. When it’s treated as a project, the work gets compressed into a few painful weeks. When it’s treated as a destination, the entire year’s financial processes can be designed to arrive there cleanly.
The difference between those two experiences usually comes down to whether someone is guiding the journey or just showing up at the end.
How Fragmentation Quietly Builds Throughout the Year
FQHCs rarely choose complexity on purpose. It accumulates. One firm handles day-to-day accounting. Another supports monthly reporting. A third arrives after year-end to prepare the cost report. Each does competent work in isolation, but no one owns the full financial picture and the seams between them create problems that don’t surface until filing season.
Cost classifications drift between systems. Allocations get handled one way for internal reporting and another for CMS compliance. Vaccine purchase records live in one system while administration logs sit in another, and neither ties cleanly to Worksheet B-1. Indirect costs get applied inconsistently across cost centers, so the numbers on Worksheet A don’t reconcile without manual rework.
None of these gaps feels urgent in March. By the time the cost report is due, they all surface at once.
Designing the Year Around the Destination
The organizations that file clean cost reports aren’t doing heroic catchup work in Q2. They built their financial processes backward from the CMS-224-14.
That means cost allocation methods are applied consistently every month and not invented during report preparation. Reporting dimensions align with CMS requirements from the first journal entry. Documentation is captured in real time: lease agreements, malpractice records, grant award letters, contract labor detail, GME program costs. When these records exist in a single structured system all year, the cost report is confirmation, not construction.
This is what optimization looks like in practice. It’s not a better spreadsheet at year-end, but a better system from day one.
Consistency Is the Real Risk Control
The biggest compliance risk in FQHC cost reporting is often a pattern of small inconsistencies:
- Shared costs split one way in the general ledger and another in the cost report
- Program costs categorized differently between operational reports and CMS worksheets
- Vaccine costs on Worksheet B-1 that don’t reconcile to purchase records because the data was maintained separately
- Indirect expenses allocated to cost centers using a method that changed mid-year without documentation
Each discrepancy is minor in isolation. Together, they trigger MAC desk review questions and you get 30 days to produce supporting documentation or lose reimbursement on those line items. Persistent inconsistencies can escalate to full audits. Late filings carry their own penalties and directly delay interim payments.
When one team maintains a single framework for how financial data is categorized, allocated, and documented all year, these risks largely disappear. The numbers in the cost report match what leadership has been reviewing every month because they came from the same system. That alignment is what real financial transparency produces inside an FQHC.
Clear Ownership Changes the Internal Experience
When cost report responsibility is split across departments, accountability gets diluted. Questions bounce between department leaders as well. Timelines stretch because each handoff requires context that was never fully transferred. Internal finance teams (who are already stretched thin) end up acting as project managers between outside providers instead of focusing on oversight and operations.
When one team owns the full financial function (accounting, reporting, monitoring, and cost report preparation), there’s no handoff. Issues get resolved directly. Internal staff shift from managing vendor communication to managing the business.
For lean FQHC finance teams, that shift is the difference between cost reporting being a quarter-long disruption and a manageable phase of normal operations.
Turning the Cost Report Into a Predictable Outcome
The real value isn’t consolidation for its own sake. It’s predictability.
When your financial processes are designed around the CMS-224-14 from the start, when someone is monitoring data quality, maintaining documentation, and resolving classification questions throughout the year, the cost report stops being a crisis. It becomes the natural output of disciplined financial management — the same approach we lay out in Simplifying Your Annual Cost Report Through Integrated Financial Processes.
At Lavoie CPA, this is the work we do with FQHCs. We guide organizations through a continuous optimization process that structures financial data, maintains consistency, and monitors compliance readiness year-round. By the time filing season arrives, the heavy lifting is already done.
If your organization is ready to stop treating the CMS-224-14 as a year-end project, we’d welcome a conversation about what a readiness assessment looks like for your center.
Start the conversation today.
by Katy Robinson | Jun 2, 2026 | FQHCs
For many Federally Qualified Health Centers, the CMS-224-14 feels like a year-end event. Finance teams brace for it in Q1, scramble to gather data, reconcile inconsistencies under deadline pressure, and explain variances they didn’t know existed until the report forced them to the surface.
However, we find that the FQHCs that are best prepared for the annual filing of CMS-224-14 are the ones that organize financial data and information throughout the year and ensure transactions entering into key reporting systems support year-end reporting.
The FQHCs that file cleanly have designed their financial processes so the cost report is substantially complete by the time the year ends. Thus, the CMS-224-14 becomes a validation exercise with the structural work already complete.
Why Cost Report Problems Start Long Before Year-End
Most cost report issues come from fragmented data and systems, inconsistent classifications, and last-minute adjustments that accumulate quietly across twelve months of operations.
When accounting, operational data, and reporting live in silos, finance teams are forced to reconstruct the financial story after the fact. While monthly financials are correct, CMS-224-14 report preparation reveals that key data points don’t actually align, cost centers may have shifted definitions mid-year, allocations were handled differently between Q1 and Q3, or documentation supporting allocations live in someone’s email.
This reactive approach is where stress and audit risk come from. Year-end pressure exposes the problems that were already there. Carefully structuring and monitoring data changes that dynamic completely, and it’s the foundation of the broader case we make in Simplifying Your Annual Cost Report Through Integrated Financial Processes.
What the CMS-224-14 Actually Demands From Your Financial Data
CMS-224-14 is asking for defensibility of the organization’s cost structure and seeks to ensure financial data is consistent, traceable, and supported by clear documentation.
To meet that standard, three things have to be true of your financial data:
- It’s consistently categorized across cost centers and reporting periods
- It’s aligned with the organization’s operational activities as they actually run
- It’s supported by documentation that exists at the time of the transaction
When these elements are built into everyday financial processes, the cost report reflects how the organization actually operates. When they’re missing, the cost report reflects how the finance team reconstructed operations under deadline pressure, and CMS can usually tell the difference.
How Year-Round Structure Reduces Reporting Risk
Structured financial data compresses the entire risk profile of the cost report.
When classifications and allocation methods are applied consistently, late-stage corrections become rare. When documentation is captured in real time, audit trails are already built. When reporting dimensions align with CMS requirements from the start, there’s no reclassification work waiting at year-end.
The downstream effect is significant: fewer reporting errors, fewer revision cycles, less internal workload during the reporting window. More importantly, leadership develops genuine confidence in the numbers because they were structured with intention all year long. This is what year-round financial transparency is supposed to produce, and the cost report is where it pays off most visibly.
The Three Areas That Need to Be Structured in Advance
Cost Allocation and Departmental Mapping
We find shared costs are a common source of cost report problems. Rent, utilities, administrative salaries, IT infrastructure – every one of these has to be allocated across cost centers using a defensible methodology.
Establishing those methodologies early, documenting the statistical bases, and applying them consistently every month means there’s no allocation work waiting at year-end. The rules are set. The data flows accordingly and is recorded in the general ledger in this manner. The cost report inherits the structure and the outputs without additional calculations or adjustments.
Consistent Reporting Dimensions
Programs, locations, services, payer types, and funding sources need to be tracked the same way across every financial system, every month, all year. Standardized dimensions let finance teams slice data accurately without manual rework, and they ensure that what shows up in the cost report ties cleanly to what shows up in internal reporting.
When dimensions drift, reconciliation becomes a project. When they’re locked in, reporting becomes a query.
Supporting Documentation and Data Trails
Documentation is another common are where cost reports quietly fall apart. Assumptions get made in March and forgotten by November. Methodologies get applied without being recorded. Supporting data lives in spreadsheets that change without version control.
Maintaining documentation in real time, methodologies, source data, calculation logic, approval trails, means validation during cost report preparation takes hours instead of weeks. And when CMS asks follow-up questions, the answers are already documented.
How Integrated Systems Simplify the Whole Process
Integration is what makes year-round structure sustainable. Manual processes can’t maintain this level of discipline at scale. Integrated systems can.
Platforms like @Sage Intacct are designed for exactly this kind of operational complexity, standardized classifications applied automatically, allocation rules executed without manual intervention, and real-time visibility into financial performance across every dimension that matters for the cost report. This is the same automation logic we describe in automating routine financial tasks inside FQHC operations, applied to the highest-leverage compliance work an FQHC does.
When the system handles consistency, finance teams stop being responsible for it. They shift from cleanup to oversight, where their time actually generates value.
The Role of a Single Financial Thought Leader
Structuring data year-round only works when one team owns the framework. Multiple departments managing different pieces of the financial function can result in unintended changes to assumptions and allocations over time.
This is why working with one financial thought leader is foundational to simplified cost reporting. Continuity in the team enforces continuity in the data, and continuity in the data is what makes the cost report predictable.
From Year-End Scramble to Predictable Process
The difference between a stressful cost report and a smooth one is almost entirely upstream of the report itself. Organizations that structure data year-round experience reporting as a confirmation of work already done. Organizations that don’t structure data experience it as a reconstruction project under deadline.
The timing of the work determines whether reporting season disrupts operations or quietly closes them out.
Why Structuring Data Pays Off Beyond Compliance
Structured financial data changes how leadership runs the organization.
When data is organized year-round, leaders can see cost per visit by site in real time. They can identify margin pressure inside specific programs before it becomes a budget problem. They can model the financial impact of adding a service line, opening a location, or restructuring payer mix, all using the same data infrastructure that produces the cost report. This is the operational visibility we describe in FQHC leader visibility, and structured data is what makes it possible.
The cost report is a compliance output. The system that produces it is a strategic asset.
How Lavoie CPA Helps FQHCs Prepare Year-Round
At Lavoie CPA, we help FQHCs structure financial data as the architecture underneath every monthly close, every operational decision, and every compliance deliverable.
Our approach integrates accounting processes, reporting frameworks, and operational insight so cost reporting becomes a natural outcome of disciplined financial management. The result is reduced risk, improved accuracy, and a finance function strong enough to support the organization beyond compliance.
If your FQHC is ready to move from year-end pressure to year-round confidence,
Start the conversation today.
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.
