Contact

DOLLARFR in Excel: Encode Decimal Prices as Fractional Quotes

Financial Intermediate Microsoft Excel

Convert ordinary decimal prices to Excel fractional-dollar notation, preserve numerator padding and avoid calculating totals on encoded quote numbers.

Verification status: See the evidence and test scope described in this guide. How formula examples are checked

Quick answer: DOLLARFR(decimal_dollar,fraction) converts an ordinary decimal amount into a fractional-price encoding. With denominator 16, =DOLLARFR(7.5,16) has expected numeric output 7.08, representing 7 and 8/16.

Syntax and what the result means

=DOLLARFR(decimal_dollar, fraction)

Both arguments are required. Decimal_dollar is an ordinary numeric amount. Fraction is the intended denominator of the quote’s fractional component. Microsoft documents truncation of a noninteger denominator.

The result is a number used as an encoding, not an ordinary decimal amount suitable for direct money arithmetic. For denominators 16 and 32, numerator digits occupy two decimal positions. A price of 7.5 becomes 7.08 in sixteenths and 7.16 in thirty-seconds.

DOLLARFR does not return a text label such as “7 8/16,” does not choose a market quote convention, and does not exchange currencies.

Example 1: encode a small decimal-price column

Enter 7.25, 7.5 and 7.9375 in A2:A4. In B2 enter and fill down:

=DOLLARFR(A2,16)

Expected encoded results are 7.04, 7.08 and 7.15. Their fractional numerators are 4, 8 and 15 out of 16.

A two-decimal number format makes the numerator positions easier to read for these denominators. It does not turn the encoded values into conventional decimal prices, so keep the original decimal values available for calculations.

Example 2: change the denominator explicitly

=DOLLARFR(7.5,16)
=DOLLARFR(7.5,32)

Expected encodings are 7.08 and 7.16. They describe the same underlying amount using different denominators.

The output’s suffix cannot be interpreted without the denominator. Sending only the number 7.16 while omitting the convention would be ambiguous to a reader or downstream system.

Advanced application: preserve trailing zero positions

For the decimal amount 7.3125 in thirty-seconds:

=DOLLARFR(7.3125,32)

Expected numeric result: 7.10, which may display as 7.1 under General formatting. The encoded numerator is 10, not 1. Displaying two decimal places can preserve the intended visual grouping for this two-digit-denominator convention.

This is a display safeguard, not an assertion that all quote systems use exactly two places. The examples deliberately stay with denominators whose numerator encoding is familiar and documented by the reference examples.

Advanced application: separate arithmetic from export notation

If 40 units have an ordinary decimal unit price of 7.5, the total is 300. Calculate that from the decimal amount, then encode a unit-price field only where the destination requires fractional notation.

Multiplying the encoded value 7.08 by 40 gives 283.2, which is not the correct price total. Encoding changes how the numeric digits are interpreted; it is not a neutral currency format.

When importing an encoded column back into a model, use DOLLARDE with the same denominator to restore ordinary decimal amounts before summing or multiplying.

Advanced check: verify an exact-increment round trip

=DOLLARDE(DOLLARFR(7.9375,16),16)

Expected result: 7.9375. The intermediate encoding is 7.15. A mismatch of denominator in the reverse call would decode a different price.

This check uses an amount that is exactly a multiple of 1/16. DOLLARFR should not be assumed to enforce a trading tick or an integer numerator for every arbitrary decimal input. If the source amount is not aligned to the intended unit, decide on an explicit validation or rounding policy before formatting a quote.

Errors and troubleshooting

Microsoft documents #NUM! when fraction is negative and #DIV/0! when it is zero. Noninteger fractions are truncated; for example, 16.9 selects the same integer denominator as 16 under the documented rule. Validate the intended positive whole number instead of depending on truncation.

If a quote appears to lose a zero, inspect the number format. If a total is incorrect, check whether arithmetic was performed on encoded rather than decimal values. Signed inputs, unusual denominators, blanks, text coercion and exact native rounding remain unverified. These examples are notation controls, not security-price or transaction advice.

Availability and version history

  • 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.

References and verification

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.