One Organization, Two Compliance Universes
Consider a community behavioral health agency in Washington State. This organization — not hypothetical, but representative of dozens operating across the state right now — holds three active funding streams:
A SAMHSA Certified Community Behavioral Health Clinic (CCBHC) grant, awarded directly from the federal Substance Abuse and Mental Health Services Administration. Federal direct award. The Uniform Guidance at 2 CFR 200 governs it. SAMHSA's program-specific terms layer on top. The organization reports to a federal program officer and will include the award on its Schedule of Expenditures of Federal Awards at Single Audit time.
A behavioral health services contract with the Washington Health Care Authority (HCA), funded primarily through the federal Substance Abuse Block Grant (SABG). Federal money arriving through the state. HCA acts as the pass-through entity. The Uniform Guidance still applies, because the funding source is federal. But HCA's contract adds its own billing requirements, credentialing expectations, and reporting mandates on top of the federal baseline.
A crisis services contract with HCA, funded entirely with state dollars. No federal money touches this award. The Uniform Guidance does not apply. Instead, the contract is governed by Washington state procurement law, HCA's standard terms and conditions, and program-specific requirements for crisis services.
Three funding streams. Same staff. Same accounting system. Same executive director. Same board. But three different compliance frameworks, three different reporting timelines, three different sets of allowable cost rules, and three different audit expectations.
This is not an edge case. This is the normal operating environment for health and human service organizations in Washington and across the country. The intersection of state and federal compliance is not a special topic you encounter occasionally. It is the daily reality for any organization doing meaningful work with public funding.
And almost nobody maps it clearly.
The Federal Baseline: 2 CFR 200
The Uniform Guidance (2 CFR Part 200) is the federal government's comprehensive framework for managing grant funds. If your organization receives federal money — directly from a federal agency or through a state pass-through — 2 CFR 200 governs how you spend it, account for it, and report on it. The key provisions that shape daily operations are worth naming specifically, because understanding them is essential to understanding where collisions happen.
Allowable costs (Subpart E, 2 CFR 200.400–200.476). Every charge to a federal award must be necessary, reasonable, allocable to the award, and consistently treated. Some costs are always unallowable — alcohol, entertainment, lobbying. Others are allowable only under specific conditions. These are auditable standards.
Procurement standards (2 CFR 200.317–200.327). Organizations spending federal funds must follow documented procurement procedures. Micro-purchases have streamlined requirements. Above that threshold: competitive processes with documented rationale for the method used and the basis for contractor selection.
Time and effort documentation (2 CFR 200.430). Employees whose compensation is charged to federal awards must maintain records reflecting an after-the-fact distribution of actual activity. The 2013 reform replaced rigid semi-annual certifications with a more flexible standard, but the core requirement remains: you must demonstrate that staff charged to a grant actually worked on that grant's activities.
Indirect cost rates (2 CFR 200.414). Organizations can negotiate an indirect cost rate with their cognizant federal agency or elect a de minimis rate of 10% of modified total direct costs. Federal awarding agencies are generally required to accept a properly negotiated rate.
Subrecipient monitoring (2 CFR 200.332). Pass federal funds to another entity and you become a pass-through entity with specific monitoring obligations — risk assessment, award documentation, ongoing oversight, and verification that the subrecipient obtains required audits.
Period of performance (2 CFR 200.309). Costs must be incurred during the approved period. Pre-award costs are allowable only under specific conditions. Post-period obligations are generally unallowable.
These provisions constitute a comprehensive operating framework. But here is the critical point: 2 CFR 200 is a floor, not a ceiling. Federal awarding agencies add program-specific requirements on top — HRSA requires Electronic Handbooks reporting, SAMHSA mandates specific data collection instruments, the CDC has its own performance measurement frameworks. And when federal money flows through state agencies, those state agencies can and routinely do add their own requirements.
The State Layer: Washington Specifics
Washington's health and human service agencies operate their own compliance frameworks — not derivatives of 2 CFR 200, but independent systems built to serve state policy objectives, governed by state law, and administered by agencies with their own contracting cultures.
The Health Care Authority (HCA) is the single largest funder of behavioral health services in Washington. HCA contracts include billing requirements tied to the Apple Health (Medicaid) system, credentialing standards for individual practitioners, reporting to the Behavioral Health Administration (BHA), and cultural competency mandates. These apply to HCA-funded activities regardless of whether the underlying dollars are federal pass-through or state general fund.
The Department of Social and Health Services (DSHS) maintains its own contracting framework: specific insurance coverage thresholds, mandatory background checks through the Background Check Central Unit (BCCU) for staff working with vulnerable populations, and program-specific reporting on DSHS timelines and formats.
The Department of Health (DOH) adds licensure requirements, compliance with the Budgeting, Accounting, and Reporting System (BARS) for state-funded programs, and coordination requirements with Local Health Jurisdictions (LHJs).
The Department of Commerce administers programs like the Community Services Block Grant (CSBG) and Community Development Block Grant (CDBG) that carry both federal pass-through obligations and state-specific performance measures, with their own reporting requirements and monitoring protocols layered on top.
Beyond individual agencies, Washington imposes cross-cutting obligations. Organizations seeking state contracts must register on the Washington Electronic Business Solution (WEBS) — a state vendor registration platform entirely separate from the federal SAM.gov. Organizations receiving state funds may face state audit requirements independent of the federal Single Audit. The state's own procurement laws establish competitive bidding thresholds that do not mirror federal thresholds.
Each of these requirements is individually reasonable. The challenge is not that any single one is onerous. The challenge is that they accumulate on top of an already substantial federal baseline.
Where They Collide
The collision between state and federal requirements is not abstract. It manifests in specific operational areas where organizations must satisfy two sets of rules simultaneously — and where those rules do not always point in the same direction.
Procurement
Federal procurement standards under 2 CFR 200.317–200.327 establish specific thresholds and procedures. Washington state has its own competitive bidding thresholds under state procurement law. The dollar amounts are not identical. The documentation requirements are not identical.
When an organization uses blended funding for a single procurement, the standard guidance is to follow the most restrictive requirement. But determining which is more restrictive requires analyzing both frameworks at the specific dollar amount and documenting the analysis. Follow one framework and ignore the other, and you risk a finding from whichever auditor reviews the other side of the funding.
Cost Allocation
Federal cost principles under Subpart E define how shared costs must be allocated — reasonably, consistently, and with documentation. State contracts may specify their own allocation methodologies. HCA, for example, may require specific approaches for shared administrative costs in behavioral health contracts. When the state and federal methodologies produce different allocations of the same cost, the organization must reconcile them or maintain parallel systems. Neither option is simple.
Reporting Timelines
Federal grants typically require quarterly financial reporting (SF-425) plus program-specific reports. State contracts often require monthly reporting. The fiscal calendars do not align — federal runs October through September, the state runs July through June, and the organization's own fiscal year may follow the calendar year.
An organization holding five or six funding streams can face reporting deadlines every week of the year. The burden is not any single report — it is the constant context-switching between formats, fiscal periods, and differing definitions of what constitutes a reportable outcome.
Indirect Costs
This may be the most financially consequential collision point. A Negotiated Indirect Cost Rate Agreement (NICRA) establishes, through a rigorous federal process, the actual rate at which an organization's overhead costs relate to direct program activities. Federal awarding agencies are generally required to honor that rate under 2 CFR 200.414.
State agencies are not bound by the same requirement. HCA, DSHS, or Commerce may cap indirect reimbursement well below the federally negotiated rate. A 10% state cap applied to an organization with a 22% NICRA means 12 percentage points of legitimate overhead go unreimbursed on state-funded work. The same finance director, office lease, and IT infrastructure supports both programs — but only the federal side reimburses at the actual rate. The gap must be absorbed by unrestricted revenue that most health and human service organizations do not have in abundance.
Personnel Documentation
Federal grants require time and effort documentation showing staff charged to the award worked on allowable activities. State contracts layer different personnel requirements: HCA requires professional credentials and Apple Health provider enrollment, DSHS requires BCCU background checks, DOH requires licensure verification. These are not time-and-effort questions — they are qualification questions. But they apply to the same employees.
A clinical supervisor charged 40% to a SAMHSA CCBHC grant, 30% to an HCA SABG pass-through contract, and 30% to an HCA state crisis contract needs: time and effort documentation satisfying 2 CFR 200.430, Apple Health credentialing, a BCCU background check clearance, professional licensure verification, and potentially separate qualification documentation for each program. Different paperwork, different systems, different renewal cycles — one person.
Data and Privacy
Federal programs impose specific data security and privacy requirements. Substance use disorder treatment records carry protections under 42 CFR Part 2 that are more restrictive than standard HIPAA. SAMHSA programs require specific data collection instruments with their own consent protocols.
Washington state layers its own data governance framework on top. An integrated electronic health record system must satisfy all applicable standards simultaneously — HIPAA as the baseline, 42 CFR Part 2 for substance use records, federal program-specific requirements, and state data governance rules. When these frameworks conflict on information sharing, consent, or reporting, the organization navigates the intersection largely without clear guidance on reconciliation.
The Pass-Through Problem
Federal money flowing through state agencies creates a particularly challenging compliance dynamic. Under 2 CFR 200.332, when a state agency passes federal funds to a subrecipient, it must identify the federal award information, communicate all applicable requirements, and monitor compliance.
In practice, a contract funded with federal pass-through carries both federal and state obligations. The organization receiving SABG pass-through from HCA faces 2 CFR 200 requirements (because the money is federal), HCA-specific program requirements (because HCA is the administering agency), and state contracting boilerplate (because HCA uses state templates). The layering creates ambiguity. A termination clause drafted under state contract law may interact unpredictably with federal period-of-performance rules. A state reporting requirement may duplicate — but not exactly mirror — a federal one.
The most practically disorienting question: when a single HCA contract includes both SABG pass-through (federal) and state general fund dollars, which terms apply to which dollars? Does the federal procurement standard govern only the federal portion, or the entire contract? If staff time is blended across funding sources, does the federal time-and-effort standard apply to all of it or only the federal share?
The technically correct answers exist — 2 CFR 200 applies to the federal funds, state requirements to the state funds, and the most restrictive standard governs overlaps. But translating that principle into daily decisions requires fiscal infrastructure that can track expenditures by funding source within a single contract, and staff who understand that the same activity may carry different obligations depending on which dollar pays for it.
This is not a failure of the organizations. It is a structural feature of a system where federal money moves through state intermediaries, each adding its own requirements to the chain.
Building a Dual-Compliance Operating Model
The collision between state and federal requirements is permanent. The practical question is how to build an operating model that manages it without consuming the organization's capacity. Six strategies, drawn from organizations that navigate this successfully:
1. Map Your Compliance Obligations by Funding Stream
Build a matrix. Rows are compliance domains: procurement, cost allocation, time and effort, reporting, audit, personnel qualifications, data and privacy, insurance, subrecipient monitoring. Columns are your funding streams.
Fill in each cell with the specific standard that applies. Not “follow procurement rules” — the specific threshold, the specific citation. For the SAMHSA CCBHC grant, procurement follows 2 CFR 200.317–200.327. For the HCA state-funded contract, Washington state competitive bidding with a different threshold structure.
This matrix is the foundation. Without it, compliance decisions are ad hoc and undocumented. With it, you can identify where collisions actually occur — often fewer places than you fear, and in more specific ways than you expect.
2. Identify Conflicts and Apply the Most-Restrictive Standard
Where your matrix reveals different standards for the same domain, apply whichever is more restrictive. Federal procurement threshold lower than state? Follow federal. State background check more comprehensive than federal personnel documentation? Follow state.
Critically: document the decision. Auditors want to see that you identified both standards, compared them, and chose deliberately. A brief memo is sufficient: “For blended-funded procurements above $10,000, we follow 2 CFR 200 competitive procedures, which are more restrictive than state requirements at this level.” What is not sufficient is no documentation at all.
3. Build Unified Policies That Satisfy Both Frameworks
Rather than maintaining parallel policy sets — one for federal compliance and one for state compliance — build a single set of organizational policies designed to meet the highest standard across all your funding sources.
Your procurement policy should incorporate both 2 CFR 200 thresholds and Washington state competitive bidding requirements, applying whichever is stricter at each spending level. Your time documentation system should capture both the after-the-fact activity distribution that 2 CFR 200 requires and the credential and qualification records that state contracts require. Your cost allocation plan should produce allocations that satisfy both federal cost principles and any state-specific allocation methodologies.
This is harder to design initially. It is dramatically easier to maintain. One policy, consistently applied, consistently documented, consistently auditable — rather than the cognitive overhead of switching between compliance frameworks depending on which funding source is paying for a given activity.
4. Create a Consolidated Reporting Calendar
Take every reporting deadline across every funding stream — federal quarterly reports, state monthly reports, annual audit submissions, credentialing renewals, registration renewals — and put them on a single calendar. Color-code by funding source. Assign a responsible person to each deadline. Build in preparation lead time.
This is not sophisticated technology. It is a spreadsheet, or a shared calendar, or a project management tool. The sophistication is in the discipline of maintaining it and the organizational commitment to treating every deadline as non-negotiable. The cost of a missed reporting deadline — potential suspension of funding, compliance findings, damaged relationships with program officers — far exceeds the cost of building and maintaining the calendar.
5. Maintain Funding-Source Consciousness Across Your Team
Staff delivering services under multiple funding streams do not need to know every requirement of every source. But they need to understand that different funding sources have different rules, and that how they document their work matters.
This is a culture challenge. The clinical supervisor charging time across three streams needs to understand why accurate time reporting matters. The program coordinator procuring supplies needs to understand why documentation exists. Funding-source consciousness does not mean burdening front-line staff with compliance complexity. It means building a culture where people understand that compliance infrastructure supports the mission — and that the fiscal office is maintaining the organization's ability to keep receiving the funding that makes the mission possible.
6. Invest in Fiscal Infrastructure
Fund accounting — tracking revenues and expenditures by funding source, by grant, by cost center — is not optional. It is the foundation that makes everything else possible. Without it, you cannot produce a clean SEFA, allocate costs accurately, or report to funders on how their dollars were spent.
A documented cost allocation methodology, a functioning time-and-effort system, and sufficient reporting capacity are not overhead. They are infrastructure. Organizations that underinvest end up spending more — in staff time, audit findings, questioned costs, and unreimbursed overhead — than the infrastructure would have cost.
Every dollar spent on fiscal infrastructure protects many dollars in grant revenue. For organizations navigating the full Washington State funding landscape, this is not a nice-to-have. It is the cost of doing business with public money.
What State Agencies Could Do Better
The compliance collision described here is not the fault of the organizations caught in the middle, nor of careless rulemaking by state agencies. It is a structural consequence of multiple government levels funding the same organizations through different mechanisms without a coordination requirement. That said, state agencies are not powerless to reduce the friction:
Harmonize where possible. When a state compliance requirement substantially parallels a federal requirement, the state agency should consider accepting the federal standard rather than maintaining a separate-but-similar state standard. If an organization already maintains time-and-effort documentation satisfying 2 CFR 200.430, requiring a different-but-equivalent state documentation format creates work without creating accountability. Harmonization does not mean abdication of state authority. It means recognizing that duplicative requirements consume the capacity of the organizations the state is funding.
Clearly label pass-through terms. In contracts that include federal pass-through funding, state agencies should clearly identify which terms flow from federal requirements, which are state additions, and which apply to which funding portion. This is required by 2 CFR 200.332, which mandates that pass-through entities communicate all applicable federal requirements to subrecipients. But the spirit of that requirement goes beyond listing the CFDA number and award amount. It means helping the subrecipient understand the compliance landscape they are operating in — not leaving them to reverse-engineer it from a 40-page contract.
Accept federal indirect cost rates. When an organization has completed the rigorous process of negotiating a federal indirect cost rate, that rate represents the actual relationship between indirect costs and direct program activities. State agencies should accept that rate for pass-through federal funds — as 2 CFR 200.414 contemplates — and should seriously consider accepting it for state-funded programs as well. Capping indirect cost reimbursement below the actual rate does not reduce overhead costs. It simply shifts them to unrestricted revenue, reducing the organization's financial stability and, ultimately, its ability to deliver the services the state is funding.
Coordinate reporting across agencies. When multiple state agencies fund the same organization, those agencies should explore whether their reporting requirements can be aligned — in timing, in format, or in content. An organization reporting to HCA, DSHS, DOH, and Commerce simultaneously is often reporting substantially similar information in four different formats on four different timelines. Cross-agency coordination on reporting would reduce burden without reducing accountability. It would require state agencies to talk to each other about their grantee portfolios — which, itself, would improve the state's understanding of how public funding actually flows to communities.
The Intersection Is the Normal Case
The organizations holding communities together — the behavioral health agencies, the community health centers, the housing providers, the workforce development programs — do not have the luxury of operating in a single compliance universe. They hold federal grants and state contracts simultaneously, from multiple agencies, with overlapping and sometimes contradictory requirements. They are expected to satisfy all of them, all the time, without a unified roadmap.
The eligibility requirements for each funding stream are just the beginning. Beyond eligibility lies the ongoing operational reality of dual compliance — the daily decisions about procurement thresholds, cost allocation, time documentation, and reporting that determine whether an organization remains in good standing with every funder in its portfolio.
This article has described the collision in detail — not to discourage organizations from pursuing diverse funding, but to make the landscape visible. The compliance burden of dual-funded operations is manageable. Organizations across Washington and the country manage it successfully every day. But they manage it through deliberate infrastructure, documented decision-making, and sustained investment in fiscal and administrative capacity.
The intersection of state and federal compliance is not a special case you prepare for when it arises. It is the operating environment. Build for it accordingly — and know that the organizations navigating the Single Audit threshold and the full spectrum of FQHC compliance obligations are dealing with the same structural reality from different angles.