Cost Transfer

A cost transfer is the reassignment of an expense already posted to one sponsored project ledger to a different sponsored project (or from a non-sponsored account onto a sponsored one) after the original transaction has occurred. It is distinct from an initial charge decision made at the time an expense is incurred: a cost transfer is always a correction or reclassification made after the fact, moving a real, previously-recorded cost rather than authorizing a new one. Under the allowability and allocability standards at 2 CFR 200.403 and 200.405, every transferred cost must independently satisfy the same tests an original charge would -- necessary, reasonable, allocable to the receiving award in proportion to the benefit it provides, and consistently treated -- a transfer does not get a lower bar just because the underlying expense was legitimate somewhere. Most research institutions require transfers to be processed within a defined window, commonly 90 calendar days from the date the original charge posted, submitted with documentation specific enough that an independent reviewer, such as an auditor, could understand how the error occurred and confirm the new charge is correct -- a generic note that a transfer corrects "a posting error" or moves a cost "to the correct project" does not meet that bar on its own.

ByCASRAI Editorial Board

· Last updated 18 Jul 2026

Worked examples

Is an instance

A lab orders a reagent and charges it to Grant A by mistake because the wrong project number was on the purchase requisition. Three weeks later, the lab manager reconciles the monthly ledger, catches the error, and processes a cost transfer moving the charge to Grant B -- the project it actually supported -- with a memo explaining the requisition error and a chart showing which experiment used the reagent.

Is an instance

A postdoc splits her effort 60% on Grant A and 40% on Grant B for a semester, but payroll initially charged 100% of her salary to Grant A. After the semester's effort report is certified and shows the actual 60/40 split, the department processes a salary cost transfer moving 40% of that period's salary cost from Grant A to Grant B, attaching the certified effort report as supporting documentation.

Looks similar, but isn't

Not an instance

Moving an overspent balance on Grant A (which is ending in two weeks) onto Grant B (which still has unspent balance and a year of performance left) purely to avoid returning unspent funds or absorbing an overrun, with no underlying error and no benefit Grant B actually received from the original expense -- this is not a legitimate cost transfer, it is exactly the pattern (a "cost transfer used to cure an overrun") federal auditors and institutional internal-audit offices are specifically trained to flag, because the receiving award never actually benefited from the cost, which fails the allocability test at 2 CFR 200.405 regardless of how the paperwork is worded.

A cost transfer is the movement of an expense from one sponsored project’s ledger to another — or from a non-sponsored (e.g., departmental or discretionary) account onto a sponsored one — after the original transaction has already posted. The defining feature is timing: a cost transfer is always retroactive, correcting where a real cost landed, rather than an initial decision about where to charge a new expense. Common categories include non-personnel cost transfers (supplies, equipment, travel charged to the wrong award or project period), salary/effort cost transfers (payroll redistributed to match a certified effort report), and transfers correcting a clerical or system-generated posting error.

Why cost transfers are subject to institutional policy limits

Because a cost transfer moves money after the fact, without the natural checkpoints (budget review, purchase approval) that govern an original charge, institutions and federal cognizant agencies treat transfers as a higher-scrutiny category by default. The near-universal control mechanism is a timing window — commonly 90 calendar days from the date the original charge posted to the sponsored ledger — within which a transfer is considered routine, and beyond which it is treated as late and requires additional written justification, often including sign-off from a departmental research administrator or the sponsored-programs office rather than the PI alone. This 90-day convention traces to NIH Grants Policy Statement language and has been adopted, in similar or identical form, by most U.S. research universities’ own cost-transfer policies, independent of any single federal regulation mandating that specific number; institutions set the exact window and escalation requirements in their own policy, and it can vary.

The underlying federal requirement that gives the policy its teeth is not a timing rule at all — it is the allowability and allocability standard in the Uniform Guidance. 2 CFR 200.403 requires every cost charged to a federal award, including a transferred one, to be necessary, reasonable, allocable, and consistently treated; 2 CFR 200.405 requires it to be assignable to the award in proportion to the relative benefit received. A transfer that fails either test is not cured by good paperwork — and a transfer processed quickly but without a real benefit to the receiving award is exactly as unallowable as one processed late.

What a defensible justification actually contains

Institutional policies converge on broadly the same required elements for a cost-transfer justification, regardless of exact wording:

