Federal Award Intake and Compliance Matrix for Nonprofits

Federal award intake is the controlled translation of a signed award into operating instructions. It should answer: what governs, who must act, when, in which system, and what proves completion? Neither QuickBooks Online (QBO) nor GrantLink creates compliance. Compliance comes from the recipient's conduct, controls, records, and adherence to the controlling award.

This guide reflects the eCFR current on August 2, 2026. Always read the program statute, agency regulations, award, incorporated terms, and later amendments; a pass-through entity's subaward may add applicable terms.

First separate the parties' duties

Do not turn every sentence in 2 CFR part 200 into a recipient checklist.

Federal agency or pass-through entity duties

• Under 2 CFR 200.208(d)–(e), before imposing specific conditions, the agency or pass-through entity must state the condition, reason, cure, cure period, and reconsideration method, and must promptly remove the condition when its cause is satisfied.
• Under 2 CFR 200.211, the Federal agency must communicate required award information and terms. That rule structures what the agency puts in the award; it is not a recipient-created-award requirement.
• Under 2 CFR 200.308(d), the agency or pass-through entity must review a revision request, should respond within 30 days, and must give a written expected decision date if review will take longer.
• A pass-through entity has separate subaward identification, risk evaluation, monitoring, corrective-action, audit-resolution, and access duties under 2 CFR 200.332. A nonprofit has those duties only when it is acting as a pass-through entity—not merely because it receives Federal funds.

Recipient or subrecipient duties

• Maintain a financial management system that identifies awards, supports required reporting, traces funds to source documentation, safeguards assets, compares expenditures with each award budget, and includes written cash-management and cost-allowability procedures (2 CFR 200.302(a)–(b)).
• Establish, document, and maintain effective internal control; evaluate and monitor compliance; act on noncompliance; and take reasonable cybersecurity measures (2 CFR 200.303).
• Oversee every program, function, or activity and relate financial data and accomplishments to award goals in performance reporting (2 CFR 200.329(a)–(b)).
• Retain and provide access to records under 2 CFR 200.334–200.337.

The operational intake matrix

The following is a recommended internal practice, not a form prescribed by part 200. Add agency- and program-specific rows.

Intake field or control	Governing evidence	Accountable owner	System/control action	Completion evidence
Legal recipient, UEI, Assistance Listing, Federal award ID, agency/pass-through entity	Signed award and § 200.211	Executive/finance	Confirm legal entity and QBO company; create one grant record	Reviewer-signed identity check
Award date, budget periods, period of performance	Award cover page and amendments	Program + finance	Enter exact dates; block out-of-period coding for review	Date-field comparison
Federal and non-Federal shares; approved budget	Award budget	Finance	Load the approved category baseline and cost-share commitment	Total-to-award reconciliation
Scope, objectives, milestones, performance measures	Award narrative and incorporated application	Program	Assign each deliverable and evidence owner	Milestone calendar
Financial, performance, property, subaward, and closeout reports	Award reporting schedule	Finance/program	Calendar preparer, reviewer, submission route, and due date	Submission receipt and accepted report
Payment method and cash rules	Award, agency payment instructions, § 200.305	Treasury/finance	Document draw/reimbursement workflow and segregation	Draw support and bank/QBO tie-out
Applicable statutes, regulations, general and program terms	Award's order-of-precedence clause	Compliance	Save or link the exact incorporated versions	Dated terms index
Specific conditions	Notice under § 200.208	Named control owner	Record cure, deadline, reconsideration path, and status	Funder removal notice—not an internal assumption
Cost principles and item-specific approvals	Award, §§ 200.403–200.476	Finance	Build allowability and approval flags before commitment	Approval attached to transaction packet
Prior-approval triggers	Award and § 200.308	Program + finance	Route proposed changes before implementation	Written approval and amendment, if issued
QBO tracking scope	Approved accounting design	Controller	Identify every Customer, Project, Class/subclass, or Location linked to this grant	QBO detail control total
Subawards versus procurements	Agreement substance and §§ 200.331–200.332	Compliance/procurement	Document classification; if pass-through, establish monitoring	Determination and monitoring file
Record-retention start and exceptions	§ 200.334 and award	Records owner	Set a trigger-based hold, not just an award-end deletion date	Disposition/hold log

