AGGRESSIVE REVENUE RECOGNITION IN CONSTRUCTION, SURETY, BANK, AND WIP CREDIBILITY RISKS.
Revenue recognition in construction isn't just an accounting policy. It's a signal that sureties and banks read as a proxy for how well the business is managed. A contractor whose WIP consistently shows overbilling positions, whose billing outruns physical completion on the early phases, and whose change order billing includes unapproved scope is telling the underwriting community a story whether he means to or not. The story is that cash management drives the billing decisions instead of production management, and that story produces lower limits, higher rates, and more scrutiny on every submission.
None of this is about being conservative for its own sake. Billing that reflects cost incurred and work performed produces the same total revenue over the life of a job as billing that runs out in front of it. What changes is what the underwriter believes about you. Front loaded billing buys cash this quarter and spends credibility you'll want in three years when you go asking for a bigger limit. Credibility builds slowly and it unwinds fast, so the practice that looks harmless on one job is the practice a surety remembers across the whole file.
WHAT IT MEANS.
Aggressive revenue recognition is billing that runs ahead of physical completion, ahead of approved scope, or ahead of the percent complete a job has truly reached.
The surety risk is direct. An underwriter who sees a history of aggressive overbilling reduces capacity and raises rates, because his read is that the financial statements overstate the current financial position. That adjustment is him pricing the uncertainty you put in front of him.
The banking risk works the same way from a different angle. A bank that sees line of credit draws lining up with periods of heavy overbilling, meaning you're billing ahead but not collecting, starts asking questions about the quality of the AR and whether the billing practice is sustainable. Those questions get asked at renewal, which is the worst time to be answering them.
The third cost is internal and it's the one owners underrate. Aggressive revenue recognition makes your own WIP schedule useless as a management tool. When billed amounts don't reflect earned amounts, the overbilling and underbilling position stops telling the owner anything true about the financial health of a project, so the report he is supposed to run the company off becomes a report he can't trust.
WHAT EACH ONE DOES TO YOUR CREDIBILITY.
The front loaded schedule of values, billing ahead of completion from day one
A front loaded SOV assigns inflated values to early mobilization and initial construction phases so the first two months of billing runs well past the work physically performed. On a $600K project with 30% of contract value in the first two SOV line items, billing $180,000 in month one while the project sits at 12% complete produces an overbilling position of $108,000. This is common and often contractually acceptable, and it carries a specific risk: if the project gets cancelled or disputed, or you fail to complete, that overbilled amount may have to go back. Sureties read overbilling positions as cash management rather than production management.
Billing change orders before they're approved
The scope was performed. The change order hasn't been approved. The billing event doesn't exist in the contract until approval, and most GC contracts prohibit billing unapproved change orders on the base pay application. Some contractors include unapproved change orders in a separate section of the pay app marked as pending, which is transparent and acceptable. Billing unapproved scope as though it were approved scope is a different practice, and it creates billing disputes and surety credibility problems at the same time.
Percent complete overstated to support a bigger current billing
Reporting 75% complete on a project that's 62% complete produces an extra 13% of contract value in the current billing event. On a $500K project that's $65,000 of additional billing this period. The overbilling position grows, and when production catches up to the billing the future pay app is proportionally smaller, so total billing over the life of the job is unchanged. The timing distortion is visible in the WIP, gets read by sureties as aggressive billing behavior, and creates a cash flow reversal at closeout during the correction period.
WHAT IT LOOKS LIKE IN DOLLARS.
Front loading is legitimate when the SOV line items correspond to real cost events. A mobilization line at 8% of contract value that matches a real $48,000 mobilization cost on a $600K project isn't aggressive. A mobilization line at 18% of contract value against a $30,000 mobilization is. Same contract, same document, and the only difference is whether the number describes a cost you're about to incur.
BILLING THAT BUILDS CREDIBILITY INSTEAD OF SPENDING IT.
Billing practices and SOV structure get reviewed at the start of every engagement, before the next contract gets signed. The test is whether the front of the schedule of values reflects real cost incurrence or manufactured billing capacity. Front loading that tracks mobilization, early material purchases, and site setup is legitimate and we will help you build it. Front loading that exists to move cash forward is the part that gets restructured.
Approved change orders go on a separate pay app line or in a clearly marked section with the approval date and the change order number. Pending change orders go in a section labeled pending, clearly separated from the approved billing. The GC's PM already knows which ones are approved, so transparency costs you nothing and prevents the dispute. Blending approved and unapproved scope into one number is what creates disputes.
SOV structure, billing behavior, and the overbilling and underbilling position get reviewed in the monthly WIP review. Anything that would create a credibility problem with a surety or a bank gets flagged in the monthly strategic meeting while there's still time to correct it on the next pay app rather than at closeout.
The objective is a billing practice that produces consistent cash flow and builds the long term financial credibility that unlocks bonding capacity and better banking terms. Those two aren't in conflict once the SOV reflects the cost structure of the job. They only conflict when billing is the tool being used to solve a working capital problem that belongs to the balance sheet.
FLAT MONTHLY FEE. NO SURPRISES.
Three tiers, priced by your trailing twelve month revenue. Which one you're in depends on how much of the work you want off your desk. No hourly billing, no payroll, and no add-ons.
Pricing
| Last 12 months revenue | Monthly fee |
|---|---|
| Up to $1M | $1,900 to $2,900 |
| $1M to $3.5M | $2,600 to $3,900 |
| $3.5M to $6.5M | $3,800 to $5,700 |
| $6.5M to $9.5M | $5,100 to $7,100 |
| $9.5M to $12.5M | $6,100 to $8,500 |
| $12.5M to $15.5M | $7,400 to $11,000 |
| $15.5M to $18.5M | $9,400 to $13,500 |
| $18.5M+ | Quoted individually |
Range reflects the three tiers below. Which one you're in depends on how much of the work you want off your desk. No payroll. No hidden line items.
You stop guessing.
You get the CFO work. Job costing built against the way you estimate, a 13 week cash forecast, monthly WIP, and a meeting every month that ends in decisions rather than a report.
Your bookkeeper keeps doing the books.
You stop touching the books.
Everything in Core, and we run the bookkeeping and the controllership as well. Nobody in your office is answering coding questions or chasing a reconciliation at month end.
We do the books. No payroll.
Every job shows its margin while it's still running.
Everything in Executive, plus the job costing and WIP platform set up, loaded with your cost codes, and managed for you every month. You never have to learn it.
We do the job costing.
FREQUENTLY ASKED.
