Financial Statements
Financial statements provide merchants with a detailed breakdown of their transactions, fees, and net amounts for each settlement period. They serve as the auditable financial record of what happened during a given time range.
What Statements Contain
Each financial statement covers a specific merchant, terminal (or merchant-level aggregate), currency, and date range. The statement includes:
Transaction volumes:
- Payin count and volume (successful payments received)
- Refund count and volume
- Chargeback count and volume
- Withdrawal count and volume (informational, not subtracted from net)
- Payout count and volume (informational, not subtracted from net)
Fees:
- Total merchant fee (single aggregate number)
Rolling reserve:
- Reserve held (new withholding from this period)
- Reserve released (prior reserve returned)
- Net reserve (held minus released)
Recurrent fees:
- Subscription or access fees charged in the period (if applicable)
Net to merchant:
netToMerchant = payinVolume - refundVolume - chargebackVolume
- merchantFee
- rollingReserve.held + rollingReserve.released
- recurrentFeesNet to provider:
netToProvider = payinVolume - refundVolume - chargebackVolume - providerFeenetToProvider represents what the provider owes the platform after deducting provider fees. This field is visible to operators only.
Withdrawal and payout volumes appear in the statement for informational purposes, but they are NOT subtracted from the net amount. Withdrawals and payouts are independent balance operations, not part of settlement economics.
Statement Generation
Automatic generation:
- Financial statements are generated first, on a daily schedule, per terminal and currency combination.
- Settlement generation then collects and aggregates the relevant statements for the period and merchant (1:N relationship). Statements are the granular building blocks; settlements are the merchant-level aggregation.
- When a settlement is finalized, its linked statements transition to
paidstatus, blocking them from re-inclusion in future settlements.
On-demand generation:
- Operators can generate statements for custom date ranges outside the regular daily cycle.
- Useful for mid-period reporting or ad-hoc financial reviews.
Statement Statuses
| Status | Meaning |
|---|---|
unpaid | Statement generated, not yet covered by a finalized settlement |
paid | Linked to a finalized settlement. Blocked from re-inclusion in future settlements |
Once a statement is marked paid, it is locked and cannot be included in another settlement. This prevents double-counting.
Viewing Statements in the Portal
Operator View
Operators can view statements for any merchant:
- Navigate to Statements in the Portal.
- Filter by merchant, currency, date range, or status.
- Click a statement to see the full breakdown.
- Export as PDF or CSV for offline review or sharing.
Merchant View
Merchants see their own statements in the Merchant Portal:
- Navigate to the Statements section.
- Browse statements by period.
- View details or export.
Merchants only see their own data. Cross-merchant visibility is not available.
Visibility rules: Merchants see net amounts, the total merchant fee, and transaction volumes only. Fee decomposition (provider fee, platform fee, tenant fee, partner commission) and netToProvider are visible to operators and owners only.
Statement Granularity
Statements can be generated at two levels:
- Per-terminal: breakdown for a specific terminal and currency combination. Shows volumes and fees for that terminal only.
- Merchant-level aggregate: combined statement across all terminals for a merchant and currency. Used for the overall settlement summary.
Relationship to Settlements
Financial statements and settlements are closely linked but distinct concepts:
- A financial statement is the granular record: per terminal + currency. It contains the transaction volumes, fees, rolling reserve, and net amounts for that specific terminal.
- A settlement is the merchant-level aggregation: per merchant + currency. It collects one or more financial statements (1:N) and adds adjustments to produce the final merchant-facing document.
- The availability transition is a separate automated T+N cron process that moves funds from
pendingtoavailableafter N business days. Neither statements nor settlements move funds.
Lifecycle: statements are generated first (daily cron). Settlement generation then collects the relevant statements and aggregates them. When the settlement is finalized, its linked statements transition to paid status.
See Settlements for details on the settlement process.
Export Formats
Statements can be exported in the following formats:
- PDF: formatted document suitable for accounting and archiving.
- CSV: tabular data for import into accounting software or spreadsheets.
Export is available from the statement detail view in the Portal.
Key Points
- Statements are generated first (daily, per terminal and currency). Settlements then aggregate them (1:N).
- Each statement covers a specific merchant, terminal (or aggregate), currency, and period.
- The
paidstatus prevents a statement from being included in multiple settlements. - Merchants see net amounts, total merchant fee, and volumes only. Fee decomposition is operator-only.
- Withdrawal and payout volumes are informational only and do not affect the net calculation.
- Adjustments are applied at the settlement level, not on individual statements.