Expense ratios in this app are stored and displayed in percent units:
0.45 means 0.45% per year. One convention applies everywhere. Ticker Metadata,
the Screener table and the Classic-score fee term all read it the same way.
Peer score and Optimize use adjusted-close returns without a separate ER term.
Why this needs saying at all
Data sources disagree about units. Yahoo's feed quotes some fund types as
fractions (0.0045) and others as percents, so imports normalize based on
the security type at fetch time. Databases that have been fed by older
imports can genuinely contain mixed units, with some rows in percent and others in
fraction.
That is why the app never runs a blanket "multiply everything by 100" repair: on a mixed database it would fix half the rows and corrupt the other half. Normalization happens on the paths where the unit is knowable (at fetch, per security type); a suspicious value is better edited by hand on Ticker Metadata than "fixed" in bulk.
Sanity check when a number looks off: real fund ERs live between about 0.02 and 1.5 in percent units. A displayed ER of 0.0045 is almost certainly a fraction that slipped through. Edit the ticker; don't mass-migrate.
CSV imports leave ER blank rather than guessing; the profile fetch is the one source trusted to fill it.