Analytics & ReportingCopy Anchor Link

Data visibility is critical for merchants. The platform provides real-time operational dashboards and tax-oriented reporting backed by canonical tax records.

The DashboardCopy Anchor Link

The default view upon logging in is the Dashboard. It aggregates real-time data across your active Sites.

Key metrics include:

• Gross volume: Total processed transactions over the selected trailing period, such as 7 days or 30 days.
• Net revenue: Gross minus refunds and computed upstream provider fees.
• Failed attempt ratios: Helps identify surges in fraudulent card testing or widespread bank outages.

Tax And VAT OSS ReportsCopy Anchor Link

Tax reports are generated from canonical tax_records, not from ad hoc transaction totals. This lets the Admin Panel aggregate sales, invoices, refunds, chargebacks, and credit notes consistently while preserving drill-down links to the source documents.

Available tax reporting views include:

• Tax by country: Net, tax, and gross amounts grouped by tax country and rate.
• Revenue by country: Revenue-style summary by country.
• VAT OSS: Quarterly EU OSS aggregation with country/rate/supply-type basis rows.

Navigate to Reports > VAT OSS for OSS filings:

1. Select the calendar year, quarter, timezone, and source basis (transactions, invoices, or both).
2. The report aggregates active tax records where OSS or OSS-reportable cross-border B2C treatment applies.
3. Refund and fund-impacting chargeback tax records reduce the relevant totals instead of mutating the original sale. Won chargebacks are voided for reporting, and chargeback credit notes are issued only for lost or accepted disputes.
4. Mixed goods/digital-service and EU/non-EU adjustments stay line-based: goods and shipping follow the shipping destination, digital service, tax, and discount lines follow billing country, and export or untaxed residual lines stay outside VAT OSS.
5. Export the data as OSS XML or Elster CSV when the local filing workflow requires it.

Historical receipt corrections use a separate guided administrator workflow. Select the later return first, then choose the previously filed return, verify its filing reference, OSS registration and filed date, and review the eligible correction, calculation preview, and authorization history. Viewers retain the read-only report and its already authorized corrections without seeing unusable mutation controls. The workflow displays currency amounts in normal units, such as EUR 19.00, and does not ask operators to copy database IDs or construct idempotency keys. Authorizing a correction is an explicit action; opening the preview does not post or file anything.

To record a previously filed return, enter the amount actually filed for the original Union OSS country and quarter in human currency units, provide the exact OSS registration identifier and filing reference, and select the evidence document. The browser computes its SHA-256 digest locally; the document is not uploaded by this workflow. Review the irreversible evidence summary before saving. New entries are registration-bearing evidence usable for receipt qualification when every scope field matches. If the exact immutable filing already exists as schema-1 history, the system preserves its ID and correction history and adds a separate immutable registration companion; divergent filing facts are rejected.

The application blocks XML and CSV filing exports when receipt-tax obligations are unresolved, the Mongo snapshot is not consistent, historical discovery is bounded but incomplete, more corrections exist than the complete bounded preview can prove, or the evidenced member state and selected return are incompatible. The report explains the full blocker count, shows a bounded set of affected records with safe navigation, and gives a next action for each blocker class. An empty report is a draft with exports disabled until reportable sales or authorized corrections exist. The JSON report remains available for review and states the incompleteness. These controls do not submit to a tax portal, do not treat missing filed history as zero, and do not claim support for national exceptions outside the normal product correction window.

See Invoicing & Tax architecture for the full tax record lifecycle.

Use Reports > Tax by Country when you need a country-level reconciliation view before filing or exporting. It uses the same canonical tax-record basis as VAT OSS reporting, then groups active records by country and rate so finance teams can drill back into the source records when reviewing totals.