Why your pay application got kicked back, and how to fix it.

When you submit a pay application (the formal monthly package a subcontractor sends to get paid, showing line-by-line progress and the math behind it), it goes to the general contractor, and often to the project architect, for review. If something is wrong, it comes back to you marked “revise and resubmit.” Sometimes you get a clear reason. Often you do not, you notice you did not get paid, and have to chase down why.

The frustrating part is that a rejection is usually not about the quality of your work. It is about whether the paperwork proves the work cleanly enough to approve. The good news in that: almost every rejection reason is predictable, and every one is preventable.

Below are the reasons pay applications get kicked back, roughly in order of how often they happen. Find yours, fix it, and use the prevention note so it does not repeat next month.

This is the most common rejection of all. A pay application is built from two linked documents: the summary page (the AIA G702 is the standard version, though many general contractors use their own form) and the detail sheet behind it (the AIA G703, which lists every line item). The number on the summary has to equal the total of the detail sheet. If they do not match, even by a few dollars, the reviewer stops there.

Common ways the math breaks:

• The summary total does not equal the sum of the line items on the detail sheet.
• Retainage (the percentage the general contractor holds back until the job is done, usually 5 to 10 percent) is applied inconsistently, calculated one way this month and another way last month, or entered on the wrong line.
• The “previous” column does not match what was actually billed and approved last period. Every month's starting numbers have to roll forward from last month's ending numbers.
• A single rounding difference compounds across many line items into a total that is off.

Prevention: the reason math errors are so common is that they are done by hand, in spreadsheets, month after month. The fix is to make sure the numbers are calculated from a single source and reconciled against last month's approved values before the package ever goes out, rather than re-keyed each cycle.

Many general contractors do not accept the standard AIA forms. They require their own custom version, with their own layout, their own fields, and their own rules about what goes where. If you submit on the standard form when the general contractor wanted theirs, or you use last year's version of their form, the package comes back before anyone even checks your numbers.

Prevention: keep a record of each general contractor's required form tied to each project, and confirm it has not changed at the start of every project, not every month. Forms change between projects more often than within one.

Your pay application is not just the billing numbers. It is a package, and the package usually has to include supporting documents. The two that most often cause rejections:

• Lien waivers (a document in which you give up your right to make a legal claim against the building, in exchange for the payment). The general contractor almost always requires the correct waiver, for the correct amount, with the correct through-date, included with the package. A missing or wrong waiver stops payment.
• Your certificate of insurance (COI, the proof that your insurance is active). If it has expired, or is about to, payment stops until it is current.

Prevention: track certificate expiration dates so you are never surprised by a lapse, and treat the waivers and certificates as part of the package checklist every month, not an afterthought.

A change order (a signed agreement for added or removed work that changes the contract price) can only be billed once it is fully approved and added to the contract sum. A common rejection happens when a subcontractor includes work from a change order that has been requested but not yet executed. The reviewer sees a contract sum that does not match their records, and kicks it back.

The opposite problem costs you money quietly: if you leave an approved change order out, you are billing for less than you earned.

Prevention: keep a running log of every change order and its status, so at billing time you know exactly which ones are approved and billable and which are still pending. Never bill on a verbal go-ahead.

Each line item on your schedule of values (the agreed price list that breaks the job into line items) has a fixed total. You cannot bill more against a line than its scheduled value, and you cannot show a line as more than 100 percent complete. Doing so, often a simple entry error, gets the package kicked back.

If you are billing for materials you have purchased and stored but not yet installed (common for big-ticket items), the general contractor usually requires proof: invoices, photos, proof of proper storage, sometimes proof of insurance on the stored materials. Billing stored materials without the required backup is a frequent rejection.

For an electrical subcontractor, this often comes up with large gear, switchgear or a big panel delivered and stored on site before it is installed. The value is real, but it has to be documented to be billed.

Most general contractors have a hard monthly cutoff, often around the 20th to the 25th, so they can roll your billing into their own application to the owner. Miss it, and your billing waits a full month. Similarly, if the general contractor requires a specific portal and you email a PDF instead, it may not count as submitted.

Prevention: work backward from the general contractor's cutoff to set your own internal deadline for progress numbers and package assembly, so a late input never makes the whole package late.

When a package comes back, run this before you resubmit:

Every reason above comes down to one of two things: a number that does not reconcile, or a document that is missing, wrong, or late. The subcontractors who get paid first are not the ones who fix rejections fastest. They are the ones who catch these issues before the package ever goes out, by checking the package against this exact list every month, before submission, rather than finding out from a bounce.

The monthly billing package is predictable. The reasons it gets rejected are a short, known list. Once you check against that list every time, first-pass acceptance stops being luck and starts being routine.