Set the report from and to dates | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/ecommerce-pos-set-the-report-from-and-to-dates Publisher: Pixie Technologies LLC Reports, audit evidence and security controls Set the report from and to dates Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Submit valid dates; reversed values are normalised by swapping them. Audience: Managers, finance staff, auditors and security reviewers; Permission: View reports or View audit; Module v1.0.0 · code-inspected; Where to goEnterprise POS → Reports / Audit What this guide helps you do Submit valid dates; reversed values are normalised by swapping them. This section explains report filters, exclusions, audit chaining and the module’s principal security controls. Follow these steps - Go to Enterprise POS → Reports / Audit and open the workflow that matches “Set the report from and to dates”. Confirm the page or record context before making a change. - Go to Reports and choose a date range. - Run the summary and review sales, collected amounts, channel breakdown and top products. - Go to Audit and review recent tenant events. - Use correlation IDs to connect order, payment, stock, return and integration events. - Escalate anomalies without rewriting records. Fields and options - Guide focus: Submit valid dates; reversed values are normalised by swapping them. - From/to dates - Location timezone - Sales and collected totals - Sales by channel - Top 20 products - Audit event type, object, actor, reason, summary, correlation and chain hash Rules and limits - Reports default to the current calendar month. - Reversed from/to inputs are swapped. - Cancelled, void, refunded and returned orders are excluded. - Top products are limited to 20. - Audit UI displays the most recent 200 events. - Each audit event HMAC includes the previous event hash and tenant context. Check it worked - The specific outcome described by this guide is visible and remains tenant-scoped. - Report totals match eligible committed orders. - Audit events form an ordered tenant chain. - Correlated operations can be reviewed without database edits. Safety checks and troubleshooting - Treat reports as operational summaries, not a substitute for formal accounting. - Do not alter audit rows. - Protect settings keys, public tokens, API secrets and webhook secrets. Stay within the supported module flow Use the supplied UI, host module lifecycle and documented endpoints. Do not bypass tenant filters, permissions, CSRF, idempotency, rate limits, audit evidence or transaction checks. A stored table or field does not imply that version 1.0.0 exposes a management screen for it. Related guides eCommerce & POS Module overview (https://pixiecrm.com/help-centre/ecommerce-pos-module-overview)Run the POS sales report (https://pixiecrm.com/help-centre/ecommerce-pos-run-the-pos-sales-report)Understand the default report period (https://pixiecrm.com/help-centre/ecommerce-pos-understand-the-default-report-period)Understand report timezone handling (https://pixiecrm.com/help-centre/ecommerce-pos-understand-report-timezone-handling)Understand sales report exclusions (https://pixiecrm.com/help-centre/ecommerce-pos-understand-sales-report-exclusions)Open the public checkout (https://pixiecrm.com/help-centre/ecommerce-pos-open-the-public-checkout)Create a POS API key (https://pixiecrm.com/help-centre/ecommerce-pos-create-a-pos-api-key)Browse the connected Reports, audit evidence and security controls topic (https://pixiecrm.com/help-centre/topic/ecommerce-pos-reports-audit)Browse all eCommerce & POS Module guides (https://pixiecrm.com/help-centre/category/ecommerce-pos)Open the related Help Centre category (https://pixiecrm.com/help-centre/category/data-privacy-security)