Three Fiscal Calendars, One Organization: Managing Federal, State, and Calendar Year Compliance
Federal grants run October-September. State contracts run July-June. Medicaid runs January-December. For braided-funded healthcare organizations, every month is the end of someone's quarter.
Every braided-funded healthcare organization runs on at least three clocks.
Federal grants from SAMHSA, HRSA, and CDC follow the federal fiscal year: October 1 through September 30. State behavioral health contracts and pass-through funding follow the state fiscal year: July 1 through June 30 in most states, including Washington. Medicaid cost reporting and many foundation grants follow the calendar year: January 1 through December 31.
These are not just different start dates. Each fiscal year creates its own quarterly reporting cycle, its own year-end close process, its own budget period, and its own audit timeline. When a single organization operates under all three simultaneously — which is the norm for CCBHCs, tribal health programs, FQHCs, and most braided-funded community health organizations — the result is a compliance calendar where every month is the end of someone's quarter, and three months per year are the end of someone's fiscal year.
This guide maps the operational reality of managing three fiscal calendars, identifies the months where deadline conflicts create the highest compliance pressure, and provides a coordination framework for finance teams.
The Three Calendars
Federal Fiscal Year (FFY): October 1 - September 30
Applies to: SAMHSA grants (CCBHC expansion, tribal behavioral health, substance use treatment), HRSA grants (Section 330, Ryan White, behavioral health integration), CDC cooperative agreements, ACF grants, and most other competitive federal awards.
Quarterly periods:
| Quarter | Period | Typical Financial Report Due |
|---|---|---|
| FFY Q1 | October - December | January 30 (SF-425) |
| FFY Q2 | January - March | April 30 (SF-425) |
| FFY Q3 | April - June | July 30 (SF-425) |
| FFY Q4 | July - September | December 30 (SF-425 + annual reports) |
Year-end activities: Final SF-425 for the budget period. Annual programmatic reports. GPRA/NOMs data submission (SAMHSA). UDS submission (HRSA, due in February). Closeout reports for ending awards. Single Audit preparation begins (if fiscal year aligns with org's audit year).
State Fiscal Year (SFY): July 1 - June 30
Applies to: State behavioral health contracts, state pass-through of federal block grants (MHBG, SABG), state opioid response funding, state public health contracts, and most state-administered health funding in Washington and the majority of other states.
Quarterly periods:
| Quarter | Period | Typical Report Due |
|---|---|---|
| SFY Q1 | July - September | October (varies by contract) |
| SFY Q2 | October - December | January (varies by contract) |
| SFY Q3 | January - March | April (varies by contract) |
| SFY Q4 | April - June | July-September (final + annual) |
Year-end activities: Final financial and deliverable reports for the contract period. Contract renewal or continuation applications. State audit compliance (if applicable). Budget submissions for the new contract year.
Calendar Year (CY): January 1 - December 31
Applies to: Medicaid cost reports and PPS rate calculations, many foundation grants, IRS Form 990 (for nonprofits using calendar year), W-2/1099 reporting, and some organizational audits.
Quarterly periods:
| Quarter | Period | Typical Report Due |
|---|---|---|
| CY Q1 | January - March | April |
| CY Q2 | April - June | July |
| CY Q3 | July - September | October |
| CY Q4 | October - December | March-April (annual cost report) |
Year-end activities: Medicaid cost report preparation (major effort — typically due 3-5 months after CY close). Foundation annual reports. IRS 990 preparation. Calendar year audit (if org uses CY as audit year). W-2 and 1099 filing.
The Conflict Calendar
When the three fiscal years overlay, a pattern emerges. Some months are relatively quiet. Others are brutal. The following calendar maps every major compliance event by month.
January: The Hardest Month
January is simultaneously:
- End of FFY Q1 (October-December). SAMHSA/HRSA/CDC quarterly financial reports (SF-425) and programmatic data due within 30 days.
- End of SFY Q2 (October-December). State contract quarterly deliverables and financial reports due per contract terms.
- End of CY (January-December of prior year). Medicaid calendar year just closed. Cost report preparation begins. Foundation annual reports come due.
What the finance team is doing in January:
- Pulling October-December financial data for federal reporting
- Pulling October-December financial and deliverable data for state reporting
- Closing the prior calendar year for Medicaid cost report preparation
- Reconciling cost allocations across all three periods (which share the October-December months but in different fiscal contexts)
- Processing W-2s and 1099s
- If the org uses CY as its audit year, beginning audit preparation
The data overlap problem: October, November, and December belong to FFY Q1 and SFY Q2 simultaneously. The same financial data must be reported to both federal and state agencies — but in different formats, under different frameworks, with different aggregation rules. The cost allocation for these three months must produce numbers that are consistent across both reports.
April: The Second Peak
April is simultaneously:
- End of FFY Q2 (January-March). Federal quarterly reports due.
- End of SFY Q3 (January-March). State quarterly reports due.
- End of CY Q1 (January-March). Medicaid quarterly data may be due.
- IRS 990 deadline (for calendar-year nonprofits, or extension filing).
- Medicaid cost report due (3-5 months after CY close, varies by state).
The data overlap problem: January, February, and March belong to FFY Q2 and SFY Q3 simultaneously — the same overlap pattern as January, but shifted three months.
July: The Third Peak
July is simultaneously:
- End of FFY Q3 (April-June). Federal quarterly reports due.
- End of SFY (July = first month of new state fiscal year). State annual close. Final contract reports due. New contract year begins.
- End of CY Q2 (April-June). Medicaid data due.
The additional complication: July 1 is the state contract renewal date. New contracts may have different terms, different budgets, and different deliverable requirements than the prior year. The finance team is simultaneously closing the old contract year and setting up tracking for the new one — while also preparing federal and Medicaid quarterly reports.
October: The Fourth Compression Point
October is simultaneously:
- End of FFY (October = first month of new federal fiscal year). Federal annual close. Final SF-425 and programmatic reports for ending budget periods. New awards begin.
- End of SFY Q1 (July-September). State quarterly reports due.
- End of CY Q3 (July-September). Medicaid data due.
The additional complication: New federal awards starting October 1 may change the organization's braided funding mix — new compliance requirements, new cost allocation percentages, and potentially new effort allocations for shared staff, all starting simultaneously.
The Quieter Months
February, March, May, June, August, September, November, and December each have fewer overlapping deadlines — but none are truly quiet. At least one fiscal calendar has a quarterly milestone every month. And the background processes — monthly cost allocation, effort documentation, budget monitoring — run every month regardless.
The Reporting Matrix
For a braided-funded organization, the annual reporting load across three calendars looks like this:
| Report | Frequency | Calendar | Due Date Pattern | Hours per Cycle (Est.) |
|---|---|---|---|---|
| SF-425 (per federal grant) | Quarterly | FFY (Oct-Sep) | 30 days after quarter end | 4-8 hrs per grant |
| SAMHSA SPARS/GPRA | Semi-annual or annual | FFY | Per award terms | 8-16 hrs |
| HRSA UDS | Annual | CY | February (for prior CY) | 40-80 hrs |
| State financial report (per contract) | Quarterly | SFY (Jul-Jun) | Per contract terms | 4-8 hrs per contract |
| State deliverable report (per contract) | Quarterly | SFY | Per contract terms | 4-8 hrs per contract |
| Medicaid cost report | Annual | CY (Jan-Dec) | 3-5 months after CY close | 40-80 hrs |
| Foundation reports | Annual or semi-annual | CY (typically) | Per grant terms | 2-4 hrs per grant |
| Single Audit | Annual | Org's fiscal year | 9 months after FY end | 40-100 hrs (org preparation) |
| IRS 990 | Annual | Org's fiscal year | 4.5 months after FY end (+ extension) | 8-20 hrs |
For an organization managing 3 federal grants, 2 state contracts, Medicaid, and 2 foundation grants:
- Federal SF-425s: 3 grants × 4 quarters = 12 financial reports per year
- State reports: 2 contracts × 4 quarters × 2 report types = 16 reports per year
- Medicaid: 1 annual cost report
- Foundation: 2 annual reports
- Plus: SPARS/GPRA, UDS (if FQHC), Single Audit, 990
Total: roughly 35-40 formal compliance submissions per year, excluding monthly cost allocation, effort documentation, and ongoing budget monitoring.
The Coordination Framework
Managing three fiscal calendars requires a coordination system. The specific tool matters less than the discipline — whether it's a shared spreadsheet, a project management system, or a compliance platform, the framework must accomplish five things.
1. Single-Source Monthly Close
Close the books monthly. Run cost allocations monthly. This produces a single set of financial data for each month that can be sliced by any fiscal year period.
Why monthly matters: If you close the books quarterly (or worse, annually), you're reconstructing data under deadline pressure for whichever fiscal year happens to be reporting. Monthly close means the data is ready when any calendar needs it.
What "close" means operationally:
- All transactions for the month are recorded in the accounting system
- Personnel effort is documented and applied
- Cost allocations are calculated and posted as journal entries
- Budget-vs-actual is updated per grant
- Allocation schedule is produced and filed
2. Rolling 90-Day Deadline View
At any point, you should know every compliance deadline in the next 90 days — across all three calendars, across all grants and contracts. Not just the report due dates, but the preparation milestones:
| Milestone | Lead Time Before Deadline |
|---|---|
| Data extraction starts | 21 days |
| Draft report prepared | 14 days |
| Internal review | 7 days |
| Final submission | Due date |
For a month with three overlapping deadlines (e.g., January: FFY Q1, SFY Q2, CY close), preparation starts in early December. That's three simultaneous report preparation cycles running in parallel, each requiring data from the same underlying allocation.
3. Period-Aware Reporting
Every financial report must pull data for the correct period:
- SAMHSA Q1 report → October, November, December data (federal fiscal year)
- State Q2 report → October, November, December data (state fiscal year)
- Medicaid annual → January through December data (calendar year)
The October-November-December data is the same underlying financial data, but the SAMHSA report and the state report may format and aggregate it differently. The system (or spreadsheet, or process) must produce period-specific outputs from a shared data source, with the totals reconciling across outputs.
4. Cross-Calendar Reconciliation
At least quarterly, reconcile across all three calendars:
Test: For any month that falls within two or more fiscal year quarters, the costs reported to the federal agency plus the costs reported to the state agency plus the costs reported to Medicaid must equal total actual costs for that month. No more, no less.
Example: In November:
- SAMHSA report includes November as part of FFY Q1
- State report includes November as part of SFY Q2
- Medicaid cost report includes November as part of CY
The cost allocation for November assigns each dollar to one (and only one) funding stream. The SAMHSA report includes the SAMHSA-allocated dollars. The state report includes the state-allocated dollars. The Medicaid report includes the Medicaid-allocated dollars. If you add them up, plus any unrestricted or unallocated costs, the total equals November's actual total expenditures.
If this reconciliation doesn't balance, there's an allocation error that will surface in an audit.
5. Year-End Triage Protocol
Three fiscal year-ends means three annual close processes. Each competes for the same staff time:
| Year-End | When | Duration | Key Deliverables |
|---|---|---|---|
| State (June 30) | July-August | 6-8 weeks | Final contract reports, renewal applications |
| Federal (September 30) | October-December | 8-12 weeks | Final SF-425, programmatic reports, SPARS/GPRA, closeout for ending awards |
| Calendar (December 31) | January-April | 12-16 weeks | Medicaid cost report, foundation reports, 990, audit prep |
Triage principle: Know which year-end is approaching 90 days in advance. Begin preparation for year-end reporting while still in the current quarter's operating cycle. Dedicate staff time based on the complexity and stakes of each year-end — Medicaid cost report preparation (which affects PPS rates and future revenue) typically warrants more time than foundation annual reports.
The Compliance Calendar Template
A starting template for a braided-funded healthcare organization managing federal grants (FFY), state contracts (SFY), and Medicaid (CY):
Month-by-Month Overview
| Month | FFY Context | SFY Context | CY Context | Compliance Pressure |
|---|---|---|---|---|
| Jan | Q1 close (Oct-Dec) | Q2 close (Oct-Dec) | Year-end (prior CY) | Critical — triple overlap |
| Feb | Q2 begins | Q3 begins | CY Q1 | Moderate — HRSA UDS due |
| Mar | Q2 operating | Q3 operating | CY Q1 close prep | Moderate |
| Apr | Q2 close (Jan-Mar) | Q3 close (Jan-Mar) | CY Q1 close + cost report due | High — double overlap + annual |
| May | Q3 begins | Q4 begins | CY Q2 | Moderate |
| Jun | Q3 operating | Year-end (SFY close) | CY Q2 | High — state year-end |
| Jul | Q3 close (Apr-Jun) | New year begins | CY Q2 close | High — triple overlap + state renewal |
| Aug | Q4 begins | Q1 operating | CY Q3 | Moderate — state closeout wrapping |
| Sep | Year-end (FFY close) | Q1 operating | CY Q3 | High — federal year-end |
| Oct | New year begins | Q1 close (Jul-Sep) | CY Q3 close | High — new awards + state Q close |
| Nov | Q1 operating | Q2 begins | CY Q4 | Low — operating month |
| Dec | Q1 operating | Q2 operating | CY Q4 close prep | Moderate — prep for January |
Critical months: January, April, July, October High-pressure months: June, September Moderate months: February, March, May, August, December Lowest pressure: November (the one month with the fewest overlapping close/reporting activities)
Staffing Implications
The three-calendar reality has direct staffing implications that braided-funded organizations must plan for:
There is no "slow season." Unlike organizations running on a single fiscal year — which have a predictable compliance rhythm with quiet months — braided-funded organizations have compliance-intensive months throughout the year. Staff vacations in January, April, July, or October create compliance risk.
Year-end capacity planning. Each year-end (state in June/July, federal in September/October, calendar in December/January) requires dedicated preparation time. If the same person handles all three, they're in year-end mode for roughly six months per year.
Cross-training is a risk mitigation. If one person understands the federal reporting cycle and another understands the state reporting cycle, a resignation creates an immediate compliance gap. Cross-training on all three calendar cycles reduces single-point-of-failure risk.
The CFO's calendar. In many community health organizations, the CFO manages compliance across all three calendars personally. This means the CFO is preparing some form of year-end or quarterly close documentation roughly 40 weeks out of 52. The remaining 12 weeks are for annual audit, budget planning, and board reporting. This is the operational reality that braided funding creates — and it explains why compliance is consistently cited as the top administrative burden by community health organization leaders.
This guide is part of GrantBridges's braided funding compliance series. See also: Cost Allocation Across Multiple Compliance Frameworks and the Compliance Framework Comparison Chart.