PTO Accrual Support Schedule for September 28 in QuickBooks Online

September 28, 2026

Bottom line: Keep PTO balances reviewable on September 28, 2026 by maintaining one support schedule per employee that ties earned hours, taken hours, and remaining balances to payroll records in QuickBooks Online, with negative balances and policy caps flagged in plain language. The useful output on September 28, 2026 is an owner-ready schedule with 212 accrued hours reconciled across 18 employees and 5 cap breaches routed for decisions, not a set of disconnected time-off requests.

Why this matters on September 28, 2026

On September 28, 2026, small business owners need payroll records that an accountant can trace without rebuilding time-off history from messages and spreadsheets. A PTO accrual support schedule makes the next payroll and staffing decision easier to see. It gives the reviewer a dated list of who earned what, who took what, and what remains, with each line tied to a payroll record or an approved time-off source. When the schedule is current on September 28, 2026, the owner can approve a time-off request, plan coverage, or confirm a payout amount without guessing whether the balance shown in a payroll screen matches supporting detail.

A virtual assistant handles routine preparation for this schedule. The VA gathers approved time-off requests, pulls payroll records showing PTO earned and PTO paid, compares balances to the written accrual policy, and flags negative balances and cap breaches for review. The owner or accountant keeps approval for policy interpretation, payout authorization, and payroll corrections. That separation protects the September 28, 2026 records from informal adjustments where a manager approves extra days by message and the payroll balance never reflects the agreement. Owners deciding what to delegate can review role boundaries on the services page, see practical delegation patterns in the bookkeeping tasks guide, and confirm payroll input discipline in the payroll inputs checklist.

Without a defined schedule, PTO evidence scatters across payroll screens, time tracking exports, approved request messages, and handwritten notes. The VA sees a balance in QuickBooks Online but cannot tell whether recent time off was recorded, whether an accrual rate changed after a tenure milestone, or whether a cap should have stopped further accrual. The September 28, 2026 schedule restores that visibility by recording the policy rate applied, the source for hours taken, the resulting balance, and the specific question for the reviewer in one place. Related discipline for payroll inputs appears in the payroll inputs checklist, and the close linkage for labor liabilities is explained in the month-end close packet.

Example on September 28, 2026: A dental practice with 18 employees maintains PTO under a written policy with accrual by tenure band and a maximum carryover cap. On September 28, 2026 the VA prepares a support schedule showing 212 accrued hours remaining across the team, built from 486 earned hours and 274 taken hours tied to payroll records. The review flags 5 cap breaches where employees reached the maximum balance and further accrual must pause or require a written exception, plus 2 negative balances where taken hours exceed earned hours because unrecorded partial-day absences were entered as paid time off. Without a schedule the owner would approve two new time-off requests that push capped employees further past the limit and would miss the negative balances until a separation payout dispute. With the September 28, 2026 schedule the VA ties each employee line to payroll records, attaches the tenure band and rate applied, isolates the 5 cap cases as one policy decision group, and routes the 2 negative balances as correction questions with source detail. That one review prevents two over-limit approvals and leaves a short list of dated owner questions instead of a full-team balance dispute.

Build the employee population on September 28, 2026

Start with a complete roster on September 28, 2026 and state the source for each line. List every active employee included in the PTO policy, plus any separated employees with a remaining payout question still open on September 28, 2026. Record the hire date basis used for tenure bands, the accrual rate applied, the policy cap that applies to each employee, and the payroll record source showing earned and taken hours. Keep the original payroll export and the time-off source export with a September 28, 2026 timestamp so a later reviewer can reproduce the 18-line starting point.

State what is excluded from the September 28, 2026 schedule. Unpaid leave, holiday schedules, sick leave buckets governed by a separate policy, contractor time, and unapproved requests without a decision maker note are not part of this PTO balance. That boundary keeps the 212-hour total honest and prevents a reviewer from assuming broader coverage than provided. If an employee transferred between full time and part time status, note the effective basis for accrual on September 28, 2026 and preserve the earlier rate beside the current rate so the change is visible.

Confirm roster changes before calculating balances on September 28, 2026. Add new hires with a start-accrual marker, remove separated employees only after the payout question is resolved, and flag status changes that alter the accrual rate. For the dental practice example, the VA confirms 18 active employees on September 28, 2026, verifies that two hygienists crossed a tenure threshold that raises the accrual rate, and records the rate change date basis in the schedule notes. That step prevents a full-schedule error where every later balance inherits a wrong rate from one missed tenure update.

Tie earned and taken hours to payroll records on September 28, 2026

For each employee, record earned hours, taken hours, adjustments, and the resulting balance on September 28, 2026, with the payroll record reference beside each figure. Earned hours come from payroll records reflecting the policy accrual for the period covered by the September 28, 2026 review. Taken hours come from payroll records showing PTO paid plus approved time-off sources for days not yet processed through payroll. When the two sources disagree, preserve both values and route the difference as a question rather than forcing a match by editing one side.

