The Transactions report is SalesThumb's own payment log — a line-by-line record of every payment your shop has taken, independent of whatever invoice or job it's attached to. It lives at Reports → Financial → Transactions, and it's built for owners, managers, and bookkeepers who need to answer "did this payment actually go through, and for how much" without opening individual invoices one at a time. Seeing it requires the "View financial reports" permission — without it, the page shows a locked message instead of the report and points you to ask a shop owner or admin to grant it in Settings → Team → Permissions.
Getting to the report
Open Reports from the main sidebar, then Transactions under the Financial category. You can also jump to it from the report navigation list that runs down the left side of every report page — click Transactions there any time you're already looking at a different report, without going back to the Reports hub first.
The KPI row
Four cards sit above the table, summarizing whatever date range is currently selected:
- Net collected — the total amount retained after refunds, with gross collected and tips broken out underneath.
- Payments — a count of completed payments, with a note underneath for how many payments in the period weren't completed — pending, failed, or refunded — or "all completed" if every payment in the period was.
- Average ticket — net collected divided by completed payments, per the card's own label.
- Refunded — the cumulative dollar amount refunded against payments in the period.
Filtering the log
A filter bar above the KPI row lets you pick a date range — presets for 7 days, 30 days, 90 days, year-to-date, or 1 year, plus a Custom option with your own start and end date. To the right, a status filter (Completed / Pending / Failed / Refunded) and a method filter (Card / Cash / Check / ACH / Financing / Other) narrow the table further, alongside an "In-person only" checkbox that limits it to card-present payments — ones run through a card reader or terminal rather than taken without the card physically present. Changing any filter resets the table back to its first page.
Reading the table
Each row is one payment: when it was paid, the customer's name, a link to the invoice it's tied to (a dash if it isn't tied to one), the payment method, a channel tag (In-person for card-present payments, Online for card payments taken without the card physically present, a dash for everything else), status, the amount charged, any tip, and Net — the amount after subtracting refunds, shown in red once a refund has been applied. A truncated, click-to-select payment reference sits at the end of the row for looking a transaction up with your processor if you ever need to.
The table loads 25 payments per page, with Previous/Next buttons and a page counter — there's no "jump to page" control, so working through a long list means clicking Next repeatedly. When nothing matches your filters, the table says so directly and suggests widening the date range or clearing the status/method filters rather than just sitting there empty.
Exporting to CSV
The Export CSV button downloads exactly what's currently on screen — date, customer, invoice, method, channel, status, amount, tip, refunded amount, net, and payment reference for the current page — as a file named `salesthumb-transactions-<start-date>-to-<end-date>.csv`. It's disabled whenever the table has no rows loaded. Any field that could be misread as a spreadsheet formula (a customer name starting with `=`, `+`, `-`, or `@`, for example) is escaped first, so opening the file in Excel or Google Sheets won't trigger anything unexpected.
Things to know
- The KPI row only responds to the date range — not to the status, method, or "In-person only" filters. If you filter the table down to, say, just Failed card payments, the cards above it keep showing totals for every payment in the period, not just the filtered rows below. Use the KPI row to read the whole period and the table to drill into a subset.
- Export CSV exports the page you're currently viewing (up to 25 rows), not the full date range. If your filtered results span more than one page, export each page separately to get everything.
- Requires the "View financial reports" permission — a role without it is blocked the same way whether it lands on the page from a link, the report nav, or a typed-in URL.
- Amounts shown are what the customer paid; Net subtracts refunds issued against that specific payment. For what SalesThumb itself charged your shop to process these payments, that's a separate report — Processing Fees, next to Transactions in the same Financial category.
Frequently asked questions
Q: Where do I find the Transactions report, and who can see it?
A: Reports → Financial → Transactions, or from the report navigation list on the left side of any report page. You need the "View financial reports" permission — ask a shop owner or admin to grant it in Settings → Team → Permissions if you don't have it.
Q: Why don't the KPI cards match the table when I filter by status or method?
A: The KPI cards only respond to the date range you've picked and always total every payment in that period. Status, method, and the "In-person only" checkbox filter the table underneath, but they don't recalculate the cards above it.
Q: Does Export CSV download every transaction in my date range?
A: No — it downloads whatever's currently loaded in the table, which is one page of up to 25 rows. If your results run longer than that, page through with Next and export each page separately.
Q: What's the difference between "Online" and "In-person" in the Channel column?
A: In-person means the card was physically present — run through a card reader or terminal. Online means a card payment was taken without the card physically present. Cash, check, ACH, and financing payments don't get a channel tag, since that distinction doesn't apply to them.
Q: Why does a row's Invoice column just show a dash?
A: Not every payment is tied to an invoice in SalesThumb. When one isn't, that column shows a dash instead of a link.
Q: Can I jump straight to a specific page of results?
A: Not currently — pagination is Previous/Next only, with a page counter showing where you are. There's no page-number picker or "jump to" field.