Skip to main content
GrantBridgesGrantBridges

Search · Articles · States · Solicitations · Tools

Assess Readiness →
AnalysisFederal Program OfficersState Agency StaffFoundation Program Officers12 min read

The Case for Harmonized Reporting: When Every Funder Asks for the Same Data in a Different Format

Five funders ask for substantially similar financial and programmatic data in five different formats, on five different schedules, through five different portals. The cost of this fragmentation falls entirely on grantees.

A certified community behavioral health center in the Pacific Northwest submits roughly 35-40 formal compliance reports per year. Eight federal financial reports. Eight programmatic data submissions. Eight state financial and deliverable reports. An annual Medicaid cost report. Foundation annual reports. The Single Audit. The IRS 990.

These reports cover substantially overlapping information. The clinician salaries reported to SAMHSA on the SF-425 are the same salaries reported to the state on quarterly financials and reflected in the Medicaid cost report. The client outcomes reported to SAMHSA through SPARS are the same outcomes reported to the state through their deliverable tracking and captured in the Medicaid encounter data.

The CFO of this organization estimates that roughly 60% of the effort in any given report goes to reformatting data she's already reported elsewhere. Not generating new information. Not performing new analysis. Reformatting — changing the aggregation period, adjusting the framework-specific treatment, populating a different template, uploading through a different portal.

This is not a technology problem. It's a coordination problem. And while the individual reporting requirements of each funder are reasonable, the collective effect of five funders independently designing their own reporting formats — each optimized for their own data needs without regard for what the grantee is simultaneously reporting to four other funders — creates an administrative burden that is both avoidable and costly.


The Anatomy of Redundant Reporting

What Gets Reported

Consider the financial data that a braided-funded healthcare organization reports across its funding portfolio:

Data ElementSF-425 (SAMHSA)State Financial ReportMedicaid Cost ReportFoundation Report
Personnel costs by programYes (budget category)Yes (contract deliverable area)Yes (cost center)Yes (budget line)
Fringe benefitsYes (budget category)Yes (contract line)Yes (cost center)Sometimes
Indirect costsYes (rate × MTDC)Yes (capped rate × base)Yes (embedded in rate)Sometimes
Total expenditures by periodYes (quarterly, FFY)Yes (quarterly, SFY)Yes (annual, CY)Yes (annual, CY)
Budget vs. actualYesSometimesImplicit in cost reportSometimes
Cost allocation methodologyReferencedReferencedRequired for cost reportRarely asked

The underlying data is the same. The personnel costs are the same salaries. The indirect costs come from the same overhead pool. The totals derive from the same general ledger. What changes across reports is the format, the aggregation period, the framework-specific adjustments, and the submission mechanism.

What Differs

DimensionSAMHSAStateMedicaidFoundation
Reporting periodFederal FY (Oct-Sep)State FY (Jul-Jun)Calendar Year (Jan-Dec)Calendar Year
Financial formatSF-425 (standardized federal)State-specific templateCMS cost report formatFunder-specific (varies)
Programmatic formatSPARS/GPRA/NOMsState deliverable templateEncounter data + quality measuresNarrative + outcomes
Submission portalPMS / SPARSState contract portalState Medicaid portalEmail / online portal
Indirect cost treatmentNICRA (full rate)Capped rate (10-15%)Embedded in PPSVaries
Review processFederal program officerState contract managerState Medicaid agencyFoundation program officer

Five reports. Five formats. Five portals. Five review processes. One set of underlying data.


The Cost of Fragmentation

Direct Time Cost

For a typical braided-funded healthcare organization managing six funding streams, the annual compliance reporting burden breaks down approximately:

