You did the work. You ran the crew. You bought the steel. And now your pay app is sitting on someone desk with a polite note that says please revise and resubmit.

Welcome to one of the most expensive 30-day round trips in commercial construction.

Here is the short answer, and we will spend the rest of this piece earning it: pay applications almost always get rejected for the same small set of reasons. Totals that do not tie between the G702 and G703, retainage math that drifted from prior periods, change orders that were billed before they were approved, lien waivers that are missing or wrong, and a Schedule of Values that does not match the work in the field. Fix those, and you fix most of the cash-flow drag in your back office.

The stakes are bigger than one rejected form. According to Billd 2025 National Subcontractor Market Report, general contractors believe payments occur within 30 days of a pay app, while subcontractors actually wait an average of 56 days. The Rabbet 2024 Construction Payments Report puts average payment cycles in U.S. construction at around 90 days, roughly double the 45 days financial analysts consider healthy for commercial enterprises. Every rejected pay app you eat compounds on top of that.

Let us get into why this keeps happening, and what to do before Friday.

What a rejected pay app actually costs you

A rejection is not a procedural inconvenience. It is a cash event.

If you submit on day 25, get reviewed on day 40, get rejected, fix it by day 45, and re-enter the review queue, you have just pushed your funding date past day 60. Your payroll, your suppliers, and your insurance carrier do not care that the architect needed a revised G703. They want their money on the original cadence.

Built 2025 survey of 250 U.S. contractors and subcontractors found that 70 percent of contractors regularly face delayed payments, and that contractors inflate bids by an average of 8 percent to protect themselves against slow payments. Mobilization Funding 2025 report adds that 56 percent of construction pros have walked away from projects due to cash-flow or payment risk. Pay app rejections feed every one of those numbers.

That is the business case for getting this right. Now the operational one.

The repeat offenders, why pay apps get rejected

These are the issues that show up in nearly every published rejection checklist from billing-software vendors, GCs, and architects. Ranked roughly by how often they cause trouble.

1. The G702 summary does not tie to the G703 continuation sheet

This is the most common rejection trigger in commercial billing. The G702 is a summary; the G703 is where the actual math lives. If the numbers on the summary do not reconcile cleanly to the line-item detail, reviewers do not investigate, they kick it back.

The usual culprits: copy-paste errors from last month spreadsheet, an overwritten cell, a manually adjusted total nobody documented.

Pre-submit fix: Reconcile cumulative totals, work completed to date, retainage, balance to finish, before you sign. If you cannot trace every number on the G702 back to a line on the G703, you are not ready to submit.

2. Retainage is calculated inconsistently

Retainage is supposed to be boring. It is also one of the top three rejection triggers.

The usual problems are applying the wrong percentage, failing to step down retainage at substantial completion, calculating retainage on stored materials differently than on installed work, or most often, applying it differently this month than you did last month. If retainage was calculated differently from prior billing periods, the reviewer returns the pay app for correction.

Pre-submit fix: Pull last month approved G703. Confirm retainage percentage matches the contract. Confirm the math rolls forward cleanly. Do not improvise.

3. Change orders were billed before they were approved

You did the extra work in good faith. The PM verbally agreed. The owner is going to sign. You billed it.

The reviewer rejects the whole thing.

One unapproved line can nuke an otherwise clean submission. Industry guides routinely cite cases of a single 25,000 dollar unapproved change order delaying an entire pay app by a full month.

Pre-submit fix: Bill only change orders with written, signed approval. Track open COs in a separate log. If a CO is in dispute, bill the base contract clean and pursue the CO on its own track.

4. The Schedule of Values is vague, lumpy, or does not match the field

The SOV is the source of truth for everything downstream. If your SOV bundled Site Work into one 400,000 dollar line, you are going to fight every reviewer for the life of the job, because nobody can tell what 40 percent complete actually means.

A vague SOV also creates room for the reviewer to under-approve. They see ambiguity, they assume the lower number.

Pre-submit fix: Break the SOV into line items that can actually be inspected and verified. Match it to how the work happens in sequence. Fix this at job setup if you can, it pays back every month.

5. Overbilling against work in place

Closely related to a weak SOV: billing for work the field cannot back up.

Reviewers, especially on lender-backed projects, are comparing your percent-complete claims against site photos, inspection reports, and the owner rep own observations. If your 60 percent line item looks like 35 percent on site, the line, and sometimes the whole app, gets revised down.

Pre-submit fix: Tie billing to documented progress. If a line is genuinely ahead because of stored materials or front-loaded mobilization, document it that way. Do not just pad.

6. Lien waivers are missing, wrong type, or wrong state form

Lien waivers cause more rejections than they should, because there are four kinds and at least a dozen state-specific forms.

Conditional progress for the current draw. Unconditional progress for the prior payment received. Conditional final at closeout. Unconditional final after the final check clears. Mix those up, and the reviewer holds the check.

It gets harder across state lines. States like California, Texas, Arizona, and Georgia have statutory lien waiver forms with specific required wording. Using the wrong form is one of the most common reasons waivers get rejected.

Pre-submit fix: Build a project setup checklist that locks in the waiver forms and statutory language before the first pay app. Standardize by state.

7. Lower-tier lien waivers from your subs and suppliers are missing

