There’s a persistent mismatch between what you enter and what markets execute when Tag 152 (CashOrderQty) interacts with venue conventions. You type 100 or 0.5 and expect the broker and exchange to honor your numeric intent, but fractional shares, lot sizes, and venue-specific rounding rules can change the quantity before the order hits the book.
When you work with FIX messages, Tag 152 is the canonical field for quantity. Some venues accept fractional shares natively; others require integer multiples of a lot size (for example, 100, 1,000, or 1,000,000). If the destination enforces a lot size, your CashOrderQty can be silently adjusted, rejected, or split into multiple orders — and your fill expectations shift accordingly.
Rounding behavior varies. A venue may apply floor, ceil, or nearest rounding rules at the gateway, accounting, or exchange level. Your algorithm that calculates position sizing based on fractional results must handle the target venue’s rule set; otherwise you risk over- or under-exposure. Some routers reconcile mismatches by splitting the order into a rounded integer plus a residual that firms either cancel or route elsewhere.
Partial fills and post-trade reporting amplify the problem. If your intended CashOrderQty is rounded down, you might see a filled quantity and assume full execution while still short of your target. If rounded up, you could unintentionally increase exposure and trigger risk limits. Your reconciliation and monitoring systems need to treat the executed quantity as the authoritative value and track adjustments originating from venue-specific rounding rules.
Mitigation steps you can adopt: fetch and store each venue’s lot size and rounding policy; validate CashOrderQty pre-route and reject or normalize values that will be altered; include comment or text fields documenting intent for downstream handlers; and test with synthetic orders to observe silent transformations. Logging the raw FIX messages both pre- and post-routing makes these invisible changes visible.
Understanding how Tag 152 is interpreted across ecosystem actors — brokers, smart routers, and exchanges — prevents silent drift between your intended exposure and the executed reality.