For more detail, use the grant compliance checklist, subaward monitoring guide, and Federal budget revision guide.

Build the QBO control plan

QBO remains the accounting source of truth. A recommended plan is:

1. Define the population. List the exact QBO tracking values that identify the award, including full parent/child paths and explicit exclusions. A grant may link multiple QBO Classes or subclasses, but links are configured per grant.
2. Preserve source lines. Keep the original QBO transaction ID and amount. Record a reviewed grant allocation separately rather than overwriting source economics.
3. Bridge accounts to the funder's categories. Maintain an effective-dated crosswalk from QBO accounts and allocation rules to the approved budget. Do not confuse this with Settings > QuickBooks Mapping, which is limited to restriction-release accounts.
4. Reconcile on a set cadence. Tie the QBO transaction population to reviewed allocations, the award category ledger, draws, reports, and cash receipts. Investigate unmapped, duplicated, stale, reversed, and out-of-period lines.
5. Separate accounting from allowability. A correctly posted QBO expense is not automatically allowable or claimable. Preserve exclusions and their reasons.

See how to reconcile a grant report to the QBO general ledger and cost allocation methods.

GrantLink can organize per-grant links, QBO-backed allocations, budgets, documents, approvals, and activity history. Reports start in Chats > New Chat. GrantLink does not automatically rewrite QBO, and its records do not replace the signed award, source documents, or required professional judgment.

Control versions and amendments

Treat the accepted award as version 1, never as a file to overwrite. This is a recommended internal control:

1. Hash or otherwise identify the accepted package; record effective and received dates.
2. Keep the original award, incorporated application/budget, terms, and correspondence together.
3. Log each proposed change with its scope, budget, milestones, cost share, reporting, and system impact.
4. Keep a proposal status of draft, submitted, approved, denied, or withdrawn. “Submitted” is not “approved.”
5. On written approval, create a new immutable baseline and an effective-dated change summary. Preserve all prior versions.
6. Update QBO coding instructions, GrantLink's grant budget and links, calendars, purchase controls, and subaward instructions only as the approval permits. Reconcile the first report under the new baseline.

When terms conflict, follow the award's order-of-precedence provision and obtain written clarification. Do not silently choose the version that produces the most convenient result.

Monitoring, recovery, and retention

Under § 200.329, monitoring is continuous oversight, not just filing reports. A recommended monthly review compares accomplishments, obligations, expenditures, cost share, cash, forecast, and conditions against the current approved baseline. Escalate adverse developments and deviations promptly under the award's reporting requirements.

If intake was incomplete or the wrong version was used:

1. stop affected commitments, draws, allocations, and submissions where practical;
2. preserve the original QBO entries and all submitted records;
3. identify the affected period and full transaction/report population;
4. compare conduct with the terms actually effective at that time;
5. notify the authorized official, finance, program lead, and legal/CPA advisers as appropriate;
6. seek funder direction or retroactive approval without representing that approval is guaranteed;
7. correct QBO only when the books are wrong, using the organization's controlled adjustment process; correct grant-layer links or allocations when that layer is wrong; and
8. resubmit, repay, or disclose when required, retaining the decision and reconciliation.

2 CFR 200.334 generally requires financial and supporting records to be retained for three years from submission of the final financial report (for a recipient) or, for a subrecipient, from submission to the pass-through entity. For awards renewed quarterly or annually, the period generally runs from the applicable report. The section extends or changes that timing for litigation, claims, audits, written notices, real property/equipment, records transferred to the Government, indirect-cost proposals, and certain program-income transactions. State law, the award, tax rules, insurance, litigation holds, or organizational policy may require longer retention. Recommendation: calculate the disposition date from the correct reporting event and suspend destruction whenever an exception applies.

Sources

• 2 CFR 200.208, Specific conditions
• 2 CFR 200.211, Information contained in a Federal award
• 2 CFR 200.302–200.303, Financial management and internal controls
• 2 CFR 200.329, Monitoring and reporting program performance
• 2 CFR 200.332, Requirements for pass-through entities
• 2 CFR 200.334, Record retention requirements

Primary authorities checked against the eCFR available August 2, 2026. This practitioner guide is not legal or accounting advice.