Appearance
Reporting Operations & Usage
This page explains how end users consume reports after the reporting administration side has been configured.
Navigation: Reporting -> Reports
Runtime Areas
The reporting runtime is organized into:
- Run Reports
- Snapshots & Presets
- Schedules
Most users work mainly in Run Reports. The other two areas support reuse, preservation, and automation.
Typical User Journey
The normal reporting journey is:
- choose a report group
- choose a report
- enter or reuse parameters
- generate the result
- review and drill down
- export, save a preset, or capture a snapshot
Run Reports
The Run Reports page is the main execution workspace.
It is usually consumed in three stages:
- group selection
- report selection
- parameter entry and execution
Group selection
The left panel shows report groups from the report catalog.
If a group is missing, the likely causes are:
- the group is not active
- no accessible reports exist inside it
- the user does not have access to the underlying definitions
Report selection
After selecting a group, the center panel shows report cards.
Each report card normally reflects:
- report name
- code or description
- report type
If a report card is missing, first check the report definition rather than blaming runtime.
Parameter entry
Once a report is selected, the parameter area lets the user control the scope of the run.
Common parameters include:
- from date
- to date
- currency
- business units
Financial statement reports may also expose:
- FS template
- column set
Presets may appear as quick actions for repeated runs.
Reviewing Results
After clicking Generate, the report viewer renders the result according to the report design.
The result may appear as:
- a standard table
- a structured financial statement
- a richer JSON-driven report layout with KPIs and multiple tables
Users should always review the visible result before exporting or scheduling a report.
Drilldown
Where supported, users can drill from a summary number into its supporting detail.
Typical drilldown patterns include:
- trial balance amount to journal detail
- statement line to supporting balances
- summarized count to transaction or account-level rows
Not every report exposes drilldown. If it is absent, that is usually a report-design decision, not a user mistake.
Export
Users can export generated reports to:
- Excel
- CSV
Recommended usage:
- use PDF for presentation and circulation
- use Excel for review and further analysis
- use CSV for lightweight extraction or external loading
Financial Statement User Flow
For financial statements, the normal business-user flow is:
- open
Run Reports - select the correct report group
- choose the required financial statement definition
- enter date range, currency, business unit, template, or column set as required
- click Generate
- review totals, subtotals, and comparative columns
- drill down where explanation is required
- export or save a snapshot
Presets
Presets save reusable parameter combinations.
Use presets when:
- the same report is run repeatedly
- month-end teams need a standard parameter pack
- managers repeatedly view the same scope
Presets reduce setup time and reduce manual entry mistakes.
Snapshots
Snapshots preserve a point-in-time copy of report output.
Use snapshots when:
- you need a frozen month-end or quarter-end result
- management wants a reviewed output preserved
- audit or follow-up work needs a stable reference point
Schedules
Schedules automate recurring report execution.
Common uses:
- morning dashboards
- weekly exception reports
- month-end statement packs
Only schedule a report after it has been validated successfully in manual execution.
Operational Troubleshooting
No report groups visible
Check:
- report groups exist
- groups are active
- accessible report definitions exist
Report card missing
Check:
- definition is active
- definition is assigned to the expected group
- user access is correct
Financial statement renders like a normal table
Check:
- report type is
FINANCIAL_STATEMENT - the correct FS template is linked
- the output mode matches the actual statement procedure
Drilldown does not open
Check whether drilldown support was designed for that report. Some reports are intentionally summary-only.