Clarification: JSON statement ContractNo linkage, settlement-date semantics and fee totals

Abierto
  • ¿Algo no está bien?
#1,304 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
json, openapi, rust, typescript
Área
api, documentation

Línea de trabajo

Start with the changelog entries for GET /v1/statement/list and GET /v1/statement/download, then compare the statement types in longbridge-terminal/src/data/statement.rs with the referenced execution history, order detail, and cash flow contracts and Rust SDK asset contracts. Document what those sources establish about contract identifiers, settlement dates, cash amounts, and fees, and identify any gaps they leave. Done means the API semantics and limitations are documented or linked, with a synthetic example if needed.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

I am implementing read-only reconciliation of official JSON account statements with the OpenAPI trade records. Could you point me to the documented contracts for the following fields? This is a request for API semantics, not account-specific troubleshooting.

References:

  1. Native identity and corrections. What is the defined relationship between StockTradeSums / OptionTradeSums → Trades[].ContractNo and execution-history trade_id / order_id? Is there a read-only endpoint or statement field that provides the explicit mapping, including grouped fills, cancellations, and corrected confirmations? A documented mapping is preferable to matching by symbol, quantity, amount, or time.

  2. Actual settlement versus scheduled settlement. What formats and time-zone conventions apply to TradeDate, SettleDate, and TradeDones[].TradeDoneTime? Does SettleDate identify the scheduled value date or confirm completed cash settlement? Which source field distinguishes actually settled cash from a pending obligation, including month-end records in OutstandingSums? If the API only reports a calendar date, please confirm that limitation; I will retain date precision rather than invent an intraday timestamp.

  3. Principal, net cash and fees. Are TradeAmount and ClearAmount respectively gross principal and actual net settlement cash? Which charges, taxes, deductions and FX effects are included? How should Fees, LbsgFees.Fees, LbsgFees.GstFee, and LbsgFees.SumAllFees be interpreted without double-counting? Are these final at statement generation, and how are later corrections or refunds identified?

No account identifiers, documents, credentials, presigned URLs, or transaction examples are attached. A documentation link or a synthetic example would be sufficient.

Lenguaje dominante
TypeScript
Estrellas
61
Forks
30
Merge medio
7 h 45 min
PR fusionados (30 d)
17

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de longbridge/developers

Todos los issues de longbridge/developers

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.