RGCI - What Government Contractors Need to Know When Using QuickBooks Data for Incurred Cost Submission

Incurred cost submission preparation often exposes problems that never surfaced during regular monthly accounting. A contractor can have a full year of QuickBooks data, a complete set of financial statements, and detailed job cost records, and still find that the information is not organized or consistent enough to support the annual submission process cleanly.

This is not an uncommon situation, and it matters most for contractors performing cost reimbursable work. The assumption that recorded data equals ready data is a costly misunderstanding in government contractor accounting.

Having Data in QuickBooks Is Not the Same as Being Ready to Use It

QuickBooks can hold a significant amount of accounting information. The question is not whether the transactions are in the system. The question is whether those transactions were recorded, classified, and maintained in a manner that holds up during submission preparation.

Routine bookkeeping and incurred cost submission support are not the same activity. Monthly accounting keeps the books current and produces financial statements. An incurred cost submission requires costs to be organized, indirect pools to be clearly explained, labor records to reconcile with accounting data, and documentation that supports how costs were treated throughout the year.

The gaps between those two things often go unnoticed until someone sits down to start pulling the submission together. At that point, the problems have usually been accumulating for months.

The Accounting Should Be Done Throughout the Year

Year-end submission work does not start in the final weeks before a deadline. The quality of that process is built or undermined by decisions made throughout the fiscal year.

When costs are classified one way in one quarter and a different way in the next, reconciling those differences at year end takes time and creates inconsistency. When indirect cost pools are not maintained with discipline, the rate calculations that depend on them become harder to support. When labor records are tracked separately from accounting records without a reliable reconciliation process, aligning them later is more difficult.

Minor errors or inconsistencies that seem manageable during the year tend to compound. By the time submission preparation begins, what started as a small discrepancy in account usage can require significant work to unwind. And when the team has been relying on manual fixes throughout the year to compensate for structural gaps in the system, those fixes become part of the problem rather than part of the solution.

Where Contractors Run into the Most Trouble

Some of the most common friction points are recognizable across many contractor situations, even if they show up in different forms.

When direct, indirect, and unallowable costs are not clearly separated in the chart of accounts, identifying and grouping them at year end becomes a manual exercise. The same data that should flow naturally into submission schedules instead requires significant effort to sort and verify.

When the account structure is too broad or does not reflect how costs should be reviewed, pulling reports by meaningful categories is harder than it should be. Totals may be available, but the breakdowns behind them require additional work to produce.

When contract and project level detail is incomplete or recorded inconsistently, supporting direct cost analysis across jobs becomes unreliable. A contractor may know what was spent in total but struggle to defend how it was allocated.

When labor records and accounting records have been maintained in parallel without regular reconciliation, bringing them together at year end is a project of its own. Timekeeping data and payroll entries need to tell the same story, and when they do not, figuring out why takes time.

And when spreadsheets carry too much of the analytical burden because the system structure isn't built to handle it, the support trail gets harder to follow. Manual regrouping and offline adjustments can accomplish the immediate goal, but they also make the underlying records harder to explain.

Why Indirect Rates and Cost Consistency Are So Central

One of the most demanding parts of incurred cost submission is demonstrating that indirect costs were accumulated, allocated, and treated consistently throughout the year. That is not something that can be assembled quickly from a disorganized base.

Indirect rate support depends on having costs in the right pools and applying them through a structure that can be explained and defended. When account usage has shifted during the year, when certain costs were recorded in different places at different times, or when unallowable costs were not consistently identified and separated, the analysis required to build credible rate support becomes substantially more difficult.

Unallowable cost treatment is particularly sensitive. These costs need to be identifiable, consistently handled, and clearly distinguished from the costs that support billing. A structure that does not make this easy creates risk throughout the year and concentrated effort at year end.

Cleanup at the End Is Not a Strategy

There is a tendency to treat year end as the right time to address problems that accumulated over the prior twelve months, but the difficulty comes when the cleanup is substantial, and the team is working against a deadline.

Last minute corrections are time consuming. They introduce additional opportunities for inconsistency. They make it harder to maintain a clean support trail because changes are happening quickly and in multiple places. And when the same cleanup happens every year, that is a signal that something in the underlying process or structure is not working, not that the team is managing the situation well.

Recurring year end strain usually reflects a structural issue that should be addressed earlier. It is also worth noting that corrections made under time pressure carry more risk than corrections made thoughtfully during the year, when there is more opportunity to verify that changes are accurate and complete.

Questions Worth Asking Before Preparation Begins

Before submission preparation starts, the following questions are worth working through honestly:

  • Does the current account structure support the way costs need to be reviewed and grouped for year-end analysis, or will significant regrouping be required?
  • Can direct, indirect, and unallowable cost activity be clearly identified from the records as they exist, without relying on offline calculations or manual categorization?
  • Are contract and project records consistent enough to support a detailed review of direct costs by job?
  • Has the accounting team been monitoring data quality throughout the year, or is the year end process the first time anyone is looking closely at how things were recorded?
  • How much of the analytical work is happening outside the system, and what does that say about whether the system is carrying the right burden?

