Recheck price, quantity and notional after rounding

Rounded values need a new check

A valid decimal grid and a valid minimum notional are different conditions. Rounding a price or quantity down can solve one mismatch while creating another. This expanded worksheet shows the entered parameters, a floor-rounded candidate and a complete second audit of the same enabled static rules.

The candidate is not an order recommendation. It is a numerical object you can inspect beside the original input. Nothing is submitted, no account is connected and no instrument rules are fetched. The question is narrowly defined: what changes in the supplied rule checks after these two exact decimal floor operations?

The original entered-value audit remains

The existing worksheet checked price tick, quantity step and optional minimum or maximum bounds for price, quantity and notional. It keeps those checks and the original example. Price is quote units per base unit; quantity is base units; multiplying them gives quote notional. This subset is for a simple limit-order interpretation.

Binance Spot documentation supplies an example of explicit price-grid, quantity-grid and notional constraints. The same document also describes other filters, including price bands and account-related limits. This local worksheet does not implement all of them, and it does not claim that another venue uses identical rules.

Sources: Binance Spot API - Filters.

Record exactly which rules you enabled

Every nonzero rule in this worksheet contributes one audit row. Zero explicitly disables that local check; it does not mean the actual venue has no restriction. A blank field is different from an explicit zero and stops calculation. Keep unknown venue rules in your research notes instead of silently treating them as disabled.

Use the exact symbol, order type and current documented parameters. Do not paste a quantity increment from one contract into another instrument or use a fiat precision setting as an exchange tick. Enabled minimum and maximum values must be consistent. If a minimum exceeds its enabled maximum, the inputs are contradictory and the tool stops.

Floor is an explicit convention

For a positive tick T, the candidate price is floor(price / T) multiplied by T. The quantity uses the same operation with its step S. If a step is disabled, the corresponding entered value is retained. Decimal coefficients are handled as integers so that a binary remainder does not decide membership of a decimal grid.

This version deliberately supplies only the floor candidate. Choosing a direction based on buy or sell intent would add an execution decision that the worksheet does not make. The original values remain unchanged. The candidate can have a different notional, fail an enabled lower bound or become zero when an entered quantity is smaller than one step.

Preserved example: three checks on the entered order

The original hypothetical input uses price 100.03, quantity 0.1054, tick 0.05, quantity step 0.001 and minimum notional 10. The entered notional is 10.543162. The entered values fail the two grid checks and pass the minimum-notional check: one of three supplied checks passes.

The floor candidate is price 100 and quantity 0.105, with notional 10.5. A new audit of those candidate values passes all three supplied checks under this example. That statement is limited to this local subset. It does not verify dynamic bands, funds, account limits, product availability or acceptance by an exchange.

Change one bound and the candidate fails

Now keep every value above but change the hypothetical minimum notional to 10.52. The entered 10.543162 still meets that bound. The rounded 10.5 does not. The candidate has repaired both grids but passes only two of the three enabled rules.

This is the new useful result of the expanded tool: it identifies which conditions changed from pass to fail or fail to pass. It does not hide the failed candidate behind a rounded-value display. If a floor operation produces zero price or quantity, the candidate is additionally labelled nonpositive and cannot be described as a passing order candidate, even if you disabled all lower bounds.

Inspect the audit row by row

Compare the entered and candidate columns under the same supplied rule. A pass-to-fail transition points to a consequence of the candidate transformation. A fail-to-pass transition shows only that a particular local condition changed; it cannot prove an executable order. Preserve the disabled-rule list with the report.

If no rules are enabled, the result says no enabled rules rather than all rules passed. This avoids converting an empty check set into a misleading approval. The exact input precision is limited to twelve fractional digits and each input to 1,000,000,000,000,000. Scientific notation, grouping commas, negative rule values and malformed inputs are rejected.

Keep the rule snapshot in UTC and Singapore time

A rule set without a retrieval time can be difficult to distinguish from an old export. The optional source-observation field records the UTC instant you entered and displays that same instant in Asia/Singapore. For the synthetic timestamp 2026-10-20T16:05:00Z, the Singapore display is 2026-10-21T00:05:00+08:00. Those are different calendar dates for the same instant.

This helps a reader organise saved parameter snapshots across a date boundary. It does not establish freshness, because the browser neither fetches the parameters nor authenticates your timestamp. With no entered observation time, the source time stays unknown. Singapore is a recordkeeping context here; the arithmetic is universal and no local trading-service eligibility is claimed.

Sources: Singapore BCA - Site Management Data Standards v 1.1, page 65.

Export the calculation, not an approval

The CSV records the enabled rules, entered values, floor candidate, both results and the declared snapshot context. Calculations use exact decimal strings, and the two price-times-quantity products can contain more decimal places than either input. Do not silently round them to a display currency before applying the notional bounds.

Keep the previous CSV and the actual source specification when changing parameters. A later rule change is a new audit, not a reason to rewrite the old evidence. The existing resource comparison remains available, and the optional Telegram offer is separate from this tool. The completed worksheet is useful even when its conclusion is that the candidate still fails.

Worked examples

Questions before you use the result

Primary sources and scope

1. Binance Spot API - FiltersChecked 2026-10-20. PRICE_FILTER, LOT_SIZE and notional constraints are distinct documented symbol filters. The documentation also describes filters outside this local limit-order subset. Zero disabling is explicitly documented for PRICE_FILTER; this worksheet separately defines zero as disabling each supplied local rule.
2. Singapore BCA - Site Management Data Standards v 1.1, page 65Checked 2026-10-20. The official format example identifies +08:00 as Singapore Standard Time; used for timestamp notation only, not an exchange rule.

Prepared from the sources listed above. Examples and calculations explain a method; they do not predict prices or certify an investment. Geographic time references do not establish where a trading service is available. Dated schedules can change: consult the named publisher before relying on a future event.

Related resources on this site

• Price Tick, Quantity Step and Minimum-Notional Checker Resources
• 10 Resources for Checking Crypto Order Parameters