What “pipette definition” means before discussing implications
A pipette is a unit that represents a fraction of a pip. In practice, “pipette definition” is the specific rule set that tells you:
- what the pip size is for a given instrument (for example, based on the number of decimal places shown), and
- what fraction of that pip is treated as one pipette (for example, one-tenth of a pip in many quote systems).
Because “pip” and “pipette” are partly conventional, the advanced consideration is not the label itself, but the measurable rule behind it: how a quote format (decimal places), contract sizing (how the trade quantity maps to price movement), and reporting conventions (rounding and precision) determine how you convert a price change into a pipette count and then into monetary terms.
A simple model you can use to check any pipette definition
Use an “input → normalization → output” model:
1) Identify the instrument’s pip scale (pip size). You need the step size that counts as one pip for that instrument under the provider’s convention. A common pattern is that a pip is tied to the last decimal place of the quoted price, but the exact pip size can vary with how the instrument is quoted.
2) Identify the pipette fraction. Next, determine how many pipettes make up one pip. Many systems use a fractional scale (for example, 0.1 pip per pipette), but you must treat it as a convention documented by the pricing/accounting system you are using.
3) Convert a price move into pipettes. Given a price change ΔP, compute a normalized pip change:
- pip_change = ΔP / pip_size Then convert to pipettes:
- pipette_count = pip_change / pipette_fraction (or equivalently pip_change × (pipettes per pip), depending on how the system defines the fraction).
4) Convert pipettes into money (if needed). If you are mapping price changes to profit/loss, you also need contract terms that link a pip (or pipette) to the account currency amount. That mapping often depends on:
- position size (lot/contract quantity)
- whether the instrument’s quote currency matches the account currency
- any conversion between currencies
This model becomes the basis for independent verification: you can reproduce the pipette count and monetary value if you know the exact pip size, pipette fraction, and contract-to-currency conversion rules.
Implementation constraints and edge cases that change the outcome
Even with a correct general model, advanced implementations usually face “small but decisive” edge cases.
Decimal precision and rounding
Systems do not always keep infinite precision. They typically apply rounding at one or more steps:
- When converting ΔP to pipettes
- When converting pipettes to money
- When aggregating results across multiple executions
A failure mode is a mismatch in when rounding is applied. If one system rounds pipettes first and another rounds monetary value first, the final reported numbers can differ, especially when price changes are near a rounding boundary.
Assumption to state when calculating examples: You must state the rounding rule you assume (e.g., rounding to the nearest pipette, truncation, or banker’s rounding) and the precision of the intermediate steps.
Fractional pip quotes vs fractional pipette reporting
A quote might show decimals that imply a pip scale, but your platform’s reported “pipette” may represent a different internal precision. For example, the displayed price might update in one granularity, while the accounting engine uses a finer internal tick. This can produce situations where two trades with the same displayed move result in slightly different pipette counts.
Currency conversion for monetary pipette value
If your account currency differs from the instrument’s quote or base currency, converting pipette value can introduce extra variability:
- the conversion rate used
- whether conversion is applied per pipette movement or at the end
- rounding during conversion
A limitation here is that different systems may use different conversion timing (for instance, using execution-time conversion vs. settlement-time conversion), which affects reproducibility unless the rules are explicit.
Instruments with different pip conventions
Not all forex-like instruments share the same pip definition behavior. Even within FX, quoting conventions can differ (such as how many decimals are presented). Exotic conventions and certain instruments outside standard 4- or 5-decimal patterns can lead to a pip size that is not what you expect.
Key practice: treat pipette definition as instrument-specific and provider-specific. Don’t assume that “one pip is always the same size” across all quote formats.
Multi-leg execution and netting
If the platform nets positions or applies partial fills, the “pipette” accounting can depend on how fills are aggregated. Two ways of getting the same net price change may still produce different pipette totals if fills have different rounding or conversion handling.
Limitations and risks you should explicitly account for
Because pipette definition is a measurement convention, the main risk is interpretational rather than mathematical.
-
Provider rules can differ. Pip size, pipette fraction, and rounding rules are often part of the provider’s platform/accounting design. If you use a mismatched assumption set, your recreated numbers won’t match.
-
Execution variability affects actual ΔP. Even without real-time data, you must assume that the realized price change differs from what you might estimate from a chart snapshot. Since pipette counts depend on the exact ΔP, execution price matters.
-
Costs can be confused with pipette movement. Transaction costs (spreads, commissions, fees) change monetary outcomes but are not the same as pipette movement. A common failure mode is attributing cost-related differences solely to pipette calculation.
-
Historical relationships do not predict future results. If you calibrate a pipette definition using historical examples, that only validates the convention for that period and setup. It does not prove the same behavior will hold for future provider updates or different instruments.
How to verify pipette definition independently (without guessing)
You can verify pipette definition using a controlled approach:
- Collect the exact rules you will use. You need a documented statement (from platform or execution/accounting documentation) of:
- pip size for the instrument
- how many pipettes per pip (the pipette fraction)
- the rounding policy
- the mapping from pip/pipette to money (including any currency conversion rule)
- Reproduce with controlled inputs. Choose a small, clearly stated price change ΔP and apply the input → normalization → output model. Ensure your assumed rounding and conversion steps match the platform’s behavior.