Review a Federal Drawdown Before Request

Federal cash requests should be boring. That is the goal. A clean drawdown packet shows why the amount was needed, which costs it paid, and who checked the request before cash moved.

The rule behind the work is simple. Under 2 CFR 200.305, advance payments must be limited to the minimum cash needed. They also need to be timed close to the actual spending. That means a drawdown is not a reserve fund. It is a cash request tied to real award costs.

This workflow helps a grants manager and finance reviewer avoid weak draws. It also makes the next SF-425 report easier because cash, spending, and support already agree.

Step 1: name the cash need

Start with the reason for the draw. Do not begin with the remaining award balance. Begin with costs.

List the items that need payment or reimbursement. This may include payroll, fringe, vendor invoices, travel, supplies, approved indirect costs, or costs already paid from operating cash.

For each line, note the vendor or payroll period, amount, grant, budget category, and planned payment date. If the request covers already paid costs, note the bank date or check date.

This keeps the request tied to cash need instead of a round number.

Step 2: confirm the cost can be charged

Check each cost against the award file. The cost should be within the period of performance. It should fit the approved budget or an approved budget revision. It should also meet the basic allowability test in 2 CFR 200.403.

Ask these questions:

• Was the cost needed for the award?
• Was it posted to the right grant?
• Is the amount supported?
• Did the cost happen during the award period?
• Does the award need prior approval for this item?

If one line fails, remove it from the draw. Fix the coding or get approval before cash is requested.

Step 3: check cash already on hand

A drawdown should not create extra federal cash in the bank. Compare the requested amount to cash already received for the award and costs already paid.

If prior federal cash remains on hand, reduce the draw. If the award is reimbursement based, confirm the costs have already been paid or meet the agency’s reimbursement rules.

Keep this cash check in the packet. Auditors often ask why the organization requested that exact amount on that exact date.

Step 4: reconcile to the ledger

Pull current ledger detail by award and budget line. The draw worksheet should agree to posted costs or approved payables. If a cost is not posted yet, include the invoice or payroll support and note when it will post.

Do not rely on a side spreadsheet alone. The spreadsheet can help explain the request, but the ledger is the accounting record.

If the ledger and worksheet do not agree, stop. Find the difference before submitting. It is easier to fix a coding issue before the draw than after the quarterly report.

Step 5: get a separate review

The preparer should not be the only person who checks the request. A reviewer should compare the worksheet, support, award budget, and cash calculation.

The approval can be simple. Use a dated email, system approval, or signed checklist. It should show who reviewed the draw, what amount they approved, and when.

Small teams may not have many people. Even then, use some separation. The person entering the draw can prepare the packet. A finance lead or executive director can review the support.

Step 6: save the full packet

Save the worksheet, ledger detail, invoices or payroll support, cash balance check, reviewer approval, payment system receipt, and bank deposit record. Put them in the grant file.

Use the same file naming pattern each time. For example: award, date, draw number, and amount.

This helps later when you build a grant documentation file or explain a cash line on the SF-425.

Review signs before submission

A good review should slow down on odd patterns. Round numbers deserve a second look. So do draws that match the remaining budget, draws requested far before payroll or vendor payment, and draws that include costs from more than one reporting period.

Also compare the request to recent draw history. If the last draw left cash unused, write down why the new request is still needed. If spending is speeding up near the end of the award, check whether costs are inside the period of performance and supported by real activity.

The reviewer should also look for split costs. Shared payroll, shared rent, shared software, and shared supplies need a clear allocation basis. If the allocation support is not ready, keep that part out of the draw until it is.

After cash arrives

The review does not end at submission. Match the deposit to the request and the bank record. Then confirm the cash was used for the costs in the packet. If the cash sits longer than expected, document why and reduce the next draw if needed.

This small after-the-fact check closes the loop between request, receipt, and use.

How GrantPipe helps

GrantPipe can keep award budgets, ledger notes, draw support, and report deadlines tied to one grant record. The value is simple: the draw request does not sit apart from the proof that supports it.