بحث موثق بالمصادر: Binance / Kraken / Kucoin

Verified source facts

1. Binance documents limited monthly statement generation, possible multi-report date segmentation and download links that expire after seven days. 2. Kraken offers Account Statement, Trades, Ledgers and Balances exports, notes that direct order-history export is unavailable, and says generation may take minutes to a week. 3. KuCoin documents up to 20 reports per month, a maximum one-year range per export and download links valid for 30 days. 4. MEXC exposes a general account-data export and separate product-specific export paths for spot, futures and funding records.

Comparison at a glance

1. Control test: Export object

A trading-control disclosure is meaningful only when converted into a testable rule. For export object, inspect statement, trade, ledger, order or balance. Use a sandbox, non-production context, or the smallest reversible test available, then define the accounting question first. Capture configuration and event evidence without recording credentials, and verify the documented cancel, reject, decrement, or history behavior.

Model the failure path, not just the setup path. Ask which strategy owns the maker and taker orders, which account boundary the venue evaluates, which message reveals intervention, and how reconciliation behaves after a partial fill or disconnect. Platform documentation describes supported settings; it cannot prove that an operator configured them correctly. In this dimension, hidden field coverage is therefore an explicit audit gap.

The export object row should end with a concrete monitoring rule tied to statement, trade, ledger, order or balance. Make the operator define the accounting question first, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; hidden field coverage remains a separate production risk until observed.

2. Control test: Date window

For date window, inspect maximum period per request. Use a sandbox, non-production context, or the smallest reversible test available, then use explicit UTC boundaries.

In this dimension, historical availability is therefore an explicit audit gap.

The date window row should end with a concrete monitoring rule tied to maximum period per request. Make the operator use explicit UTC boundaries, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; historical availability remains a separate production risk until observed.

3. Control test: Quota

For quota, inspect monthly generation allowance. Use a sandbox, non-production context, or the smallest reversible test available, then track requests in an archive ledger.

In this dimension, account-tier variance is therefore an explicit audit gap.

The quota row should end with a concrete monitoring rule tied to monthly generation allowance. Make the operator track requests in an archive ledger, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; account-tier variance remains a separate production risk until observed.

4. Control test: Generation time

For generation time, inspect synchronous or queued creation. Use a sandbox, non-production context, or the smallest reversible test available, then schedule before reporting deadlines.

In this dimension, peak delay is therefore an explicit audit gap.

The generation time row should end with a concrete monitoring rule tied to synchronous or queued creation. Make the operator schedule before reporting deadlines, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; peak delay remains a separate production risk until observed.

5. Control test: Notification

For notification, inspect email, SMS, onsite or manual checking. Use a sandbox, non-production context, or the smallest reversible test available, then verify completion inside the official account.

In this dimension, delivery reliability is therefore an explicit audit gap.

The notification row should end with a concrete monitoring rule tied to email, SMS, onsite or manual checking. Make the operator verify completion inside the official account, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; delivery reliability remains a separate production risk until observed.

6. Control test: Download lifetime

For download lifetime, inspect expiration of generated links. Use a sandbox, non-production context, or the smallest reversible test available, then download promptly into encrypted storage.

In this dimension, future policy is therefore an explicit audit gap.

The download lifetime row should end with a concrete monitoring rule tied to expiration of generated links. Make the operator download promptly into encrypted storage, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; future policy remains a separate production risk until observed.

7. Control test: Sub-accounts

For sub-accounts, inspect inclusion and attribution. Use a sandbox, non-production context, or the smallest reversible test available, then preserve source-account identifiers.

In this dimension, entity boundaries is therefore an explicit audit gap.

The sub-accounts row should end with a concrete monitoring rule tied to inclusion and attribution. Make the operator preserve source-account identifiers, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; entity boundaries remains a separate production risk until observed.

8. Control test: File semantics

For file semantics, inspect orders versus fills versus balance changes. Use a sandbox, non-production context, or the smallest reversible test available, then join records with stable references.

In this dimension, schema drift is therefore an explicit audit gap.

The file semantics row should end with a concrete monitoring rule tied to orders versus fills versus balance changes. Make the operator join records with stable references, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; schema drift remains a separate production risk until observed.

9. Control test: Onchain evidence

For onchain evidence, inspect TxID and network linkage. Use a sandbox, non-production context, or the smallest reversible test available, then retain explorer-verifiable identifiers.

In this dimension, offchain movements is therefore an explicit audit gap.

The onchain evidence row should end with a concrete monitoring rule tied to TxID and network linkage. Make the operator retain explorer-verifiable identifiers, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; offchain movements remains a separate production risk until observed.

10. Control test: Control test

For control test, inspect reconciliation of a known period. Use a sandbox, non-production context, or the smallest reversible test available, then compare opening plus flows with closing balance.

In this dimension, support correction outcome is therefore an explicit audit gap.

The control test row should end with a concrete monitoring rule tied to reconciliation of a known period. Make the operator compare opening plus flows with closing balance, retain the venue response, and assign an owner for exceptions. Documentation quality is a useful signal, but it does not certify the exchange or the trading system; support correction outcome remains a separate production risk until observed.

Decision scenarios

Scenario 1: when export object becomes decisive

Consider a reader whose main constraint is statement, trade, ledger, order or balance. The correct response is not to infer a universal platform or product winner. It is to define the accounting question first, retain the evidence, and define a stop condition before funds or permissions are committed. If the evidence changes, the decision must be reopened. This produces a repeatable operating rule rather than a one-time opinion.

Scenario 2: when date window becomes decisive

Consider a reader whose main constraint is maximum period per request. It is to use explicit UTC boundaries, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 3: when quota becomes decisive

Consider a reader whose main constraint is monthly generation allowance. It is to track requests in an archive ledger, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 4: when generation time becomes decisive

Consider a reader whose main constraint is synchronous or queued creation. It is to schedule before reporting deadlines, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 5: when notification becomes decisive

Consider a reader whose main constraint is email, SMS, onsite or manual checking. It is to verify completion inside the official account, retain the evidence, and define a stop condition before funds or permissions are committed.

Scenario 6: when download lifetime becomes decisive

Consider a reader whose main constraint is expiration of generated links. It is to download promptly into encrypted storage, retain the evidence, and define a stop condition before funds or permissions are committed.