Pay particular attention to partial-day absences, schedule changes, and corrections on September 28, 2026. A four-hour early departure recorded as a full PTO day creates a false taken amount that compounds across the 18-person roster. A schedule change from five days to four days without a policy note creates confusion about whether accrual should prorate. Capture the source line that supports the observation on September 28, 2026, including the payroll check date basis, the hours shown, and the time-off approval reference, then state what an authorized reviewer must decide, such as correct the taken entry, confirm the accrual rate, or approve a written exception.

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 earned and taken tie-out; an authorized reviewer records the correction or payout approval.

Flag caps and negative balances as decisions on September 28, 2026

Group cap breaches together on September 28, 2026 so one policy answer can clear a pattern. For each of the 5 flagged employees, show the cap limit, the current balance, the excess or paused accrual amount, and the options available under the written policy, such as pause accrual, require use within a defined window managed by the owner, or approve a written carryover exception. Do not adjust a capped balance without written approval recorded on September 28, 2026. Preserve the original calculated balance beside any approved exception so the schedule shows both the policy result and the authorized deviation.

Treat negative balances as correction questions on September 28, 2026, not as automatic deductions. For each negative case, show the earned total, the taken total, the negative remainder, and the likely cause supported by evidence, such as an advance approved in writing, a data entry error on taken hours, or a missing accrual line in payroll records. Route the item to the owner or accountant with a specific request, for example confirm whether the two-hour negative balance for one front-desk employee reflects an approved advance or a four-hour taken entry that should have been two hours. This keeps a payroll correction from being presented as a disciplinary finding.

Follow a short review sequence on September 28, 2026. First, confirm the roster and tenure rates. Second, tie earned hours to payroll records. Third, tie taken hours to payroll and approval sources. Fourth, calculate balances and compare each to the cap. Fifth, write one specific question for every cap breach and every negative balance and assign the next reviewer. Avoid vague notes such as check PTO and write confirm carryover exception or correct taken hours for the named employee before the next payroll instead.

What to put in the September 28, 2026 handoff

Add a second view grouped by flag type so the owner can clear patterns at once. For instance, list all 5 cap breaches together with balances and policy options on September 28, 2026, then ask the owner to approve one consistent approach for capped employees rather than five separate exceptions. Keep reconciled employees in a separate completed section from flagged employees so progress is visible without losing the remaining questions. If the schedule feeds a close packet such as the month-end close packet or payroll review work in the payroll inputs checklist, link them explicitly.

Keep the queue useful on September 28, 2026

Do not close a PTO flag just because coverage is tight. Do not edit earned or taken hours to make a balance look acceptable when the source detail shows a gap. Preserve the original payroll value beside any proposed correction, and attach the approval reason after the authorized reviewer approves it. On September 28, 2026, a visible waiting state with a named reviewer is more useful than a quiet edit that hides a cap breach until a payout dispute.

Filter the queue so the owner sees payout and separation questions first on September 28, 2026, then negative balances, then cap breaches, then routine accrual confirmations. Group items with the same root cause together so one confirmation clears a pattern, for example both negative balances tied to partial-day entry errors. Keep the 212-hour reconciled total visible at the top so the reviewer sees the population size beside the 7 flagged lines that still need judgment. If time-off requests arrive after the schedule is prepared on September 28, 2026, log them as new items with approval references rather than overwriting the reviewed balances.

Practical handoff note for September 28, 2026

End the file with the September 28, 2026 review date, the number of employees 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 18 employees were reconciled, 212 accrued hours remain supported by 486 earned hours and 274 taken hours, 5 cap breaches are routed as a policy decision group, and 2 negative balances are routed as correction questions with named reviewers. If the work touches a close review, link it to the related close packet and keep the payroll and time-off exports with the queued questions.

Archive the packet with the payroll record export, the time-off approval export, the policy basis note, and evidence links so a later reviewer can repeat the check. Keep the archive location consistent and limit access to the approved payroll team on September 28, 2026. A reviewer should be able to answer five questions quickly after reading the packet: what roster was covered, what payroll records supported earned and taken hours, which balances hit caps, which balances went negative and why, and who owns each open decision. That clarity keeps PTO balances 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
• IRS Publication 15 for payroll record and procedure context on September 28, 2026
• SBA Manage Your Finances for payroll and staffing cadence on September 28, 2026
• QuickBooks Online Support for payroll and employee record workflows on September 28, 2026
• Internal: services page, bookkeeping tasks guide, payroll inputs checklist, and month-end close packet for delegation boundaries on September 28, 2026

Owner CTA for September 28, 2026

If PTO balances are still tracked across payroll screens and message threads on September 28, 2026, define the accrual schedule and the payout approval path before the next payroll. Get a free VA consultation to map the first handoff with a named owner and a review cadence for September 28, 2026. Keep payouts, policy exceptions, and payroll corrections with an authorized reviewer on September 28, 2026.