BDS / Intraday usability
Session Close: Report Open Exposure as Well as Closed Trades
A same-session promise needs an operating policy and evidence that the account reached the intended state.
Declare the boundary before observation
Name the venue, calendar, selected product and reporting cutoff. A midnight in the reader's location is not automatically the session close. Holidays, shortened sessions and different instruments can require different boundaries.
The product should explain who manages positions approaching the boundary. A label such as intraday does not settle whether late entries, partial exits or failed closes are permitted.
Distinguish message and account state
A provider close message is an instruction or report. The subscriber needs the corresponding accepted order, filled quantity and remaining position to establish the account state. A source account becoming flat does not prove a follower did the same.
Keep cancelled, rejected and unfilled closing requests visible. Do not overwrite them with the intended result.
Worked partial-close case
Hypothetical example: a position has an intended same-session exit, but only part of the closing quantity fills before the declared cutoff. The closed part and remaining exposure are separate records. The account cannot be described as flat solely from the original close message.
No procedure for closing the actual remainder is prescribed here. The point is the evidence boundary and the need to consult the relevant official account policy.
Use complete session accounting
Report closed operations, open quantity and marking assumptions separately. A favorable closed-trade tally can coexist with unresolved open exposure. A win rate alone does not establish the account's equity state.
Retain costs and funding context with account results. Adding the returns of isolated instructions does not describe simultaneous positions or available capital.
Ask about stopping the service
Subscription expiry, pausing copying and losing a connection can have different operating consequences. Obtain the selected product's written policy before starting. Do not assume a billing cancellation liquidates positions.
For an account-connected workflow, the reader should understand the official failure owner. An unverified chat promise is not a substitute for documented behavior.
Finish with a reconciled or unresolved state
The journal should explicitly say whether the close is reconciled, partly supported or unresolved. An unresolved state is more informative than a silent assumption that every intended exit succeeded.
BDS has not connected funded follower accounts. This chapter is a reporting design, not a certified close process or an account-management instruction.
A flat source is not every follower
The source account and follower may have different instruments, quantities or operations. A close event needs the corresponding follower record. Do not assume that a source curve marked at the session end establishes the buyer's state. An unpaired event can remain a reconciliation gap.
Closed-trade selection
A summary containing only completed favorable operations can omit a significant unresolved remainder. The complete reporting boundary should identify the open position and marking assumption. This is a general audit question, not an allegation about a named service. Preserve the source and period behind any actual claim.
The next-session handover
If a position remains after the intended boundary, preserve its state and the documented responsible party. Do not silently move it into another session to maintain a same-session success label. The publication cannot prescribe how to handle a live remainder; it can require that the evidence and scope stay visible.
Evidence Packet
| Evidence object | Record to retain |
|---|---|
| Cutoff | Venue calendar and declared boundary |
| Position trail | Closed and remaining quantities |
| Failure policy | Official owner of uncompleted exits |
Related Session Questions
Primary References
The sources support documented mechanisms and source definitions. Our procedure and teaching examples are not completed paid-feed, latency or account tests.