A pay application looks like an invoice. To a WIP schedule, it's the primary source data.
A controller at an electrical contracting firm is pulling together the quarterly WIP schedule before it goes to the company's surety. Job 4417 should be showing billing right in line with the work performed, work is roughly 70 percent done and billing has kept pace all year. Instead, the WIP shows a $60,000 underbilling position with no obvious explanation.
She traces it back two billing cycles. A change order had been approved and added to the contract value, but the percent complete on that month's pay application was entered against the old contract total instead of the new one. The math on that single invoice was off by a few points. Every WIP calculation since has carried the error forward.
Nobody caught it at the time because nobody was looking at the pay application as WIP data. They were looking at it as an invoice.
What a Pay Application Actually Feeds
A pay application asks a general contractor to release payment. It also answers a different question for a WIP schedule: how much of the contract has actually been earned so far. Those are two uses of the same percent-complete figure, and most electrical subs only think about the first one when they are filling out the form each month.
The percent complete entered on the pay application is the same number a WIP schedule multiplies against the total contract value to calculate earned revenue. Enter it wrong once, against the wrong contract total or the wrong line item, and the error does not stay contained to that one invoice. It carries forward into every WIP calculation until someone finds it. For how that same percent complete gets entered and calculated on the pay app itself, see our blog on setting up the pay application in Sage Intacct.
What One Wrong Percentage Distorts
A single data entry error on a pay application shows up in more than one place on the WIP schedule, because several WIP figures are calculated from the same underlying billing data.
- Earned revenue, calculated directly from percent complete multiplied by the contract's total value.
- The overbilling or underbilling position, which is the gap between what has been billed and what the percent-complete figure says has actually been earned.
- Gross profit to date, which depends on earned revenue lining up correctly against the cost incurred on the job so far.
- The remaining backlog on the job, since it is calculated from what has already been billed, and an understated billing figure makes the work still ahead look larger than it actually is.
None of these numbers are wrong because the WIP schedule was built incorrectly. They are wrong because the pay application that feeds them was. That is the part of the process most controllers are not reviewing for accuracy, because it does not look like the kind of number that needs a second look.
How the Two Documents Usually Get Disconnected
In a spreadsheet-based billing process, the pay application and the WIP schedule are typically two separate files, and there are a handful of specific points where the numbers between them can drift apart.
- Percent complete gets entered once on the pay application to generate the invoice, then re-entered separately into the WIP spreadsheet, sometimes weeks later and sometimes from memory.
- A change order gets updated in the billing file but never carried over into the WIP schedule's contract total, or the other way around.
- The retainage percentage gets applied differently in the two documents, especially when a different person maintains each one.
Sage Intacct removes those re-entry points. Because the schedule of values and the percent complete entered on the pay application are the same data the WIP schedule calculates from, there is no second version of the number to keep in sync. The application and the WIP schedule are reading from the same source at the same time.
Why This Matters More When a Surety Is Reading It
A single billing error on one job is usually recoverable once it is found. The bigger risk is what it looks like from the outside. Sureties and lenders read the WIP schedule as a direct indicator of financial discipline, and an underbilling position with no clear explanation raises the exact kind of question that slows down a bonding renewal or a credit line increase.
The contractor in this scenario has a real, correctable error. What a surety cannot easily tell from the outside is whether that is a one-time mistake or a sign that the WIP schedule is not reliable more broadly. Clean, consistent billing data is what lets a controller answer that question with confidence instead of an explanation after the fact.
What This Doesn't Fix
Connecting the pay application to the WIP schedule removes one specific failure point: the second manual entry where a number can drift. It does not fix a percent-complete estimate that was wrong in the field to begin with. If the person filling out the pay application misjudges how much of the job is actually done, that number flows cleanly into the WIP schedule and is just as wrong as it would have been in a spreadsheet.
It also does not replace a monthly review. A controller still has to look at the WIP schedule and ask whether the numbers make sense for each job. What changes is that the numbers she is reviewing are the same ones that went out the door on the pay application, not a second version that might have already drifted from it.
Frequently Asked Questions
Does a pay application error always show up as an underbilling or overbilling position?
Not always as visibly as in this example, but any mismatch between the percent complete billed and the percent complete actually earned shows up somewhere in the WIP calculation, whether that is earned revenue, gross profit to date, or the overbilling or underbilling figure itself.
Can Sage Intacct catch an error like this automatically?
It removes the most common cause of it. Because the same billing data drives both the pay application and the WIP schedule, there is no separate manual entry step where a percentage or contract total can drift out of sync between the two.
Make Sure Your WIP Is Actually Telling the Truth
The controller in this scenario found her error before the surety did, but only because she happened to trace a number that looked wrong. Sage Intacct removes the gap between the pay application and the WIP schedule at the source, so the percent complete entered once is the same figure every report downstream is built on.
