Definition of “costs” in a complaint
In a forex context, “complaints” often involve a dispute about what you were charged or what you effectively received. “Costs” can be direct (amounts billed per transaction) or indirect (amounts that arise from how positions are carried, priced, or executed). A clear description helps you separate what is a stated charge from what is an outcome influenced by market conditions.
Direct costs that can be disputed
Direct costs are typically observable in transaction-related records. Common examples are:
- Spread-related cost: when the buy and sell prices used to enter or exit differ, the difference acts like a cost (or reduced proceeds) even if no explicit fee is shown.
- Commission or fees: some providers apply explicit commissions per trade or account maintenance charges.
Assumption for examples: suppose a trade is executed at a quoted price using a bid/ask mechanism, and you compare the provider’s execution price to what you consider the “expected” price. Any difference can be framed as spread-related or fee-related depending on whether a commission is separately stated.
Indirect costs created by mechanics
Indirect costs are not always listed as a single line item. They come from financing and risk mechanics or from order execution details.
- Financing and carry effects: positions held over time can lead to daily/periodic financing charges or credits. If your complaint involves holding duration, financing becomes a relevant cost driver.
- Margin and leverage effects: leverage does not create profit by itself, but margin rules can increase the impact of price movement. If a complaint centers on outcomes near limit levels, the issue may relate to the cost of exposure and forced position changes.
- Execution quality (slippage and latency): in fast-moving markets, the price you see may differ from the price at which the order is filled. This can create an outcome that feels like an additional cost, even when no explicit fee is charged.
Assumption for an execution example: if you place a market order and the market moves between request and fill, the net result changes. The difference between the intended execution price and the actual fill price is a useful way to describe an indirect cost.
Material limitations and failure modes
Several factors can limit how well “costs” explain a complaint:
- You may mix costs with outcomes: price movement can dominate the difference you observe, even if fees were correct. Costs should be isolated from market-driven gains/losses.
- Different cost definitions: some providers present gross amounts; others present net amounts after fees and financing. Without stating which view you are using, comparisons can be misleading.
- Record mismatch: transaction reports, statements, and execution logs may use different timestamps or rounding. Small differences can change the disputed number.
- Historical relationships don’t predict: even if a cost pattern was similar in the past, it does not ensure the same behavior in a different market regime.
Verification: what you can check independently
You can verify relevant facts by making your assumptions explicit and matching them to records. A practical approach is:
- Start with a timeline: order placement time, fill time, and any holding period boundaries.
- Identify each cost component type: commission/fee lines (direct), bid/ask difference used for fills (spread-related), and financing lines for held time (indirect).
- Reconcile prices used: compare your understanding of prices to the provider’s recorded execution prices and timestamps.
- Compute with stated assumptions: when showing the disputed number, separate (a) fee/commission totals, (b) spread-related effects derived from recorded bid/ask prices, and (c) any financing or carry entries.
Next question to clarify your complaint
To explain a complaint accurately, you need one clarification: are you disputing (1) what was charged, (2) how pricing was applied at execution, or (3) how holding and risk mechanics changed the net result? Each answer points to different cost components and different records to verify.