Picture a $12 million mechanical subcontractor pursuing a $5 million single-project bonding limit to qualify for a larger job. Its surety asks for current financial statements and a supporting construction WIP schedule. The company has a profitable-looking income statement and a healthy backlog – but its internal records don’t clearly reconcile job-level costs, estimated costs to complete, billings, and gross profit. This is a hypothetical scenario built to illustrate how job-cost accounting, WIP reporting, and CPA financial statements come together for surety underwriting – not a real NexusWorks client or a documented case study. A CPA-reviewed statement does not automatically qualify a contractor for a $5 million bond; bonding decisions depend on the surety’s own underwriting criteria and the contractor’s complete financial and operating profile.
Strong annual revenue, a full backlog, and positive net income don’t, on their own, establish bonding capacity. A surety is underwriting the contractor’s ability to finance work while it’s underway – a different question than whether the company can generate revenue. The broader financial picture a surety may consider includes:
Underwriting requirements vary by company, bond type, project, and risk profile – there is no single financial threshold that applies uniformly across sureties or contractors.
A construction WIP schedule is a job-by-job report comparing contract values, costs incurred, estimated total costs, billings, and earned revenue or gross profit under the contractor’s applicable accounting method. It’s more than a list of active projects – it’s the connective layer between project-level operating information and the financial statements, and it’s usually the first thing a surety’s underwriter reviews after the statements themselves.
Fields and terminology vary by contractor, accounting method, and surety requirements. Common elements include:
Not every field is universally required, and not every contractor uses identical terminology. What matters is consistent definitions, reliable source records, and a clear cutoff date applied the same way across every job on the schedule.
An underbilling generally arises when revenue recognized to date exceeds billings to date under the applicable accounting method. Common causes include billing milestones lagging behind actual work performed, approved change orders not yet incorporated into billings, retainage or contractual billing restrictions, billing schedules misaligned with project progress, or cost and percentage-of-completion estimates that need review.
Substantial underbillings can raise legitimate questions about cash conversion, billing discipline, documentation, and collectability. But an underbilling is not automatically a loss, a particular type of receivable, or evidence of poor management – its meaning depends on the specific contract, accounting method, and underlying facts.
An overbilling generally arises when billings to date exceed revenue earned to date. Overbillings can provide a useful source of project cash flow, while also representing work or performance obligations the contractor still has to complete. A surety may assess whether the contractor has sufficient resources, cost controls, and remaining margin to finish the work its billings have already been collected against.
Not every overbilling is debt, and not every overbilling is free cash – its economic significance depends on the contract and on how the cash has actually been used across the business.
Two contractors with similar revenue can carry very different WIP profiles. One with modest, well-documented underbillings tied to normal billing lag looks very different from one with unusually large underbillings, persistent margin fade across multiple jobs, or aggressive front-loaded billing that has funded overhead rather than project costs. No single metric determines bonding capacity – sureties weigh the entire financial picture, and one unusual number is typically a prompt for more questions, not an automatic red flag.
The WIP schedule helps identify whether projects are tracking toward the margins originally bid. Key terms:
Labor productivity, material price swings, subcontractor performance, schedule delays, rework, and change-order disputes can all move estimated costs to complete – which is exactly why cost-to-complete estimates need regular, honest review rather than a year-end guess.
All figures below are illustrative only.
Line Item | Illustrative Amount |
|---|---|
Revised contract value | $2,000,000 |
Costs incurred to date | $900,000 |
Estimated cost to complete | $900,000 |
Estimated total cost | $1,800,000 |
Estimated total gross profit | $200,000 |
Estimated total gross margin | 10% |
This assumes a cost-to-cost percentage-of-completion method is appropriate and that the costs used are consistent with that method. Percent complete: $900,000 ÷ $1,800,000 = 50%. If the accounting method supports recognizing revenue on that basis, earned revenue would be $1,000,000 (50% of the $2,000,000 revised contract value).
Comparing that earned revenue to two different hypothetical billing totals shows how the same project economics can produce opposite billing positions:
These are simplified calculations for illustration, not a substitute for evaluating actual contract terms, retainage, cost eligibility, change orders, and the applicable accounting framework.
A WIP schedule is only as reliable as the underlying project records feeding it:
Incomplete cost accruals can make a project look more profitable than it actually is, and unrealistic estimates to completely distort every downstream WIP calculation. There’s a real difference between a bookkeeping cleanup, an internal management WIP report used to run the business day to day, and a financial reporting package prepared specifically for an external user like a surety, lender, or general contractor – the last of those needs a level of consistency and documentation the first two often don’t.
Contractors should confirm the specific reporting requirement directly with their surety or bond producer – the three engagement levels below provide materially different assurance, and using the wrong term for the wrong one is a common, avoidable mistake.
Engagement | Assurance Level | What the CPA Does | Typical Use |
|---|---|---|---|
Compilation (AR-C 80) | None | CPA assists management in presenting financial statements using an acceptable framework, but does not verify accuracy, test balances, or express any opinion or conclusion. | May be acceptable for some sureties, smaller bond programs, or internal/lender use |
Review (AR-C 90) | Limited assurance | CPA performs inquiry and analytical procedures and concludes whether it is aware of any material modifications needed for the statements to conform to the applicable framework. | Often requested for larger bond limits or more demanding programs |
Audit | Reasonable assurance | CPA performs audit procedures under applicable auditing standards and expresses an opinion on whether the statements are fairly presented. | May be required for some contractors or bonding programs; not universal |
A review does not include a detailed audit of every job, and the CPA does not independently verify every amount in the WIP schedule through review procedures alone. An audit provides reasonable, not absolute, assurance – it is not a guarantee against every possible misstatement. Never describe a compilation as a review, or a review as an audit; they are distinct engagements under professional standards, not points on a marketing spectrum.
How a supplementary WIP schedule is treated depends on the engagement terms, applicable professional standards, the reporting framework, and whether the schedule is presented as supplementary information accompanying the financial statements. Confirm with both the CPA and the surety:
Depending on the surety’s underwriting process, a package may include:
Not every contractor submits every item – core financial records apply broadly, while several of the above are requested only in particular cases.
☐ 1. Ask the surety or bond producer for its exact financial reporting requirements
☐ 2. Confirm the reporting date and required engagement level
☐ 3. Close the books and reconcile job-cost records
☐ 4. Review every active contract and update cost-to-complete estimates
☐ 5. Investigate significant underbillings, overbillings, and margin changes
☐ 6. Reconcile the WIP schedule to the general ledger and financial statements
☐ 7. Assemble supporting schedules and explanations
☐ 8. Allow sufficient time for CPA procedures and any necessary adjustments
☐ 9. Submit the package and respond to follow-up questions
A CPA can meaningfully improve the reliability and presentation of the financial information behind a bonding submission – but cannot guarantee a bond approval, a particular bond limit, or any specific underwriting outcome.
☐ The surety’s required reporting level is confirmed
☐ Financial statements use the requested reporting date and framework
☐ WIP covers the relevant active contracts
☐ Contract values and approved change orders are updated
☐ Costs incurred and estimated costs to complete are reviewed
☐ Gross profit and margin changes are explained
☐ Underbillings and overbillings are calculated consistently
☐ WIP totals reconcile to the accounting records
☐ Significant loss jobs and disputes are documented
☐ Supporting schedules are available
☐ The CPA has confirmed the scope of the engagement and any supplementary reporting
☐ The submission timeline accounts for CPA work and surety review
Request a Bonding-Ready Statement Quote
To help organize this process, NexusWorks put together the Contractor WIP & Bonding Readiness Pack – a practical resource, not an official surety underwriting form or a substitute for CPA advice, covering a sample WIP schedule field checklist, a job-cost and cost-to-complete review checklist, an underbilling and overbilling reconciliation worksheet, a CPA financial statement engagement comparison, a bonding-package document checklist, and questions to ask your surety or bond producer.
Construction-focused accounting and advisory support can help a contractor improve the financial information behind its WIP schedule and bonding package. That typically starts with bookkeeping and general-ledger reconciliation that job-cost reporting depends on, extends into WIP preparation support and review of estimated costs to complete and margin changes, and can include coordinating financial reporting requirements between the contractor and its surety, along with CPA financial statement services, subject to engagement acceptance and the firm’s actual service scope. Financial advisory and optimization and, for contractors managing several active jobs at once, fractional CFO support can add cash-flow visibility and planning on top of the reporting itself. For a plain explanation of how a CPA review differs from a compilation or an audit, NexusWorks has a dedicated comparison; as part of its construction industry work, the firm can help determine which level fits a given bonding situation.
This article does not claim NexusWorks has a specific construction bonding track record, formal surety partnerships, or documented client results – the focus is financial reporting readiness, not a promise about how a surety will respond. Contractors ready to discuss their reporting needs can get in touch with NexusWorks directly.
A construction work-in-progress schedule is a job-by-job report showing contract values, costs incurred, estimated total costs, billings, and earned revenue or gross profit under the contractor's applicable accounting method.
A WIP schedule connects project-level operating detail to the financial statements, helping a surety assess billing discipline, job-cost accuracy, margin trends, and the contractor's capacity to finance work already underway.
An underbilling generally occurs when revenue earned to date exceeds billings to date; an overbilling generally occurs when billings to date exceed revenue earned to date. Their significance depends on the contract, accounting method, and underlying project facts.
Not in every case. The required level of CPA financial reporting depends on the surety's underwriting criteria, the contractor's circumstances, and the bond or program involved. Confirm requirements directly with your surety or bond producer.
A compilation (AR-C 80) provides no assurance - the CPA helps present the statements but doesn't verify or opine on them. A review (AR-C 90) provides limited assurance through inquiry and analytical procedures, with the CPA concluding whether any material modifications appear needed.
