Spot order status and history: reconcile a partial fill

Separate the order from its executions and account balance

An order is an instruction with a requested quantity and conditions. An execution (fill) is a trade that actually matched. An order can have zero, partial or complete execution; order history describes its lifecycle, while trade or fill records show individual matched amounts and prices. A balance is a separate account record that can also reflect commissions, holds and other activity.

The status names below come from Binance's Spot API enum documentation as checked on 2026-10-26. The repository's master branch is mutable. API status fields are not a promise that Binance.com, Binance.US, every regional service or each user interface displays identical labels or workflows. This guide explains records; it does not connect to an API or place an order.

Evidence: Spot API order-status enums · Binance.com terms and ADGM entities · Binance.US terms and named operator

The quoted lifecycle labels and descriptions are from the documented Spot API enum, not a claim about identical Binance.com, Binance.US or regional user-interface wording. The master branch can change; verify its current revision before operational use.

The page currently names Nest entities regulated in ADGM. This is evidence for the entities and scope stated on that page only, not a universal operator list or terms for every region, product or customer.

These are Binance.US terms, not Binance.com terms. The page names BAM Trading Services Inc. and related entities for those services; this does not establish the operator or user rights for another region or product. Read the terms applicable to the specific account and jurisdiction.

Read common documented Spot API states cautiously

In the cited Binance Spot API documentation, NEW means the order was accepted by the matching engine; it does not mean it filled. PARTIALLY_FILLED means part of the quantity filled, and FILLED means the order completed. CANCELED, REJECTED and EXPIRED are different states: the enum documentation describes a canceled order, a request not accepted/processed, and an order ended under its type's rules or by the exchange, respectively.

The same API reference lists other states, including PENDING_NEW, PENDING_CANCEL and EXPIRED_IN_MATCH. Their presence is a reminder not to compress every label into 'open' or 'failed'. A consumer-facing app may use localized wording or expose fewer details. Check that product's current help and the final refreshed order and fill records before deciding what happened.

Evidence: Spot API order-status enums · Binance Spot Order Types

The quoted lifecycle labels and descriptions are from the documented Spot API enum, not a claim about identical Binance.com, Binance.US or regional user-interface wording. The master branch can change; verify its current revision before operational use.

Binance.com order types and partial-fill/product behaviors; current controls can vary.

Solved fictional timeline: part filled, remainder canceled

Assume a fictional BUY limit order for 5 AAA with a maximum price of 10 BBB per AAA. No account or real pair is involved. At the first checkpoint its order record says NEW, executed quantity 0 AAA, remaining 5 AAA. Later, a fictional match fills 2 AAA at 9.90 BBB each: cumulative quote amount is 2 × 9.90 = 19.80 BBB, executed quantity 2 AAA, and remaining quantity 3 AAA. The order state is now PARTIALLY_FILLED.

In the paper example, a cancellation of the remaining quantity is accepted and the final refreshed order record is CANCELED, with executed quantity still 2 AAA and remaining quantity 3 AAA. CANCELED does not erase the earlier 2 AAA fill. A real cancellation request can race with further matching, so an acknowledgement alone is not the final reconciliation: read the resulting state, cumulative executed quantity and associated fill records.

Evidence: Spot API order-status enums

The quoted lifecycle labels and descriptions are from the documented Spot API enum, not a claim about identical Binance.com, Binance.US or regional user-interface wording. The master branch can change; verify its current revision before operational use.

Reconcile a hypothetical commission without treating it as a rate

Extend only the fictional arithmetic above. If the 2 AAA fill were charged a hypothetical commission of 0.002 AAA, the net AAA credited from that fill would be 2 − 0.002 = 1.998 AAA. The order still records 2 AAA executed; a commission is a separate line and may be charged in a different asset under a product's rules. The remaining 3 AAA was canceled and was not part of the fill in this simplified example.

The number 0.002 AAA is invented solely to demonstrate subtraction; it is not a Binance fee rate, discount, estimate or offer. Real commission assets, rates, rebates, account settings, pair rules and regional fee schedules can differ and change. Binance.com and Binance.US publish separate product-specific fee information. Check the currently applicable schedule and the actual commission field/asset in the records for the exact service; do not infer a fee from the order-status label.

Evidence: How to Calculate Transaction Fees · Trading Fee Rate · Fee Schedule

Binance.com fee calculation concepts; old example values are not reused. Currency/settings can depend on product.

Live Binance.com fee schedule; rates can vary by account, pair, VIP level and promotion; no rate copied as evergreen fact.

Separate dynamic Binance.US schedule; not applied to Binance.com or other regions.

A read-only reconciliation that has a defined result

For a completed review, align records using the same account, product, pair and time range. Compare the order ID and final status with executed quantity and remaining quantity; then total the individual fills by quantity and quote amount. Read each commission amount with its asset, and compare those net effects with the corresponding balance/activity records. Never add a commission in AAA to a quote total in BBB without converting units using an explicitly documented method.

The worked result is internally consistent: the two fill records would sum to 2 AAA and 19.80 BBB gross; the hypothetical 0.002 AAA commission leaves 1.998 AAA net from the fill; the final canceled order has 3 AAA unfilled in this example. If the order totals, fill records, commission asset or balance activity do not reconcile, the check is not complete. Preserve the records and use the verified support channel for that exact service; do not repeat or resubmit an order to test a discrepancy.

Before acting on any real record, confirm the product entity, region, account and current documentation. Binance is the service operator, BNB is an asset, and BNB Chain is a network family; a Spot order ID is not an onchain transaction hash. No financial outcome is predicted or recommended here.

Evidence: Spot API order-status enums · How to Calculate Transaction Fees · Trading Fee Rate · Fee Schedule · Binance.com terms and ADGM entities · Binance.US terms and named operator

The quoted lifecycle labels and descriptions are from the documented Spot API enum, not a claim about identical Binance.com, Binance.US or regional user-interface wording. The master branch can change; verify its current revision before operational use.

Binance.com fee calculation concepts; old example values are not reused. Currency/settings can depend on product.

Live Binance.com fee schedule; rates can vary by account, pair, VIP level and promotion; no rate copied as evergreen fact.

Separate dynamic Binance.US schedule; not applied to Binance.com or other regions.

The page currently names Nest entities regulated in ADGM. This is evidence for the entities and scope stated on that page only, not a universal operator list or terms for every region, product or customer.

These are Binance.US terms, not Binance.com terms. The page names BAM Trading Services Inc. and related entities for those services; this does not establish the operator or user rights for another region or product. Read the terms applicable to the specific account and jurisdiction.

Paper check and solved answer

Without an account, write the requested amount, the matched amount, the canceled remainder, each fill's price and quote total, and a hypothetical commission with its own asset. Explain why a final CANCELED state can coexist with earlier fills. State which fields would need to agree before you call a real reconciliation complete.

Solved answer: of 5 AAA requested, 2 AAA filled at 9.90 BBB for 19.80 BBB gross; 3 AAA remain unfilled and are canceled in the final hypothetical snapshot. If 0.002 AAA were charged as an invented fee, the net acquired from the fill is 1.998 AAA. CANCELED describes the remaining order lifecycle here; it does not mean zero executions. The values are fictional and do not establish a live fee or account outcome.

Evidence: Spot API order-status enums · How to Calculate Transaction Fees

The quoted lifecycle labels and descriptions are from the documented Spot API enum, not a claim about identical Binance.com, Binance.US or regional user-interface wording. The master branch can change; verify its current revision before operational use.

Binance.com fee calculation concepts; old example values are not reused. Currency/settings can depend on product.