Organization data
Overview cards
Summary metrics loaded from the reports endpoint for the selected dashboard period.
Browse this guide
Understand the Reports workspace
The dashboard and report library look related, but they do not all have the same data guarantees.
Source-backed
Integrated report cards
Named reports that request their own backend endpoint and return rows, summaries, and chart data.
Preview only
Remaining library cards
Reports without an integrated endpoint currently generate randomized preview content in the frontend.
A polished report is not automatically a source-backed report
Preview reports use the same detail view, charts, and export actions as integrated reports. Their appearance does not make the figures real. Confirm the report name against the lists below before using a result in a business decision or sending it outside your organization.
Use the source-backed report cards for organization records
The following cards have explicit backend report endpoints in the current frontend. Results still depend on the records and period returned by your organization.
- Sales by Product
- Sales by Employee
- Revenue Trends
- Pipeline Conversion
- Deals Won vs Lost
- Recurring Revenue (MRR)
- Customer Lifetime Value
- Churn Report
- Source Attribution
- Outstanding Invoices
- Expense Breakdown
- Stock Movement
- COGS Report
Source-backed does not mean audited
These cards request organization data rather than generating a local preview. Reconcile important totals with the underlying invoices, expenses, deals, customers, or stock records before relying on them.
Treat every other report card as a preview
Cards not named in the source-backed list currently fall back to locally generated sample rows, summaries, and charts.
Preview values change between generations
The frontend uses randomized values for non-integrated reports. This includes Profit & Loss, Balance Sheet, Cash Flow Statement, Trial Balance, Tax Summary, Aged Debtors, Bank Reconciliation, and the current industry-specific report library. Other unlisted cards should also be treated as previews.
- Do not use preview totals for accounting, tax, payroll, or compliance work.
- Do not compare two preview generations as a trend; the values can change randomly.
- Use the preview to understand the intended report layout, not the state of the business.
- Return to the source records when a decision requires evidence.
Generate and review a report
Choose the data status first, then use the period and detail view deliberately.
- 1
- 2
Choose the dashboard period
Use the period control beside the page heading to refresh the overview cards. This control applies to the dashboard summary. - 3
Choose a source-backed card when accuracy matters
Select a category, compare the card name with the source-backed list in this guide, then generate the report. - 4
Set the report period in the detail view
The generated report has its own reporting-period control. Changing it regenerates the current report; do not assume the dashboard period was carried into the detail view. - 5
Inspect the rows behind the summary
Review the subtitle, summary cards, table rows, and chart together. Empty rows mean there is no report data to export for that result.
Export only after checking the report source
PDF, print, and CSV actions package the report currently open in the detail view.
Tabular copy
CSV
Downloads the current title, subtitle, summary, columns, and rows for spreadsheet review.
Formatted copy
PDF and print
Generate a formatted copy of the current report for saving or printing.
Exports may contain preview data
Export actions are available for preview reports as well as source-backed reports. Downloading a PDF or CSV does not validate the figures or convert preview content into organization data.
Account for currency and access limitations
Use the report interface within the guarantees the current frontend can make.
- The Reports page requires the view_reports permission.
- Report data does not include a reliable report-level currency definition.
- Several dashboard, detail, and preview values are formatted with a dollar sign.
- The interface does not prove that mixed-currency records were converted before aggregation.
Do not treat the dollar sign as conversion evidence
Confirm the currency of the underlying invoices, expenses, deals, and products before sharing a monetary total. For mixed-currency reporting, reconcile the records outside this view until the report contract supplies explicit currency and conversion metadata.