Cost transfers can happen in any SBIR/STTR or federal award accounting system.

 

A payroll entry may be posted to the wrong project. A vendor invoice may be coded to the wrong award. A consultant cost may be charged to the wrong budget category. A founder’s time may be split incorrectly. A credit card transaction may be assigned to the wrong project code during month-end close.

 

Some cost transfers are legitimate corrections.

 

But cost transfers can also create compliance risk when they are late, frequent, poorly documented, unsupported, or used to move costs because one project has remaining budget.

For SBIR/STTR awardees, the question is not only whether a cost transfer can be made. The question is whether the correction is timely, documented, approved, and tied to the actual project or award that benefited from the cost.

 

At Peter Witts CPA PC, we help SBIR/STTR companies review cost transfer support so accounting corrections are documented before they become drawdown, invoice, reporting, or audit readiness problems.

 

What Is a Cost Transfer?

 

A cost transfer is an accounting correction that moves a cost from one account, project, award, cost category, or cost objective to another.

 

A cost transfer may move a cost:

• From one federal award to another

• From one project code to another

• From a general business account to an award

• From an award to a non-award project

• From direct costs to indirect costs

• From indirect costs to direct costs

• From one budget category to another

• From an unallowable account to a non-award account

• From an incorrect payroll allocation to the correct labor distribution

The transfer may be necessary because the original entry was wrong.

 

But every transfer should answer one basic question:

 

Why does the corrected destination benefit from this cost?

 

Why Cost Transfers Matter for SBIR/STTR Awardees

 

SBIR/STTR companies often operate quickly.

 

Founders may be managing technical work, payroll, consultants, agency reporting, customer activity, investor discussions, and internal R&D at the same time.

 

That pace can lead to coding mistakes.

 

Cost transfers matter because they affect:

• General ledger accuracy

• Project costing

• Payroll and labor distribution

• Budget-to-actual reports

• Drawdowns

• Invoices and vouchers

• Indirect rate calculations

• Unallowable cost tracking

• Financial reports

• Closeout records

• Agency or DCAA-related review

A single correction may be small. A pattern of corrections can suggest that the accounting system is not controlling costs properly.

 

Cost Transfers Are Not Automatically a Problem

 

A cost transfer is not always a red flag.

 

Corrections may be needed when:

• A transaction was coded to the wrong project

• Payroll was assigned to the wrong award

• A vendor invoice was posted before the correct project code was available

• A consultant invoice was split incorrectly

• A cost was originally coded to a holding account

• A credit or refund was applied to the wrong account

• A budget category was corrected after review

• An entry was posted to direct costs but should have been indirect

• A cost was charged to an award but later determined to be non-award

The issue is whether the correction is supported.

 

A well-documented transfer made promptly can help clean up the records.

 

An unsupported transfer made late can create review risk.

 

Why Cost Transfers Become Compliance Risk

 

Cost transfers become risky when they appear to be used for convenience instead of correction.

 

Warning signs include:

• Transfers made long after the original cost was incurred

• Transfers made near the end of the award

• Transfers that move costs into an award with remaining funds

• Transfers that move costs out of an overspent project

• Transfers with vague explanations

• Transfers with no approval

• Transfers that lack supporting documentation

• Transfers that affect drawdowns or invoices but are not reconciled

• Transfers that move costs across different federal awards

• Transfers that change direct and indirect treatment without rationale

• Transfers that happen repeatedly for the same type of cost

2 CFR 200.405 states that a cost allocable to a particular federal award may not be charged to other federal awards to overcome funding deficiencies, avoid restrictions, or for other reasons.

 

That is the core risk.

 

Costs should follow benefit, not budget availability.

 

Start With Allocability

 

Before making a cost transfer, ask whether the cost is allocable to the corrected award or project.

 

A cost is allocable when it benefits the award, project, or activity being charged.

 

The transfer should not be based on:

• Which award has remaining funds

• Which budget category is underspent

• Which project can absorb the cost

• Which report needs to look better

• Which drawdown needs support

• Which invoice needs more cost

• Which project is easier to explain

The transfer should be based on actual benefit.

 

If the corrected project did not benefit from the cost, the transfer should not be made to that project.

 

Review the Original Charge

 

Every cost transfer should begin with the original entry.

 

Review:

• Original transaction date

• Original vendor, employee, or payee

• Original amount

• Original account

• Original project code

• Original budget category

• Original invoice or payroll record

• Original approval

• Original documentation

• Original drawdown or invoice impact

The company should understand how the cost was first recorded before deciding how to correct it.

 

Review the Corrected Charge

 

Next, review the proposed corrected destination.

 

Confirm:

• Correct project or award

• Correct account

• Correct budget category

• Correct period of performance

• Correct direct or indirect treatment

