New webinar on 3rd March 2026 | 9:00 am PT
In this webinar, discover how Sopact Sense revolutionizes data collection and analysis.
Grant compliance built into the record. 990 Schedule I, Schedule H, Uniform Guidance, state filings, board packets. Two-way sync to your finance system
Grant compliance software
Grant compliance software is the system foundations and hospital community-benefits teams use to meet regulatory and board reporting obligations, including IRS Schedule H and I for nonprofit hospitals, state attorney general filings, and internal board or committee reporting. Effective compliance software integrates with finance systems like Workday to pull budget actuals, captures a defensible audit trail of every grant decision, and assembles recurring reports automatically from source records rather than requiring manual data entry.
This page covers Stage 06 (Finance) and Stage 08 (Comply). For program-side reporting and grantee tracking, see Post-Award Grant Management →
The real bottleneck
Foundations do not lack data. The grantee submitted the metrics. The enterprise finance system has the spend. The board has the minutes. What is missing is a way to assemble those pieces into the specific shapes each regulator, board, and auditor expects, on the recurring cadence they expect them, without a six-week scramble before every deadline.
01 · Federal
Nonprofit hospitals report community-benefit activity on Schedule H Part I (financial assistance) and Part II (community-building). Each grant is mapped to a category. Spend must reconcile to general ledger. One filing per tax year.
02 · State
Massachusetts, New York, California, and others require annual charitable-trust filings with grant-by-grant disclosure. Some states also require Department of Public Health reporting for hospital community-benefits programs.
03 · Committee
The community-benefits advisory committee meets quarterly. The board sees the annual rollup. Each needs program performance, spend summary, equity-lens metrics, and narrative themes pulled from grantee qualitative reports.
04 · Audit
Auditors ask why a decision was made, who approved it, and when. Without a captured audit trail, the response is a six-week document hunt. With one, it is a query.
Definitions, with the specificity SmarterSelect skipped
Grant compliance is three obligations stacked on top of each other. Most platforms collapse them into one bucket and lose the differences that matter. This page is built on the first two. The third is partially covered by post-award grant management.
01 · Regulatory
IRS (Schedule H, Schedule I, Form 990), state attorneys general, state departments of public health, and federal funders if pass-through dollars are involved. The deadlines are fixed, the formats are fixed, and the consequences of missing them are public.
Owner: CFO, compliance officer
02 · Funder-internal
The foundation's commitments to its own board, audit committee, and (for hospital systems) the community-benefits advisory committee. Recurring packets, allocation against approved budget, equity-lens reporting, and answers to questions the board asked last quarter.
Owner: Program officer, VP community benefits
03 · Grantee-side
Grant agreement terms the grantee agreed to: metric submission deadlines, allowable expenses, scope changes, no-cost extensions. The lighter touch of this trio, and the one that overlaps with program monitoring.
Mostly on post-award grant management →
The centerpiece
Most "Workday integration" claims are a one-way export. Real two-way integration means a grantee submitting a deliverable in Sopact triggers an invoice in Workday, and a payment cleared in Workday closes the milestone on the grant record. No re-keying, no reconciliation spreadsheet, no end-of-quarter scramble to match what was paid against what was promised.
Source of truth · grant program
Source of truth · finance
SYNC CADENCE
Real-time webhook on AP status. Nightly batch for budget rollups.
AUTHENTICATION
SSO + service account. Data residency configurable.
ALSO SUPPORTED
NetSuite, Sage Intacct, Oracle Cloud ERP. Same two-way model.
Worked example · hospital community-benefits program
Federal layer
Nonprofit hospitals file IRS Schedule H every tax year. Part I covers financial assistance and means-tested government programs. Part II covers community-building activities, including community-benefit grants to outside organizations. Schedule I covers all 501(c)(3) grants to organizations and individuals.
The annual filing is the visible artifact. The real work is the mapping: every grant to a Schedule H category, every dollar reconciled to general ledger, every recipient organization documented with EIN, address, and purpose statement. Foundations that do this in a spreadsheet spend three to six weeks per year on assembly. The data was already in their systems.
Sopact pre-maps each grant program to the relevant Schedule H category at the time the program is created. The annual report assembles itself from already-captured grantee data plus Workday-synced spend. The CFO and compliance officer review an assembled draft. They do not build the draft.
Community-building activities · tax year FY24 · assembled by Sopact
State layer + the audit trail
State attorney general filings, Department of Public Health Determination of Need reporting, and federal funder audits all converge on the same question. Not "what did you spend?" but "why did you spend it, who approved it, and on what evidence?"
"Why did this grantee receive a year-2 payment when their year-1 metrics were below the renewal threshold?"
Without a captured audit trail, the answer is a six-week document hunt across email, Slack, board minutes, and program-officer memory. With one, the answer is a query against the immutable event log on the grantee record. Every decision, edit, approval, and exception is captured with timestamp, actor, and rationale.
Role-based access keeps the trail surgical. The CFO sees finance. The program officer sees programs. The board sees aggregates. The external auditor gets read-only access to everything during the engagement, with no privileged data export.
Year 2 payment decision · immutable event log
2027-04-12 09:14 EST
Year-1 annual report submitted by grantee. 4 of 6 KPIs at threshold. 2 KPIs below.
2027-04-14 11:02 EST
Narrative analysis flagged staffing turnover as the documented cause of 2 below-threshold KPIs.
2027-04-18 14:33 EST
Program officer recommendation by J. Reyes: continue with corrective action plan. Rationale logged: "documented exogenous cause, mitigation underway."
2027-04-21 10:00 EST
Compliance review by S. Patel: approved. Cited grant-agreement clause 4.b.iii (corrective action provision).
2027-04-22 08:30 EST
Payment authorized: $145,000. Enterprise finance system invoice INV-9821 created.
2027-04-29 16:11 EST
Payment cleared in finance system. Grant record updated. Next milestone exposed to grantee.
Committee layer
The grants or program committee meets quarterly. The full board sees the annual rollup. The audit committee sees the audit-trail summary. Each packet is a different cut of the same underlying grant records.
Recurring packets get assembled automatically from already-captured data. The program officer reviews, adds a one-paragraph framing note, and exports. The night-before scramble disappears.
The grantee qualitative reports already analyzed by Intelligent Cell during the reporting cycle feed the "narrative themes" section directly. No re-reading. No paraphrasing.
CBAC
Quarterly · ~4 hours prep
FULL BOARD
Annual · ~6 hours prep
AUDIT CMTE
Semi-annual · ~3 hours prep
Auto-assembled
01
28 active grants, spend vs budget by program, milestone completion. Live from grant records
02
Budget vs actual by cost center, variance flags, period-over-period. From Workday GL
03
Demographic reach, geographic distribution, partner organization profile. From grantee KPI submissions
04
Top barriers, top accelerators, surprises. From Intelligent Cell analysis
05
Renewals up, exceptions requested, allocation recommendations. Program officer review
Manual compliance vs Sopact
Seven operational rows. Left column is what most foundations do today: Excel sheets, email threads, Workday exports, and a six-week assembly window per major report. Right column is the same work on a persistent-record platform with a two-way ERP integration. The time savings are real. The audit-trail completeness is what the auditor actually cares about.
| Compliance operation | Manual Excel + email + Workday exports |
Sopact persistent record + two-way ERP |
|---|---|---|
| Workday spend pull | Manual CSV export per cost center, per period. Re-key into grant tracker. | Webhook on AP status change. Grant record reflects current spend in real time. |
| Budget vs actual reconciliation | Pivot table built quarterly. Drifts between cost-center coding in Workday and program names in the tracker. | Cost center to program mapping locked at grant creation. Reconciliation is automatic and continuous. |
| IRS Schedule H / I assembly | Three to six weeks of mapping grants to categories, requesting EINs and addresses, reconciling totals to GL. | Categories pre-mapped at program creation. Filing draft assembled. CFO reviews instead of building. |
| State AG filing | Separate spreadsheet, re-keyed grant data, manual signature workflow. | Same source records. State-specific template populated. Sign-off captured in audit log. |
| Board / committee packet | PowerPoint built from scratch every meeting. Stale numbers, narrative pasted from email. | Auto-assembled from live grant data and Intelligent Cell narrative analysis. Reviewed in hours, not days. |
| Audit trail completeness | Decisions live in email and program officer memory. Six-week document hunt when the auditor asks. | Every decision, edit, approval, and exception captured with timestamp, actor, and rationale. One query. |
| Time per reporting cycle | Schedule H: 4-6 weeks. AG filing: 2-3 weeks. CBAC packet: 5-8 days. | Schedule H: 3-5 days review. AG filing: 1-2 days review. CBAC packet: 4-6 hours review. |
Common questions
Grant compliance is the work of meeting the rules and reporting obligations attached to a grant program. For foundations and nonprofit grant-makers, that is three obligations stacked together: regulatory compliance with the IRS, state attorneys general, and (for federal pass-through funders) the OMB Uniform Guidance single-audit rules; funder-internal compliance with your own board, audit committee, and program committees; and grantee compliance, which is the foundation enforcing terms on its grantees. Most platforms collapse these into one bucket and lose the differences.
Grant reporting is the act of producing the documents: Schedule H, the AG filing, the board packet, the audit response. Grant compliance is the broader practice of operating the grant program in a way that lets those reports be produced quickly, accurately, and defensibly. Reporting is the output. Compliance is the discipline of capturing every decision, every approval, and every dollar in a form that the report can pull from without manual re-keying.
Yes. Nonprofit hospitals file IRS Schedule H every tax year, with Part II specifically dedicated to community-building activities including grants to outside organizations. Many states layer additional requirements on top. Massachusetts requires a Department of Public Health Determination of Need report. New York and California have separate state-level community-benefit filings. The federal filing is the floor, not the ceiling.
Schedule H is the IRS form nonprofit hospitals attach to Form 990 to report community-benefit activity. Part I covers financial assistance and means-tested government programs. Part II covers community-building activities, including community-benefit grants to outside organizations. Part III covers bad-debt expense. For grant compliance specifically, the work is mapping each grant to a Schedule H category, documenting each recipient organization, and reconciling spend to general ledger. A platform that pre-maps categories at grant creation converts the annual filing from a multi-week assembly project into a multi-day review.
Two-way integration is the right model. From the grant platform to Workday: an invoice is created automatically when a grantee submits a deliverable and the milestone is approved. From Workday back to the grant platform: AP status updates flow in real time (submitted, approved, paid) and budget vs actual is reconciled nightly. Authentication is typically SSO plus a service account. Data residency is configurable. The same two-way model also works with NetSuite, Sage Intacct, and Oracle Cloud ERP.
An audit trail is an immutable event log capturing every decision, edit, approval, and exception against a grant record, with timestamp, actor, and rationale. When an auditor asks why a year-2 payment was authorized despite below-threshold year-1 metrics, the audit trail answers in a query rather than a six-week document hunt. A defensible audit trail requires that records cannot be silently edited after the fact, that approvals are signed by named users, and that the rationale for exceptions is captured at the time of decision, not reconstructed later.
Most foundations land on a three-tier cadence. The grants or program committee meets quarterly and sees program performance, spend, and emerging issues. The full board meets annually or semi-annually for the rollup and major strategy decisions. The audit committee meets semi-annually and sees the audit-trail summary plus risk register. Auto-assembled packets cut prep time from days to hours and let the program officer focus on framing rather than building.
Yes, with one caveat. The assembly can be fully automated when the underlying grant program is structured so that compliance categories are mapped at grant creation, financial data is synced from the ERP, and grantee reports are captured in a structured form. The review and sign-off cannot and should not be automated. The CFO, compliance officer, and program officer still own accuracy and judgment. Automation moves them from data assembler to data reviewer, which is where their time belongs.
Bring a real compliance cycle
Discovery call · 45 minutes · with the founder & CEO. Bring one active grant program, a sample Workday cost-center structure, and the last Schedule H or AG filing you assembled by hand. We'll walk through how Sopact would handle the next cycle against your own data and your own integrations, not a sandbox.
