Sorting saved transactions in QuickBooks Desktop for Mac: fields and steps

A recurring question from QuickBooks Desktop for Mac users reads simply: sort saved transactions. Behind it sits a familiar frustration. Every invoice, bill, and payment stays on file, and long lists are hard to search by eye. The community’s accepted answer says sorting is built in, but it works window by window, and the fields on offer change with the transaction type.

The problem: long lists with no obvious order

Each transaction type in QuickBooks Desktop keeps its own window and its own saved history. After a busy month, an invoice list can run well past one screen. Finding a single unpaid invoice from early in the month means reading entries one at a time. That friction is what the community question captures. Users wanted to reorder saved records by the detail that matters to them, whether that is a due date for collections or an amount for a fast review.

Where the sort control lives

The control sits in the transaction window itself. For invoices, open the Customers menu and choose Create Invoices, then open the Sort by dropdown and pick a data type. Choose Due Date, for instance, and the list reorders around payment deadlines. The same pattern holds elsewhere. Sales receipts, estimates, credit memos and refunds, payments, entered bills, purchase orders, written checks, credit card charges, deposits, transfers, and general journal entries all carry their own sort choices.

Sort options by transaction type

A core set of five fields repeats through most of these windows: Date, Number, Amount, Customer, and Date Entered. Invoices add a sixth, Due Date, and that is the field collections work leans on hardest. Purchase orders add Date Expected, which reflects when ordered goods should arrive. The remaining types work from the core five. Date Entered deserves a note of its own, because it tracks when you created the record rather than the transaction date printed on it.

Why not one global control? Each window is its own list with its own columns, so a field like Due Date only means something where invoices live. The vendor placed the sorting where the columns are, which is logical once you see it, but easy to miss if you went looking for a master settings page.

Which way does the list sort?

One behavior catches people out. The list sorts itself in descending order by default, so a Due Date sort puts the latest dates at the top. If you would rather see the oldest deadlines first, you can set the list to ascending order instead. No separate settings screen is involved. The order you choose applies to what you see on screen, not to the records behind it.

The release caveat worth checking

Version matters here. The guidance we verified ties these sort options to QuickBooks 2024 for Mac, release 8 and earlier. That phrasing stops short of promising the same menu in anything newer, and we could not confirm identical behavior past that point. If your copy runs a later release, treat the field list above as what release 8 and earlier provide. Open the Sort by dropdown in your own copy and see which choices appear before you rely on a field that is not there.

A quick worked example

Consider a small service business that invoices a few dozen customers each month. Opening Customers, choosing Create Invoices, and setting Sort by to Due Date turns the window into a collections queue, with the nearest deadlines grouped in one reading order. Setting the same field to Amount turns it into a review of the largest sales on record. Nothing moves in the books. Sorting only changes the order of the list in front of you.

The short answer

There is no single sort screen for saved transactions in QuickBooks Desktop for Mac. Open the window for the transaction type you care about, find the Sort by dropdown, and pick a field. Invoices carry Due Date, purchase orders carry Date Expected, and the rest sort on the core five. On a 2024 for Mac release at R8 or earlier, it behaves exactly that way, and that is the scope we can stand behind. If a field you expected is missing, the release you are running is the usual explanation.