Reporting changes planned for 6 November 2026
Planned rollout: 6 November 2026
We plan to update reporting on 6 November 2026. This article explains what will change in Merchant Console reports and the dashboard, the POS sales summary, and scheduled transaction-report emails.
These updates will make it easier to match YQueue payment and refund activity with payment gateway collection records by reporting each payment or refund on its processing date. They will also give you a clearer view of cash refunds and outstanding payments, and bring POS sales totals into line with other sales reports.
You may see payments or refunds move between dates, additional payment activity in POS summaries, and different overpaid or underpaid exceptions. Historical figures can also change when you regenerate a report after the update.
The examples below are simplified illustrations for one outlet, using its local reporting dates and no other activity unless stated. They do not describe a particular merchant's transactions.
Payment and refund dates
Payments that finish processing on another day
Successful payment figures will use the date the payment finished processing. The Transaction Summary currently selects payments by the date they were started; after the update, it will select finalised payments by their processing date.
For example, a $10.00 payment starts at 11:50pm on Monday and succeeds at 12:10am on Tuesday. Once it has succeeded:
| Transaction Summary | Before the update | After the update |
|---|---|---|
| Monday's report | Includes the $10.00 payment | Excludes the payment |
| Tuesday's report | Excludes the payment | Includes the $10.00 payment |
This date change also applies to scheduled daily transaction-report CSV attachments.
While a payment is still being processed, Transaction Summary will continue to select it by its creation date. Processed will show - until processing finishes; scheduled CSV attachments leave that cell blank. An unsuccessful or pending payment amount does not contribute to Total Collected.
Refunds on a later day
Refunds will count on the date they are successfully processed, rather than reducing the original payment's day.
For a $10.00 payment on Monday and a $4.00 refund on Tuesday, regenerating both daily reports after the refund will show:
| Total Collected | Before the update | After the update |
|---|---|---|
| Monday | $6.00 | $10.00 |
| Tuesday | $0.00 | −$4.00 |
| Across both days | $6.00 | $6.00 |
A day with more refunds than successful payments can therefore show a negative Total Collected or dashboard Payment Total.
In Transaction Summary, the original transaction reference can appear again in the refund period. A row included only because of a later refund will show Payment Amount $0.00, the refund amount for that period, and a negative Total Collected. Its Processed time will reflect the latest included refund.
Refunds using a different payment method
Payment Methods reports and Cash Collected will use the method actually used to return the money.
For example, a $100.00 card payment is refunded by $20.00 in cash, with both events in the selected period:
| Figure | Before the update | After the update |
|---|---|---|
| Card Total Collected in Payment Methods | $80.00 | $100.00 |
| Cash Collected | $0.00 | −$20.00 |
| Total Collected across methods | $80.00 | $80.00 |
The Payment Method column in Transaction Summary still identifies the original payment method. Use Payment Methods reports to see how the refund affects the method used to return the money.
Refund counts and empty rows
In the POS sales summary, the count beside Refund Amount will count individual successful refunds. Two successful refunds against one payment in the selected period will show 2 refund(s), rather than one refunded payment. This brings it into line with Refund Count in Payment Methods reports.
Refund amount/count reports will also omit payment methods with no successful refunds in the selected period. A missing all-zero row does not mean that the payment method's sales or payments have been removed from other reports.
Which payments and refunds are included
POS payment summaries will include all successful outlet payments, including payments on orders that are still in progress, cancelled or merged, and payments without an associated order. Payments and refunds will also remain visible in periods with no sales.
For example, if no orders were placed today but a $4.00 refund of an earlier payment was processed today:
| POS sales summary | Before the update | After the update |
|---|---|---|
| Order Count | 0 | 0 |
| Refund Amount | $0.00 | $4.00 |
| Total Collected | $0.00 | −$4.00 |
A cancelled or merged order can therefore have successful payment activity in a payment report while being excluded from sales figures.
Comparing POS and dashboard totals
The meaning of Payment Total will remain the same on each screen:
- In the POS sales summary, Payment Total shows successful payments before refunds. Refund Amount and Total Collected are shown separately.
- On the Merchant Console dashboard, Payment Total shows successful payments less refunds.
For a reporting period containing a $10.00 payment and a $4.00 refund:
| Figure | Amount after the update |
|---|---|
| POS Payment Total | $10.00 |
| POS Refund Amount | $4.00 |
| POS Total Collected | $6.00 |
| Dashboard Payment Total | $6.00 |
When comparing net collections, compare POS Total Collected with dashboard Payment Total. Sales totals measure orders, so they can differ from payment totals when orders are unpaid or payments and refunds fall in another period.
Sales and order counts
Orders still in progress
The POS sales summary will include orders already sent to the outlet, even if they are still in progress. These orders will contribute to sales, order counts, item quantities, discounts, surcharges and taxes before completion, bringing the POS summary into line with other sales reports.
For two $10.00 orders sent to the outlet in the reporting period, with one complete and one still in progress:
| POS sales summary | Before the update | After the update |
|---|---|---|
| Order Count | 1 | 2 |
| Order Total | $10.00 | $20.00 |
Cancelled orders and orders merged into another order are excluded from these sales figures. If an in-progress order is later cancelled, it will be removed from sales when the original period's report is regenerated.
Average Order Value
Average Order Value (ATV) will round to the nearest cent rather than truncate fractional cents. For example, two eligible orders with a combined subtotal of $10.01 have an average of $5.005: the displayed ATV will change from $5.00 to $5.01. This rounding change does not change the order subtotals or sales total.
Merged orders
If your POS supports order merging, the remaining combined order will contribute to sales, item and order-count totals. Original orders merged into it will appear under Merged (Orders) in the POS summary, separately from cancellations.
For example, merging a $10.00 order into a $20.00 order leaves one $30.00 order contributing to sales. The original $10.00 order appears as a merged order. Combined sales stay with the remaining order's original order date, even if the merge happens on a later day.
Successful payments remain attached to the order against which they were recorded. If a payment succeeds on an original order around the time of a merge, the original stays merged and the payment remains on it. The merchant must review payments on both orders and reconcile them manually.
The Merged Orders with Payments exception will highlight originals merged during the selected period, or with payment/refund activity in that period, that still retain successful payments not fully refunded as at the report end. For example, a $10.00 payment retained on a merged original can appear here and in payment totals, while the combined order carries the sales. This exception identifies payments needing review; it does not transfer or refund them.
Cancellation and merge dates
In the POS summary, cancellation and merge exceptions will use the date the action occurred.
For example, a $10.00 order placed Monday and cancelled Tuesday will move from Monday's cancellation figures to Tuesday's cancellation figures when you regenerate those reports after the update. It will remain excluded from sales. Merged originals follow their merge date in Merged (Orders).
Overpaid and underpaid orders
Payment-difference checks for completed orders will take earlier successful payments and refunds into account, up to the report's end date. Later payments and refunds will be excluded from that historical balance check.
Completed orders closed off during the reporting period will also be checked when no successful payment was recorded:
| Situation at the report end | Before the update | After the update |
|---|---|---|
| A completed $25.00 order has no successful payment | Could be absent from the exceptions | Shows $25.00 underpaid |
If that order is paid the next day, its earlier report will still show the unpaid balance as at the earlier report end. Earlier completed orders with payment or refund activity in the selected period will also be checked.
Historical reports and exports
Original orders remain available in historical reports and exports after a merge. A detailed order-history export can include both original orders and the combined order, and its footer totals the selected rows. Use order-status filters when comparing these exports with sales-only figures.
Regenerating a historical report after the update can change its figures where payment/refund dates differ, cancellations happened in a later period, activity was previously omitted, or ATV rounding applies. An export you already downloaded will keep its existing contents.
Mall sales submissions
For outlets using mall/GTO reporting, merged originals will be excluded from duplicate order and item figures. Eligible successful payment and refund amounts, and any transaction counts required by the mall integration, will remain included. The submitted fields and eligible payment methods depend on the mall integration.
Preparing for the update
When comparing reports after the rollout:
- Use the same outlet, date range, reporting timezone and order-status filters.
- Compare sales figures with sales figures, and net collections with net collections.
- Check the payment and refund processing dates when an amount moves between periods.
- Review Merged Orders with Payments when it appears.
- Check whether an order-history export includes cancelled or merged orders before comparing its footer with sales totals.
For an overview of the available reports, see Reports. If you need help reconciling a difference, contact your account manager with the outlet, report name and date range.