Consultants are common in SBIR/STTR projects.

 

A company may need outside technical expertise, regulatory guidance, commercialization support, testing support, engineering review, data analysis, market research, or specialized scientific input that is not available internally.

 

Consultants can strengthen a project, but they can also create post-award documentation issues when the financial terms are not clear before work begins.

 

A consultant cost may be included in the proposal, but that does not automatically mean every invoice will be easy to support after award. The company should have a clear agreement, defined scope of work, rate support, deliverables, invoice detail, payment terms, period of performance, budget limits, and documentation process.

 

At Peter Witts CPA PC, we help SBIR/STTR companies strengthen consultant cost support so consultant agreements, invoices, budgets, documentation, and award records are aligned before problems appear.

 

Why Consultant Agreements Need Financial Review

 

Consultant agreements are not just legal documents.

 

They are also financial support documents.

 

A strong consultant agreement helps answer:

• What services will the consultant provide?
• How does the work support the approved award?
• What rate will be charged?
• How was the rate determined?
• How many days or hours are expected?
• What deliverables are required?
• When will invoices be submitted?
• What detail must invoices include?
• When will payment be made?
• Is the work within the period of performance?
• Is the cost within the approved budget?
• What records must be retained?

Without clear terms, consultant costs can become difficult to support during invoicing, drawdowns, reimbursement requests, budget-to-actual reviews, agency questions, or closeout.

 

Start With the Approved Budget

 

Before any consultant begins work, review the approved budget.

 

Do not rely only on the proposal draft or an earlier planning spreadsheet. The final award may have changed, reduced, removed, or restricted consultant costs.

 

Review:

• Was the consultant included in the approved budget?
• What services were approved?
• What rate was approved?
• How many days or hours were budgeted?
• Were travel costs included?
• Was the consultant listed separately from subcontractors or subawards?
• Were agency-specific limits or restrictions included?
• Was prior approval required before work begins?
• Does the budget match the agreement?

If the consultant work is not in the approved budget, or if the scope has changed, review the award terms before signing the agreement or authorizing work.

 

Confirm the Consultant Classification

 

A consultant is not always the same as a subcontractor, subrecipient, vendor, or research partner.

 

Classification matters because it can affect budget forms, workshare requirements, indirect cost treatment, invoice review, documentation, and monitoring responsibilities.

 

SBIR.gov explains that consultants and subcontractors are different categories and that agencies using Grants.gov budget forms generally expect consultant budgets to be separated from subcontractor budgets. SBIR.gov also notes that, for SBIR, up to 33% of a Phase I project and up to 50% of a Phase II project may be subcontracted to a consultant, subcontractor, or both, while STTR requires a subcontract with a research institution.

 

Before work begins, ask:

• Is this person or organization a consultant?
• Is the work advisory or technical support?
• Is the consultant making project decisions or providing specialized input?
• Is the relationship actually a subcontract or subaward?
• Is the consultant an individual or organization?
• Does the agency require separate budget treatment?
• Does the classification affect minimum workshare requirements?
• Does the classification affect indirect costs?

The agreement should match the correct classification.

 

Define the Scope of Work Clearly

 

The consultant agreement should include a clear scope of work.

 

The scope should explain what the consultant will do and how the work supports the approved SBIR/STTR project.

 

A strong scope of work may include:

• Project name
• Award number, if available
• Technical task supported
• Specific services to be provided
• Expected deliverables
• Meetings or reviews required
• Timeline
• Responsible company contact
• Reporting expectations
• Documentation required
• Travel expectations, if any

The scope should be specific enough that someone reviewing the file later can understand why the consultant was needed.

 

A vague description such as “technical consulting” or “business advisory services” may not be enough.

 

Tie the Work to the Award Purpose

 

Consultant work should connect to the approved statement of work, budget, and project objectives.

 

Before approving the agreement, document:

• Which project task the consultant supports
• Why internal staff cannot perform the work
• How the consultant’s expertise supports the project
• Whether the work is technical, regulatory, commercialization-related, or administrative
• Whether the work is allowed under the award
• Whether the work is within the period of performance
• Whether the cost belongs directly to the award or elsewhere

This project-purpose note can be simple, but it should be saved with the agreement.

 

Review Rate Support

 

Consultant rates should be reasonable and supportable.

 

2 CFR 200.459 explains that professional and consultant service costs may be allowable when the services are reasonable in relation to the services rendered and are not contingent upon recovery of costs from the federal government. It also identifies considerations such as the nature and scope of the service, the necessity of contracting for the service, and the consultant’s qualifications.

 

Before work begins, retain support for the rate.

 

Support may include:

• Consultant proposal
• Rate sheet
• Prior invoice
• Market comparison
• Quote
• Resume or qualifications
• Explanation of specialized expertise
• Internal rate reasonableness note
• Agency budget justification
• Letter of commitment

The company should be prepared to explain why the rate is reasonable for the services provided.

 

