The following is an illustrative, synthetic scenario—not a substantiated customer record. A GC portal may show a "Pay App #14" line while the bank deposit is short and QuickBooks shows the invoice as open and aging. Those signals do not prove where the difference arose. Compare the supplied records before assigning Drumtap's internal labels: G-01 (QuickBooks-only / missing portal), G-02 (portal-only / missing QuickBooks), G-03 (short payment), and G-04 (portal rejection). The place the invoice disappears is the chain between QuickBooks and disbursement: the bid you signed at award, the schedule of values the GC issued against the bid, the pay-app you submitted against the schedule, the GC's review portal where pay-app status codes live, and the disbursement that finally hits your account. A discrepancy can arise at any handoff in that chain: a line may differ between the records, be omitted from a submitted pay-app, or be rejected under the GC's review process. Your QuickBooks ledger may not reflect that difference unless someone compares the supplied records. The portal pays the GC's version of the SOV, not your invoiced version. The G-03 short payment or G-04 portal rejection sits on the pay-app until somebody pulls the conditional waiver to close out the under-payment; meanwhile your invoice has cycled once. The change-order you logged in QB may or may not have been sequenced into the GC's side of the SOV before pay-app #14 closed. Whenever the portal's verdict differs from your billed version, the discrepancy lives where AR cannot see it and QB does not write it down — and that is the structural reason the same subcontractor can be profitable on jobs and cash-poor at the office. If the portal route has left an invoice unresolved for two pay cycles and the dispute packet is still empty, lien-rights questions may need counsel's review. The exact window, form, sequencing, and legal effect are state- and contract-specific; Drumtap can organize supplied records but does not sign, file, transmit, or decide on a lien or waiver. This is not legal advice, and no notice or comparison guarantees payment or recovery. Drumtap's planned reconciliation workflow surfaces the gap at the line-item level when a pay cycle closes, before the next pay-app is due rather than after the next month-end close. Every QB invoice row gets paired to the corresponding portal CSV row for the same pay-app; change-order sequencing, conditional/unconditional waiver status, and the SOV delta the GC posted back explain the difference. A single line that does not match receives a Drumtap reconciliation label, the dollar gap is recorded, and the per-line evidence list prepares a review packet. The owner decides what to send. The /pricing page describes planned tiers for information only; billing and checkout are disabled pending legal review. Request early access through /signup for timing and final terms. For the specific portal statuses and the lien-rights / lien-waiver sequencing that drives most of those gaps, start with portal reconciliation: the core problem Drumtap solves .