A cost transfer moved within days of the original charge draws almost no scrutiny. The same transfer moved after 90 days needs extenuating circumstances and a documented corrective action, because a late correction is read as evidence the institution's controls did not catch the error when they should have.
"To correct an error" is not an acceptable justification on its own. A cost transfer has to explain how the error happened, not just that one occurred, and a transfer used to cover a budget overrun on a different project is not a correction at all. It is disallowed.
Cost transfers and budget modifications are not the same request, even though departments often use the terms interchangeably. A cost transfer corrects where a cost already posted. A budget modification changes what the institution is allowed to spend going forward, and federal awards may require the sponsor's prior approval for the second one.
A cost transfer moves an expense that already posted to one account onto a different one, and auditors treat cost transfers as one of the highest-risk categories a Single Audit samples for a specific reason: a transfer is the mechanism an institution would use, intentionally or not, to shift an unallowable or over-budget cost onto a grant with available funds. Most cost transfers are legitimate corrections of genuine posting errors. The audit risk exists because the same transaction type is also how cost-shifting abuse happens, which means every transfer has to carry documentation strong enough to distinguish the two.
Institutional cost transfer policy generally sets a 90-day window from the original transaction date, inside which a correction is treated as routine. The NIH Grants Policy Statement is explicit that a cost transfer justification stating only "to correct error" is not sufficient; the explanation has to describe how the error actually happened, and a responsible official has to certify the corrected charge is accurate. Notre Dame's own cost transfer policy documents this timing expectation directly: transfers after 90 days are allowed only under extenuating circumstances, such as a late award issuance, and require additional justification and approval precisely because a late correction signals the institution's own controls did not catch the error in time.
Before a cost transfer question even arises, the underlying cost has to clear four tests under 2 CFR 200.403 through 200.405: a cost charged to a federal award must be allowable under the award's terms, allocable to the specific project that benefits from it, reasonable in that a prudent person would agree it was necessary, and treated consistently across every funding source the institution uses. A cost transfer that moves an expense onto a grant it was never allocable to in the first place does not become allowable just because the transfer paperwork is properly filled out. The transfer can only fix the accounting. It cannot fix a cost that never belonged on that project, and retaining the documentation that proves it stays under the same three-year retention rule that governs every other award record.
The single most common reason a cost transfer draws a finding is using it to move an expense onto a grant with remaining budget simply because another project ran over. NIH policy states directly that transfers made solely to cover a cost overrun, whether on the same project's next segment or a different project entirely, are unallowable, no matter how the justification is worded. An institution under budget pressure to keep every award looking balanced has a real incentive to smooth costs across projects this way, which is exactly why auditors treat any transfer near a project's period-of-performance end date with extra scrutiny.
A cost transfer fixes where money already spent got recorded. A budget modification changes the budget itself, the amounts approved for future spending in each category. Departments often ask for one when they mean the other, and the two carry different requirements: certain budget modifications, particularly reallocations above a defined threshold between categories, need the sponsor's prior written approval before the new spending can happen, while a cost transfer is a correction to spending that already occurred and does not require that same forward-looking sponsor approval, only proper documentation.
|
Dimension |
Cost transfer |
Budget modification |
|
What it changes |
Where an expense that already posted is recorded |
What the institution is approved to spend going forward |
|
Timing expectation |
Routine within 90 days; extenuating circumstances required after |
Requested before the spending it covers occurs |
|
Sponsor approval |
Not typically required if properly documented |
May require prior written approval above defined thresholds |
|
Common audit finding |
Used to cover a cost overrun on another project |
Reallocation exceeding threshold without prior approval on file |
Whether a cost is allowable, allocable, reasonable, and consistently treated is evaluated before it posts, catching a misallocation before it ever needs a correction.
A cost transfer request shows immediately whether it falls inside or outside the routine window, consistent with the same timing discipline NIH's own policy documents, rather than requiring someone to calculate the elapsed time manually.
The workflow requires a description of how the error actually occurred and a responsible official's certification, rejecting a submission that only says "to correct error."
A request outside the 90-day window is flagged for the extenuating-circumstances justification and additional approval institutional policy requires, rather than processed the same way as a routine correction.
A request to change future spending authority routes through the sponsor prior-approval check, separate from the cost transfer path entirely.
The documentation an auditor would sample, the error explanation, the certification, the approval chain, stays attached to the transaction rather than filed separately from the record it explains.
Kissflow is the governed execution layer at the edges of the grant expenditure tracking stack. It does not replace the institution's general ledger or its grants management system as the system of record for what was actually spent. It replaces the email justification and the standalone spreadsheet that currently track whether a given cost transfer falls inside the 90-day window and whether its documentation would actually hold up under audit.
If your institution runs Banner, Workday, or a dedicated research administration system, Kissflow does not compete with any of them for the underlying ledger. It sits alongside them as the layer that enforces the allowability tests, the 90-day timing rule, and the distinction between a cost transfer and a budget modification, before either request ever reaches finance for final approval.
The differentiation that matters to a CFO: when a sponsor's specific cost transfer policy differs from the institution's default, or a new threshold applies to a particular award, the office that owns grant expenditure tracking updates the workflow directly, instead of retraining every department on an exception a general ledger was never built to flag on its own.
It refers to the general expectation, reflected in NIH and most institutional policy, that a cost transfer correcting a posting error should happen within 90 days of the original transaction. Transfers after that window require documented extenuating circumstances and additional approval.
No. The justification has to explain how the error occurred, not simply state that one occurred, and a responsible official has to certify that the corrected charge is accurate.
No. Using a transfer solely to move costs onto a grant with remaining budget because another project ran over is specifically disallowed, regardless of how the request is worded.
A cost transfer corrects where an expense that already posted is recorded. A budget modification changes what the institution is approved to spend going forward, and larger reallocations may require the sponsor's prior written approval before the new spending happens.
It has to meet four tests under the Uniform Guidance: allowable under the award's terms, allocable to the specific project, reasonable, and treated consistently across every funding source the institution uses.
No. Kissflow is the workflow layer that enforces allowability checks, tracks the 90-day cost transfer window, and routes budget modifications through the sponsor approval they require. The ledger and research administration system remain the systems of record.
Request a 30-minute walkthrough to see how Kissflow routes cost transfers and budget modifications through the documentation and timing windows a sponsor audit expects.Book a demo today.