WIP reporting in Sage Intacct Construction: How it works and how to set it up

Every month the controller pulls a WIP export out of Sage Intacct, opens last period’s spreadsheet, and fixes the numbers by hand before the bank sees them. The system holds the data. The schedule people trust still lives in Excel, because the project managers keep the real forecast in their own files.

Sage Intacct Construction is a strong WIP reporting fit for contractors willing to govern job cost and forecasts inside the system. A smaller contractor who only needs a static WIP schedule for a bank or bonding company, and does not want to change field-to-office behavior, should fix the process first or look at a lighter system.

WIP, work in progress, reporting shows earned revenue and expected margin on open jobs. The formula is rarely the hard part. Getting current source data into Sage Intacct Construction fast enough for the report to mean something is. If your controller still rebuilds the WIP schedule in Excel before sending it to the bank, bonding company, ownership, or auditors, start by finding which job-cost inputs are not trustworthy enough to report from the system.

We implement and support construction ERP systems, the finance and job-management platforms contractors use to run accounting, projects, and reporting. In discovery, WIP conversations usually start with a spreadsheet that everyone depends on and nobody fully likes. That spreadsheet often contains the company’s real reporting rules, the bank’s preferred format, and a long trail of manual corrections.

We sat down with Troy Guevara, our Construction Technologist focused on Sage Intacct Construction, because he sees this pattern often. Troy’s point is practical: contractors are good at adapting around obstacles, and that habit can hide accounting problems for years. Workarounds become the process.

Troy also framed WIP as forecast discipline, not report design. “Contractors should be re-budgeting their jobs every week, asking, ‘Where am I today, what’s my projected profitability, am I going to make or lose more than I expected?’”

Sage Intacct Construction is useful for reducing manual report-building when the implementation is designed around clean job data. Treating it as a way to reproduce the old spreadsheet with a fresher export usually preserves the same close problems.

How WIP reporting works in construction accounting

WIP shows how much revenue and profit a contractor has earned on open jobs compared with how much has been billed and spent. It is a close process input, a management report, and often a schedule that outside stakeholders ask to see.

Most WIP schedules use a percent-complete calculation built from these inputs:

• Contract value: the current value of the job, including changes according to your company’s policy.
• Billings to date: what has been invoiced to the customer so far.
• Costs incurred: job costs posted to date.
• Estimated total cost: what the job is currently expected to cost when finished.
• Percent complete and earned revenue: costs incurred divided by estimated total cost, then applied to contract value.
• Overbilling or underbilling: the difference between billings to date and earned revenue.
• Forecast margin: expected profit based on current contract value and current estimated total cost.

Management signals come from comparing those numbers over time. A job can look healthy because billings are ahead while forecast margin is falling. Another job can look weak because it is underbilled even though the field work is on track.

A useful WIP process separates billing timing from job performance. It helps finance and operations see whether profit changed, whether billing matches progress, and whether the forecast is current enough for leaders to act.

No single WIP format satisfies every bank, bonding company, auditor, executive, and project leader. The company needs one governed source of job data, then different views can be created from that source for each stakeholder. A cloud-native system assumes remote access, workflow routing, and dashboards, so finance, project managers, and leadership all read those views from the same current source.

Where Sage Intacct Construction fits

Construction buyers should confirm they are evaluating Sage Intacct Construction, not standard Sage Intacct. The two are different products, and WIP depends on the construction version.

WIP depends on job costing and project workflows more than general ledger reporting. Troy identifies construction-specific capabilities in Sage Intacct Construction such as job costing, project profit and loss, cost codes, compliance, project management, and change management.

What should you set up first?

Start with the WIP process before the WIP layout. Settle the policy and stakeholder needs first, then the job and cost-code structure, forecast ownership, change-order rules, and the source processes that feed job cost. Build the report views last, from one governed source of data, and reconcile against your last trusted schedule before anything goes outside the company. If cost-to-complete ownership is unclear, a better report layout will only make stale forecasts easier to distribute.

Decisions to make before you build the WIP report

In our construction ERP discovery work, the matrix below is where WIP usually succeeds or fails.

Dimensions deserve restraint. Sage Intacct is often evaluated for dimensional reporting, and that can help construction companies that need WIP by entity, division, location, project manager, or work type. Add a dimension when it changes a decision, an approval, a forecast, or a required stakeholder view. If it does none of those, it may create more coding work than value.

Separate calculation inputs from review controls

Some numbers drive the WIP calculation: contract value, billings to date, costs incurred, and estimated total cost. Other controls tell leaders whether the schedule is ready for use.

The controller can calculate WIP correctly and still be wrong for management if 30 invoices are waiting for approval or labor posts after close. Treat queue age, late posting, and forecast signoff as close controls before the schedule is released.

