AUDITEDTRADER / STATEMENT RECONSTRUCTION
Statement Package Requirements and Submission Status
Prepare original records and scoped questions; no active receiving inbox or audit engagement is confirmed.
Include the claim scope
State the preferred display name, whether the record is personal, competition, model, or product evidence, the covered dates, account or division, base currency, and which metrics you want checked.
Send source material safely
Provide statements, administrator links, competition records, or timestamp receipts through an agreed channel. Never send broker passwords, API keys, recovery codes, or unrestricted account access. Redact unrelated personal information where it does not affect verification.
Expect questions
The review may ask about deposits, withdrawals, open positions, account transfers, benchmark definitions, missing months, or a difference between a headline return and the reconstructed series. A question is not a rejection; it is how claim scope is kept honest.
Publication is conditional
A submitted package can be declined, published with limitations, or corrected later. AuditedTrader does not publish synthetic sample identities as audited traders, and a product or customer-performance claim needs evidence that actually covers that product or customer population.
These pages describe the registry's evidence boundary. They do not turn historical evidence into financial advice or a promise of future performance.
No active receiving inbox or audit desk has been verified. Consult the submission-status page before transmitting records; never disclose credentials or unnecessary private account details.
A useful submission is a source package, not a performance headline. The audit desk needs enough context to identify the claim, inspect the period, and explain the boundary of any public record.
Submission readiness is not a live submission endpoint
No verified receiving inbox, upload backend or formal engagement is provided by this page. The checklist describes the evidence a real reconstruction would need. Retain the original records privately until an accountable recipient and appropriate channel are confirmed.
A provider should never need a password, recovery code, private key or unrestricted broker access to receive a scoped explanatory record. Redaction may protect unrelated identifiers, but the remaining fields still need to support any proposed account and period join.
Prepare a reproducible, bounded request
Identify the claim, measured account or model, covered interval, reporting currency and requested calculation. Include source provenance, flow and charge treatment, open-position marks and unresolved exceptions where relevant. Separate operator-prepared summaries from original issuer records.
If only a supplied historical headline exists, label that limitation. A request can ask which records would resolve it without implying an audit was completed. The source dossier helps organise notes but does not transmit them, certify them or create an assurance contract.
The smallest useful first request
Before sending confidential files, describe the proposed question without exposing unnecessary account identifiers. State whether the question concerns one personal account, a competition division, a model ledger or a customer population. Identify the interval and which original sources exist. That lets an accountable recipient explain the required scope before private data are transferred.
A single headline, credential or digest is not a complete evidence package. A recipient may need originals, redaction mapping, transaction classification, marked equity and cost treatment. If those records are unavailable, ask for an explicit limited deliverable rather than a clean opinion. This page remains a preparation checklist and submission-status notice, not an active upload endpoint or verified private review service.
Complete authored statement packet | Monetary reconciliation bridge | Calendar coverage map