Surfaces
Finance Analytics
Payment provider totals, account capacity, balance offsets, and reconciliation signals.
First created Last updated
Overview
Finance Analytics explains where money was collected, which configured payment accounts received it, how much platform fee has been collected, and how much remains to be remitted through settlements. It is a review surface, not an editing surface. Use it before changing payment accounts, recording settlements, closing an event, or explaining finance discrepancies to event leads.
The page combines completed registration payments, Dealers Den registration payments, POS transactions, payment account settings, manual balance offsets, and settlement records.
Dashboard route
/ems/manage/finance-analytics?id=:eventId
Page header and event context
The page loads the selected event title, date range, and timezone. It also rewrites the Payments Config link so it stays attached to the same event id. If the event id is missing or the dashboard session is unavailable, the page shows an error instead of displaying empty finance numbers.
Overview chips
| Chip | What it means | Why it matters |
|---|---|---|
| Gross collected | Total tracked money collected across the event finance sources. | Gives a top-level total before looking at provider or account splits. |
| Tracked sources | Count of registration, Dealers Den, and POS entries contributing to totals. | A sudden low count usually means the event has little activity or a data source is not included yet. |
| Providers configured | Number of payment providers configured for the event. | Shows how many payment methods are available for collection and reconciliation. |
| Accounts configured | Total receiving accounts across all configured providers. | Helps staff understand whether collections are spread across multiple accounts. |
Summary cards
| Card | What it shows | How to use it |
|---|---|---|
| Total duty-free amount | Base event revenue before platform and processor fees. | Use this to separate event revenue from fee money. |
| Total platform fees collected | Platform fees currently collected through active event transactions. | This is the starting point for what may need remittance to Furries PH. |
| Total processor fees collected | Payment processor fees collected across active transactions. | Use this when explaining why gross collected is higher than the duty-free base. |
| Still to remit | Platform fees collected minus recorded settlements. | Use this before opening Settlements. |
| Over remitted | Appears when recorded settlements exceed collected platform fees. | Investigate duplicates, incorrect settlement amounts, or finance data corrections. |
Tracking hint
The page displays a tracking hint from the finance API. This text exists to explain what the current financial picture needs next, such as reviewing configured providers, checking account capacity, or recording settlements.
Do not ignore this hint when the totals look normal. It often points to the operational reason a finance lead opened the page.
Provider sections
Each provider section groups collections by payment provider. A provider might be a QR payment method, bank transfer channel, wallet provider, or another configured method from Payments Config.
| Provider metric | What it means | Why it matters |
|---|---|---|
| Duty-free | Base amount collected through that provider before platform and processor fee portions. | Helps compare provider volume without fee noise. |
| Platform fees | Platform fee amount collected through that provider. | Helps estimate settlement responsibility by payment channel. |
| Processor fees | Processor fees collected through that provider. | Helps explain extra payment costs. |
| Gross collected | Total tracked amount collected through that provider. | Helps reconcile provider statements or receiving-account balances. |
| Collected entries | Number of tracked payment entries for that provider. | Useful when totals look high or low compared with expected transaction count. |
If a provider has no payment accounts configured, the page says so. That is a setup problem if staff expect the provider to receive live payments.
Account cards
Account cards explain receiving-account capacity and status. Account numbers are masked except for the last digits so staff can identify accounts without exposing the full number on the analytics surface.
| Account field | What it means | How to interpret it |
|---|---|---|
| Account title | Internal name, public label, or provider fallback. | Use it to match the card to the intended account in Payments Config. |
| Account name and masked number | Bank, wallet, or payment account identity. | Confirm the receiving account without exposing the full account number. |
| Active badge | Whether the account is currently active. | Inactive accounts should not be receiving new payments. |
| Local default / Intl default | Whether the account is preferred for local or international flows. | Explains why the system may route collections or suggested payments to this account. |
| Full badge | The account reached or exceeded its configured capacity. | Review before allowing more payments into that account. |
| Needs review badge | The account needs operational attention. | Check capacity, offset, and real-world account balance. |
| Cap | Configured receiving limit. | Use it to understand how much should be allowed through the account. |
| Offset | Manual balance adjustment configured for the account. | Should reflect real-world movement, not cosmetic correction. |
| Tracked collected | Event collections assigned to the account. | Compare with external account statements. |
| Remaining cap | Available capacity after tracked balance is considered. | Negative or zero values need review before more payments are routed there. |
| Tracked balance | Manual offset plus tracked collections. | This is the dashboard’s effective balance estimate for that account. |
Related actions
Use Payments Config to correct provider setup, account labels, caps, preferred accounts, surcharging, or offsets. Use Point of Sales to inspect onsite sale behavior. Use Settlements only after confirming the remaining platform fee amount and checking whether any account card needs review.
Common mistakes
Do not change balance offsets to hide warnings. Offsets should represent real money movement such as transfers, withdrawals, or corrections. Do not record a settlement from a provider total alone; use the platform fee remaining amount and the settlement quote flow.