Verification starts with definitions
“Exotic pair” usually means a currency pair that is less commonly traded than major pairs. “Broker” information may include instrument specifications, order handling, costs, and risk disclosures. Because terms can vary by provider, start by verifying what the specific provider means by “exotic” and which instruments it includes. Treat any label as a claim that should map to an observable description (for example, an instrument list and its trading rules).
Build a source hierarchy (what to trust first)
Use a hierarchy so you do not rely on promotional summaries:
- Primary documents: the broker’s legal or regulatory disclosures, agreement terms, and instrument/trading documentation.
- Platform or operational records: account opening steps that display instrument availability, order-entry screens, and any downloadable statements or reports that show prices and costs.
- Time-stamped user-facing information: official announcements, change logs, and documented updates that explain when terms or specifications changed.
- Third-party commentary: use only to generate questions, not as proof. Treat it as secondary until you can trace claims back to primary documentation.
Even without real-time market data, you can still verify consistency by checking whether the same facts appear across multiple broker documents and account screens.
How verification can work in practice (reproducible steps)
Follow a checklist you can repeat:
- Extract the exact “instrument definition.” Write down the instrument name/code shown on the platform and any stated trading conventions (contract size, quote conventions, trading hours, and execution method if disclosed).
- List all costs and where they appear. Separate (a) stated fees/commissions, (b) cost embedded in pricing (if described), and (c) any additional charges in account statements. Don’t assume a cost is absent just because it is not mentioned in one place.
- Reconcile a small, documented simulation. Use a hypothetical example with explicit assumptions: choose an example position size, assume a reported bid/ask at a given timestamp, and compute the spread/expected cost using only the broker’s displayed pricing and stated conventions. Keep the assumptions written so someone else can repeat the calculation.
- Check agreement-versus-screen consistency. Confirm that what the platform shows for costs and instrument rules matches what the agreement says. If they differ, record the exact wording and the screen/document where each version appears.
- Look for update mechanisms. Identify how you would be informed of changes to instrument specs or order handling rules. A verifiable system has a clear versioning or notification path.
Evidence and example you can reproduce (without relying on predictions)
Example verification logic (illustrative, not a recommendation):
- Assumptions: You assume the broker provides an instrument with a stated quote convention and you select a single timestamp where the platform displays bid and ask.
- Computation: You compute the quoted spread as (ask − bid) in quote-currency units, then translate it using the broker’s stated contract/lot convention.
- Consistency check: You compare whether the computed cost aligns with how the broker describes transaction costs (for example, whether the agreement implies additional commissions beyond the spread).
This approach tests whether the broker’s pieces fit together. It does not test future profitability; it only tests internal consistency between displayed data, stated rules, and contract conventions.
Limitations and failure modes to account for
Material limitations can cause verification to fail even when documents exist:
- Ambiguous terminology: “exotic” may be used informally; only instrument lists and specs provide an unambiguous mapping.
- Hidden or indirect costs: costs may appear via pricing or conversions rather than a clearly labeled fee.
- Execution and order handling differences: even with correct instrument definitions, execution quality can vary with liquidity and the broker’s order handling approach.
- Jurisdiction and account setup variability: the same broker may apply different terms depending on the account or region; verify the terms that apply to the specific account type.
- Historical relationships don’t generalize: past price behavior or reported spreads do not prove future trading conditions.
Verification checklist results in a “what to ask next” plan
After you complete the checks, you should be able to answer three questions using your notes:
- **What exactly is the instrument and how is it quoted? ** (name/code, conventions, trading rules)
- **Where do all costs come from, and how do they show up in records?