Prepare an SF-425 Quarterly Report

The SF-425 is a financial report, but it is also a control point. It tells the federal agency how much cash came in, how much was spent, what share the recipient paid, and what obligations remain.

Do not prepare it from memory. Prepare it from the award file, the ledger, drawdown records, and support for open obligations.

This workflow pairs well with a drawdown review. If every draw packet is clean, the quarterly report becomes much easier to prepare. See review a federal drawdown before request for that earlier step.

Step 1: confirm the report setup

Start with the award terms. Confirm the federal award number, recipient name, reporting period, due date, and submission system. Check whether the report is quarterly, annual, or final.

Then pull the prior SF-425. The current report should continue from the prior report unless the agency gives different instructions.

Use the Grants.gov SF-425 instructions for the line names, but also check agency terms. Some agencies add instructions for remarks, program income, or attachments.

Step 2: close the reporting period

Ask finance to confirm the ledger period is ready. Late entries can change the report. If accruals, payroll, or corrections are still open, note them before the report is drafted.

Pull ledger detail by award for the period. Also pull inception-to-date totals. The report often needs cumulative numbers, not just current quarter numbers.

Save the ledger export in the report packet.

Step 3: reconcile cash

Compare federal cash received to drawdown records and bank deposits. If the payment system shows a draw that did not reach the bank by period end, document the timing difference.

The cash lines should make sense with the drawdown record. A large cash balance should have a clear reason. If there is no clear reason, review whether the organization drew too much cash.

This is where 2 CFR 200.305 matters. Federal cash should stay close to real payment need.

Step 4: support expenditures

Tie federal expenditures to the ledger. Review any large, unusual, or late-posted costs. Make sure they are inside the period of performance and fit the approved budget.

If the report includes recipient share or match, pull match support too. Do not report match just because the budget expected it. Report what the organization can support.

If the award has program income, check the terms before reporting. Program income treatment can differ by award.

Step 5: review obligations

Unliquidated obligations are costs the organization has committed but not yet paid. They should be real, supported, and tied to the award.

Examples may include signed contracts, purchase orders, or approved payroll commitments. Do not use obligations as a way to park budget left to spend.

If obligations appear on the report, keep the support in the packet. A reviewer should be able to trace the amount.

Step 6: run a line-by-line review

Before submission, compare each SF-425 line to the worksheet. Use a second reviewer when possible.

Check these items:

• report period and award number
• cash received
• cash disbursed
• federal share of expenditures
• recipient share, if required
• program income, if any
• unliquidated obligations
• remarks
• certifying official

If a line is blank, make sure it should be blank.

Step 7: save the submission proof

After submission, save the final report, worksheet, ledger support, reviewer approval, attachments, and submission receipt.

Put the packet in the grant file by report period. This makes future reports, closeout, and audit review easier.

For closeout planning, connect this report to the federal grant reporting requirements guide and your grant documentation checklist.

Common review questions

Before the certifying official signs, ask whether the report can be explained by someone who did not prepare it. That is the practical test.

Look for jumps from the prior report. If cash, spending, recipient share, or obligations changed sharply, add a note. A sharp change can be correct, but it should not be unexplained.

Check whether reported spending agrees with award life-to-date records. If the award budget says $300,000 and the report shows $312,000 in federal spending, the file needs an explanation or correction before submission.

Also check whether the remarks field should be used. A short remark can explain timing differences, late deposits, a corrected prior report, or program income treatment. Do not use remarks to hide weak support. Use them to make a clean report easier to read.

After submission

Add the next report due date to the calendar. Note whether the agency accepted the report or asked for a change. If a change is requested, save both versions and the reason.

The next quarter should start from the accepted report, not from the draft worksheet.

How GrantPipe helps

GrantPipe can keep the reporting calendar, award terms, support files, and report status in one place. It does not replace finance review, but it helps the team avoid rebuilding the report trail each quarter.