Petty Cash Expense Support Log for September 25 in QuickBooks Online

September 25, 2026

Bottom line: On September 25, 2026, stop treating petty cash as too small to document. Keep one dated support log in QuickBooks Online where every cash payout has a photo, an expense account, a business purpose note, and a reimbursement status. The useful output on September 25, 2026 is a complete replenishment packet the owner can approve without hunting for slips.

Why this matters on September 25, 2026

On September 25, 2026, petty cash leakage rarely comes from one large misuse. It comes from thirty small payouts with missing slips, vague descriptions such as supplies, and reimbursements entered to the wrong expense account. Over a quarter, those gaps distort office, mileage, meal, and repair totals in QuickBooks Online and leave the owner unable to explain variances. A petty cash expense support log prepared on September 25, 2026 restores accuracy by forcing each payout to carry its own evidence before it is coded. That discipline keeps small cash spending reviewable at the same standard as vendor bills.

A bookkeeping virtual assistant can own the tedious parts on September 25, 2026 without owning the judgment. The VA photographs slips, logs date and payee and amount, matches each line to the narrowest expense account in QuickBooks Online, flags personal versus business questions, and queues out-of-pocket reimbursements for approval. The owner approves the coding and the cash replenishment. For teams mapping those boundaries, the QuickBooks VA services page clarifies preparation versus approval, while the bookkeeping tasks guide shows where petty cash fits beside bank feed review and receipt matching on September 25, 2026.

Without a log, petty cash lives in a metal box, a glove compartment envelope, and a drawer of faded thermal receipts. The September 25, 2026 review fixes that by recording the cash box count, the outstanding advances, and the specific question for every unsupported line in one packet. When the owner reviews on September 25, 2026, the decision is clear: approve the account coding, request a replacement slip, or decline the reimbursement with a reason. Linking the log to the bank reconciliation support packet and the month-end close packet also keeps cash withdrawals and reimbursed expenses tied to bank activity on September 25, 2026.

Example on September 25, 2026: A field services business counts 38 cash expenses totaling 3,120 dollars for the period ending on September 25, 2026. The VA logs each payout on September 25, 2026 with a phone photo, payee, amount, and purpose note. Twenty nine lines have clear slips and match cleanly: 940 dollars to vehicle fuel and parking, 680 dollars to job supplies, 420 dollars to postage and courier, 310 dollars to office refreshments for crew onboarding, and the remainder to small hardware and safety items. Nine lines totaling 615 dollars are missing slips on September 25, 2026: three fuel purchases with no receipt, two parking stubs faded beyond reading, two supply runs paid by a technician out of pocket with only a credit card notification, and two meal purchases where business purpose is unclear. The VA codes the supported lines, holds the nine exceptions with photos of the log pages and card notifications, and routes three batched owner questions. The owner approves six, requests two replacement receipts, and declines one personal meal on September 25, 2026. Replenishment is documented to the dollar.

Start with a defined population on September 25, 2026

Write down the cash sources, count method, and period covered ending on September 25, 2026 before coding anything. Record the opening cash box balance, the counted cash on hand on September 25, 2026, outstanding advances to staff, and out-of-pocket claims submitted but not yet reimbursed. Photograph the count sheet and the cash box log page with a timestamp reference to September 25, 2026. Save the original photos without cropping out dates or totals. If additional slips arrive after the count, log them as a second batch with their own receipt date reference tied to September 25, 2026 preparation rather than backdating them into the first count.

State the coverage rule on September 25, 2026. For example, the log covers all petty cash payouts and all employee out-of-pocket claims under 200 dollars for the period ending on September 25, 2026, including fuel, parking, postage, small supplies, and crew meals with a documented business purpose. Larger purchases routed through bill or card are out of scope for this log but cross-referenced so the reviewer sees the boundary. Advances not yet spent are listed as outstanding advances, not expenses, on September 25, 2026. That distinction prevents unspent cash from inflating expense totals in QuickBooks Online on September 25, 2026.

State what is excluded and how replenishment is calculated on September 25, 2026. Items without a business purpose, items dated outside the period ending on September 25, 2026, and duplicate claims already reimbursed through payroll or bill are not part of the replenishment total. Show the math: opening balance minus supported payouts minus approved out-of-pocket reimbursements equals expected cash on hand, reconciled to the physical count on September 25, 2026. If the math does not tie, record the shortage or overage as its own exception line rather than burying it in supplies on September 25, 2026.

Separate evidence from judgment on September 25, 2026

For each payout, record the date within the period ending on September 25, 2026, payee or vendor, amount, business purpose in plain words, QuickBooks Online expense account proposed, and photo location on September 25, 2026. A slip photo, a card notification screenshot paired with a purpose note, or a signed advance slip may support the line. The presence of a payout in the cash log is not proof the expense account is correct or that the purchase was for business use. Those conclusions require owner review on September 25, 2026.

