What a “complaint” should mean in this context
A complaint is a claim that something went wrong, usually described as a disagreement about actions, handling, or outcomes. When evaluating a complaint, focus on the specific facts being asserted rather than on the emotional tone. Stable parts are the definitions, the steps in a complaint process, and the type of evidence typically used (for example, account records or communication logs). Variable parts are conditions that can change what happened and why, such as market volatility, order execution, costs, and differences in reporting.
A helpful starting assumption is that the complaint may be incomplete: the complainant might not have all logs, might misunderstand how costs or execution work, or might lack context for decisions. Your goal is to transform the complaint into testable statements.
Evidence and document checks (afvinkpunten)
Use a checklist that converts vague statements into verifiable items:
- Clear allegation and scope: What exact behavior is claimed (for example, refusal to respond, incorrect handling, or dispute about charges)? What account(s) and date range does it cover?
- Timeline: Create a dated sequence of events from the complaint text. Check whether the dates are consistent with any attachments or account activity.
- Evidence of what the user saw: Look for screenshots, statements, emails, or platform messages that show what was displayed at the time.
- Evidence of what was executed or charged: Request the underlying records the claim depends on, such as statements showing deposits/withdrawals and transaction history.
- Correspondence trail: Verify whether the complainant can show attempts to raise the issue with the provider and the provider’s responses.
- Identification of disputed items: Separate disputes into categories (fees/costs, order execution, account access, withdrawal handling, recordkeeping). This helps avoid mixing issues.
Mechanics: how to test the complaint logic (bewijs of document)
Complaints often combine multiple mechanisms. To evaluate fairly, isolate each mechanism and ask what evidence would support it:
- Process failure: If the complaint says “the provider did not act,” check whether the complainant’s record shows a request was actually made, when it was received, and what the provider replied.
- Cost or balance mismatch: If the complaint claims the account balance changed “unfairly,” confirm what costs and adjustments are included in the account records (for example, commissions, fees, and other deductions). Assume the complaint may omit cost components unless documents show otherwise.
- Execution disagreement: If the complaint blames outcomes on execution, separate order direction and timing from reported fill details. Assume that market conditions can change what is filled compared with what the user expected.
A simple example with stated assumptions
Assume a complainant claims that withdrawal “failed.” To test this claim, you would check: (1) the withdrawal request timestamp; (2) the amount requested; (3) the withdrawal status shown in records; and (4) any documented reason for rejection. If the records show a completed status but the complainant reports non-receipt, you then need evidence about transfer processing and timing. Without those documents, the complaint remains a statement, not a conclusion.
Limitations and risks (rode vlaggen) + failure modes
Key limitations mean you should not treat a complaint as automatically reliable:
- Incomplete evidence: Missing screenshots, partial statements, or an unclear timeline prevent verification.
- Misunderstood terms: Users can misunderstand how costs, execution, or platform reporting works, leading to correct feelings but incorrect conclusions.
- Variable conditions: Market volatility and execution effects can produce outcomes that differ from expectations, even without wrongdoing.
- Selective reporting: A complaint may focus on one event while ignoring earlier trades, fees, or adjustments.
At least one material failure mode to watch for: conflating account outcomes with process responsibility. For example, a negative outcome can be caused by costs or execution conditions, while the complaint claims a handling error. Evidence must connect the alleged process failure to the financial or operational result.
Verification and “klarcriterium”: what would change your view?
Decide what evidence would be decisive. A “klarcriterium” is a specific set of documents or facts that, if present, would support the allegation.
Examples of criteria you can apply without predicting outcomes:
- If the complaint alleges refusal to process requests, the decisive items would include timestamps and the provider’s written responses.