--- title: "Sales - Transaction Type Crosstab" url: "https://help.aurapos.com/en/article/sales-transaction-type-crosstab" language: "en" last_updated: "2026-10-22T07:24:46.550Z" --- # Sales - Transaction Type Crosstab The Transaction Type Crosstab report breaks your store's sales down by transaction type (for example Counter, Delivery or Table) against a grouping you choose: hour of day, day of week, date, month, cashier, sales channel, shift or POS. It shows three grids: turnover, number of transactions and average transaction value. It's for store managers and franchisees who want to see when and where each kind of sale happens, plan staff for busy hours, or compare delivery and sit-down trade across the week. Updated Thu 22 Oct 2026 ## Running the report 1 Open **Reports** for your store and choose **Transaction Type Crosstab** under **Sales**. 2 Choose your start and end dates, how you want the rows grouped, and whether to see figures including or excluding VAT (see Report options). 3 Run the report. You get three grids, one under the other: **Turnover**, **Number of transactions** and **Average transaction value**. Each has one row per value of your grouping and one column per transaction type, plus a **Total** column. **Tip**Group by **Hour of day** over a few normal weeks to see when each kind of trade peaks, then plan your shifts and delivery drivers around it. Group by **Day of week** to compare weekdays with weekends. ## Report options ### Select a start date / end date The first and last trading day to include. Your store's close of trade time is used, so a sale after midnight but before close of trade counts towards the previous trading day. Both default to today. ### Select your preferred grouping Hour of day Cashier name Date Day of week Month POS name paid into POS name rung up on POS number paid into POS number rung up on Sales channel Shift number What each row of the grids stands for. The report title changes with it, for example **Transaction type by day of week crosstab**. Cashier name The person who rang up the sale. Shows **Unknown** when the employee code on the sale can't be matched to a person. Date One row per trading day, oldest first, for example **12 Oct 2026**. Day of week One row per weekday, Sunday first. Every Monday in the period is added together. Hour of day The default. One row per clock hour the sale was rung up in, for example **18 to 19**. The last hour of the day is **23 to 00**. Month One row per month with its year, for example **October 2026**, oldest first. POS name / number paid into The till the sale was cashed up into. POS name / number rung up on The till the sale was rung up on. This can differ from the till it was paid into, for example when a waiter rings up on one device and pays in on another. Sales channel The channel the sale came through, for example your own app or an online ordering partner. Shift number The till and cashup number, for example **3-14**, in number order. Sales not cashed up yet show as **Not allocated yet**. ### Show sales figures Inclusive (Brand default) Exclusive Whether the turnover and average transaction value figures **include** or **exclude** VAT (value-added tax or your country's equivalent sales tax). Your brand chooses which one is the default: it's always first in the list, marked **(Brand default)**, and already selected when you open the report. If your brand has chosen exclusive, the list reads **Exclusive (Brand default)** and **Inclusive**. Choose **Inclusive** to compare with your cash-ups, which count the money customers actually paid. Choose **Exclusive** to look at your sales without the VAT you pay over to your tax authority. The grid headings tell you which one you're looking at: **Turnover (incl VAT)** or **Turnover (excl VAT)**. **What changes and what doesn't**Only rand figures change. The number of transactions and the rows and columns you see are the same either way. Each sale's VAT is the VAT on that sale's own items, so a sale of zero-rated items shows the same amount in both modes. ## The report at a glance Bob's Burgers Times Square Transaction type by day of week crosstab From Mon 12 Oct 2026 00:00 until Sun 18 Oct 2026 23:59 The dates are your trading days. If your store's close of trade time is after midnight, the date line shows that time and ends with **\***, and a note at the bottom of the page explains that sales between midnight and close of trade count towards the previous day. 1. Turnover: how much each transaction type sold, per row 2. Number of transactions: how many sales made up that turnover 3. Average transaction value: turnover divided by transactions 4. Voids note: voided sales that are left out, with a link to the voids report The examples below are grouped by **Day of week**. The column headings are the transaction types your store actually traded in the period, in alphabetical order, followed by **Total**. ## Turnover The value of your sales, per row and transaction type. Headed **Turnover (incl VAT)** or **Turnover (excl VAT)**, depending on **Show sales figures**. | | Transaction types | | | | | | --- | --- | --- | --- | --- | --- | | Day of week | Collect | Counter | Delivery | Table | Total | | Sunday 1 | 2 553.60 | 4 630.30 | 4 714.60 | 14 626.75 | 26 525.25 | | Monday | 1 057.20 | 2 960.00 | 3 133.50 | 5 968.80 | 13 119.50 | | Tuesday | 1 258.95 | 3 238.65 | 3 382.40 | 6 765.00 | 14 645.00 | | Wednesday | 1 448.80 | 3 488.70 | 3 565.75 | 7 541.60 | 16 044.85 | | Thursday | 1 661.85 | 3 785.10 | 4 039.40 | 9 097.40 | 18 583.75 | | Friday | 2 824.50 | 4 990.00 | 6 771.95 | 17 032.80 | 31 619.25 | | Saturday | 3 422.70 | 5 552.80 | 7 319.40 | 19 164.60 | 35 459.50 | | Total turnover 2 | 14 227.60 | 28 645.55 | 32 927.00 | 80 196.95 | 155 997.10 | ### 1 A row Each cell is the total of every completed sale of that transaction type in that row. Turnover is what the customer was charged for the sale, including any delivery charge and after discounts. Tips are not part of turnover. The **Total** column adds up the transaction types in the row. ### 2 Total turnover The bottom row adds each column up. The bottom right figure (**155 997.10** in the example) is the turnover for the whole period. ## Number of transactions How many sales make up each turnover figure above. Each sale counts once, however many items it had. This grid is the same whichever VAT option you choose. | | Transaction types | | | | | | --- | --- | --- | --- | --- | --- | | Day of week | Collect | Counter | Delivery | Table | Total | | Sunday 1 | 14 | 38 | 22 | 41 | 115 | | Monday | 6 | 25 | 15 | 18 | 64 | | Tuesday | 7 | 27 | 16 | 20 | 70 | | Wednesday | 8 | 29 | 17 | 22 | 76 | | Thursday | 9 | 31 | 19 | 26 | 85 | | Friday | 15 | 40 | 31 | 47 | 133 | | Saturday | 18 | 44 | 33 | 52 | 147 | | Total transactions 2 | 77 | 234 | 153 | 226 | 690 | ### 1 A row The number of completed sales of each transaction type in that row, and in total. ### 2 Total transactions The number of sales for the whole period, per transaction type and in total (**690** in the example). ## Average transaction value The turnover cell divided by the number of transactions cell, so it is the average spend per sale. Headed **Average transaction value (incl VAT)** or **(excl VAT)**. | | Transaction types | | | | | | --- | --- | --- | --- | --- | --- | | Day of week | Collect | Counter | Delivery | Table | Total | | Sunday 1 | 182.40 | 121.85 | 214.30 | 356.75 | 230.65 | | Monday | 176.20 | 118.40 | 208.90 | 331.60 | 204.99 | | Tuesday | 179.85 | 119.95 | 211.40 | 338.25 | 209.21 | | Wednesday | 181.10 | 120.30 | 209.75 | 342.80 | 211.12 | | Thursday | 184.65 | 122.10 | 212.60 | 349.90 | 218.63 | | Friday | 188.30 | 124.75 | 218.45 | 362.40 | 237.74 | | Saturday | 190.15 | 126.20 | 221.80 | 368.55 | 241.22 | ### 1 A row Each cell is that cell's turnover divided by its transactions. For example on Saturday the **Table** column sold 19 164.60 over 52 transactions, an average of 368.55. The **Total** column is the row's total turnover divided by its total transactions (241.22 on Saturday), not the average of the cells next to it, so busy transaction types weigh more. **No total row**This grid has no total row, because adding averages together doesn't give a meaningful figure. ## Voids note If any sales were voided in the period, a note under the grids tells you how much, for example **There are R 845.00 worth of voided invoices for this date range that are not included on this report.** Voided sales are never part of the grids. Click the note to open the voids report for the same dates. The amount always includes VAT: in exclusive mode the note says **(incl VAT)** so you know. If nothing was voided, the note doesn't appear. ## Watch the video A short walkthrough of running the report and reading the three grids. [Sales - Transaction Type Crosstab walkthrough](https://www.youtube-nocookie.com/embed/Z6FsW3f6bM8?rel=0) Can't see the video? [Watch it on YouTube](https://www.youtube.com/watch?v=Z6FsW3f6bM8). ## Frequently asked questions Why doesn't the turnover match my cash-up? First check **Show sales figures**: cash-ups count what customers paid, so compare them with **Inclusive** figures. Also check the dates and the close of trade time, and remember that this report leaves out voided sales and tips. A sale that is still open (not paid yet) is not counted either. Why is a sale made after midnight shown under the previous day? Your store has a close of trade time after midnight. Sales between midnight and that time belong to the previous trading day, for **Date**, **Day of week** and **Month**. **Hour of day** always uses the actual clock time, so those sales appear under **00 to 01**, **01 to 02** and so on. Why is the Total average not the average of the other columns? It's the row's total turnover divided by its total transactions. A transaction type with many sales counts for more than one with a few, which gives you the true average spend per sale for that row. Why are the exclusive figures not lower by exactly the standard VAT rate? VAT comes off each sale according to the VAT on that sale's own items. Zero-rated items and any items with a different rate change the amount, so the difference between the two modes is seldom exactly the standard rate. Why does a cashier show as Unknown? The employee code on those sales couldn't be matched to one person, for example because the code was reused by more than one person. The sales are still counted. Contact AuraPOS support if it happens often. What does Not allocated yet mean under Shift number? Those sales haven't been cashed up into a shift yet. Once the shift is cashed up they move to their shift number. Why is a transaction type missing from the grid? A column only appears if your store had at least one completed sale of that type in the period. Why does Month show the year? So that a period that crosses into a new year keeps the months apart. October 2025 and October 2026 are separate rows, in date order. ## Glossary Average transaction value Turnover divided by the number of transactions: the average spend per sale. Brand default The VAT setting your brand chose for sales reports. It is preselected in **Show sales figures**. Close of trade The time your store's trading day ends. Sales after midnight but before this time belong to the previous day. Crosstab A grid with one thing down the side (your grouping) and another across the top (transaction types). Exclusive (excl) Figures with VAT taken out. Grouping What each row stands for, chosen in **Select your preferred grouping**. Inclusive (incl) Figures including VAT: what the customer was charged. Transaction One completed sale, however many items it had. Transaction type How the sale was made, for example Collect, Counter, Delivery, Drive Thru, Lounge or Table. Turnover The value of completed sales after discounts, including delivery charges, excluding tips. VAT Value-added tax or your country's equivalent sales tax. Voided invoice A sale that was cancelled. Voids are left out of the grids and shown in the voids note.