Blog Summary
The QuickBooks general ledger is where every financial transaction in a client's file lives. It is also where every error hides before it reaches the financial statements — and by the time an error shows up in the P&L or balance sheet, it has usually been compounding for months.
In this guide:
- What the QuickBooks general ledger is and how it works in QBO
- How to run and read the GL report in QuickBooks Online
- What a proper GL review looks for — and what most reviewers miss
- The most common GL errors and how to find them
- How automated anomaly detection catches what manual review overlooks
Every number in every financial statement your firm produces started in the general ledger.
Revenue recognized? GL entry. Expense recorded? GL entry. Bank reconciliation adjustment? GL entry. Payroll posted? GL entry. The GL is the complete record of every financial transaction — every debit, every credit, in every account, for every period.
It is also where errors live before they reach the reports.
By the time a misposted transaction shows up as an unusual number in the P&L, it has already been sitting in the GL for weeks or months. The question is not whether errors exist — they always do. The question is whether your review process catches them at the source, or discovers them after the statements have already gone to the client.
This guide covers how to review the QuickBooks general ledger effectively — what to run, what to look for, and what most reviews miss.
Part of our complete guide: complete QuickBooks bookkeeping guide
What Is the General Ledger in QuickBooks?
The general ledger (GL) in QuickBooks is the complete, chronological record of every financial transaction recorded in the file. It shows, for each account in the chart of accounts, every transaction that affected that account — with the date, amount, description, and running balance.
In double-entry accounting, every transaction has a debit and a credit. The GL shows both sides. When you record a customer payment, the GL shows the debit to your bank account (or undeposited funds) and the credit to accounts receivable.
What the QuickBooks GL contains:
The GL is the most detailed view of a QuickBooks file. Reports like the P&L and balance sheet are summaries built from GL data. If the GL has errors, every report built from it inherits those errors.
Why GL Review Matters for CPA Firms
Financial statements are only as reliable as the GL data they are built from. A GL review is how you confirm that the underlying data is accurate before producing or relying on any report.
For CPA firms, this matters at three specific points:
Pre-engagement: Before quoting a cleanup or ongoing bookkeeping engagement, a GL review reveals the scope of issues in the file — mispostings, duplicates, wrong-period entries, and journal entries without documentation.
Month-end close: Before producing financial statements, a GL review confirms that all entries for the period are correct, complete, and in the right accounts.
Pre-proposal diagnostic: Before presenting a books health report to a prospect, a GL-level review shows what is actually in the file versus what the surface-level reports suggest.
Most firms review the P&L and balance sheet before close. Fewer review the GL itself. The ones that skip the GL review are the ones that discover errors after statements go out — which is always more expensive to fix than catching them during the review.
Who Should Review the QuickBooks General Ledger?
Who does the GL review: Senior accountant or reviewer — someone with enough accounting knowledge to recognize patterns that are off, account types that do not match the transactions, and entries that need documentation.
Who should not be the only reviewer: The bookkeeper who entered the transactions. GL review is a verification step — it requires a different set of eyes on the work.
How review responsibility divides:
In firms without a formal GL review step, errors typically surface one of two ways: the client finds something, or an auditor finds it. Neither is a good outcome.
When Should the GL Be Reviewed in the Close Cycle?
The GL should be reviewed after all transactions for the period are entered and before any financial statements are finalized.
In a standard 10-day close cycle:
A GL review done only at day 9 — after adjusting entries — catches some errors but misses the ones that were introduced during transaction entry earlier in the cycle. The most efficient approach is a two-pass review: once after initial entry, once after adjustments.
How to Run the General Ledger Report in QuickBooks Online
Standard GL report:Reports → For my accountant → General Ledger
Set the date range to the period you are reviewing. The report shows every account and every transaction in that account for the period.
Useful customizations:
For a focused GL review, pull three reports:
- Full GL for the period — all accounts, all transactions — for the complete picture
- Journal entries only — to review every manually entered adjustment, accrual, and correction
- Transaction detail by account for high-risk accounts — cash, AR, AP, payroll, owner draws
What to Look For in a QuickBooks GL Review
Large or unusual transactionsSort each account by amount. Any transaction significantly larger than typical activity for that account needs a description and a source document. A $45,000 entry to office supplies is not miscellaneous — it needs investigation.
Transactions without memos or descriptionsJournal entries with no description are a red flag. Any manual entry should have a clear explanation of what it is for and why it was made. An undocumented journal entry is an unexplained adjustment.
Round numbers in non-round-number accountsA $10,000 entry to payroll expense in a file where every other payroll entry is $8,740 or $9,215 deserves scrutiny. Round numbers in accounts that should not have round numbers often indicate estimates, errors, or manual overrides.
Duplicate amounts on the same dateTwo transactions for the exact same amount, on the same date, in the same account — one of them is almost always a duplicate. This is especially common with payroll entries and vendor payments.
Transactions posted to the wrong periodAn entry dated December 31 in a file that had a clear close in November. A January transaction backdated to December. Wrong-period entries distort the monthly financials even when the annual totals are correct.
Credits in expense accounts or debits in income accountsThese often indicate a refund or reversal that was entered incorrectly — or an offsetting entry that went to the wrong side.
Owner or shareholder account activityAny transactions in owner draw, shareholder loan, or related party accounts should be reviewed closely. These accounts are high-risk for personal expenses being coded to business accounts.
Common QuickBooks General Ledger Errors — and How to Find Them
GL Review Checklist for CPA Firms
Use this before signing off on any period close:
Transaction review:- All high-value transactions have source document support- No duplicate entries in any account- All manual journal entries have memos explaining their purpose- No transactions in wrong-period dates without documentation
Account-level review:- Cash and bank accounts match reconciliation- AR balance ties to the AR aging report- AP balance ties to the AP aging report- Payroll entries match payroll reports from the payroll provider- Owner draw and related party accounts reviewed and documented
Journal entry review:- Every JE has a description- Every reversing entry has the corresponding original entry- Accrual entries from prior month were reversed at period start- No unsupported adjustments without partner or manager sign-off
Variance review:- Current period GL compared to prior period for each account- Any account with more than 20% variance from prior period has an explanation- Unusual accounts flagged for management review
A Scenario We See Often: A Duplicate Payroll Entry Undetected for 9 Months
A CPA firm is managing payroll accounting for a 25-employee services firm. The client used ADP for payroll processing. Every pay period, the bookkeeper imported the payroll summary from ADP and manually entered a journal entry in QBO to record gross wages, tax withholdings, and net pay.
The problem: ADP also integrated directly with QBO through an automated sync. So every pay period, the payroll was recorded twice — once by the bookkeeper's manual JE, and once by the automated ADP integration.
Over 9 months, this created $247,000 in duplicate payroll expense entries. The P&L showed payroll expenses nearly double what they should have been. The client reported declining profitability — and was planning staffing cuts based on financial statements that were materially wrong.
The error was found during a GL-level review run as part of a year-end cleanup. Sorting the payroll expense account by date showed identical entries on every pay date — always two entries, always the same amounts.
Fixing it required voiding 9 months of duplicate journal entries, restating the affected months, and setting up ADP integration correctly so it did not double-post going forward.
How it should have been caught: A monthly GL review that checked for duplicate amounts on the same date in payroll accounts would have flagged the first occurrence in month 1. Running a Xenett Pulse diagnostic before the year-end review would have surfaced the duplicate pattern automatically — flagging it as a critical finding across 18 pay periods.
How Xenett Pulse Automates GL-Level Anomaly Detection
Xenett Pulse includes anomaly detection as part of its 20-point QuickBooks diagnostic. Rather than requiring a manual line-by-line GL review, Pulse scans the transaction data and flags patterns that deviate from expected behavior.
What Pulse detects in the GL:
- Duplicate transactions — same amount, same date, same account
- Unusual transaction amounts compared to historical patterns for that account
- Transactions coded to accounts that do not match the typical transaction type
- Journal entries without supporting memos or documentation
- Transactions in unexpected time periods relative to the close date
- GPT-powered customizable conditions — firms can define their own rules for what Pulse flags
How the anomaly detection works:
Step 1: Pulse reads the full transaction history for the QBO fileStep 2: It builds baseline patterns for each account — typical transaction amounts, frequency, and typeStep 3: It flags any transaction that deviates significantly from those patternsStep 4: Findings are ranked by severity and included in the Books Health Score
The output is a prioritized list of GL-level issues — the ones that need immediate attention vs. the ones that can be monitored. All of it goes into a white-labelled PDF report your firm produces in under two minutes.
For pre-proposal reviews, this means a prospect can see the GL-level issues in their own books — surfaced by an objective diagnostic — before any scope or pricing conversation happens. The report does the convincing because it shows the actual problems, not a description of possible problems.
Sign up free at Xenett Pulse — run a diagnostic on your next QBO file and see GL-level issues ranked by severity before the engagement starts.
Conclusion
The general ledger is where the financial statements come from. Every number on every report your firm produces traces back to a GL entry. Which means every error in the financial statements also traces back to a GL entry — one that existed in the file before the report was produced.
The difference between firms that catch errors before statements go out and firms that discover them after is one thing: a systematic GL review built into the close process.
Not a spot-check of the P&L. Not a review of only the largest accounts. A disciplined, account-by-account GL review that looks for the specific patterns where errors consistently hide — duplicates, wrong periods, unsupported journal entries, unusual amounts.
The time investment is real. But it is always less than the time required to restate financial statements, explain errors to clients, and rebuild trust after something that should have been caught in review.
Frequently Asked Questions
What is the general ledger in QuickBooks?
The general ledger is the complete record of every financial transaction in a QuickBooks file — organized by account, with each entry showing the date, amount, description, debit/credit direction, and running account balance. It is the source data from which all financial reports are built.
How do I run the general ledger report in QuickBooks Online?
Go to Reports → For my accountant → General Ledger. Set the date range to the period you want to review. You can customize the report to filter by specific accounts, add a memo column, sort by amount, or compare to a prior period — all useful adjustments for a thorough review.
What should I look for when reviewing a QuickBooks general ledger?
Focus on: large or unusual transactions that lack descriptions, duplicate amounts on the same date in the same account, transactions posted to the wrong period, manual journal entries without memos, round numbers in accounts that should not have them, and credits in expense accounts or debits in income accounts. These patterns indicate the most common GL errors.
How often should the QuickBooks general ledger be reviewed?
At minimum once per month as part of the close process — after all period transactions are entered and before financial statements are produced. For higher-risk files or new client engagements, a GL review should also be run before any scope or fee is committed.
What is the difference between the general ledger and the trial balance?
The general ledger shows every individual transaction in every account — the full detail. The trial balance summarizes the ending balance of each account and confirms that total debits equal total credits. The trial balance is a mathematical check. The general ledger is where you review the actual transactions to confirm they are correct.
Can QuickBooks Online generate a general ledger report?
Yes — it is listed under Reports → For my accountant → General Ledger in QBO. The report shows all accounts and all transactions for a selected date range. It can be exported to Excel for more detailed analysis, filtered by account type, or sorted by amount for a faster review of high-value items.
How does Xenett Pulse help with general ledger review?
Xenett Pulse runs automated anomaly detection on the QuickBooks transaction data as part of its 20-point diagnostic. It identifies duplicate entries, unusual amounts compared to historical patterns, misclassified transactions, and unsupported journal entries — ranked by severity. For CPA firms, this replaces hours of manual GL review with a two-minute automated scan that surfaces the same types of issues systematically across every account in the file.
Related guides
- Start here: QuickBooks Bookkeeping: What Clean Books Look Like
- QuickBooks Chart of Accounts — How to structure the chart of accounts so coding stays clean.
- Undeposited Funds in QuickBooks — Why undeposited funds builds up and how to clear it correctly.
- QuickBooks Accounts Receivable — How AR overstates assets and how to fix each cause.