• Correct unallowable or non-award treatment, if applicable

• Correct labor distribution, if payroll-related

• Correct impact on drawdowns, invoices, or reports

The corrected charge should be supported by the award terms, approved budget, accounting policy, and underlying documentation.

 

Document the Reason for the Transfer

 

A cost transfer explanation should be specific.

 

Weak explanations include:

• “Correction”

• “Reclass”

• “Budget adjustment”

• “Move to grant”

• “Fix coding”

• “Clean up”

• “Per management”

• “To match budget”

Stronger explanations answer:

• What was wrong with the original charge?

• How was the error discovered?

• Why is the new project or account correct?

• How did the corrected award or activity benefit?

• What documentation supports the correction?

• Who reviewed and approved the transfer?

• Does the transfer affect prior drawdowns, invoices, or reports?

The explanation should allow someone outside the company to understand the correction.

 

Timing Matters

 

Timing is a major factor in cost transfer risk.

 

NIH says cost transfers to NIH grants that correct clerical or bookkeeping errors should generally be accomplished within 90 days of when the error was discovered, and recipients must maintain documentation and make it available for audit or review.

 

Even when a specific agency rule does not use the same timeframe, the principle is useful.

 

Corrections should be made promptly after the error is discovered.

 

Late transfers may raise questions such as:

• Why was the error not found earlier?

• Was monthly review happening?

• Was the transfer made to spend down funds?

• Did the cost already support a drawdown or invoice?

• Were financial reports already submitted?

• Did the correction affect closeout?

The longer a correction waits, the stronger the documentation should be.

 

Approval Matters

 

Cost transfers should not be made casually.

 

The company should define who can request, review, and approve transfers.

 

Approval may involve:

• Project lead

• Principal investigator

• Finance lead

• Controller or accountant

• Founder or executive

• Grants administrator

• Compliance advisor

• Subaward manager, if applicable

Approval should confirm that the cost belongs to the corrected project or account.

 

The person approving the transfer should understand the technical or business reason for the correction, not just the accounting entry.

 

Tie Transfers to Actual Benefit

 

A cost transfer should explain the benefit received by the corrected award or activity.

 

For example:

• A vendor invoice was coded to Phase I, but the supplies were used for Phase II prototype testing.

• A payroll allocation was posted to the wrong project code, but timesheets show the employee worked on the NIH award.

• A consultant invoice was coded to general R&D, but the agreement and deliverables support the DOE award.

• A travel cost was charged to the wrong project, but the trip agenda and report show it supported the approved award work.

• A software cost was charged directly to one award, but usage records show it benefited several projects and should be allocated or treated as indirect.

The benefit rationale is what separates a supported correction from a budget-driven reclassification.

 

Payroll Cost Transfers Need Extra Care

 

Payroll cost transfers can receive close attention because labor is often one of the largest SBIR/STTR cost categories.

 

Before transferring payroll costs, review:

• Timesheets

• Payroll registers

• Labor distribution reports

• Employee project codes

• Pay period

• Direct labor classification

• Indirect labor classification

• Founder time

• Supervisor approval

• General ledger posting

• Budget-to-actual impact

• Drawdown or invoice impact

DCAA’s pre-award checklist considers whether the accounting system identifies employee labor by cost objective and distributes direct and indirect labor appropriately.

 

If payroll transfers are frequent, the company may need to improve timekeeping, payroll coding, or labor distribution procedures.

 

Founder Time Transfers Need Extra Care

 

Founder time can be especially sensitive.

 

A founder may work on award-funded technical tasks, fundraising, investor conversations, commercial product work, customer pilots, hiring, general management, and internal R&D in the same period.

 

Before transferring founder compensation to a federal award, confirm:

• The founder’s approved role

• Actual work performed

• Timesheets

• Payroll records

• Labor distribution

• Award scope

• Direct versus indirect treatment

• Fundraising time separated

• Commercialization time separated

• Customer work separated

• Internal R&D separated

• Approval and explanation

Founder compensation should not be moved onto an award simply because the award has budget remaining.

 

Vendor Cost Transfers Need Invoice Support

 

Vendor costs should not be transferred without documentation.

 

Before moving a vendor cost, review:

• Vendor invoice

• Purchase approval

• Receipt or proof of delivery

• Project purpose

• Budget category

• Payment record

• Original coding

• Corrected project code

• Explanation of benefit

• Prior approval, if required

A credit card charge alone may not be enough.

 

The transfer file should show what was purchased, why it was needed, and which award or project benefited.

 

Consultant Cost Transfers Need Scope Support

 

Consultant costs often require more than an invoice.

 

Before transferring consultant costs, review:

• Consultant agreement

• Scope of work

• Approved budget reference

• Deliverables

