Define “data and platform fees” before you verify
Data and platform fees are charges related to access to market data and the use of trading or execution technology. “Data fees” typically cover the right to receive specific data products (for example, different feeds or tiers). “Platform fees” typically cover access to a service used to place and manage orders and to interact with the market.
A key point for verification is that fee information may mix stable definitions (what a fee is and what it covers) with variable mechanics (how the fee is calculated under different usage or trading conditions).
Build a source hierarchy for fee information
Use a hierarchy that starts with the most direct and controllable documents:
- Official fee schedule / pricing page: The primary place where fee names, amounts (if applicable), currencies, and calculation methods are described.
- Service terms and disclosures: These often define scope, what triggers charges, and how changes are handled.
- Data product documentation: If the provider sells multiple data products, documentation clarifies what each product includes.
- Account and transaction statements (receipts): These show what was actually charged for a specific period.
- Third-party summaries: Use only as leads. They are harder to rely on for exact wording and calculation details.
Use reproducible verification steps
You can verify fee information without assuming future results by using a repeatable workflow.
-
Extract the “fee components” separately Write down each named charge (for example: a platform access fee, a market data subscription, or per-activity charges). Keep them separate, because totals are often a sum of multiple components.
-
List the calculation rule exactly as stated For each component, record the rule (for example: fixed per month, per unit of data, per executed action, or based on volume). If the provider uses tiers or thresholds, note those explicitly.
-
State assumptions for any example you test If there is a numerical example, copy the underlying assumptions: dates, data tier, expected usage level, and what “activity” means. Then recompute the total from the published numbers.
-
Confirm with an independent observation After you have a concrete period and a specific account activity, compare your computed expectation to what appears on the provider’s statement/receipt for that same period. This checks whether the stated rule matches real billing.
-
Track material limitations and mismatches Look for differences caused by timing (when a charge posts vs when activity happens), rounding, currency conversion, or whether intermediate parties pass through costs. These are common failure modes when fee information is incomplete or overly simplified.
Understand limitations and failure modes
Even when documents look clear, verification can fail for material reasons:
- Missing scope details: A pricing page may list a headline fee but omit what exactly qualifies as billable “data” or “platform usage.”
- Variable factors not reflected in examples: Some fees depend on usage patterns, execution behavior, or subscription tier selection.
- Change management: Fee schedules and terms can be updated; a statement from a prior period may not reflect current rules.
- Hidden intermediaries: Costs may be split across direct charges and pass-through charges.
Treat any single document as insufficient. Verification is stronger when you cross-check the pricing description against the terms and then against at least one statement period.
Verification checklist: what you should be able to explain
When you finish, you should be able to explain—using only the provider’s own documents—(1) what each fee component covers, (2) how it is calculated, (3) what assumptions are required to compute an example, and (4) what limitation could change the outcome. If any of those points cannot be derived from official materials, that uncertainty should be recorded rather than resolved by guessing.