If you are a GC, your owner or lender will usually want waivers from everyone below you, too. If you are a sub with second-tier suppliers, expect the same.

Chasing those waivers in the last 48 hours before submission is how good billing teams burn out. And one missing waiver from a small supplier can hold the entire pay app.

Pre-submit fix: Start collecting lower-tier waivers the day prior payment hits, not the week of submission. Use a tracker. Make it a vendor onboarding requirement.

8. Stored materials are not documented properly

If you are billing for materials on site but not yet installed, most contracts require specific backup: invoices, photos, off-site storage agreements, certificates of insurance covering the materials, and sometimes UCC filings. Skip any of those and the stored-materials line gets pulled.

Pre-submit fix: Build a stored-materials packet template. Every billing period, the packet either applies or it does not, but the format never changes.

9. Wrong form, wrong format, or missed deadline

This one stings the most because it has nothing to do with the work.

Many GCs do not use the standard AIA billing forms, always confirm the specific form requirements for each project before preparing. Some owners require an Excel version, a custom cover sheet, certified payroll attached, or a specific PDF naming convention. Miss it, and the package never gets reviewed.

Then there is the calendar. Most GCs run a strict monthly billing cycle. Miss the 25th and you are billing the 25th of next month.

Pre-submit fix: At kickoff, confirm: which form, what backup, what submission portal, what day of the month. Put the cutoff on the team calendar with a 5-day internal buffer.

10. Signature authority and certifications are off

The G702 is a certification. Whoever signs it is certifying, in writing, that the work is complete to date and the numbers comply with the contract. If the wrong person signs, or the notary block is incomplete, or the certified payroll attachment is missing on a prevailing-wage job, that is enough for a rejection.

Pre-submit fix: Document who has signature authority on each project. Keep a notary in-house or on call. Build the prevailing-wage attachments into the standard package.

A short pre-submit checklist (steal this)

Before any pay app leaves your office, walk this list:

• G702 totals tie to G703 line-item totals, to the penny
• Prior-period values roll forward without unexplained changes
• Retainage percentage matches the contract and prior periods
• Every billed change order has a signed approval on file
• Billing percentages match documented field progress
• Correct SOV format, job-specific, not generic
• Correct lien waiver type for this period
• Correct state-specific waiver form, if required
• Lower-tier waivers from subs and suppliers attached
• Stored materials packet complete, invoices, photos, insurance
• Correct form version and submission portal confirmed
• Authorized signature, notary, and certified payroll where required
• Submitted by the contractual cutoff with a buffer

If even one of those is shaky, fix it now. Fixing it tomorrow costs you 30 days.

What to do if you have already been rejected

First, do not panic and resubmit. Resubmitting the same package without fixing the underlying issue almost always results in another rejection. You will lose another cycle.

Instead:

• Ask for the specific reason in writing. Does not tie is not enough. You want the line item.
• Reconcile back to the prior approved period. Most tie-out problems are roll-forward problems.
• Fix once, fix completely. If retainage drifted, recompute the entire SOV, not just the line that was flagged.
• Resubmit with a short cover note that flags exactly what changed. Reviewers reward clarity. They have ten more apps in the queue.

The Breva point of view

We built Breva because the work-to-cash cycle in construction is the most under-managed financial asset in the industry. Pay apps are where that cycle either accelerates or stalls.

Our construction platform handles Schedule of Values, pay apps, job costing, WIP, sub management, and cash planning in one place, because those are the same numbers, viewed from different angles. When your SOV, your billing, your job costs, and your cash plan agree with each other, your pay apps stop coming back.

Pay apps are not paperwork. They are how your business gets paid.

Want a clearer view of what your billing cycle is doing to your cash? See how Breva works for contractors, or start a free Breva account and get your billing, job costs, and cash plan working from the same numbers. Prefer to talk it through? Book a meeting.

Win jobs. Get paid.

Frequently Asked Questions

What is the most common reason a pay app gets rejected?

Totals that do not tie. The G702 summary and the G703 continuation sheet have to match, and the current period has to roll forward cleanly from the last approved period. Most rejections trace back to this single issue.

How long does a rejected pay app usually delay payment?

At least one full billing cycle, typically 30 days, sometimes more. Subcontractors already report waiting an average of 56 days for payment after submission (Billd, 2025), and a rejection effectively restarts that clock.

Can a pay app be rejected for a missing lien waiver?

Yes. Missing or incorrect lien waivers, including lower-tier waivers from your subs and suppliers, are a routine rejection reason. State-specific statutory forms in places like California, Texas, Arizona, and Georgia add another layer of risk.

What is the difference between the G702 and the G703?

The G702 is the one-page summary and certification of payment owed. The G703 is the continuation sheet that breaks the contract into line items and shows progress against each. The G702 is what reviewers read first; the G703 is where the math has to hold.

Should I bill an unapproved change order if I have already done the work?

Not on the main pay app. Bill the base contract clean, track the change order on its own paper trail, and pursue it as a separate item. Billing unapproved COs is one of the fastest ways to get an entire application rejected.

This article is for educational purposes. It is not legal, tax, or accounting advice. Lien waiver rules, retainage caps, prompt payment statutes, and contract requirements vary by state, contract, and project type. Confirm specifics with your attorney, accountant, or lender for your situation.