ActivityAnnual HoursWhat It Involves
Monthly cost allocation240 hrs (20/month)Running allocations, posting journal entries, producing schedules
Federal financial reports (SF-425)48-96 hrsData extraction, framework-specific formatting, submission, revision
Federal programmatic reports48-96 hrsSPARS, GPRA, quality measures, program narratives
State financial reports48-96 hrsData extraction, state template formatting, submission
State deliverable reports48-96 hrsDeliverable documentation, outcome data, narratives
Medicaid cost report40-80 hrsCalendar year cost compilation, CMS formatting, rate reconciliation
Foundation reports8-16 hrsAnnual narratives, financial summaries
Single Audit preparation40-100 hrsWorking paper preparation, auditor support, finding responses
Cross-report reconciliation60-120 hrsEnsuring consistency across all submissions

Total: roughly 580-1,000 hours per year — equivalent to 0.3 to 0.5 FTE dedicated solely to compliance reporting.

The line item that should draw attention is the last one: cross-report reconciliation. This is the work of ensuring that the numbers reported to SAMHSA are consistent with the numbers reported to the state, which are consistent with the Medicaid cost report, which are consistent with the audited financials. This reconciliation work exists solely because the reports are submitted in different formats, for different periods, through different systems. It would not exist if the reporting were harmonized.

Opportunity Cost

The 0.3-0.5 FTE consumed by compliance reporting is time not spent on:

  • Program development and quality improvement
  • Staff supervision and training
  • Community outreach and patient engagement
  • Strategic planning
  • Grant writing for additional funding

For a behavioral health center facing a workforce crisis — where every clinician hour matters — the opportunity cost of reformatting the same data five different ways is measured in patient access.

Error Risk

Every reformatting introduces error risk. When the same financial data is manually extracted, adjusted for framework-specific treatment, and re-entered into a different template, each step is an opportunity for inconsistency. A rounding difference here, a misallocated month there, an indirect cost calculated at the wrong rate — these errors may be individually minor, but they compound across reports and create the inconsistencies that auditors find.

The more reports, the more reformatting, the more error risk. Harmonized reporting would not eliminate errors, but it would eliminate an entire category of them — the errors caused by translating the same data across formats.


What Harmonization Could Look Like

Reporting harmonization doesn't require a single universal format. It doesn't require funders to abandon their specific data needs. It requires reducing the unnecessary differences — the ones that exist because each funder designed their reporting independently rather than in coordination with the other funders their grantees also serve.

Tier 1: Common Financial Core

A standardized financial reporting format that all funders accept as the base layer. The grantee produces one set of financial data — total costs by category, allocated by funding stream, reconciled to the general ledger — in a common format. Each funder receives the portion relevant to their award, with framework-specific adjustments (indirect cost rate, allowable cost exclusions) applied as a supplement rather than a separate report.

What this eliminates: Reformatting the same financial data for each funder's template. The SF-425, state financial report, and Medicaid cost report all require substantially the same financial information — total expenditures by category, allocated to the award, for the reporting period.

What this preserves: Each funder's ability to apply their own framework-specific analysis. SAMHSA still tests allowability under 2 CFR 200. The state still applies their indirect cost cap. Medicaid still uses CMS methodology for PPS rate calculation.

Tier 2: Aligned Reporting Periods

The three-fiscal-year problem creates the most reconciliation burden. If funders aligned on a common reporting period — or at minimum, aligned quarterly cutoffs — the grantee could produce one quarterly data set rather than three overlapping ones.

The realistic version: Full fiscal year alignment may not be feasible (Congress controls the federal fiscal year, states control theirs). But quarterly cutoff alignment is possible. If federal Q1 (Oct-Dec), state Q2 (Oct-Dec, in states with Jul-Jun FY), and calendar Q4 (Oct-Dec) all accepted the same October-December data — even if labeled differently for each funder's fiscal year — the reconciliation burden would drop significantly.

Tier 3: Shared Portals

Five portals for five funders means five sets of credentials, five submission processes, five confirmation workflows. A shared submission infrastructure — even if each funder maintains their own review process — would reduce the mechanical burden of compliance reporting.

The federal government has moved in this direction with Grants.gov (submission) and PMS (financial management). But state systems remain independent, Medicaid reporting is separate, and foundation reporting has no standardization at all.


What Funders Can Do Now

Full harmonization is a systemic change that will take years. But individual funders can reduce the reformatting burden on grantees through actions within their current authority:

