How your WIP report determines bonding capacity — and what to fix before your surety review
Your WIP schedule is the primary financial document surety underwriters use to set your single and aggregate bonding limits. Most WIP reports submitted to sureties are either out of date, missing required columns, or built in a spreadsheet that doesn't reconcile to the balance sheet — any of which gives underwriters a reason to hold capacity flat, even when your financials are otherwise healthy.
Key takeaways
Here is what matters most before you compare options.
What sureties actually read: The WIP schedule is the document surety underwriters weight most heavily when setting single and aggregate bonding limits — ahead of the income statement or balance sheet alone.
The reporting gap: QuickBooks Online does not produce a surety-ready WIP schedule natively, and the columns most underwriters require — estimated cost to complete, percentage of completion, and projected profit — must be calculated outside the system.
The three capacity levers: Underbilling discipline, backlog accuracy, and working capital are the three variables finance teams can actively manage to increase bonding capacity without waiting for project completions.
What monthly discipline delivers: Contractors who submit a reconciled, consistently formatted WIP schedule every month build the trend history that gives sureties the confidence to raise limits.
The software answer: Flow ERP produces multi-entity, surety-ready WIP reporting natively, while LiveFlow FP&A delivers a live WIP pack for finance teams still running QuickBooks Online and a project management platform.
How do surety underwriters use the WIP schedule to set your bonding capacity?
Surety underwriters use the WIP schedule to assess whether a contractor's backlog is manageable, margins are holding, and billing is in line with work performed. The WIP schedule — which is a job-by-job summary of contract values, costs incurred, billings, and projected profit on all active contracts — gives the underwriter a forward-looking view of financial health that the income statement alone cannot provide.
Underwriters cross-reference WIP data against financial statements to look for consistency. If the net underbilling position on the WIP schedule doesn't match the corresponding asset on the balance sheet, that's a flag. If projected margins at completion are lower than the margins the contractor bid, that signals execution risk. The WIP schedule is where these patterns surface before they show up in annual financials.
Inaccurate or infrequent WIP reporting constrains bonding capacity even when the contractor's overall financials look healthy. An underwriter who receives a WIP once a year, prepared under time pressure, has no trend data to anchor confidence. That absence of consistency limits how far they'll extend single-project limits or aggregate capacity.
What underwriters look for beyond the numbers
Trend consistency is one of the strongest qualitative signals an underwriter tracks. A contractor who submits a reconciled WIP every month, using the same format and methodology, is demonstrating internal controls — not just financial results. That consistency tells the underwriter that the numbers are being actively managed, not assembled at year-end to satisfy a requirement.
Underwriters also scrutinize whether the WIP reconciles cleanly to the balance sheet each period. A WIP that doesn't tie to the balance sheet raises questions about whether the underlying job cost data is reliable. Contractors who submit monthly and reconcile consistently give underwriters a basis for confidence that supports capacity increases.
How bonding capacity is calculated from WIP data
Most sureties calculate aggregate bonding capacity using a working capital multiplier — industry-observed ranges typically fall between 10x and 20x net working capital, though the specific factor varies by surety, contractor risk profile, and relationship history. Single-project limits are a subset of that aggregate number. For construction accounting software built for contractors, the critical connection is that the WIP schedule directly feeds the underwriter's working capital calculation: underbillings increase current assets, and overbillings increase current liabilities.
That means a WIP schedule with inaccurate billing positions doesn't just misrepresent project status — it distorts the working capital figure the underwriter multiplies to set your capacity ceiling. Getting the WIP right is not a reporting exercise; it's a capital management decision.
What columns do surety underwriters expect on a WIP schedule — and what does QuickBooks not produce natively?
A surety-ready WIP schedule must include contract value, costs incurred to date, estimated cost to complete, percentage of completion, billings to date, cost-based percentage of completion calculation, projected profit at completion, and the over/underbilling amount for each active job. QuickBooks Online produces partial job cost data natively but cannot generate the forward-looking and calculated columns that underwriters depend on without manual work outside the system. For a step-by-step look at how to create a WIP schedule in QuickBooks Online, the gap between what QBO produces and what sureties require becomes clear.
WIP schedule columns: what underwriters require vs. what QuickBooks Online produces natively | |||
WIP column name | What the column measures | Does QuickBooks Online produce this natively? | What's required to produce it |
|---|---|---|---|
Contract value | Total agreed contract price, including approved change orders | Partial | Manual update required when change orders are approved; QBO does not track contract amendments automatically |
Costs incurred to date | All costs posted to the job as of the report date | Yes | Available via job cost reports in QBO Projects; export required for WIP compilation |
Estimated cost to complete | PM's current forecast of remaining cost to finish the job | No | Manual input from PM platform or spreadsheet; QBO has no forward-looking cost field |
Percentage of completion | Costs incurred to date divided by total estimated costs | No | Manual formula combining QBO actuals and PM estimate; requires both data sources |
Billings to date | Total amounts invoiced to the owner as of the report date | Yes | Available via accounts receivable reports; export required for WIP |
Cost-based % complete calculation | Alternate POC check using cost ratio rather than billing ratio | No | Manual calculation outside QBO |
Projected profit at completion | Contract value minus total estimated cost (original and revised) | No | Manual formula; requires updated cost-to-complete from PM |
Over/underbilling amount | Difference between earned revenue (POC × contract) and billings to date | No | Manual calculation; must tie to balance sheet asset/liability lines |
When critical columns are absent or manually calculated in a spreadsheet that doesn't reconcile to the balance sheet, the underwriter draws the logical conclusion: the contractor's internal controls around job costing are not mature. That conclusion constrains capacity regardless of what the income statement shows.
Percentage of completion: why QBO can't calculate it automatically
Percentage of completion (POC) is the ratio of costs incurred to date divided by total estimated costs for each job. Calculating it accurately requires pulling actual costs from the accounting ledger and the total cost estimate from the project management platform — two data sources that live in different systems for most contractors. QBO holds one side of that equation; the PM platform holds the other.
POC is the column underwriters weight most heavily because it drives everything else: earned revenue, over/underbilling position, and projected profit at completion. A POC figure that's wrong because the cost estimate hasn't been updated is more dangerous than no WIP at all — it presents false precision on the most consequential number in the schedule.
Estimated cost to complete: the column that shows job intelligence
Estimated cost to complete is a forward-looking number that requires a judgment call from the project manager, not a figure any accounting system generates. The gap between what was estimated at contract award and what the PM now forecasts is the profit fade signal that over- and underbilling in construction ultimately creates. Underwriters read revised cost estimates as a direct indicator of field execution quality and estimating discipline.
How do underbilling, backlog, and working capital affect your bonding capacity?
Underbilling discipline, backlog size relative to working capital, and the working capital position on the balance sheet together determine how much bonding capacity a surety will extend to a contractor. These three variables are actionable between surety reviews — finance teams don't need to wait for project completions to move the needle on any of them. For context on construction cash flow management, the same financial levers that protect cash also protect bonding capacity.
Underbilling as a financial signal — not just a billing error
Chronically underbilled jobs communicate to underwriters that a contractor is financing their customers, which puts working capital at risk. Underbilling occurs when the amount earned on a contract (POC × contract value) exceeds the amount invoiced to date — meaning the contractor has done work they haven't collected on yet. A single late billing event is unremarkable. A pattern of underbilling across multiple jobs on the WIP schedule raises questions about billing discipline and PM-to-finance communication that underwriters track over time.
The financial consequence is direct: persistent underbilling suppresses current assets, which lowers net working capital, which reduces the base number the surety multiplies to set aggregate capacity. Billing promptly and accurately isn't just cash management — it's bonding capacity management.
Backlog-to-working-capital ratio: what the number tells the surety
A large backlog relative to working capital signals execution risk — the contractor may not have the liquidity to fund the work they've committed to. Backlog is the dollar value of contracted work not yet completed, and it represents future cash obligations for labor, materials, subcontractors, and overhead before collections arrive. Underwriters look at whether backlog growth is outpacing the contractor's financial capacity to perform. This ratio is not a formal GAAP metric, but it is standard in surety underwriting analysis and is read directly from the WIP schedule alongside the balance sheet.
Working capital and why it's the denominator in every capacity calculation
Working capital — current assets minus current liabilities — is the base number the surety's internal factor multiplies to arrive at aggregate bonding capacity. Industry-observed multipliers range from 10x to 20x, with the specific factor driven by the surety's risk assessment, the contractor's history, and the job types in the backlog. Underbillings increase current assets; overbillings increase current liabilities. An accurate WIP schedule directly affects the working capital figure the underwriter uses, which is why WIP accuracy is a capital allocation issue, not just a reporting one. Percentage-of-completion accounting standards set by AICPA provide the methodological framework underwriters expect contractors to follow.
What does monthly WIP discipline look like for a multi-entity general contractor?
Monthly WIP discipline means submitting a reconciled WIP schedule every 30 days, tied to the balance sheet, with consistent methodology across all entities. For a multi-entity general contractor managing three to ten legal entities, that rollup is typically done manually, inconsistently, or only when the surety asks — exactly the pattern that signals weak internal controls to underwriters. For job costing reporting for specialty trade contractors, the WIP discipline challenge compounds when each entity runs its own job cost ledger with no automated consolidation layer.
The practical close process for a surety-ready WIP looks like this:
Pull updated costs incurred to date from the accounting system for each active job, by entity.
Collect revised estimated cost to complete from the PM platform or PM sign-off for each job.
Calculate POC, projected profit, and over/underbilling for each job.
Roll up to a consolidated WIP schedule across all entities.
Reconcile the net underbilling/overbilling position to the balance sheet before submission.
Surety-ready WIP discipline and a tight month-end close are the same motion. Teams that run a clean close every month produce a surety-ready WIP as a byproduct, not as a separate workstream.
The WIP-to-balance-sheet reconciliation check
The net underbilling/overbilling position on the WIP schedule must match the corresponding line items on the balance sheet before any submission to a surety or CPA. If those numbers don't agree, the surety flags it — and so will the CPA during the annual review. Running the reconciliation check before submission takes three steps:
Sum the over/underbilling column on the WIP schedule for all active jobs. Jobs with billings exceeding earned revenue are overbilled (a current liability); jobs with earned revenue exceeding billings are underbilled (a current asset).
Compare those totals against the "costs and estimated earnings in excess of billings" and "billings in excess of costs and estimated earnings" line items on the balance sheet.
Investigate any variance — even small ones — because a mismatch means either the WIP calculation or the journal entries are wrong, and either will create a problem during CPA review or surety underwriting.
Profit fade — how to calculate it and how to explain it to your underwriter
Profit fade is the difference between the projected profit margin at contract award and the current projected margin at completion, expressed as a percentage of the original contract value. Underwriters expect some fade on complex jobs — field conditions change, material costs shift, and subcontractor performance varies. What they watch for is systematic fade across the portfolio, which signals estimating problems or execution patterns that repeat across jobs.
The calculation is straightforward: take the original projected margin percentage at award, subtract the current projected margin percentage using the updated estimated cost to complete, and note the delta. A controller presenting this to an underwriter should be prepared to attribute the cause — scope changes, labor productivity, material cost escalation, or estimating error — because the explanation matters as much as the number. An underwriter who hears "materials ran 8% over on three jobs due to lumber escalation, and we've built that into our current estimates" reads that very differently than an unexplained margin decline with no commentary.
How do you build a surety-ready WIP pack from live QuickBooks and project management data?
A surety-ready WIP pack combines live job cost data from QuickBooks Online with estimated cost to complete data from the project management platform — two systems that don't talk to each other by default. The accounting system holds the actual costs posted to date; the PM platform holds the forward-looking estimates that drive POC, projected profit, and the over/underbilling calculation. Producing a WIP schedule without both data sources current means the most important columns are wrong.
Connecting PM software to QuickBooks for live WIP data
The PM platform holds the forward-looking estimate data — estimated cost to complete, revised contract values, change orders — while QBO holds the actual costs posted to date. The integration between these systems determines whether the WIP roll-forward is automated or manual each month. Buildertrend and QuickBooks WIP sync handles this connection for residential and light commercial contractors; Procore's QuickBooks integration covers commercial GCs, and the JobTread and QuickBooks integration serves smaller specialty trades. In each case, the sync determines how much manual reconciliation remains in the WIP process.
What LiveFlow FP&A handles in this stack
LiveFlow FP&A connects to QuickBooks Online and pulls live job cost data into a structured WIP report without manual exports. For finance teams managing two to three entities where the PM-to-QBO integration is already in place, the gap is the reporting layer — not the accounting system. LiveFlow FP&A closes that gap by keeping the WIP pack live against QBO data, so the numbers the controller reviews before a surety submission reflect current balances, not last week's export. According to LiveFlow's Finance in the AI Era report (May 2026), 78% of finance teams still move data primarily via manual spreadsheet exports — a pattern that directly undermines the reporting consistency sureties expect.
When does a spreadsheet WIP schedule stop working — and what do multi-entity GCs use instead?
A spreadsheet WIP schedule breaks when a contractor is managing more than two or three entities and needs a consolidated view of backlog, underbilling, and projected profit across all of them simultaneously. The problem isn't the spreadsheet format — it's that entity-level WIP schedules built in separate workbooks cannot roll up to a consolidated view without manual assembly, and that manual step is where errors accumulate and close timelines extend. Flow ERP for construction is built for exactly this inflection point.
What breaks when you're managing 3 or more entities in spreadsheets
The specific failure modes that appear at scale are predictable. Entity-level WIP schedules can't roll up to a consolidated view without a manual assembly step that someone has to own and execute every month. Intercompany jobs — where one entity performs work billed through another — distort the backlog number if eliminations aren't applied correctly. Formula errors in the workbook only appear when a surety's CPA audits the file, at exactly the wrong moment. And the close process for WIP alone can consume two to three days per entity, meaning a five-entity GC is spending two weeks just on WIP before it ever reaches the surety.
How Flow ERP handles multi-entity WIP natively
Flow ERP's native multi-entity architecture houses all entities in a single workspace, so there is no manual consolidation step for the WIP rollup. Entity-level drill-down and consolidated views are available with a single click — the same job cost data that feeds the entity P&L also feeds the consolidated WIP schedule without a separate export. Job costing is built into the ledger rather than maintained in a parallel system, which means the actuals feeding the WIP are always current and always reconciled to the books. Teams migrating from QuickBooks Online move data in under 2 minutes with books live in 11 days or less, so the reporting discipline improvement doesn't require a months-long implementation project.
For a controller running a five-entity GC who is submitting WIP to a surety, the practical outcome is a consolidated WIP schedule that ties to the balance sheet, requires no manual assembly across files, and is available as of the last transaction posted — not as of the last export. That's the reporting posture that surety underwriters increasingly expect from contractors seeking capacity increases above their current limits.
Get your WIP right before your next surety review
Your WIP schedule drives bonding capacity, and finance teams that invest in monthly discipline and accurate job cost data expand their capacity faster than those who treat WIP as a once-a-year exercise. Whether you're on a QBO and PM stack that needs a live reporting layer, or you're managing multiple entities and ready for a system built for consolidation at the ledger level, the path to a higher capacity ceiling runs through WIP accuracy, billing discipline, and consistent submission. Book a demo to see how Flow ERP produces surety-ready WIP reporting natively across every entity you run.
Frequently asked questions
Quick answers to the questions contractors ask most about this topic.
How is bonding capacity calculated?
Surety underwriters calculate aggregate bonding capacity by multiplying a contractor's net working capital by an internal factor — industry-observed multipliers typically range from 10x to 20x, depending on the surety, the contractor's history, and the job types in the backlog. Single-project limits are a subset of the aggregate number. The WIP schedule feeds directly into this calculation because underbillings appear as current assets and overbillings appear as current liabilities, both of which affect the working capital base the surety multiplies.
What is included in a WIP report?
A surety-ready WIP report includes contract value, costs incurred to date, estimated cost to complete, percentage of completion, billings to date, projected profit at completion, and the over/underbilling amount for each active contract. It must reconcile to the corresponding underbilling asset and overbilling liability on the balance sheet. QuickBooks Online produces some of these columns natively — specifically costs incurred and billings to date — but estimated cost to complete, POC, and projected profit require manual calculation or a connected PM platform.
How does a 10% performance bond work?
A 10% performance bond means the surety's obligation is capped at 10% of the contract value if the contractor defaults. Performance bonds (which guarantee contract completion) are typically written at 100% of contract value; a "10% bond" is a specific surety product used on smaller contracts or in jurisdictions where partial coverage is accepted. The bond premium — the contractor's cost — is a percentage of the bond amount, not the contract value, and it varies based on the contractor's WIP history, working capital, and surety relationship.
What are the three C's of surety bonding?
The three C's of surety bonding are character, capacity, and capital. Character refers to the contractor's reputation, track record, and relationships — the surety's assessment of whether the contractor will perform. Capacity refers to the contractor's ability to complete the work — equipment, workforce, management depth, and backlog relative to resources. Capital refers to the contractor's financial strength, measured through working capital, net worth, and the WIP schedule, which provides the most current view of the contractor's financial position across active jobs.
How does underbilling affect bonding capacity?
Underbilling reduces bonding capacity by signaling to underwriters that a contractor is financing their customers rather than collecting payment in line with work performed. Chronically underbilled jobs suppress current assets, which lowers net working capital, which in turn reduces the base number the surety multiplies to set the aggregate capacity ceiling. A pattern of underbilling across the WIP schedule also raises questions about billing discipline and PM-to-finance communication — qualitative signals that constrain how far underwriters will extend limits. Flow ERP produces the consolidated, balance-sheet-reconciled WIP reporting that makes underbilling patterns visible and manageable before they reach the surety.