For petty cash work, pay particular attention to faded thermal slips, split purchases where only part is business related, round-dollar advances with no itemization, and out-of-pocket claims missing a purpose note on September 25, 2026. Capture the exact evidence gap, then state what the owner must decide. For example, note that a 68-dollar meal on September 25, 2026 preparation shows two crew members but no client or job reference, and ask the owner to confirm business purpose or mark it personal. Note that a 145-dollar supply run has only a card notification and ask for a replacement slip or a written confirmation of items purchased on September 25, 2026. This keeps factual logging separate from reimbursement approval on September 25, 2026.

Sidebar: Evidence notes describe what was seen on September 25, 2026. Decisions describe who approved the account coding and reimbursement and when. Keep those two layers distinct. A VA prepares the observation; an authorized reviewer records the decision.

A useful review sequence for September 25, 2026

1. Count and photograph on September 25, 2026. Count cash on hand, list outstanding advances, gather all slips and out-of-pocket claims for the period ending on September 25, 2026, and photograph each slip before ink fades further. Save the count sheet with a reference to September 25, 2026.
2. Log every payout in one table on September 25, 2026. Enter date, payee, amount, purpose, advance versus direct payout flag, and photo file name. Total the 38 lines to 3,120 dollars and subtotal by purpose group so the owner sees concentration on September 25, 2026.
3. Match each line to the narrowest QuickBooks Online expense account on September 25, 2026. Use fuel, parking, postage, job supplies, office, meals with business purpose, and safety equipment separately rather than defaulting everything to office expense. Flag any line where two accounts could apply and state the question on September 25, 2026.
4. Queue reimbursements and replenishment separately on September 25, 2026. Mark supported lines as ready for coding, missing-slip lines as awaiting owner decision, and out-of-pocket claims as ready for reimbursement only after approval on September 25, 2026. Calculate the replenishment check as a separate line the owner authorizes.
5. Write one specific question per exception and assign the owner on September 25, 2026. Avoid vague notes such as missing receipt. Write confirm 68-dollar crew meal business purpose for job 412 on September 25, 2026 based on attached photo, or approve 145-dollar supply reimbursement to technician Alvarez pending replacement slip, instead.

What to put in the September 25, 2026 handoff

Add a second view grouped by evidence gap on September 25, 2026 so the owner can clear all faded parking stubs together, all out-of-pocket claims awaiting purpose notes together, and all personal-use questions together. Include a cash proof that ties opening balance to payouts to expected on-hand to counted on-hand on September 25, 2026. That proof turns a shoebox of slips into an auditable packet on September 25, 2026.

Keep the queue useful on September 25, 2026

Do not code an unsupported payout to a placeholder account just to clear the list on September 25, 2026. Keep the nine missing-slip lines visible with their 615-dollar subtotal until the owner decides on September 25, 2026. Preserve the original purpose note beside any reclassification and attach the approval reason after the owner approves it. On September 25, 2026, a visible waiting state protects the profit and loss detail more than a forced completion.

Filter the packet so the owner sees money-out decisions first on September 25, 2026. Lead with reimbursement approvals and replenishment amount, follow with account coding confirmations, and close with the full 38-line log for reference. If the log feeds broader close work, link it to the month-end close packet so the reviewer sees expense completeness on September 25, 2026. For owners evaluating ongoing support, the services overview maps cash handling preparation to approval controls, and the contact page routes the first log setup to a named owner on September 25, 2026. The bookkeeping tasks guide shows how weekly cash logs reduce catch-up effort on September 25, 2026.

Practical handoff note for September 25, 2026

End the file with the review date of September 25, 2026, the 38 expenses and 3,120 dollars checked, the nine missing slips with owners assigned, and the replenishment amount awaiting approval. Note which lines are ready to post and which lines are held pending slips or purpose confirmation on September 25, 2026. The goal is a record another bookkeeper can pick up without re-counting the box or re-reading faded slips from work completed on September 25, 2026. Keep the photos, count sheet, and reimbursement queue together so every posted expense traces back to evidence on September 25, 2026.

Sources and further reading for September 25, 2026

• IRS Recordkeeping for supporting document retention on September 25, 2026
• IRS Publication 334 for small business expense record context on September 25, 2026
• SBA Manage Your Finances for cash handling cadence on September 25, 2026
• QuickBooks Online Support for expense entry and attachment workflows on September 25, 2026
• Bookkeeping tasks guide and bank reconciliation support packet for delegation boundaries on September 25, 2026

Owner CTA for September 25, 2026

If petty cash still lives in envelopes and faded slips on September 25, 2026, define the photo log and approval path before the next replenishment. Get a free VA consultation to map the first handoff with a named owner and a review cadence for September 25, 2026. Keep account coding, business purpose approval, and cash authorization with an authorized reviewer on September 25, 2026.