Review Agency-Specific Consultant Requirements

 

Consultant requirements can vary by agency.

 

NSF SBIR/STTR guidance requires a signed agreement or letter of commitment from each consultant confirming the services to be provided, primary organizational affiliation, number of days committed to the research effort, availability to provide services, and consulting daily rate.

 

NIH SBIR/STTR budget instructions ask applicants to identify each consultant, the services the consultant will perform, the total number of days, travel costs, and total estimated costs.

 

Before finalizing a consultant agreement, review:

• Current solicitation
• Notice of Award
• Agency application instructions
• Award terms
• Budget justification
• Prior approval requirements
• Consultant rate limits, if applicable
• Work location restrictions, if applicable
• Travel treatment
• Documentation requirements

Do not assume that one agency’s consultant documentation rules will work for another agency.

 

Include Deliverables

 

Deliverables help support consultant costs.

 

They show what the company received in exchange for the consultant payment.

 

Deliverables may include:

• Technical memo
• Design review
• Test plan
• Data analysis
• Regulatory review
• Prototype feedback
• Market research report
• Commercialization support memo
• Meeting notes
• Presentation
• Written recommendations
• Review comments
• Training materials

If the consultant’s work is advisory, the deliverable may be a meeting summary or written recommendation. If the work is technical, the deliverable may be tied to a milestone or project file.

 

The agreement should identify what the consultant must provide before payment is approved.

 

Define Invoice Detail Before the First Invoice

 

Consultant invoices should include enough detail to support the cost.

 

Before work begins, tell the consultant what must appear on each invoice.

 

A strong consultant invoice should include:

• Consultant name
• Invoice date
• Invoice number
• Award or project name
• Period covered
• Description of services
• Dates worked
• Hours or days worked
• Rate
• Total amount
• Deliverables completed
• Travel costs, if any
• Receipts for reimbursable expenses
• Payment instructions

A one-line invoice that says “consulting services” is not enough.

 

The invoice should show what work was performed, when it was performed, and how the cost was calculated.

 

Align Payment Terms With Award Cash Flow

 

Payment terms can affect cash flow.

 

Some consultants require retainers. Others invoice monthly. Some bill by milestone. Some expect payment immediately after services are delivered.

 

Before signing, review:

• Invoice frequency
• Payment due date
• Retainer or deposit requirements
• Milestone payment terms
• Final payment conditions
• Reimbursable expense rules
• Late fees
• Termination terms
• Whether payment depends on deliverable approval
• Whether the company must pay before reimbursement or drawdown

An agreement may be technically acceptable but financially difficult if the company must pay the consultant long before award funds are received.

 

Confirm the Period of Performance

 

Consultant work should fall within the award period unless the award terms allow otherwise.

 

Before work begins, confirm:

• Award start date
• Award end date
• Consultant start date
• Consultant end date
• Whether pre-award costs are allowed
• Whether work after the award end date is allowed
• Whether closeout-related work is included
• Whether delays require agreement changes

Consultant invoices outside the period of performance may be difficult to support.

 

The agreement should not authorize work outside the period unless the company has reviewed the award terms and documented the treatment.

 

Track Budget Limits

 

Consultant costs should be monitored against the approved budget.

 

Each month, review:

• Approved consultant budget
• Consultant agreement amount
• Invoices received
• Payments made
• Remaining consultant budget
• Deliverables received
• Work remaining
• Budget variances
• Potential rebudgeting needs
• Prior approval questions

If consultant costs exceed the approved budget, the company should review whether rebudgeting or agency approval is needed before additional costs are incurred.

 

Review Consultant Travel Separately

 

Consultant travel should not be handled casually.

 

If consultant travel is allowed, the agreement should explain:

• Whether travel is permitted
• Who approves travel
• What costs are reimbursable
• Whether receipts are required
• Whether per diem applies
• Whether airfare class is limited
• Whether travel must follow company policy
• Whether foreign travel is prohibited or requires approval
• Whether travel counts toward outsourcing limits

NSF SBIR/STTR guidance notes that consultant travel should be shown under domestic travel but still counts as an outsourcing expense for determining whether the small business meets minimum level-of-effort requirements.

 

This is why consultant travel should be reviewed before expenses are incurred.

 

Separate Consultant Work From Commercialization or Fundraising

 

Consultants may support technical work, commercialization, business strategy, fundraising, sales, or investor readiness.

 

Not all of that belongs on the award.

 

NIH SBIR/STTR budget instructions state that SBIR/STTR funds cannot support commercialization activities except through TABA or Commercialization Readiness Pilot funding opportunities.

 

Before charging consultant costs to the award, ask:

• Is the consultant supporting approved R&D?
• Is the work technical or commercialization-related?
• Is it allowed under TABA, CRP, or another approved category?
• Is the work fundraising, sales, or investor-related?
• Is the work included in the approved budget?
• Is the work within the period of performance?
• Does the invoice separate award and non-award services?

