Best Futures SignalsContract / Cash / Execution

Futures / Original case research

Partial Futures Fills, Cancellation and OCO Records

Reconcile filled quantity and remaining orders before calling a futures instruction complete or flat.

An observation, its retained evidence and a bounded conclusion
Illustrative research workflow; the worked record below is fictional.

State and quantity belong together

A three-contract order can have one filled contract and two still outstanding. The initial request size is not the filled size. NinjaTrader's order-state documentation distinguishes submission, acceptance, working orders, partial fills, cancellation and rejection. Those definitions help structure a review; they do not certify a specific account. Retain quantity, average price, individual execution times and the remaining order state. One terminal status without those quantities can leave residual exposure unexplained.

A cancellation request is not the same as confirmation. A fill can occur while a request is in flight, so preserve the event order rather than retroactively applying the request time as the flat time. An exit order must also use the actual position quantity. Do not substitute the original alert's desired size. If a provider reports a completed idea while the subscriber retains one contract, those are different outcomes with different endpoints.

Linked orders need their own evidence

An OCO label describes an intended order relationship, not proof that every counterpart was cancelled correctly. Identify the platform or broker mechanism, link identities and each order's state. After an exit, reconcile the residual position and any working instructions. Unknown linked-order handling cannot be solved by reading a profit marker on a chart. A review should explicitly separate intended protection from observed state transitions.

Report no-fill and partial cases honestly

A hypothetical publisher outcome can coexist with a missed customer entry, provided the convention is visible. Do not insert a best-price fill into the customer's ledger to complete a summary. For partial fills, quantity-weight the actual cash and preserve unexecuted quantities. A completed signal population and a completed account population may differ. Report the difference rather than silently deleting awkward cases or multiplying one profitable update into several independent wins.

A reconciliation that another reader can follow

Start with intended quantity, then show each execution and cancellation confirmation. Sum the open inventory after each event and record the final state. Leave undocumented transitions unknown. This procedure can reveal whether an account is demonstrably flat without evaluating the strategy's edge. The review also needs the relevant clock and contract month. Repeating a message through two delivery channels is not a second order unless actual instructions or fills establish it.

Completed fictional record

An invented buy request is for three contracts. One fills at 100; two remain working. A cancellation request is issued, but a second contract fills at 101 before cancellation confirms for the final one. Position quantity is now two, not one or three. Selling one at 102 leaves one open contract. With a declared value of 10 per point, closing the first lot would have a gross component of 20, but that cannot describe the entire position while the second lot remains open. Its final value and total costs stay unknown. A complete request-state ledger is therefore not yet a complete account result.

Recorded objectValue or stateInterpretation
First fill1 at 100One open
Second fill1 at 101Two open
Cancel confirmed1 unfilledTwo still open
Partial exit1 at 102One remains

Primary references and scope

Public documents inspected 13 October 2026. Cases here are original fiction; sources support bounded mechanisms or product functions, not an account test.

Continue this investigation