Progress Invoicing and Retainage Support in QuickBooks Online: September 28 Control Review
September 28, 2026
Research question
How should a QuickBooks Online virtual assistant document progress invoices and retainage balances without deciding revenue recognition on September 28, 2026? A fixed-price project billed in milestones on September 28, 2026 earns its value gradually as work completes, yet the invoices issued may follow the contract schedule, the customer's approval pace, or the VA's memory of what was billed last. A helpful VA might invoice the next milestone because the calendar says so, yet that invoice can overstate earned revenue if the underlying work is behind, or understate it if completed work was never billed.
QBOAssistant frames the VA as a preparer of billing evidence and milestone questions on September 28, 2026. Progress billing work intersects bookkeeping, accounts receivable, and reporting. Daily project activity creates completion evidence, accounts receivable encounters customer approvals and retainage holds that delay collection, and reporting relies on whether billed, earned, and collected amounts reconcile for the period ending September 28, 2026. The research question therefore asks what evidence packet on September 28, 2026 lets an owner see each milestone, its completion evidence, its billed status, its retainage holdback, and its collection state, then decide the billing treatment without ceding revenue judgment to preparation work.
Why this fits QBOAssistant work
QBOAssistant provides Bookkeeping VA, Accounts Receivable VA, and Reporting Support VA services that delegate preparation while retaining approval on September 28, 2026. Bookkeeping VAs record estimates, log milestone completion evidence, and draft progress invoices. Accounts receivable VAs track customer approvals, retainage balances, and collection follow-up. Reporting support VAs assemble packets where unbilled completed work and uncollected retainage distort receivables and revenue accuracy for the period ending September 28, 2026.
Clients delegate milestone tracking, invoice drafting, and retainage ledger maintenance, but retain approval for the related billing and revenue decisions on September 28, 2026. That division requires the packet on September 28, 2026 to be inspectable rather than narrative. A progress billing packet lets an owner confirm on September 28, 2026 whether each invoiced milestone was actually complete, whether retainage was withheld at the contract rate, whether the customer approved the application for payment, and whether the next action is assigned to a reviewer with authority.
Without a defined billing packet, evidence scatters across contract PDFs, emailed progress photos, customer approval threads, change order logs, and the QuickBooks Online invoice list. The September 28, 2026 review restores visibility by recording the contract value and milestone schedule, each milestone's completion evidence, each invoice with date and amount, retainage withheld and released, change order treatment, and the specific question for the reviewer in one place. Owners building milestone discipline can pair this packet with the bookkeeping VA tasks guide and the service map in the QuickBooks VA services overview.
Methodology and scope
This brief on September 28, 2026 uses documentary synthesis. It reviews IRS business income and recordkeeping guidance, SBA project cost and cash-flow guidance, public internal control frameworks, and Intuit progress invoicing guidance. No customer contract, project cost file, QBO company file, or private invoice image was used on September 28, 2026. Scope is a qualitative design for the progress billing packet: what to collect, how to link milestones to invoices to collections, and how to track retainage, intended for September 28, 2026, not a statistical estimate of milestone billing error frequency.
Methodology on September 28, 2026 is limited to synthesis of public guidance and a proposed record design. No survey, no receivables file extraction, and no project margin testing of QBOAssistant clients was performed on September 28, 2026. Analysis therefore addresses design reviewability rather than measured unbilled revenue.
Facts and analysis separation
Fact on September 28, 2026: IRS guidance requires businesses to keep records that support gross receipts, including invoices, contracts, and evidence of completed work that substantiate reported income. Analysis on September 28, 2026: each progress invoice on September 28, 2026 should therefore cite its milestone completion evidence and contract reference, or state that support is missing and name the project lead who was asked to provide it.
Fact on September 28, 2026: GAO internal control standards emphasize complete and timely recording of transactions and reconciliation of subsidiary records to control totals. Analysis on September 28, 2026: the billing packet dated September 28, 2026 should reconcile contract value to billed-to-date, retainage held, and remaining balance on every review, with each figure traceable to a dated document rather than carried forward from memory.
Fact on September 28, 2026: SBA cash-flow guidance advises businesses to align billing timing with cost outlays so project work does not drain operating cash. Analysis on September 28, 2026: milestone billing status on September 28, 2026 should be reviewed against project costs incurred, so completed-but-unbilled work and billed-but-uncollected balances surface before they become cash surprises.
Inference boundary on September 28, 2026: source guidance describes what records to keep, not what percentage of project value a small business should invoice at each milestone. Milestone percentages are contract terms, and any claim about appropriate percentages would require contract review outside this brief.
Packet design for September 28, 2026
The progress billing packet on September 28, 2026 contains one row per milestone with seven fields: contract milestone definition with percentage and amount, completion evidence with date and verifier, invoice reference with date and amount billed, retainage withheld at the contract rate, customer approval status, collection state, and the reviewer question. A milestone that is complete, invoiced at the agreed amount, approved, and either collected or in normal terms is marked current. Any gap between completion and billing, any retainage deviation, any unapproved application for payment, or any past-due balance routes the milestone to the exception section with a named owner and a due date.
Change orders on September 28, 2026 receive the strictest rule in the packet because they are the most common source of unbilled project value. No change order work is treated as billable until the customer authorization is documented in writing with scope and price. The VA logs requested-but-unauthorized changes in a pending-authorization section, cites the work performed to date, and poses the authorization question to the reviewer weekly. Verbal approvals are recorded as claimed with the date and parties named, but do not move the change into the billable schedule until written confirmation arrives.
Retainage tracking on September 28, 2026 runs as a separate ledger inside the packet because retainage behaves differently from ordinary receivables. Each invoice contributes its withheld percentage to a cumulative retainage balance by project, with release conditions quoted from the contract, substantial completion dates recorded when certified, and release invoices linked when issued. Retainage that remains unreleased past its contractual release trigger appears as an aged exception with the blocking condition named, whether it is punch-list completion, lien waiver delivery, or customer sign-off. The VA never writes off or discounts retainage without reviewer approval.
A useful review sequence for September 28, 2026
Example on September 28, 2026: A remodeling contractor on September 28, 2026 holds a $120,000 fixed-price contract with four 25 percent milestones of $30,000 each and 10 percent retainage. Milestones one and two are complete, invoiced, and collected net of $6,000 retainage held. Milestone three is certified complete September 26 by the project lead with photo evidence, but no invoice has been issued. Milestone four is 40 percent complete and not yet billable. A $4,500 change order for upgraded fixtures has been performed with only verbal customer approval.
The VA on September 28, 2026 prepares the packet showing $60,000 billed, $54,000 collected, $6,000 retainage held, a $30,000 completed-but-unbilled milestone three, and a $4,500 unauthorized change order, then poses three reviewer questions: approve the milestone three invoice at the contract amount less retainage, authorize written follow-up on the change order before further work, and confirm the milestone four billing trigger. The owner approves the milestone three invoice, directs the change order confirmation letter, and sets the milestone four evidence standard. The packet preserves the contract reconciliation at $120,000 agreed, $60,000 billed, $60,000 remaining plus the pending change. Firms that repeat this review per billing cycle can connect it to the month-end close packet for cutoff alignment and to Get a free VA consultation when assigning standing billing ownership.
Billing calendar and cutoff discipline on September 28, 2026
Progress billing fails most often on timing rather than arithmetic on September 28, 2026, so the packet enforces a billing calendar with cutoff rules. Each project carries a billing date, typically month end or a contractual application date, and a cutoff hour after which newly certified milestones roll to the next cycle. The VA assembles the draft application three business days before the billing date, giving the reviewer time to verify completion evidence without forcing invoices out on unreviewed milestones. Milestones certified after cutoff appear in a certified-unbilled section that the next cycle opens with, so completed work is never lost between periods and cutoff timing never becomes an excuse for stale billing.
Cutoff honesty on September 28, 2026 also governs the period close. Invoices dated before period end for work certified after period end misstate both revenue and receivables, while completed work left unbilled across a period boundary understates them. The packet therefore records both the certification date and the invoice date per milestone, and the reviewer confirms at close that certified-but-unbilled and billed-but-uncertified items are correctly stated. Retainage release invoices receive the same discipline: the release is dated when contractually earned and certified, not when cash arrives, with collection tracked separately so earned-but-uncollected retainage stays visible as a receivable rather than vanishing into a cash-basis assumption.
Customer dispute evidence file on September 28, 2026
Disputed applications for payment on September 28, 2026 need their own evidence file because disputes turn on documentation quality as much as on work quality. The dispute file for each contested invoice records the customer's stated objection verbatim with date and source, the contract clause or milestone definition at issue, the completion evidence the business relies on, correspondence history with dates and commitments, and the amounts in three buckets: agreed, disputed, and withheld as retainage against the disputed work. The VA maintains this file without negotiating; negotiation positions and settlement authority remain with the owner.
Back-charges and offsets claimed by the customer on September 28, 2026 receive symmetrical treatment. A customer deduction for alleged defects, delays, or cleanup is logged as a claimed offset with the customer's documentation cited, matched against the business's own records of the same events, and routed to the reviewer as an exception rather than netted silently against the receivable. Accepting a back-charge requires the same written approval as any other cost, and accepted back-charges post as their own documented transactions linked to the dispute file. This prevents the common failure where a short-paid invoice is written down to cash received with no record of what the customer claimed or whether the claim had merit, which destroys both collection leverage and margin history.
Limitations and what would change the conclusion
This brief on September 28, 2026 does not determine revenue recognition timing; recognition is an accounting decision for the owner and their accountant, and the packet supports that decision without making it. It does not address cost-plus contracts, time-and-materials billing, or percentage-of-completion accounting methods, each of which needs its own evidence design. It assumes milestone definitions in the contract are objectively verifiable; vague milestones such as substantial progress require contract clarification before any packet can track them reliably.
The conclusion on September 28, 2026 is that a milestone-level billing packet with an embedded retainage ledger, maintained by the VA and approved by the owner, converts progress invoicing from a calendar habit into an inspectable control. The packet works because it reconciles contract value every cycle, isolates retainage from ordinary receivables, and keeps unauthorized change work visible until it is authorized or stopped.
Sources verified September 28, 2026
- IRS: Publication 334 Tax Guide for Small Business
- IRS: Publication 583 Starting a Business and Keeping Records
- IRS: What kind of records should I keep?
- SBA: Manage Your Finances
- SBA: Fund Your Business
- GAO: Standards for Internal Control
- Intuit: Set up progress invoicing in QuickBooks Online
A statement that restates source language is labeled a fact as of September 28, 2026. Guidance on how to stage that fact in a VA packet is analysis for September 28, 2026.
Related QBOAssistant coverage
- QuickBooks VA services overview maps preparation versus approval across receivables work.
- Bookkeeping VA tasks guide places milestone tracking among recurring tasks.
- Bank reconciliation support packet ties collected milestone payments to cleared deposits.