The Schedule of Values is the GC-authored roster of line items used for a payment application. The contract, approved changes, portal instructions, and supplied records determine what a particular GC will accept or pay; a QuickBooks ledger alone cannot answer that question. Your draw is the percentage-completed-versus-SOV number you submit each billing cycle, but portal status still needs separate payment evidence. Drumtap applies G-01 through G-06 only after comparing supplied QuickBooks and portal records, and those are Drumtap internal comparison labels—not GC-portal codes. The full SOV-portal-QB triad is laid out in portal reconciliation: the core problem Drumtap solves . Three line items are common places to look, each requiring comparison with the job's own records. (a) A change order may be folded into a master line while the subcontractor tracks it separately; that can produce a G-02 internal comparison result if the supplied portal record has no matching QuickBooks row. (b) Stored-material treatment may differ between the SOV and the books, creating a possible G-03 short-payment or G-04 rejection review. (c) Equipment, mobilization, and closeout lines may be changed after award, so the owner should compare the contract, approved changes, and portal export before drawing a conclusion. These are illustrative review patterns, not substantiated outcomes. 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 current workflow compares supplied QB rows with the corresponding portal CSV rows, organizes the change-order trail and waiver records for owner review, and identifies a possible dollar gap. It does not turn a G-code comparison into a payment, a next-draw result, or a recovery guarantee. The owner reviews any packet and may explicitly send an approved follow-up; autonomous sending is planned or disabled. The full reconciliation walkthrough is at portal reconciliation: the core problem Drumtap solves ; for the next read—when cycles have already passed and lien-rights questions arise—the state-by-state clocks are jurisdiction-specific and statute-controlled; consult counsel for your specific job.