These are not questions with obvious or comfortable answers for every contractor. But asking them before preparation is underway gives the team time to address what they find. Asking them after the deadline is already closed does not.

What Submission Difficulty Often Signals About the Broader Situation

When preparing incurred cost submissions consistently creates significant difficulty, the issue is rarely just the submission itself. The annual process tends to reflect how well the accounting system is structured, how consistently it has been maintained, and whether it is genuinely suited to the demands of the contracting environment in which the company operates.

A contractor that struggles each year to produce clean, organized cost support from QuickBooks may be dealing with a chart of accounts that was not built with government contracting in mind, processes that have drifted over time, or a system that has outgrown the company's current contract complexity. The submission deadline makes those issues visible, but it does not create them.

Addressing recurring difficulty at its source, whether that means improving structure, strengthening internal processes, or evaluating whether the current system still fits, tends to produce better results than working harder at year end to compensate for a foundation that was not built for this kind of work.

The Work Happens All Year

Incurred cost submissions are an annual requirement, but they are not an annual problem. For government contractors using QuickBooks, submission readiness is built or undermined by the accounting decisions made throughout the entire fiscal year.

The contractors who move through the annual submission process most efficiently are generally those who have kept their records organized and consistent from the start, maintained their indirect cost structures with discipline, and reviewed their data quality regularly rather than only when a deadline creates urgency.

The harder part of submission preparation is rarely finding the data. It is being able to trust it, organize it, and explain it, and that work cannot be compressed into the weeks before a submission is due.

Building Submission Readiness Before the Deadline

Redstone GCI works with government contractors throughout the year to help ensure accounting data can support incurred cost submission requirements when preparation begins. This includes evaluating the chart of accounts structures, helping contractors properly segregate direct, indirect, and unallowable costs, aligning labor, payroll, and accounting processes, reviewing contract requirements that affect cost treatment, and training accounting teams on government contracting cost principles and documentation expectations. By addressing these areas before year end, contractors are often better positioned to produce consistent indirect rate support, reconcile labor and accounting records more efficiently, and reduce the amount of manual cleanup required during incurred cost submission preparation.

Written by Dylan McMurrey

Dylan McMurrey Dylan McMurrey is a Senior Managing Consultant in Redstone Government Consulting’s Collaborative Accounting Solutions Group, where he provides strategic accounting support, government contractor-specific reporting, and financial system optimization. With experience spanning public accounting, financial management, and compliance, Dylan offers a comprehensive approach to accounting solutions that helps government contractors navigate complex financial environments. His expertise in account reconciliations, project analysis, revenue recognition, and software implementations allows him to support clients in streamlining processes and improving operational efficiency. Dylan began his career in the banking industry, supporting financial operations and developing a strong foundation in accounting systems and reconciliations. He later transitioned into public accounting, where he gained extensive experience in financial reporting, tax preparation, attestation services, and compliance for various industries, including government contracting. His background in managing financial closes, payroll and sales tax compliance, and financial analysis gives him a well-rounded perspective on the unique challenges government contractors face. Before joining Redstone GCI, Dylan held roles in accounting and financial consulting, where he was responsible for monthly and annual financial closes, accounts payable and receivable, tax filings, and developing financial models to support budgeting and forecasting. His expertise extends to accounting software solutions, where he has supported clients using multiple accounting software packages. At Redstone GCI, Dylan plays a key role in collaborative accounting support, assisting government contractors with monthly accounting and reporting activities, financial system implementations, and process improvement initiatives. He also supports Redstone GCI’s compliance and software implementation teams, leveraging his experience to assist clients in DCAA-compliant system set-up, including supporting policies. Dylan’s strong technical background, problem-solving skills, and commitment to client success make him a trusted resource for government contractors seeking to enhance financial operations and maintain compliance with confidence.

About Redstone GCI

Redstone GCI is a consulting firm focused on fulfilling the needs of government contractors in all areas of compliance. With a singular mission to help contractors through the multiple layers of “red tape,” we allow contractors to focus on what they do best – support their mission with the U.S. Government. We are home to a group of consultants made up of GovCon industry professionals, CPAs, attorneys, and retired government audit and acquisition professionals.

Our focus and knowledge of audit and compliance functions administered by DCAA and DCMA will always be at the heart of what we do. However, for the past decade, we’ve strategically grown to support other areas of the government contractor back-office with that same level of focus and expertise. We’ve added expertise in contracts management, subcontract administration, proposal pricing, various software systems, HR and employment law, property administration, manufacturing, data analytics/reporting, Grant specialists, M&A, and many other areas. When we see a trend in the needs of contractors, we act to ensure we can provide the best expertise in the market to fulfill those needs.

One thing our clients can be certain of is that with the Redstone GCI Team in your corner, there is no problem too big and no issue too technical for our team to tackle.

Topics: Accounting System Compliance, Incurred Cost Proposal Submission (ICP/ICE), Small Business Compliance, Quickbooks