What happened — a specific, factual explanation of how the original charge ended up on the wrong account (e.g., wrong project number entered on a requisition, a payroll distribution not updated after an effort change), not a generic statement that the transfer “corrects an error.”
Why the receiving award is the correct one — evidence the cost genuinely benefited the project it is being moved to: which experiment used the reagent, which aim the travel supported, what percentage of actual effort the salary reflects.
Timing, if late — for transfers outside the routine window, an explanation of why the delay occurred and why it does not indicate an attempt to move an overrun, plus (per most policies) a higher level of institutional sign-off than a routine transfer requires.
Certification — confirmation from a responsible official (department administrator, PI, or both, depending on institutional policy) that the explanation is accurate and the new charge is correct.

A justification that only restates that the transfer moves a cost “to the correct project” or “to fix a posting error,” without the specifics above, does not meet the standard reviewers and auditors are trained to expect — and is one of the most commonly cited deficiencies when cost transfers surface in an audit finding.

Why cost transfers are a frequent audit red flag

Cost transfers draw disproportionate audit attention, under both institutional internal-controls review and federal oversight (including under a Single Audit), for a specific, well-documented reason: a transfer is the easiest mechanism available to move a cost off an award for a reason that has nothing to do with where the cost actually belongs. The pattern federal reviewers are specifically trained to look for is a transfer used to “clean up” an award nearing its end date — moving an overspent charge from an award that is about to close onto a different award that still has unspent balance, where the receiving award received no actual benefit from the original expense. This fails the allocability standard outright, regardless of how the justification is worded, and repeated or systemic instances of it are a classic driver of a qualified or adverse audit finding, and in more serious cases have supported False Claims Act exposure where the pattern was knowing and repeated.

Salary cost transfers carry their own layer of scrutiny because they interact directly with effort reporting: a salary transfer that is not reconciled against the individual’s certified effort risks charging a federal award for work that was not, in fact, performed on that project during that period. Institutions commonly require salary transfers to reference the underlying effort report or a subsequent effort certification, and treat late salary transfers — especially ones made just before an award’s close-out or just after an effort-reporting period is certified in a way inconsistent with the transfer — as a heightened-scrutiny category within an already heightened-scrutiny category.

How this differs from related concepts

A cost transfer is not the same as indirect cost recovery (a separate, formula-driven allocation of F&A costs, not a discretionary correction of a specific direct charge) and it is not the same as a rebudgeting request (which reallocates unspent budget authority between categories going forward, not an already-incurred cost). It is also distinct from routine payroll distribution changes made prospectively, before a cost has posted — once the charge has posted to the sponsored ledger, any subsequent correction is a cost transfer and falls under the institution’s cost-transfer policy, not ordinary budget administration.

Use in your systems

JATS XML <role> element

xml

<role vocab="credit"
      vocab-identifier="https://casrai.org/dictionary/"
      vocab-term="Cost Transfer"
      vocab-term-identifier="https://casrai.org/dictionary/term/cost-transfer" />

Schema.org DefinedTerm (JSON-LD)

json

{
  "@context": "https://schema.org",
  "@type": "DefinedTerm",
  "@id": "https://casrai.org/dictionary/term/cost-transfer",
  "name": "Cost Transfer",
  "identifier": "https://casrai.org/dictionary/term/cost-transfer",
  "description": "A cost transfer is the reassignment of an expense already posted to one sponsored project ledger to a different sponsored project (or from a non-sponsored account onto a sponsored one) after the original transaction has occurred. It is distinct from an initial charge decision made at the time an expense is incurred: a cost transfer is always a correction or reclassification made after the fact, moving a real, previously-recorded cost rather than authorizing a new one. Under the allowability and allocability standards at 2 CFR 200.403 and 200.405, every transferred cost must independently satisfy the same tests an original charge would -- necessary, reasonable, allocable to the receiving award in proportion to the benefit it provides, and consistently treated -- a transfer does not get a lower bar just because the underlying expense was legitimate somewhere. Most research institutions require transfers to be processed within a defined window, commonly 90 calendar days from the date the original charge posted, submitted with documentation specific enough that an independent reviewer, such as an auditor, could understand how the error occurred and confirm the new charge is correct -- a generic note that a transfer corrects \"a posting error\" or moves a cost \"to the correct project\" does not meet that bar on its own.",
  "inDefinedTermSet": "https://casrai.org/dictionary/domain/compliance-regulatory#set",
  "url": "https://casrai.org/dictionary/term/cost-transfer",
  "sameAs": [],
  "license": "https://creativecommons.org/licenses/by/4.0/",
  "publisher": {
    "@id": "https://casrai.org/#organization"
  },
  "dateModified": "2026-07-18T03:33:31",
  "inLanguage": "en"
}