A GC pay-app moves through four discrete states, and the GC portal shows them as four separate labels in the same column. "Submitted" is the file you dropped into the upload box. "Accepted" is the portal confirming the file arrived and matched the schema it expects — a dollar amount on a line, an invoice number, the GC's project code on the row. "Approved" is the next step: the PO line is funded and the change orders are sequenced against the GC's schedule of values. "Paid" is the cleared wire your bank shows on the statement. "Accepted" is none of those three things. "Accepted" is the GC's portal confirming receipt. It is the status the GC pay-app summary shows next to the dollar amount, and it is the moment trade AR teams stop pushing. The first thing to internalise: accepted does not mean approved. Accepted does not mean paid. The dollar on the accepted line is not what lands in your account. Here is a synthetic, illustrative 43-day composite—not a substantiated customer account—showing why "accepted" cannot be treated as "approved" or "paid." Day 0 the invoice is submitted against the schedule of values. Day 2 the row flips to Accepted ; a later comparison finds a missing reference, and Drumtap's internal G-02 label is assigned after comparing the supplied portal and QuickBooks records. A partial payment or waiver record may then require separate owner review. The illustrative record does not establish a payment or recovery outcome. The line to take from it: accepted means the portal indicates receipt; approval and cleared payment need separate evidence. Drumtap's current workflow compares supplied QuickBooks and portal CSV records at the line-item level and prepares an owner-reviewed discrepancy list. Live QuickBooks and GC-portal connectors, banking-feed verification, and portal-log ingestion are planned and not active. Drumtap does not connect to a bank, submit to a portal, or send dispute emails automatically; after review, a user may explicitly send an approved follow-up. The honest framing: the comparison shows a possible gap, while you decide what to send, when to send it, and what the bank confirms. Access and any paid terms remain disabled pending legal review. Walk the reconciliation loop end-to-end on the /how-it-works page — the three-step CSV upload, line-by-line reconcile, and owner-reviewed follow-up. The /pricing page describes planned tiers for information only; access, billing, and checkout remain disabled pending legal review. Request early access through /signup if you want timing and final terms when the private beta opens. For the structural framing of the same problem (QB invoice vs GC portal paid, the line-by-line gap that becomes the dispute packet), start with portal reconciliation: the core problem Drumtap solves . For the specific SOV mechanics — what the schedule of values sets as your draw ceiling, the three line items most commonly missed, and how retainage compounds every rejection — read how to read a GC payment application before it's too late .