Accept Existing Reports

If a grantee produces an SF-425 for a federal award covering October-December, and the state contract also needs financial data for October-December (which falls in the state's Q2), the state could accept the SF-425 as the base financial document rather than requiring a separate state-formatted report. The grantee would supplement with state-specific information (deliverables, indirect cost cap calculation) rather than reformatting the entire financial submission.

Where this applies: Any funder whose reporting period overlaps with a federal quarter. The SF-425 format is well-understood, standardized, and auditable.

Coordinate With Co-Funders

When a funder knows that their grantee also receives funding from specific other sources — which is usually apparent from the grantee's budget or disclosure — the funder can coordinate reporting expectations. Simple coordination: "We know you submit SF-425s to SAMHSA quarterly. We'll accept the same financial data in SF-425 format for our reporting period."

This is most feasible among state agencies. A state behavioral health agency and a state public health agency funding the same CCBHC could agree on a common reporting template rather than each requiring their own.

Reduce Format-Specific Requirements

Every custom field, every unique template, every portal-specific formatting requirement adds to the reformatting burden. Funders reviewing their reporting requirements should ask: does this field capture information that isn't available in a standard format (SF-425, organizational financial statements)? If not, consider accepting the standard format.

Support Compliance Infrastructure

Funders who include compliance infrastructure as an allowable cost — and who actively encourage grantees to invest in systems that automate cost allocation and reporting — are investing in the accuracy and timeliness of their own data.

A SAMHSA program officer whose grantee uses a compliance system that produces accurate, timely, consistent financial data across all funding streams benefits directly: more reliable SF-425s, fewer questioned costs, better programmatic data, and a grantee whose staff spends more time on program delivery and less on spreadsheet reconciliation.


The Foundation Opportunity

Private foundations occupy a unique position in the harmonization conversation. Unlike federal and state funders, foundations have broad discretion over their reporting requirements. Many have already simplified through the trust-based philanthropy movement — reducing application burden, streamlining reporting, and shifting from compliance-oriented to learning-oriented relationships with grantees.

Foundations funding braided-funded organizations can go further:

Accept the funder financial report. If the grantee produces an SF-425 for their federal awards, the foundation can accept the same financial data rather than requiring a separate financial report. The foundation's portion of the allocation is identifiable within the broader financial data.

Align reporting periods. If the grantee's primary reporting cadence is quarterly (to match federal and state schedules), the foundation can align its annual report due date with the grantee's calendar year close — reducing the number of distinct reporting cycles.

Ask what's useful, not what's standard. Foundation reporting should capture what the foundation needs to evaluate impact and learn from the investment. Often, that's a conversation — not a form. A 30-minute call with the program director may yield more insight than a 10-page narrative report that the grants manager spent 8 hours writing.


The Long View

The reporting fragmentation described in this piece is not anyone's fault. Each funder designed their reporting to serve their specific accountability needs. Federal financial reporting follows federal standards. State reporting follows state standards. Medicaid reporting follows CMS standards. Each makes sense in isolation.

The fragmentation is a systems-level problem that emerges from the interaction of individually rational decisions. No single funder created it. No single funder can solve it. But every funder can contribute to reducing it — by accepting existing formats where possible, coordinating with co-funders, reducing unnecessary format-specific requirements, and supporting the compliance infrastructure that makes accurate multi-stream reporting possible.

The grantees managing braided funding today are the organizations providing behavioral health crisis services, primary care in underserved communities, tribal health programs, and substance use treatment. The time they spend reformatting data for five funders is time they don't spend serving patients. The compliance errors introduced by redundant reformatting create audit risk that threatens programs serving vulnerable populations.

Harmonized reporting isn't an administrative convenience. It's a program effectiveness issue. Every hour a CCBHC CFO spends reformatting a financial report she's already submitted to another funder in a different format is an hour that could have been spent on the mission every funder shares: improving health outcomes in the communities they serve.


This article is part of GrantBridges's braided funding compliance series. See also: What Happens Inside a Grantee and Braided Funding Is an Operations Problem.