What should leaders be able to see in the WIP report?

A useful WIP report should make management attention obvious. The report should help leaders see which jobs are drifting, why margin changed, and whether billing is ahead or behind earned revenue.

The WIP review should answer questions like these:

• Which jobs need review before the next close?
• Did forecast margin change because of labor, subcontractor cost, materials, scope, or estimate updates?
• Are pending changes masking a job that is losing margin?
• Are committed costs higher than the latest forecast suggests?
• Is underbilling a billing timing issue or a job performance issue?
• Are approvals or labor timing making the report unsafe to rely on?

The layout matters, but it should follow the management questions. A clean schedule that hides stale estimates is still a risky schedule.

How often should the team update and review WIP?

WIP becomes useful when forecasts are current enough to change job behavior. If the forecast is too old to influence cost, billing, or scope decisions, it is too old for management WIP.

Troy’s weekly re-budgeting standard sets the bar. Some contractors will not issue a formal weekly WIP package, but risky jobs need a regular rhythm for cost-to-complete updates and job explanations before finance publishes a schedule that executives trust.

Troy also warned, “If your data is a week behind, you can’t make those adjustments in time.” Labor is the area he watches closely, because it can move margin faster than any other cost.

Who has to keep the WIP numbers current?

Invoice routing is a WIP issue because unapproved costs make job cost look better than it is. The implementation work is deciding routing rules, approval owners, and integration paths before the close process depends on those costs.

AP owns routing visibility. Approvers own queue age. Project managers own cost-to-complete and explanations. Finance owns the schedule. Executives own enforcement.

What should you test before you trust the report?

Before sending WIP from Sage Intacct Construction to a bank, bonding company, ownership group, or auditor, test the process through real jobs and a real close cycle. Do not stop at whether the report looks right on screen.

• Compare against the last trusted WIP schedule. Reconcile differences and decide whether each difference is a setup issue, timing issue, policy issue, or old spreadsheet adjustment that should no longer exist.
• Trace several jobs from budget to billing. Pick active jobs with different risk profiles and follow original budget, revised estimate, actual cost, billing, and contract value through the report.
• Test approved and pending changes. Confirm that change-order status affects contract value and forecast review the way your policy says it should.
• Confirm labor timing. Check whether labor reaches job cost soon enough for the WIP review to matter.
• Review open AP and commitments before close. Make sure approvers, project managers, and finance can see the costs that are not yet posted but may affect the job.
• Check overbilling and underbilling logic. Confirm that the report separates billing timing from actual job performance.
• Run one close cycle before external use. Let finance and operations work through corrections before the report becomes the outside-facing schedule.

This testing step is where teams find the real gaps. A report that looked finished during setup may fail because a project manager updates forecasts after close, a payroll file arrives too late, or pending changes are treated differently by job.

What should you bring to a demo or discovery call?

A good Sage Intacct Construction discovery session should use your real WIP pressure points. Bring the materials that show how WIP is built today and where the team makes offline corrections.

• Your current WIP schedule, including stakeholder versions and reporting requirements.
• A sample job budget and your cost-code list.
• Examples of approved, pending, rejected, and internal change orders.
• Evidence of AP and labor timing, such as queue aging, late invoices, payroll timing notes, or field time cutoffs.
• A list of spreadsheet adjustments the controller makes before WIP is shared.

The last item is often the most useful. Offline adjustments show which inputs the team does not trust yet.

What usually breaks first

The most expensive WIP mistake is using new software to preserve old habits. Troy sees the same first-month failure often: teams hold onto the workarounds they brought with them, and the new system inherits the old problems.

For WIP reporting, the old habits cluster in a few places. Teams rebuild the controller’s spreadsheet as the system design, carrying the offline corrections along with it, when the move is to bring the real stakeholder rules into Sage Intacct and retire the corrections. Revised estimates go unmaintained, so margin fade shows up late. Approval queues and late payroll hide cost, leaving leaders to read a schedule that is missing money. Pending change orders get treated as likely revenue on one job and placeholders on the next, which makes the whole schedule hard to defend.

None of these are software defects. They are process gaps, and a new system surfaces them, it does not solve them. If leadership tolerates a stale forecast or a backed-up approval queue, no report layout will enforce what the company will not.

Are you ready to trust WIP from Sage Intacct Construction?

A team is ready to trust WIP when it can explain the source of the number and name the owner of each update before close. If not, evaluate software, but do not start by redesigning the report layout.

Start by finding the offline adjustments

Pick the jobs that need the most spreadsheet cleanup today, then name which numbers are corrected offline, who owns them, and why they are not trusted from the system. Once those inputs are governed, Sage Intacct Construction WIP reporting becomes a report finance can defend, no longer one more spreadsheet to rebuild every period.