Bank Fee and Interest Review Log for September 28 in QuickBooks Online

September 28, 2026

Bottom line: Log every bank fee and interest line on September 28, 2026 so each charge has a statement source, a QuickBooks Online coding decision, and a clear flag when the amount looks unusual or disputable. The useful output on September 28, 2026 is a dated review log where routine monthly charges are confirmed, interest income is tied to the correct account, and a short flagged list with dollar amounts goes to the owner, not a bank statement left unexamined in the feed.

Why this matters on September 28, 2026

On September 28, 2026, small business owners need bank fee and interest records in QuickBooks Online that an accountant can trust without re-reading three statements line by line. Fees hide inside bank feeds as small generic withdrawals, and interest posts as small deposits with vague descriptions. When neither line gets a deliberate coding decision on September 28, 2026, the books accumulate miscoded bank charges in office expense, interest income in the wrong account, and duplicate entries where a feed line and a manual entry both record the same monthly service charge. A review log fixes that by listing every fee and interest line once, recording the coding for each, and separating routine items from items that need judgment.

A virtual assistant handles the daily preparation for this log. The VA pulls the statements or bank activity for the accounts in scope, lists each fee and interest line with date and amount, matches each line to its QuickBooks Online transaction, and checks whether the coded account and payee logic matches the house pattern. The owner or accountant keeps approval for disputes, write-offs of disputable charges, reclassification of miscoded items, and confirmation of interest treatment. That separation protects the September 28, 2026 records from quiet assumptions where a onetime analysis charge spike gets coded as a routine monthly fee and never questioned. Owners deciding what to delegate can review role boundaries on the services page, see practical delegation patterns in the bookkeeping tasks guide, and route the first handoff through the contact page.

Without a defined log, evidence for small charges scatters across bank portals, paper statements, feed memos, and unlinked QuickBooks Online attachments. The VA sees a $145 charge labeled analysis service but cannot tell whether it matches the prior pattern, whether it belongs to a different account, or whether it duplicates a fee already recorded. The September 28, 2026 review restores that visibility by recording the source location, the statement description, the QuickBooks Online transaction reference, the coded account, and the specific question for the reviewer in one place. Related discipline for outstanding bank items appears in the bank reconciliation support packet, and the close linkage is explained in the month-end close packet.

Example on September 28, 2026: An e-commerce seller operates 3 accounts on September 28, 2026: one operating checking account, one marketplace payout account, and one business savings account. Across the review window the VA lists 22 fee lines totaling $1,240 and 6 interest lines totaling $84 in income. Routine items include monthly maintenance fees, per-item transaction charges, wire fees for two supplier payments, and credit card processing passthrough charges that post through the bank. The VA confirms 19 fee lines totaling $930 as routine and correctly coded to bank service charges, then flags $310 across 3 lines: two overdraft charges of $35 each on the operating account tied to a payout timing gap, and one $240 analysis charge spike on the marketplace account where the prior pattern averaged near $95. Interest of $84 across the savings account ties to the bank statement and is confirmed in interest income. Without the log the owner would absorb the $240 spike as a normal fee. With the September 28, 2026 log the VA attaches the statement lines, shows the prior-pattern comparison, confirms the two overdraft lines are coded but need a cash-timing decision, and routes three flagged questions instead of leaving $310 unexamined.

Build a complete fee and interest population on September 28, 2026

Write down the accounts, the statement period, the QuickBooks Online report or list, filters, export times, and preparation date of September 28, 2026. Keep the original bank statements or bank activity exports and the QuickBooks Online transaction list export for the same window. If a bank posts a late fee after the first export, preserve the earlier snapshot and note what changed. That preserves traceability for the September 28, 2026 review and lets a later reviewer reproduce the starting population of 22 fee lines and 6 interest lines.

State whether the review covers every bank account or only the accounts in scope. For this September 28, 2026 log, the practical approach is to name all 3 accounts, list every fee and interest line above zero, and record a scope statement so the population can be reproduced, for example all bank service charges, overdraft charges, analysis charges, wire fees, and interest income posted to the operating, payout, and savings accounts in the window ending September 28, 2026. Record the threshold plainly so the September 28, 2026 review does not drift into unrelated card processing fees booked inside sales receipts.

State what is excluded. Merchant discount fees netted inside marketplace payouts and recorded through sales receipts, credit card annual fees billed on a card statement rather than a bank statement, and payroll tax penalties are not part of this September 28, 2026 fee log. That boundary keeps the flagged list honest and prevents a reviewer from assuming broader coverage than provided. If the fee review touches outstanding reconciliation work, link it to the related support packet and keep the source exports with the queued questions.

Separate routine coding from flagged charges on September 28, 2026

For each fee line, record the statement date, the bank description, the amount, the QuickBooks Online transaction reference and coded account, and whether the line is routine, unusual, or disputable on September 28, 2026. A statement line, a prior-statement comparison, a fee schedule, or a bank notice may support the entry. The presence of a feed line coded to bank service charges is not proof the coding is correct when the description points to a wire fee that belongs with a supplier cost or a passthrough that belongs against payout income on September 28, 2026.

