A cost transfer moves an already-posted expense from one sponsored project’s ledger to another — or from a non-sponsored account onto a sponsored one — after the original charge has occurred. Because the transfer happens after the fact, without the budget-check or purchase-approval controls that govern an original charge, federal sponsors and institutional policies treat late transfers as a specific, named risk area. This guide covers the timing convention most institutions use, what an auditor-proof justification actually contains, and the fact patterns that turn a routine correction into an audit finding.
The 90-day convention: where it comes from and what it actually requires
The Uniform Guidance at 2 CFR Part 200 does not itself set a specific day-count deadline for cost transfers. What it requires, at 2 CFR 200.403 and 200.405, is that every cost charged to a federal award — including one that arrives via a transfer — be necessary, reasonable, and allocable to the receiving award in proportion to the benefit that award actually received, and that costs be treated consistently regardless of the funding source. Nothing in that standard gets weaker because the charge moved after the fact.
The 90-day figure that research administrators actually work against comes from a layer above the regulation: individual sponsor and institutional policy. NIH, in its Grants Policy Statement, and the large majority of US research institutions with a delegated cost-transfer policy, set an outer window — commonly 90 calendar days from the date the original charge posted — inside which a transfer is treated as routine and outside which it requires additional, specific written justification (and, at many institutions, an extra level of sign-off, such as a department chair, dean’s office, or the sponsored programs office). Some institutions use 60 or 120 days instead; the exact number is set locally, so confirm your own institution’s policy rather than assuming 90 days applies. Last verified 2026-08-16 — institutional cost-transfer windows are set by local policy and change independently of federal regulation, so re-confirm the current number against your own institution’s sponsored-programs policy before relying on it.
The window itself is not a hard legal cutoff the way, say, an award closeout deadline is — it is a control mechanism. Crossing it does not make a transfer automatically unallowable. It does mean the transfer now has to clear a higher bar of documentation, because the delay itself becomes a fact an auditor will ask about: why did it take this long to notice, and does that delay call the accuracy of the correction into question?
What “adequate justification” actually means
The single most common reason a late cost transfer draws scrutiny is not the lateness itself — it is a justification that restates the transfer instead of explaining it. A memo that says the transfer “corrects a posting error” or moves a cost “to the correct project” describes what happened, not why, and gives an independent reviewer nothing to check the correction against. An adequate justification for a late transfer needs to answer four things:
| Question an adequate justification must answer | What that looks like in practice |
|---|---|
| What was the original error, specifically? | Named cause — wrong project number on a requisition, a payroll distribution keyed before an effort report was finalized, a shared-use item split incorrectly — not “administrative error.” |
| When was it discovered, and why only then? | A dated discovery event (a ledger reconciliation, an effort-certification cycle, a subaward invoice review) that explains the gap between the original posting and the correction, not silence on the delay. |
| Why does the receiving award actually benefit? | Direct evidence the receiving project used the good or service — a notebook entry, a shipping record tied to a specific experiment, a time allocation — not just an assertion that it did. |
| Why is the transfer amount correct? | The dollar figure traces to a specific calculation (e.g., a certified effort percentage, an itemized invoice split) rather than an approximate round-number reallocation. |
Every research-administration training curriculum built around this topic — and the internal-audit and sponsor-compliance offices that review transfers — apply some version of the same test: could someone with no prior knowledge of the transaction read the justification and independently reach the same conclusion the preparer did? A justification that only makes sense to the person who wrote it fails that test even if the underlying transfer was, in fact, correct.
Worked example: a late transfer that survives scrutiny versus one that doesn’t
Passes review. A lab orders a specialized reagent in month 2 of a grant, and the purchase requisition is keyed to Grant A because it is the PI’s only active award in the ordering system at the time. In month 5, during a routine ledger reconciliation, the lab manager discovers the reagent was actually used exclusively in an experiment funded by Grant B, which started the following month. The transfer memo names the requisition-entry error, the specific reconciliation that caught it, attaches the lab notebook page showing the reagent’s use in a Grant-B-funded experiment, and transfers the exact invoiced amount. It is well past a 90-day window, but the documentation lets a reviewer independently verify every element.
Fails review. A grant is six weeks from its end date and has an unspent balance; a second grant with the same PI is nearly exhausted with a year of performance remaining. A transfer moves a round-number amount of prior non-personnel charges from the second grant onto the first, with a memo stating only that the charges were “originally miscoded.” There is no discovery event, no evidence the first grant’s project used the transferred items, and the timing — shortly before the underlying award closes — matches a pattern auditors are specifically trained to flag: a transfer used to relieve a cost overrun on one award by shifting it onto another with available balance, rather than to correct a documented error. This fails the allocability test at 2 CFR 200.405 regardless of how the memo is worded, because the receiving award did not actually benefit from the original cost.
Patterns that turn a cost transfer into an audit finding
- Transfers used to cure an overrun. Moving a cost from an award that is over budget or ending soon onto one with remaining balance, where the receiving award received no actual benefit from the original expense. This is the single most consistently cited cost-transfer finding in federal audit and Office of Inspector General reviews of research institutions.
- Repeated late transfers involving the same account, PI, or cost category. A single late transfer with a strong justification is a normal correction. A pattern of frequent late transfers — especially recurring between the same two accounts — reads to an auditor as evidence the institution’s original-charge controls are not working, which is a broader finding than any individual transfer.
- Salary/effort transfers made after certification without updated support. Moving payroll costs between awards after an effort report has already been certified, without a new or corrected certification to match, breaks the link between the effort report and the payroll ledger that federal reviewers check first.
- Justification language that restates rather than explains. Boilerplate phrases — “to correct coding error,” “moved to correct account” — with no discovery event, no named cause, and no benefit evidence.
- Transfers with no independent approval where institutional policy requires one. Most institutional policies escalate approval authority once a transfer crosses the late-transfer threshold; processing a late transfer through the same single-approver path as a routine one is itself a control gap, separate from whether the transfer was substantively correct.
None of these patterns make a transfer automatically disallowed on their own — they are the fact patterns that draw the closer look that either confirms the transfer was legitimate or turns it into a finding. The difference between the two outcomes is almost always the documentation the requester attached at the time, not anything discovered later.
A short justification checklist
- Named, specific cause of the original error (not “administrative error” or “miscoding”)
- Dated discovery event explaining why the correction is happening now
- Direct evidence the receiving award benefited from the original cost
- A transfer amount that traces to a specific calculation, not a round number
- Sign-off from whatever approval level your institution’s policy requires once the transfer is late
- No proximity to the receiving or losing award’s period-of-performance end date without an independent, documented reason
Frequently asked questions
Is there a federal regulation that sets a 90-day cost transfer deadline?
No single number is set in 2 CFR Part 200 itself. The regulation requires every charge — original or transferred — to be allowable, allocable, and reasonable under 2 CFR 200.403 and 200.405. The 90-day (or 60- or 120-day, depending on the institution) window is a policy convention set by individual sponsors and institutions as an internal control, not a Uniform Guidance requirement with that specific figure attached.
Does a late cost transfer automatically trigger an audit finding?
No. Lateness raises the documentation bar; it does not by itself make a transfer unallowable. A late transfer with a specific, verifiable justification routinely clears review. What draws a finding is the combination of lateness with weak or generic justification, or a fact pattern — like relieving an overrun near an award’s end date — that suggests the transfer wasn’t correcting a genuine error.
Who typically has to approve a late cost transfer?
This varies by institution, but many policies require an approval level above the person who processes routine transfers once a transfer crosses the late threshold — commonly a department chair, dean’s office, or the sponsored programs/research accounting office. Confirm the specific escalation path in your own institution’s policy.
How is a salary cost transfer different from a non-personnel cost transfer?
A salary cost transfer redistributes payroll costs already charged to an award, and needs to match the effort actually certified for that period; a non-personnel cost transfer moves a specific purchased good or service. Salary transfers draw particular scrutiny when they happen after an effort report has already been certified, since the payroll ledger and the certified effort record are expected to match.
For the underlying cost-allowability framework this guide builds on, see 2 CFR 200 Subpart E: The Cost Principles Governing Federal Grant Costs and Uniform Guidance (2 CFR 200): The Governing Framework for Federal Research Grants. For the payroll side of cost transfers specifically, see Effort Reporting and Payroll Certification for Federally Funded Research and the Time and Effort Reporting and Effort Certification dictionary terms. Related concepts: Cost Transfer, Allocability, Unallowable Cost, and Federal Grant Budget Mechanics: Prior Approval, Rebudgeting, and Cost Allowability.
