Reports & Store Operations
How MiniTill recognises sales and refunds in reports
Understand payment-time revenue recognition, refund attribution, date boundaries, and why a later refund can change an earlier sales period.
Overview
- Recognised revenue is based on successful Payment created time, not simply Order created time.
- Revenue includes APPROVED, PARTIALLY_REFUNDED, and REFUNDED payment records after subtracting approved refund amounts.
- An approved refund is attributed back to the original Payment's recognised revenue cohort. A refund approved later can therefore reduce the report period in which the original payment was recognised.
- Orders CANCELLED, VOIDED, or FAILED before recognised revenue are excluded from normal revenue payment reporting.
- Standard report ranges are from-inclusive and to-exclusive in the selected IANA timezone.
- Order count is distinct orders with recognised revenue payments; linked customer counts are based on those counted orders.
When to use this
- Read this before comparing MiniTill to a report that uses Order date, settlement date, bank-deposit date, or refund-created date.
Step-by-step
- Confirm the report timezone.
- Check the selected from/to boundaries.
- If investigating one order, inspect its successful Payment timestamps.
- If a historical net-sales figure changed, check whether a later approved Refund belongs to a payment in that period.
- Use Payments/Refund details for transaction-level confirmation.
Common mistakes
- Do not assume a refund always belongs to the day the manager pressed Refund.
- Do not count split-payment orders twice; report Order count is distinct within the recognised revenue cohort.
- Do not compare provider payout date with recognised Payment date without reconciliation.
Troubleshooting
- If an order seems missing from Sales, check whether it actually has a recognised successful Payment in the range.
- If Net sales changed retrospectively, inspect approved refunds on payments originally recognised in that period.