Walkthrough
Checklist
Success check
Walkthrough: Report Export
Find the right report, apply filters, confirm totals, export safely, and share report evidence with the right people.
Reports help teams review inventory, procurement, sales, POS, finance, vendors, workflows, and exceptions. A useful export depends on correct filters, dates, status, branch, warehouse, and permissions.
Before You Start
- You can access the report and export action.
- You know the report purpose, date range, branch, warehouse, customer, vendor, item, status, or payment method needed.
- You understand whether the report should include draft, approved, posted, paid, cancelled, pending, or synced records.
- You know who should receive the export and whether it contains sensitive data.
Steps
- Open Reports or the module-specific report page.
- Select the report type, such as inventory, procurement, vendor, sales, POS, finance, workflow, or sync report.
- Apply date range, branch, warehouse, item, customer, vendor, status, payment method, or other filters.
- Review the on-screen results before exporting.
- Compare totals with a known record, dashboard card, or previous report if needed.
- Select export format, such as PDF, CSV, Excel, or print if available.
- Name and store the export according to your organization's process.
- Share only with authorized users.
Filter Checklist
| Filter | Why It Matters |
|---|---|
| Date range | Most report mismatches come from different start or end dates. |
| Status | Draft, approved, posted, cancelled, pending, and paid records may appear differently. |
| Branch / warehouse | Reports can change when scoped to one location instead of all locations. |
| Item / customer / vendor | Specific entity filters can hide records users expected to see. |
| Currency / tax / payment method | Finance and sales reports may require these filters for reconciliation. |
Common Mistakes
- Exporting before checking filters.
- Comparing reports with different date ranges or statuses.
- Sharing exports with users who should not see sensitive data.
- Assuming a missing record is absent before checking status and permissions.
- Using screenshots instead of exports when finance or audit needs full data.
Report mismatch? Include report name, filters, date range, expected value, actual value, and example record numbers.
Support escalation
Open support guide
Need help with this topic?
Capture the module, record number, branch or warehouse, user, visible message, and what you expected to happen before contacting support.