A clean dispute is not a clean email. It is a per-reason evidence list. A generic "please pay, attached is our invoice" reply may not answer why a portal row is missing, short, or rejected. A useful review names the comparison label, gathers the supplied records that bear on it, and leaves the owner to decide what to send. Most subs do not have that packet on file because each label points to a different evidence question: G-01 (QuickBooks-only / missing portal), G-02 (portal-only / missing QuickBooks), G-03 (short payment), G-04 (portal rejection), G-05 (aged over 60 days / no portal record), and G-06 (small reconciliation delta). Keep the records separate GC portal submission status is a distinct, manually recorded state on a source row: Not submitted , Submitted , Accepted , or Rejected . It describes the portal submission record. A portal rejection alone does not establish correction-tracking eligibility, and it does not determine whether an invoice is unpaid, partially paid, paid, or recovered. Correction tracking has a separate eligibility check. It is available only for an eligible saved invoice whose matched source row is standardized and has GC portal status Rejected , while that invoice's separate normalized status is also rejected. Its local progress values are not started , in progress , and ready to resubmit . Ready to resubmit records a local next step; it does not mean the invoice was refiled in the portal, accepted, or paid. Payment and recovery outcomes rely on their own payment or recovery evidence and tracking. Portal rejection alone proves none of those outcomes. Conversely, payment or recovery evidence does not establish the invoice's portal submission status or correction-tracking eligibility or progress. Here is an illustrative, synthetic 43-day composite — not a substantiated customer record — showing why one packet can be misleading. Day 0 the invoice lands on the portal against the SOV, and its portal submission status is manually recorded as Submitted . Day 3 the owner records the portal row as Accepted and AR logs a separate receipt; a later comparison finds that this portal record has no matching QuickBooks record, so Drumtap's internal G-02 label applies. The portal status and receipt are separate records, and the receipt does not establish a recovery result. Day 8 a replacement line has a QuickBooks record with no matching portal record, creating a separate G-01 comparison result. Day 18 supplied payment evidence shows a partial payment on a matched item, leaving a possible G-03 short-payment difference. Separately, a matched portal rejection or denial would be reviewed as G-04; that label alone does not establish payment or correction status. Day 27 a back-charge appears for review. Day 43 the illustrative payment record is still not a recovery result: the owner must compare the supplied records, confirm the gap, and decide what—if anything—to send. G-03 calls for billed-versus-paid evidence and G-04 calls for the supplied rejection record; a back-charge needs its own scope and daily-log review. The six internal labels The six labels below are Drumtap internal comparison labels assigned after comparing supplied QuickBooks and portal records; they are not codes emitted by a GC portal. Their registry meanings are: G-01 QuickBooks-only / missing portal (the QuickBooks record exists and the portal has no matching record); G-02 portal-only / missing QuickBooks (the portal record exists and QuickBooks has no matching record); G-03 short payment (a matched portal payment is lower than the billed amount); G-04 matched portal rejection or denial (the portal rejected or denied the matched submission); G-05 aged over 60 days / no portal record (the QuickBooks due date is at least 60 UTC calendar days before the supplied report date and has no portal record); and G-06 small reconciliation delta (matched billed and paid amounts differ by no more than $1.00). Evidence to review for each label The per-code evidence list is a planned, owner-reviewed comparison output. For G-01 , review the QB ledger entry, contract or PO reference, supplied portal export, and work records. For G-02 , review the supplied portal row, SOV line, QB ledger, and any change-order record. For G-03 and G-04 , review the portal CSV, QB billed amount, and the supplied payment or rejection evidence. For any waiver material, Drumtap can organize and surface the record for review; it does not sign, file, transmit, convert, or decide on a waiver, and counsel—not the label—determines legal effect. A back-charge needs its own scope, daily-log, photo, and change-order review. Product and legal limits Drumtap's current workflow compares supplied QuickBooks and portal CSV records and prepares a review packet with the dollar gap and line-by-line comparison. The owner reviews it and may explicitly send an approved follow-up; Drumtap does not submit to a portal or send automatically. Live connectors and p