Sales Commission Support Schedule for September 28 in QuickBooks Online
September 28, 2026
Bottom line: Keep commissions reviewable on September 28, 2026 by computing one support schedule per sales rep that ties the commission base, the plan rate, adjustments, and the payable amount to sales and collections evidence in QuickBooks Online. The useful output on September 28, 2026 is an owner-ready schedule covering 6 reps and a 41,200 commission base with 2 split-deal questions routed, not a payout list without sources.
Why this matters on September 28, 2026
On September 28, 2026, small business owners need commission work that an accountant can verify without rebuilding sales detail from separate rep sheets. A sales commission support schedule makes the payout decision easier to see. It gives the reviewer a dated population of reps and deals, a short evidence trail back to invoices, receipts, or sales reports in QuickBooks Online, and a clear list of rate and split questions that still need judgment. When the schedule is prepared on September 28, 2026, the owner can approve each payout, resolve a split, or confirm a tier calculation without guessing what the preparer already checked.
A virtual assistant handles routine preparation for this schedule. The VA pulls sales and collections data, applies the written plan rates, separates eligible from ineligible lines, documents splits and adjustments, and flags questions for review. The owner or accountant keeps approval for payouts, split decisions, plan interpretation, and accounting treatment. That separation protects the September 28, 2026 records from informal deals where a rep expects commission on a cancelled order or a discounted sale that the plan excludes. Owners deciding what to delegate can review role boundaries on the services page, see practical delegation patterns in the bookkeeping tasks guide, and confirm sales evidence discipline in the invoice entry workflow.
Without a defined schedule, commission evidence scatters across sales reports, invoice copies, payment receipts, credit memos, rep messages, and unlinked QuickBooks Online attachments. The VA sees a sales total but cannot tell whether the orders shipped, whether the customer paid, whether a return reduced the base, or whether two reps share one deal. The September 28, 2026 schedule restores that visibility by recording the source location, the base amount, the rate applied, the adjustment reason, and the specific question for the reviewer in one place. Related discipline for receivables appears in the AR aging review, and the close linkage is explained in the month-end close packet.
Example on September 28, 2026: An equipment dealer pays 6 reps under a tiered plan with higher rates above defined sales thresholds and reduced rates for discounted orders. On September 28, 2026 the VA prepares a support schedule showing a 41,200 commission base drawn from 268,000 in eligible sales, with 12,400 excluded for cancelled orders, unpaid balances past the plan cutoff basis, and discount-tier reductions. The calculated payable totals 3,860 before owner approval, including tier uplifts of 420 for two reps who cleared the threshold and discount adjustments of 310 across four orders. Without a schedule the owner would pay on the full 268,000 plus excluded lines and overpay by an estimated 940. With the September 28, 2026 schedule the VA ties each rep line to invoice and receipt evidence in QuickBooks Online, isolates 2 split-deal questions where two reps claim the same commercial account order, and routes the tier and discount math as a reviewable calculation. That one review prevents the 940 overpayment and leaves two batched owner questions instead of six separate payout disputes.
Define the commission population on September 28, 2026
Write down the reps covered, the plan version basis, the base definition used, the QuickBooks Online sales and collections sources, filters, export times, and preparation date of September 28, 2026. Keep the original sales detail export, the collections or receipt export, the credit memo export, and the plan summary used for rates. If a payment or credit posts during the review after the first export, preserve the earlier snapshot and note what changed on September 28, 2026. That preserves traceability for the September 28, 2026 schedule and lets a later reviewer reproduce the 41,200 base starting point.
State whether commission is calculated on booked sales, shipped sales, or collected receipts. For this September 28, 2026 schedule, the practical approach is to follow the written plan exactly and state the basis in the file, for example collected receipts applied to eligible product sales in the September 28, 2026 review, net of returns and cancellations. Record the threshold and tier definitions used so the September 28, 2026 calculation can be reproduced, including the sales levels that trigger higher rates and the discount levels that trigger reduced rates.
State what is excluded. Cancelled orders, unpaid balances that fail the plan collection test, intercompany transfers, parts sold at cost under a service accommodation, sales tax and freight lines, and deals closed outside the plan coverage are not part of this September 28, 2026 base. That boundary keeps the commission base honest and prevents a reviewer from assuming broader coverage than provided. If the schedule touches receivables work, link it to the related review such as the AR aging review and keep the source exports with the queued questions.
Apply plan rates with visible math on September 28, 2026
For each rep, record the eligible base, the tier rate applied, the gross calculation, adjustments, and the resulting payable on September 28, 2026, with invoice and receipt references beside each line. Show tier math explicitly so the reviewer can follow the uplift without recalculating from raw data. Show discount reductions explicitly with the order reference and the plan clause basis. When a deal sits near a threshold, preserve both the base figure and the threshold figure so the reviewer sees how close the tier decision is on September 28, 2026.
Pay particular attention to returns, partial payments, and discount codes on September 28, 2026. A return posted as a credit memo after the sales export reduces the base and can move a rep below a tier. A partial customer payment may fail the plan collection test and must stay out of the base until the balance clears. A discount code may trigger a reduced rate rather than full exclusion. Capture the source line that supports the observation on September 28, 2026, including invoice number, receipt reference, credit memo reference, and amount, then state what an authorized reviewer must decide, such as confirm the tier, approve the discount treatment, or hold one deal for the next review.
Sidebar: Evidence notes describe what was seen on September 28, 2026. Decisions describe who approved what and when. Keep those two layers distinct. A VA prepares the rate math and ties each line to sales evidence; an authorized reviewer records the payout approval.
Resolve splits and exceptions as questions on September 28, 2026
Isolate split deals in their own section on September 28, 2026 so one decision clears the dispute. For each of the 2 split-deal questions, show the order value, the reps involved, the claimed shares, the customer evidence, and the plan language basis for splitting or assigning the deal. Do not divide a commission by assumption when the plan requires owner assignment or documented agreement. Preserve each claimed amount beside the VA-proposed treatment so the September 28, 2026 file shows both the request and the evidence-based option.
Treat threshold and discount edge cases as explicit questions on September 28, 2026, not as silent inclusions. For each edge case, show the base with and without the disputed line, the payable under each reading, and the dollar effect of the decision. Route the item to the owner with a specific request, for example approve a 60 and 40 split of the 8,400 commercial order between two named reps based on attached activity notes, or confirm that a discounted order at the stated discount level earns the reduced rate shown. This keeps a compensation decision from being presented as a reporting output.
Follow a short review sequence on September 28, 2026. First, confirm the 6-rep roster and the plan version basis. Second, build the eligible base from sales and collections evidence with exclusions documented. Third, apply tier and discount math with visible calculations. Fourth, isolate splits and edge cases with dollar effects shown. Fifth, write one specific payout or split question per open item and assign the owner as reviewer on September 28, 2026. Avoid vague notes such as check commissions and write approve 3,860 total payout with 2 splits held for separate decision instead.
What to put in the September 28, 2026 handoff
| Field | What to record on September 28, 2026 |
|---|---|
| Scope | Reps covered, plan version basis, base definition, report names, and preparation date of September 28, 2026 |
| Rep line | Eligible base, tier rate applied, gross calculation, adjustments, and payable with source references |
| Evidence | Invoice location, receipt location, credit memo reference, or explanation for missing support |
| Exclusions | Cancelled, unpaid, discounted, and out-of-plan lines with amounts and reasons |
| Split group | Order value, reps involved, claimed shares, and proposed treatment with dollar effect |
| Question | The payout, split, or plan interpretation decision still needed, in plain language |
| Owner | Person responsible for payout approval and rep communication |
Add a second view grouped by payout status so the owner can approve clean lines at once. For instance, list the 4 reps without disputes together with payable amounts and evidence references on September 28, 2026, then ask the owner to approve those payouts while holding the 2 split-affected reps for a separate decision. Keep supported lines in a separate approved section from held lines so progress is visible without losing the remaining questions. If the schedule feeds a close packet such as the month-end close packet or sales workflow work in the invoice entry workflow, link them explicitly.
Keep the queue useful on September 28, 2026
Do not close a commission question just because payroll timing is tight. Do not pay a disputed split to keep the peace when the evidence shows shared activity without an agreed share. Preserve the original calculated payable beside any proposed split or adjustment, and attach the reason for a change after the authorized reviewer approves it. On September 28, 2026, a visible held state with a named owner decision is more useful than a rushed payout that creates a clawback conversation.
Filter the queue so the owner sees held splits first on September 28, 2026, then tier edge cases, then discount treatments, then clean approvals. Group items with the same root cause together so one confirmation clears a pattern, for example both split questions tied to the same commercial account handoff. Keep the 41,200 base and the 3,860 calculated payable visible at the top with held amounts shown separately, so the reviewer sees the population size beside the open questions. If new receipts arrive after the schedule is prepared on September 28, 2026, log them as dated additions with source references rather than overwriting the reviewed base.
Practical handoff note for September 28, 2026
End the file with the September 28, 2026 review date, the number of reps checked, the unresolved questions, and the next checkpoint. The goal is a record another person can pick up without reconstructing the September 28, 2026 work. For this schedule, state that 6 reps were calculated, the 41,200 commission base ties to 268,000 in eligible sales with 12,400 excluded and documented, the calculated payable of 3,860 is ready subject to owner approval, and 2 split-deal questions are open with named reviewers and dollar effects shown. If the work touches a close review, link it to the related close packet and keep the sales, receipt, and credit memo exports with the queued questions.
Archive the packet with the sales detail export, the collections export, the credit memo export, the plan basis note, split evidence, and calculation notes so a later reviewer can repeat the check. Keep the archive location consistent and limit access to the approved finance team on September 28, 2026. A reviewer should be able to answer five questions quickly after reading the packet: what reps and sales were covered, what evidence supported the 41,200 base, how tier and discount math was applied, what splits remain open, and who owns each payout approval. That clarity keeps commissions explainable while keeping authority where it belongs on September 28, 2026.
Sources and further reading for September 28, 2026
- IRS Recordkeeping for supporting document retention on September 28, 2026
- IRS Publication 334 for small business recordkeeping context on September 28, 2026
- SBA Manage Your Finances for sales reporting and control cadence on September 28, 2026
- QuickBooks Online Support for sales and reporting workflows on September 28, 2026
- Internal: services page, bookkeeping tasks guide, invoice entry workflow, and AR aging review for delegation boundaries on September 28, 2026
Owner CTA for September 28, 2026
If commissions are still calculated across rep sheets and message threads on September 28, 2026, define the support schedule and the payout approval path before the next payout. Get a free VA consultation to map the first handoff with a named owner and a review cadence for September 28, 2026. Keep payouts, splits, and plan interpretations with an authorized reviewer on September 28, 2026.
QuickBooks VA workflow table
| Workflow area | What the VA prepares |
|---|---|
| Daily queue | Invoices, receipts, bank feeds, and open QuickBooks questions |
| Weekly review | Owner approvals, exception list, and unresolved transaction notes |
| Monthly packet | Reports, missing documents, and accountant-ready source material |
Related resources
Compare the service fit on the QuickBooks VA services page, then use the free consultation form to map the first handoff. For platform context, review QuickBooks Online.