For interest lines, pay particular attention to whether the deposit is bank interest income or a different credit such as a fee reversal, an earnings credit, or a promotional bonus. Capture the statement line that supports the observation on September 28, 2026, including posting date and amount, then state what an authorized reviewer must confirm, such as the correct income account, the correct class or location when tracking is in use, and whether a fee reversal should net against the original charge instead of posting as income. This keeps an operational fact from being presented as an accounting conclusion.

Sidebar: Coding notes describe what was seen on September 28, 2026. Dispute and reclassification decisions describe who approved what and when. Keep those two layers distinct. A VA prepares the flagged observation with amounts; an authorized reviewer records the dispute or correction decision.

Check the common miscoding patterns deliberately on September 28, 2026. Confirm that monthly maintenance fees do not sit in office supplies, that wire fees tied to inventory purchases are not buried where job or product costing cannot find them, that overdraft charges are visible as bank charges rather than netted against deposits, and that interest income does not sit in other income when the chart of accounts carries a dedicated interest income account. Confirm that duplicates do not exist where a bank rule auto-added a fee and a manual entry recorded the same charge. Where the bank feed suggests a match, verify amount, date, and account before accepting it on September 28, 2026.

A useful review sequence for September 28, 2026

1. Define the population, accounts, period, and source locations on September 28, 2026. Export bank activity or save statements and export the QuickBooks Online fee and interest transaction list with a September 28, 2026 timestamp.
2. List every fee and interest line with date, description, and amount on September 28, 2026. Match each line to its QuickBooks Online transaction and record the coded account before labeling any item as routine or flagged.
3. Compare each charge to the prior pattern on September 28, 2026, separating stable monthly fees, volume-driven per-item charges, and onetime spikes, so one owner answer can clear a pattern rather than one row at a time.
4. Mark each line as confirmed routine, miscoded and proposed for correction, unusual and needing owner context, or disputable and ready for a dispute draft on September 28, 2026. Preserve the original QuickBooks Online value beside any proposed correction.
5. Write one specific question for every flagged charge and assign its next reviewer on September 28, 2026. Avoid vague notes such as check fees and write approve $240 analysis charge dispute draft for the payout account or confirm new fee schedule instead.

What to put in the September 28, 2026 handoff

Add a second view grouped by charge type so the owner can clear a pattern at once. For instance, group all routine monthly maintenance lines together with the confirmed total, then present the two overdraft charges totaling $70 as one cash-timing question and the $240 analysis spike as a separate dispute question on September 28, 2026. Include an interest tie-out section showing each interest posting matched to the statement with the income account confirmed.

Keep the queue useful on September 28, 2026

Do not close a flagged fee just because the amount is small. Do not code an analysis spike as routine when the evidence shows a break from the prior pattern. Preserve the original QuickBooks Online coding beside any proposed correction, and attach the reason for a change after the authorized reviewer approves it. On September 28, 2026, a visible flagged state with a named bank follow-up is more useful than a quietly absorbed charge that repeats next cycle.

Filter the log so the owner sees disputable charges first on September 28, 2026, then proposed reclassifications, then cash-timing questions tied to overdrafts. Group items with the same root cause together so one confirmation clears a pattern. Keep confirmed routine lines in a separate completed section from the flagged items so progress is visible without losing the remaining questions. If the log feeds a close packet such as the month-end close packet or the bank reconciliation support packet, link them explicitly so the reviewer understands downstream effects on reconciled balances.

Practical handoff note for September 28, 2026

End the file with the September 28, 2026 review date, the number of lines checked, the flagged questions, and the next checkpoint. The goal is a record another person can pick up without reconstructing the September 28, 2026 work. For this log, state that 22 fee lines totaling $1,240 across 3 accounts were matched, 19 lines totaling $930 are confirmed routine, 3 lines totaling $310 are flagged with 2 overdraft charges and 1 analysis charge spike, 6 interest lines totaling $84 are tied to interest income, and three owner questions are open with named contacts. If the work touches a close review, link it to the related close packet and keep the source exports with the queued questions.

Archive the packet with the bank statements or activity exports, the QuickBooks Online transaction export, fee schedules, prior-pattern comparison, and evidence links 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 was reviewed, what evidence supported each flagged charge, what corrections are proposed, what dispute decisions are still needed, and who owns each open bank follow-up. That clarity keeps small charges 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 bank fee review cadence on September 28, 2026
• QuickBooks Online Support for bank activity and coding workflows on September 28, 2026
• Internal: services page, bookkeeping tasks guide, bank reconciliation support packet, and month-end close packet for delegation boundaries on September 28, 2026

Owner CTA for September 28, 2026

If bank fees and interest lines are still coded without a comparison to the prior pattern on September 28, 2026, define the review log and the dispute approval path before the next statement cycle. Get a free VA consultation to map the first handoff with a named owner and a review cadence for September 28, 2026. Keep dispute filing, reclassification approval, and income treatment decisions with an authorized reviewer on September 28, 2026.