When Two QuickBooks Desktop Reports Disagree, the Answer Is Source vs. Targets

QuickBooks Desktop users keep running into a quiet puzzle. Two reports, drawing on the same company file, refuse to agree. A transaction appears in one and not the other, and the gap looks like a bug. The formally accepted answer on this topic comes from Intuit’s own documentation. Its conclusion is simple. The program reads every transaction in two distinct layers, and each report chooses which layer it reads.

The symptom: reports that should agree, and do not

The complaint takes a few familiar forms. A Profit & Loss and a sales report return different totals for the same period. A filtered report misses an entry the user knows exists. An advanced find drags or returns rows nobody expected. Sometimes the difference matches one transaction exactly, which deepens the suspicion that something is broken. None of it points to a damaged file. Per the accepted explanation, these are the visible results of a deliberate design choice in how the program assembles reports.

Why do two reports show different totals?

Every report in Desktop runs on a fixed set of instructions built into the program. That set defines the report’s structure and the filters embedded in it. Default filters layer on top, followed by whatever you change on the Display and Filters tabs. When you open the report, the program walks your data line by line and pulls in every line that matches.

The crucial detail comes next. Those same instructions decide whether the report reads the source side of a transaction, the target side, or both. Two reports can therefore read the same sale or the same bill in different ways. Neither is wrong. They are simply not measuring the same lines, so their totals can honestly differ.

Source and targets, in plain terms

The source is the summary layer of a transaction. It holds the main account, name, memo, and amount in a single line. The targets are everything beneath it: the detail accounts, names, memos, and amounts that form the body of the entry.

You can watch the split in seconds. Open any saved transaction, an invoice for example, and press Ctrl+Y. The transaction journal opens on screen. Its first line is the source; every line under it is a target. On an invoice, that opening line is the receivable, and the income and tax lines below it are the targets.

The pattern holds for every transaction type. On a check written to a supplier, the bank line is the source and the expense lines beneath it are the targets. On a bill, the payable sits at the top and the expenses follow.

The general journal entry exception

Every transaction type carries a fixed source line except one. General journal entries let you insert a line above the first line. Do that, and the program reclassifies the entire entry as target data, with no source line left. The entry remains valid. It just stops appearing anywhere a report reads only source data. That is worth remembering when a filtered report comes back empty and the journal entry behind it begins on an inserted line.

Which side is your filter reading?

This is where the explanation turns practical. Before assuming a report is broken, open one of the transactions behind the number and press Ctrl+Y. The journal shows you exactly which lines sit on each side. Then revisit the Filters tab and ask a single question: does this filter describe source data or target data? A filter aimed at the summary layer will not behave like one aimed at the detail lines. Most report surprises trace back to that distinction.

The same knowledge shapes advanced finds. Pointing a find at the right layer, instead of scanning everything, returns results sooner. The vendor’s documentation makes the point directly: knowing the split is what lets filters do more work and finds run faster.

Every report sits in one menu

These mechanics apply across the whole report library in Desktop Pro and Premier. The Reports menu groups everything by purpose. Company & Financial holds the Profit & Loss and the Balance Sheet. Customers & Receivables holds the aging summaries. Banking keeps the reconcile discrepancy lists, and Accountant & Taxes keeps the trial balance. Pull from whichever group you need; the same line-reading rules decide what makes the cut.

Our read on the issue: the confusion is genuine, but the reports are behaving as designed. Before suspecting the file, check the split with Ctrl+Y. The report is likely reading the side of the transaction you did not expect.