Reporting

In MustardHub, reporting refers to structured, record-based outputs designed for oversight, reconciliation, auditability, or formal review.

Reports are:

Based on defined data records and time ranges
Deterministic and reproducible
Intended to answer what happened, when it happened, and what was recorded

Reporting exists to support clarity, accountability, and traceability. It is not designed to provide interpretation, guidance, or recommendations.

Reporting in MustardHub spans several functional areas. Not all reporting requires an upgraded account, and not all reporting lives in a single location.

At a high level, reports fall into these categories:

Activity and participation reporting

Summarizes engagement activity across the Organization, such as participation levels, recognition volume, or usage patterns over a defined period.

Financial and transaction reporting

Provides structured records related to points, transfers, billing, and balances.

Compliance and tax-related reporting

Supports compliance workflows by providing exports or summaries required for tax classification or regulatory review. Detailed treatment of these topics is owned by dedicated tax and compliance articles and is not restated here.

Analytics-backed reporting (advanced)

Supported by the Advanced Analytics Engine and available only on upgraded plans. These reports aggregate and structure data across larger time horizons or dimensions, while remaining record-based rather than interpretive.

What questions reporting is designed to answer

Reporting is designed to answer factual, bounded questions, such as:

What activity occurred during a defined period?
Who participated, and at what level?
What transactions or records exist for review?
What totals, distributions, or summaries can be produced from recorded data?

Reporting is not intended to answer why behavior occurred, what action should be taken, or what is likely to happen next.

Where reports live and who can access them

Reporting in MustardHub does not live in a single, isolated area.

Depending on the type of report:

Some aggregate reporting appears directly on dashboards as summary views or snapshots
Some reporting lives within the functional area it relates to, such as Treasury or Wallet history
Advanced or cross-dimensional reporting lives in the Analytics Studio and may require an upgraded account

Access to reporting is governed by Admin roles and permissions. Not all Admins see the same reports, and not all reports are available in every plan tier.

For more information about access and permissions, see C.5: Members, Roles & Permissions.

Reporting versus insights (high-level distinction)

Reporting is retrospective. It describes what has already occurred, based on recorded system data.

Insights are prospective. They use accumulated context and models to suggest what patterns may mean or what outcomes may be emerging.

If you need hindsight and traceability, reporting is the correct surface.

If you need foresight or interpretation, insights are the correct surface.

For a deeper explanation of interpretive outputs, see C.6: Predictive Insights.

Reporting in MustardHub is not intended to provide financial, tax, or legal advice, recommend business actions or review cadence, replace compliance judgment or professional review, or predict outcomes or assess future risk.

Reports provide structured inputs. Interpretation and decision-making occur outside the reporting layer.

Reporting

What questions reporting is designed to answer

Where reports live and who can access them

Reporting versus insights (high-level distinction)

Recommended articles