• Dates of service

• Invoice detail

• Rate support

• Payment records

• Project purpose

• Original project code

• Corrected project code

If the consultant work supported multiple activities, the cost may need allocation instead of being moved fully to one award.

 

Subaward Cost Transfers Need Partner Review

 

Subaward or subcontract costs can affect reporting, monitoring, and closeout.

 

Before transferring partner costs, review:

• Subaward agreement

• Partner budget

• Scope of work

• Invoice detail

• Deliverables

• Payment records

• Monitoring notes

• Period of performance

• Prior approval terms

• Reporting impact

If a partner invoice was charged to the wrong award or category, the correction should be documented before it affects drawdowns, invoices, or financial reports.

 

Direct and Indirect Reclassifications Need Rationale

 

Some transfers move costs between direct and indirect categories.

 

These transfers need careful review.

 

A cost should not be direct on one award and indirect in similar circumstances without a clear reason.

 

2 CFR 200.403 states that a cost must not be assigned to a federal award as a direct cost if another cost incurred for the same purpose in like circumstances has been allocated to the award as an indirect cost.

 

Before reclassifying direct and indirect costs, review:

• Company accounting policy

• Cost purpose

• Benefit received

• Like-circumstance treatment

• Indirect rate impact

• Budget impact

• Drawdown or invoice impact

• Documentation support

Changing classification only to improve budget position can create risk.

 

Unallowable Cost Transfers Need Careful Handling

 

Sometimes costs are transferred because they were identified as unallowable or non-award activity.

 

This can include:

• Fundraising

• Investor activity

• Certain lobbying

• Entertainment

• Sales activity

• Non-award commercialization

• Unsupported costs

• Personal or non-business costs

• Costs outside the period of performance

SBIR.gov explains that a good accounting system should isolate unallowable costs.

 

If a cost is moved out of an award because it is unallowable, the company should document the correction and review whether any drawdowns, invoices, reports, or indirect rate calculations were affected.

 

Cost Transfers Can Affect Drawdowns

 

For grant-funded awards, cost transfers may affect drawdowns.

 

If a cost was included in a drawdown and later transferred out of the award, the company should review:

• Whether the drawdown is still supported

• Whether cash on hand changed

• Whether a refund or adjustment is needed

• Whether PMS or payment system records need reconciliation

• Whether SF-425 or other financial reports are affected

• Whether the transfer should be disclosed or explained internally

Drawdowns should tie to supported award costs.

 

A transfer can break that connection if not reconciled.

 

Cost Transfers Can Affect Invoices and Vouchers

 

For contract-based awards, cost transfers may affect invoices or vouchers.

 

If transferred costs were already billed, review:

• Which invoice included the cost

• Whether the invoice remains accurate

• Whether a credit or adjustment is needed

• Whether the contracting office should be notified

• Whether indirect costs changed

• Whether subcontractor or consultant costs changed

• Whether the billing support file should be updated

Each invoice should continue to have complete support after the transfer.

 

Cost Transfers Can Affect Indirect Rates

 

Cost transfers can affect indirect rates when they change cost pools or allocation bases.

 

Review whether the transfer affects:

• Direct labor base

• Total direct cost base

• Fringe pool

• Overhead pool

• G&A pool

• Unallowable cost exclusions

• Commercial activity base

• Internal R&D treatment

• Provisional rates

• Actual rates

• Proposal rates

A small transfer may have a larger rate impact if it changes the base or cost pool.

 

Cost Transfers Can Affect Budget-to-Actual Reports

 

Budget-to-actual reports should be updated after transfers.

 

Review:

• Original budget category

• Corrected budget category

• Actual costs by category

• Remaining budget

• Variance explanations

• Prior approval questions

• Drawdown or invoice impact

• Reporting impact

If a transfer moves costs into a category that is already overspent or restricted, the company should review whether prior approval or additional explanation is needed.

 

Cost Transfers Near Award End Need More Scrutiny

 

Transfers near the end of an award can raise questions.

 

End-of-award transfers may appear to be:

• Spending down remaining funds

• Moving costs away from overspent categories

• Cleaning up reports before closeout

• Shifting unsupported costs

• Reclassifying costs after results are known

• Correcting issues that should have been found earlier

Some end-of-award corrections are legitimate.

 

But the later the correction, the more important the documentation.

 

The company should be able to show when the error was discovered, why it was not corrected earlier, and why the corrected charge is appropriate.

 

Frequent Transfers Signal a Process Problem

 

One cost transfer may be a normal correction.

 

Frequent transfers may signal a weak accounting process.

 

Patterns to watch include:

• Repeated payroll transfers

• Frequent project code corrections

• Multiple transfers at month-end

• Large transfers near reporting deadlines

• Transfers from commercial activity to federal awards

