Skip to content
Genesis Ark

11 / Reporting

Available

Statements, confirmations and regulatory reports from the same records you trade on

Qubit's reporting module turns orders, fills, ledger entries and transfers into the documents clients, auditors and regulators ask for. Because reports are built from the trading records themselves, the numbers in a statement match the numbers on the blotter.

Layer
Standalone, read-only
Works on its own
Yes
Interfaces
PDF, CSV, JSON; email, SFTP, API
Fig. 1. A monthly report pack: statements, confirmations and a TDS summary. Illustrative composition with sample data.

01 / The problem

Reports built by hand never quite match

Client statements come from one export, regulatory reports from another, and the finance team rebuilds its own figures in a spreadsheet. Each copy drifts a little from the others. When a client disputes a balance or an auditor asks for every trade on one day, finding the right number takes longer than it should, and in India, tax deducted at source on crypto transfers adds another set of figures that must reconcile with everything else.

02 / What it does

What the module produces

  1. 01

    Trade confirmations

    Per trade or per day, with instrument, side, quantity, price, fees and settlement details.

  2. 02

    Client statements

    Periodic statements of trades, balances, deposits, withdrawals and fees per client account.

  3. 03

    Activity and P&L reports

    Daily, monthly and custom-period activity and P&L by entity, desk, account and instrument.

  4. 04

    Best-execution reports

    Periodic summaries from TCA by instrument, venue and client, including RFQ quote comparisons.

  5. 05

    Audit exports

    The full event history for an order, an account or a time range, from the audit trail, in a format auditors can use.

  6. 06

    Regulatory exports

    Trade and transaction data in configurable formats for regulators and compliance tools, by jurisdiction.

  7. 07

    India TDS reports

    TDS computation on transfers of virtual digital assets under section 194S, per client and per period, with the data your finance team needs for filing.

  8. 08

    Scheduled delivery

    Reports run on a schedule and are delivered by email, SFTP or API, or kept in the console for download.

03 / How it works

From records to delivered reports

Fig. 2. The stages below, in order. Each one writes to the audit trail.
  1. 01

    Source

    Reports read orders, fills, ledger entries, transfers and audit events from Qubit, or from records you import.

  2. 02

    Template

    Each report type has a template with your branding, fields and format: PDF, CSV or JSON.

  3. 03

    Generate

    Reports run on demand or on a schedule, for a period, an entity or a client group.

  4. 04

    Check

    Totals in each report reconcile with the ledger for the same period; differences are flagged before delivery.

  5. 05

    Deliver

    Reports go to clients and internal teams by the channel you configure, and every delivery is logged.

04 / Specifics

Technical specifics

Formats

PDF for client documents; CSV and JSON for data exports; custom templates per report type.

Periods

Daily, weekly, monthly, quarterly, annual and custom date ranges, in the time zone you set per entity.

Grouping

Legal entity, desk, client account, client group, instrument, venue.

India TDS

TDS rate and thresholds are configured, not hard-coded, so changes in rules can be applied without a release. Qubit computes and reports; filing remains with your firm. Qubit does not give tax advice.

Data retention

Set by your firm to meet your record-keeping obligations. In a self-hosted install, all report data stays in your environment.

05 / Controls and audit

What you configure, and what gets written down

Configurable

  • Templates per report type: branding, fields, format
  • Schedules, periods and time zone per entity
  • Grouping by entity, desk, client account or group
  • TDS rate and thresholds
  • Delivery channel per recipient
  • Data retention period

Logged to the audit trail

  • report generated · type, period, scope
  • ledger check · totals matched or difference flagged
  • delivery · channel, recipient, time
  • template change · user
  • TDS configuration change · old and new values

06 / Where it fits

Works on its own
Yes. It is read-only and can work from trade records you provide by file or API.
Needs the core
No. With the core installed, it reads orders, fills, the ledger and the audit trail directly.
Who uses it
Brokers and exchanges sending client statements, compliance and finance teams, banks reporting to regulators, Indian intermediaries handling TDS.

FAQ

Questions we get asked

  • Can we brand client statements?

    Yes. Statements and confirmations use your templates, logo, legal entity details and disclaimers.

  • Which regulators do you report to?

    Qubit produces exports in configurable formats; your firm submits them. We work with each client on the formats their regulators require, and the Compliance page describes regional support.

  • Does the TDS report file returns for us?

    No. Qubit computes TDS per transaction and client and produces the reports your finance team uses to file. Filing and the final tax position stay with your firm and its advisers.

  • Can we generate reports from data that was not traded through Qubit?

    Yes. The standalone module accepts trade and transfer records by file or API and produces the same reports.

One set of records behind every report

A scoping call with an engineer, then a demo on sample data that mirrors your venues, desks and limits.