If a consultant performs both award and non-award work, invoices should separate the costs.

 

Document Cost Reasonableness

 

Cost reasonableness should be documented before work begins.

 

NSF’s professional service cost resources note that professional service costs are allowable when reasonable in relation to the services rendered and not contingent upon federal cost recovery. NSF also highlights common issues such as organizations not documenting cost or price analyses before issuing professional service agreements.

 

A simple cost reasonableness file may include:

• Consultant qualifications
• Rate support
• Comparison quotes, if available
• Explanation of why the expertise is needed
• Budget justification
• Scope of work
• Internal approval
• Agency approval, if required

This does not need to be overly complicated, but it should be documented.

 

Maintain Consultant Files

 

Each consultant should have a complete support file.

 

The file may include:

• Approved budget reference
• Consultant agreement
• Scope of work
• Letter of commitment, if required
• Rate support
• Cost reasonableness note
• Deliverables
• Invoices
• Receipts for expenses
• Payment records
• Project purpose note
• Prior approval, if applicable
• Correspondence
• Budget-to-actual tracking
• Closeout notes

This file should be updated throughout the award, not only when closeout begins.

 

Review Invoices Before Payment

 

Consultant invoices should be reviewed before payment.

 

The company should confirm:

• The invoice matches the agreement
• The work falls within the period of performance
• The services support the approved award
• The rate matches the agreement
• Hours or days are reasonable
• Deliverables were received
• Travel or expenses are supported
• Budget remains available
• Prior approval was obtained, if required
• The invoice is coded correctly
• The cost is ready for drawdown, reimbursement, or invoicing support

Do not pay first and review later.

 

Consultant Costs Should Tie to the General Ledger

 

Consultant costs should be coded properly in the accounting system.

 

The company should be able to trace consultant costs from:

• Approved budget
• Agreement
• Invoice
• Payment record
• General ledger
• Project cost report
• Budget-to-actual report
• Drawdown, invoice, or reimbursement request
• Closeout file

If consultant costs are tracked only in email or spreadsheets, the company may struggle to support them later.

 

Common Consultant Agreement Mistakes

 

SBIR/STTR companies often run into problems when consultant agreements are informal.

 

Common mistakes include:

• Starting work before an agreement is signed
• Using a vague scope of work
• Not documenting the consultant’s role
• Missing rate support
• Not confirming total days or hours
• Accepting invoices with little detail
• Paying before deliverables are reviewed
• Ignoring the period of performance
• Exceeding the approved consultant budget
• Not separating consultant and subcontractor costs
• Charging commercialization or fundraising support incorrectly
• Missing consultant travel documentation
• Not reviewing prior approval requirements
• Waiting until closeout to organize records

These issues are easier to prevent before work begins.

 

Questions to Ask Before a Consultant Starts Work

 

Before authorizing consultant work under an SBIR/STTR award, ask:

• Was the consultant included in the approved budget?
• Is the person or organization properly classified as a consultant?
• What scope of work will be performed?
• How does the work support the award?
• What rate will be charged?
• Is rate support documented?
• How many days or hours are expected?
• What deliverables are required?
• What must invoices include?
• What are the payment terms?
• Is the work within the period of performance?
• Are travel costs allowed?
• Is prior approval required?
• How will the cost be coded and tracked?
• What documentation will be saved?

These questions help turn consultant costs from a weak support file into a manageable award cost.

 

Monthly Consultant Cost Review Checklist

 

Each month, review:

• Consultant invoices received
• Services performed
• Deliverables received
• Hours or days billed
• Rate used
• Travel or expense support
• Payment status
• General ledger coding
• Budget remaining
• Budget-to-actual variance
• Prior approval questions
• Documentation gaps
• Upcoming consultant work
• Closeout support

Monthly review helps prevent consultant costs from becoming a reporting or closeout issue.

 

Final Thoughts: Consultant Costs Should Be Supported Before Work Begins

 

Consultants can strengthen an SBIR/STTR project, but consultant costs need clear financial support.

 

Before work begins, the company should review the approved budget, confirm classification, define scope, document rate support, identify deliverables, set invoice detail requirements, align payment terms, confirm the period of performance, monitor budget limits, and maintain a complete support file.

 

At Peter Witts CPA PC, we help SBIR/STTR companies strengthen consultant cost support so agreements, invoices, deliverables, documentation, and award records are ready for reporting, drawdowns, reimbursement, closeout, or review.

 

Need Help Strengthening Consultant Cost Support?

 

If your company is preparing for or managing an SBIR/STTR award, Peter Witts CPA PC can help review consultant agreements, scope of work, rate support, deliverables, invoice detail, payment terms, period of performance, budget limits, documentation, and cost tracking.

 

Backed by 35+ years of government contract accounting experience and first-hand DCAA knowledge, our team helps innovators organize consultant costs before they become reporting, billing, or closeout problems.

 

Schedule a strategic consultation with Peter Witts CPA PC to strengthen consultant cost support.