How to read a GC payment application before it's too late

The Schedule of Values is the GC-authored roster of every line item on the project, and the values printed on it are the only values the GC will pay against — not the values you bid, not the values in your QuickBooks ledger, and not the values on the schedule of unit prices you negotiated at award. Your draw is just the percentage-completed-vs-SOV number you submit every billing cycle: line by line, you mark each item at whatever percentage of work is in place, the GC portal multiplies that against the SOV's per-line dollar amount, and that product is the only number the disbursement check can ever equal. That single structure is the reason the SOV sets the ceiling: if a line you billed on does not appear on the GC's SOV, no portal status code will pay it — no G-01 approval, no G-02 missing PO/reference resolution, no G-04 partial or short payment cure — because the portal pays its version of the SOV and stops, and your QB ledger never gets the news. The full SOV-portal-QB triad and what it usually hides at the line-item level is laid out in portal reconciliation: the core problem Drumtap solves.

Three line items are the ones subcontractors most commonly miss on a GC payment application, each carrying a recognizable portal signature. (a) Change orders the GC folded into a master line but never sequenced against your pay-app: the GC consolidates the original scope plus the change into a single SOV line, your side tracks it as a separate invoice, and the portal pays against the consolidated master while your change-order row reads as a G-02 missing PO/reference that nobody on your AR desk is plumbing the portal log to find. (b) Stored-but-not-installed materials the GC marks at a discounted rate: the portal routinely discounts stored materials 20–30% against the SOV's stored-material value, your QB books full value, and the delta attaches to your bill as a G-04 partial or short payment withholding that persists until install certification catches back up. (c) Equipment, mobilization, and closeout lines the GC zeroed out after award: these are the lines the sub is permitted to bill at the start and end of the project, and a post-award zero sends the entire mobilization-and-closeout recovery into the rejected pile without any portal status code at all. The specific rejection codes, the per-line treatments, and what the line-by-line verdict looks like inside the dispute packet are at portal reconciliation: the core problem Drumtap solves.

Retainage on a commercial GC payment application is set by the subcontract and the applicable state — there is no uniform percentage across commercial GCs, the held funds may or may not sit in escrow, and the dollar impact of a single rejected line cannot be assumed at a fixed percentage. Whatever the per-contract terms, retainage compounds across cycles in a way most subcontractors underestimate: every billed retainage sits on top of every billed line, so a single rejected line costs the subcontractor the line itself plus the retainage that should have accrued against it, which the GC keeps rather than releases on the cure. The GC-side retainage release schedule is its own window on top of the pay-app cycle: many GCs release retainage only at substantial completion, others withhold through final punchlist, and most condition the release on the unconditional-waiver sequence — three different clocks the subcontractor has to track in addition to the running change-order / waiver / SOV-delta clock that the pay-app itself runs on. The waiver sequencing around retainage release and what partial retainage payments look like inside a dispute packet is jurisdiction-specific and statute-controlled; consult counsel for a specific job.

Drumtap's reconciliation is what catches all three of those misses — change orders folded into master SOV lines, stored-material discounts, and zeroed equipment / mobilization / closeout lines — at the end of every pay cycle, before the next pay-app is due rather than two months later. The SOV-delta is the connective tissue: every QB row is paired against the corresponding portal CSV row for the same pay-app, the change-order trail and the conditional/unconditional waiver status are slotted between them, and the discrepancy list sums into the dollar amount of the dispute. That packet ships pre-filled inside the pay-app window instead of after the next month-end close, which is what turns a quiet G-02 missing PO/reference or G-04 partial or short payment into a paid line on the next draw rather than an aged-out invoice at month-end. The full reconciliation walkthrough is at portal reconciliation: the core problem Drumtap solves; for the next read — when two cycles have already passed and the lien-rights fallback is what you actually have — the state-by-state clocks are jurisdiction-specific and statute-controlled; consult counsel for your specific job.