Understanding units and currencies in Scaler – Scaler

Purpose of this article

This article explains how units and currencies are handled in Scaler, including where units are defined, how data is converted, and which settings affect reporting versus display.

How units and currencies work in Scaler (at a glance)

Scaler separates data entry, data storage, data display, and reporting logic.

This means:

Data may be entered in different units or currencies

Data is stored in a consistent internal format

Users can choose how values are displayed

Reports are always generated using a single, consistent unit system

Understanding this separation helps explain why values may appear differently in different contexts.

Unit systems in Scaler

Scaler uses three distinct unit contexts:

Asset unit system

Portfolio default unit system (reporting)

User display preferences

Each serves a different purpose.

Asset unit system

Each asset has an asset unit system, set to either metric or imperial.

The asset unit system is descriptive. It tells Scaler which unit system the asset’s values are already in — it does not convert or change any values.

Changing the asset unit system:

Does not change existing input values

Does not trigger unit conversion in the Data Collection Portal

Simply reinterprets the existing numbers using the newly selected unit system

Important: Changing the asset unit system does not convert values.

For example:

An asset has Gross floor area (GFA) entered as 10 with the asset unit system set to metric

If the asset unit system is later changed to imperial, the value remains 10

Scaler will now interpret that value as 10 square feet, not 10 square metres

If an asset’s data was entered in the wrong unit system, you must:

Update the asset unit system, and

Manually update the affected values so they match the new unit system

Failing to update the values will result in incorrect analytics and reporting.

Best practice: Always confirm the correct asset unit system before entering floor areas or other unit-locked fields.

Asset setup basics

Portfolio default unit system (reporting units)

The default unit system at portfolio level controls how data is processed and converted for reporting.

This setting determines whether reports are generated using:

Metric units, or

Imperial units

Because reports must use one consistent unit system, Scaler converts all relevant data to the portfolio’s default unit system when generating reports.

Important: The portfolio default unit system affects report calculations, not how data is entered or displayed during day-to-day use.

Portfolio settings overview

User display preferences

Each user can choose how units are displayed in the Analytics Portal.

User display preferences affect analytics views only — they do not affect:

How data is entered

How data is stored

How values appear in the Data Collection Portal

How reports are calculated

From the user profile, users can select preferred display units for Area, Energy, Emissions, Water, and Waste.

Users can also choose their preferred language and date format.

Important: The Data Collection Portal always displays values exactly as they were entered, using the unit associated with that field or asset. For example, if an asset’s floor area is entered in square metres, all users will see that value in square metres in the Data Collection Portal — regardless of their personal display preferences.

Account & user settings overview

Currencies in Scaler

Scaler supports multiple currency contexts, depending on the data type.

Portfolio currency (financial fields only)

Portfolio currency applies only to specific financial fields, including:

Gross asset value

Market value

Financial data-tab fields

Loan data-tab fields

These values must use a single portfolio-level currency because fields such as gross asset value are often converted using client-specific methodologies and data sources. To avoid imposing a standardised conversion approach, Scaler does not apply currency conversion logic to these fields.

Portfolio settings overview

Currencies for cost inputs and measures

For other cost-related inputs, such as roadmap measures:

Each cost line item can be entered in its own currency

Currency conversion is applied automatically where relevant

Converted values are used for analytics and reporting

This allows flexibility while still supporting consistent comparisons.

Currencies for consumption data

Consumption data (energy, water, waste) is entered using unit-specific measures, such as:

kWh, MWh, kBtu (energy)

m³ or gallons (water)

metric tonnes or US tons (waste)

In addition, each consumption record can include an associated cost value, and:

Each cost value has its own currency field

Costs can be entered in different currencies across records

Currency conversion is applied automatically where relevant

Important

Portfolio currency does not control consumption costs.

Each consumption cost is handled independently and converted as needed for analytics and reporting.

Currency conversion sources

For data types where Scaler applies currency conversion (such as roadmap measures and consumption costs), conversions are performed using a standardised external exchange rate source.

The specific source, conversion logic, and update methodology are documented in detail in a dedicated methodology article.

Currency conversion methodology

Note: Portfolio-level financial fields (such as gross asset value) are excluded from Scaler’s currency conversion logic and must be provided in a single portfolio currency.

Common sources of confusion

Why do values look different in analytics vs reports?

Because:

Analytics always reflect user display preferences

Reports always use the portfolio default unit system

Analytics views are personalised, while reports are standardised.

Why can assets use different unit systems?

Assets can use different unit systems to reflect how data is collected locally, while reports still standardise outputs at portfolio level.

Does changing display units change my data?

No. Display preferences never change stored data, calculations, or reports.

Best practices for onboarding

Review asset unit systems before entering floor areas

Confirm portfolio default unit system before reporting

Ask users to set their display preferences early

Avoid changing reporting units late in the reporting cycle

Additional resources

If you are starting data entry:

Meters & consumption in Scaler

If you are preparing reports:

Reporting overview