DOLLARDE in Excel: Decode Fractional Price Notation

=DOLLARDE(fractional_dollar, fraction)

Both arguments are required. Fractional_dollar is the encoded numeric quote; fraction supplies its denominator. The digits after the decimal symbol represent a numerator according to the denominator’s digit scale, rather than an ordinary decimal fraction of the price.

For denominators such as 16 or 32 in the examples, the numerator occupies two decimal places. Therefore 7.08 represents a numerator of 8, while 7.8 is numerically 7.80 and represents a numerator of 80. Preserve leading zeros in the numerator’s position.

This is a notation conversion, not an exchange-rate operation or the DOLLAR text-formatting function.

=DOLLARDE(7.08,16)
=DOLLARDE(7.04,16)
=DOLLARDE(7.15,16)

Expected decimal amounts are 7.5, 7.25 and 7.9375. The fractional components are 8/16, 4/16 and 15/16 respectively.

If the first input were treated as ordinary decimal money, it would mean 7.08 rather than 7.5. Label the input column with its quote convention and denominator so the meaning survives export or handoff.

=DOLLARDE(7.08,32)
=DOLLARDE(7.08,16)

Expected results are 7.25 and 7.5. The same encoded numeric input has different meanings when the denominator changes.

Microsoft’s documented examples similarly distinguish 1.02 with denominator 16 from 1.10 with denominator 32. The denominator is part of the data, not an optional display preference.

Suppose one quote is 7.08 and another is 7.04, both in sixteenths. Convert each before computing the difference:

=DOLLARDE(7.08,16)-DOLLARDE(7.04,16)

Expected difference: 0.25. Directly subtracting the encoded inputs gives 0.04, which is a numerator-code difference rather than the ordinary decimal price difference.

For quantity 40 at the first decoded price, =40*DOLLARDE(7.08,16) gives 300. Arithmetic on raw encoded values would produce a different and misleading total.

=DOLLARFR(DOLLARDE(7.08,16),16)

Expected encoded result: 7.08. The denominator must match both conversions. This checks the chosen representation for an exact multiple of the stated fractional unit; it does not establish that every external quote string follows this encoding.

If source data contains a hyphenated quote or another market-specific marker, parse and validate that format before passing a numeric value to DOLLARDE. The function does not infer a venue’s quoting rules from punctuation.

Microsoft documents truncation when fraction is noninteger. =DOLLARDE(7.08,16.9) therefore uses denominator 16 under the stated rule. Do not rely on truncation to conceal malformed reference data.

A negative fraction produces documented #NUM!. A fraction in the range 0≤fraction<1 produces documented #DIV/0!. In the normal workflow, validate a positive intended integer denominator before conversion.

If the result is unexpectedly large, inspect numerator padding: 7.8 is not the same encoding as 7.08 for a two-digit denominator. If the result differs by a factor in its fractional part, confirm the denominator used by the source.

The worked cases use positive quotes and denominators 16 and 32 with exact fractional increments. Signed-price behavior, uncommon denominator scales, coercion, blanks and native numerical boundaries remain unverified. No transaction or security valuation is implied; the examples demonstrate only a numeric notation conversion.

• Current documentation: the dedicated Microsoft reference lists Excel for Microsoft 365, Excel for Microsoft 365 for Mac, Excel 2024, Excel 2024 for Mac, Excel 2021, Excel 2021 for Mac, Excel 2019, Excel 2016.
• Introduced: the first introduction version/build is not established by the dedicated reference used here.
• Last functioning version: unknown; a current help listing is not a last-working-build test.
• Evidence checked: October 15, 2026. Official documentation was freshly retrieved; examples were independently calculated. No native Excel, Mac or web-client execution was performed.

• Microsoft DOLLARDE reference.
• Microsoft function catalog and introduction-marker explanation.
• Editorial testing standards.

Examples use English function names and comma separators. Expected numbers are rounded independent mathematical calculations; documented error expectations are labeled as such. They are not captured Excel output. All illustrative data and policies are fictional.