• Transfers between Phase I and Phase II

• Transfers from indirect to direct costs

• Transfers into awards with remaining funds

• Transfers without consistent explanations

If transfers are frequent, the company may need to fix project coding, timekeeping, chart of accounts setup, invoice review, or monthly close procedures.

 

Set a Cost Transfer Policy

 

SBIR/STTR companies should have a written cost transfer policy.

 

The policy should explain:

• When transfers are allowed

• Who can request a transfer

• What documentation is required

• How timing is reviewed

• Who approves transfers

• How benefit is documented

• How drawdowns or invoices are reviewed

• How reports are updated

• How recurring errors are addressed

The policy should make it clear that cost transfers are corrections, not a budget management tool.

 

What a Cost Transfer Support File Should Include

 

Every cost transfer should have support.

 

The file should include:

• Original transaction

• Original account

• Original project code

• Corrected account

• Corrected project code

• Amount transferred

• Date of original charge

• Date error was discovered

• Date transfer was posted

• Reason for correction

• Benefit explanation

• Supporting documentation

• Approval

• Drawdown or invoice impact

• Budget-to-actual impact

• Indirect rate impact, if applicable

This file helps the company explain the transfer during review.

 

Review Transfers Monthly

 

Cost transfers should be reviewed monthly, not only at reporting or closeout.

 

A monthly review should include:

• New transactions without project codes

• Payroll coding errors

• Vendor invoice coding

• Consultant charges

• Subaward invoices

• Direct versus indirect classification

• Unallowable costs

• Budget category errors

• Drawdown or invoice support

• Pending corrections

• Repeating error patterns

Monthly review helps corrections happen closer to the original transaction.

 

Common Cost Transfer Mistakes

 

SBIR/STTR companies often create risk when cost transfers are handled informally.

 

Common mistakes include:

• Moving costs without explaining benefit

• Using vague descriptions like “reclass”

• Making transfers long after the error was discovered

• Moving costs to use remaining budget

• Moving costs between awards without documentation

• Transferring payroll without timesheet support

• Moving founder time without activity detail

• Reclassifying direct and indirect costs inconsistently

• Not reviewing drawdown or invoice impact

• Not updating budget-to-actual reports

• Not obtaining approval

• Not retaining the original support

• Waiting until closeout to clean up records

These mistakes can turn a simple correction into a compliance issue.

 

Cost Transfer Review Checklist

 

Before posting a cost transfer, review:

• Original transaction

• Original coding

• Corrected coding

• Award or project that benefited

• Period of performance

• Approved budget category

• Supporting invoice, timesheet, or payroll record

• Reason for correction

• Date error was discovered

• Timing of correction

• Approval

• Direct versus indirect treatment

• Unallowable cost impact

• Drawdown impact

• Invoice impact

• Budget-to-actual impact

• Indirect rate impact

• Reporting impact

• Documentation file

This checklist helps determine whether the transfer is a supported correction.

 

Questions to Ask Before Moving a Cost

 

Before transferring a cost, ask:

• What was wrong with the original charge?

• When was the error discovered?

• Why is the new project or account correct?

• Which award, project, or activity benefited?

• Is the cost within the period of performance?

• Is the cost included in the approved budget?

• Is the cost allowable and allocable?

• Is the correction timely?

• Is there documentation?

• Who approved the transfer?

• Does the transfer affect a drawdown?

• Does the transfer affect an invoice?

• Does the transfer affect indirect rates?

• Does the transfer affect a submitted report?

• Would this explanation make sense during an agency or DCAA-related review?

If the answer is unclear, the transfer should be reviewed before posting.

 

Final Thoughts: Cost Transfers Need More Than a Journal Entry

 

Cost transfers can be legitimate corrections, but they should not be casual journal entries.

 

For SBIR/STTR and federal award accounting, moving costs between projects or categories requires documentation, timing, approval, and a clear reason tied to actual benefit.

 

At Peter Witts CPA PC, we help SBIR/STTR companies review cost transfer support so accounting corrections are documented, reconciled, and aligned with award requirements before they create compliance risk.

 

Need Help Reviewing Cost Transfer Support?

 

If your SBIR/STTR company has messy project coding, late corrections, payroll reclassifications, unsupported journal entries, or cost transfers affecting drawdowns, invoices, reports, or indirect rates, Peter Witts CPA PC can help.

 

Our team can review your cost transfer support, project coding, timekeeping, labor distribution, invoices, indirect rate impact, unallowable cost treatment, and documentation process.

 

Backed by 35+ years of government contract accounting experience and first-hand DCAA knowledge, we help innovators clean up award records before corrections become compliance problems.

 

Schedule a strategic consultation with Peter Witts CPA PC to review cost transfer support.