What is the difference between currency & fx currency type fields in ServiceNow?

Community Alums · ‎01-29-2023

mmcdonnell · ‎11-06-2023

Thanks for your question.

Use the FX Currency field type in place of the standard currency fields when you must:

Support values expressed in multiple currencies, for example, EUR 100, JPY 200, USD 30, as values in a field. FX Currency fields provide better support for multi-currency applications than do standard currency fields.

Control how the FX Currency field is configured, including specifying its internal behavior and currency value formatting. For more info: https://docs.servicenow.com/en-US/bundle/vancouver-platform-administration/page/administer/currency/...

To learn more about currency configuration, see Configuring FX Currency field behavior.

Create custom conversion rate tables.

To learn more about custom table rates, see Add conversion rates using a custom rate table.

Have more control over when the actual currency conversion occurs. FX Currency values convert on demand only, making the conversion results much more transparent.

To learn more about currency conversions, see Understanding how FX Currency field conversions work.

Provide greater transparency into currency conversion calculations. You can view and configure the calculation components, including conversion dates, reference currency, and number of displayed decimals.

Build query conditions using FX Currency field values. For available query conditions, see Operators available for filters and queries.

Access FX Currency fields through richer scriptable APIs.

Aggregate currency values as entered by users, or aggregate them in selected reference currencies, for reporting purposes.

For more information refer here: https://docs.servicenow.com/bundle/vancouver-platform-administration/page/administer/currency/concep...

VijayKan · Tuesday

Thanks @mmcdonnell for your response. But, it seems a copy paste from the existing documentation than answering the question raised.

I have managed to generate below with some help from ChatGPT, hope it helps the others.

Aspect Standard Currency Field FX Currency Field

Purpose	Basic currency handling	Advanced multi-currency scenarios
Currency support	Primarily single-currency oriented (with automatic conversions)	Designed for true multi-currency input (EUR, USD, JPY in same field) (ServiceNow)
User input	Amount (currency often implicit via locale)	Amount + explicit currency selection dropdown (ServiceNow)
Conversion behavior	Automatic (on save/display using system rates)	On-demand and configurable (you control when/how conversion happens) (ServiceNow)
Reference currency storage	Stored automatically in background	Explicitly stored as reference amount + reference currency (ServiceNow)
Rate source	Uses system fx_rate table (ECB, scheduled jobs)	Can use custom rate tables and logic (ServiceNow)
Transparency	Limited visibility into conversion logic	Full visibility (rate, date, reference currency, decimals) (ServiceNow)
Configuration flexibility	Low	High (per-field configuration possible)
Scripting/API access	Basic	Rich APIs, dot-walkable structure
Filtering & reporting	Uses reference currency behind the scenes	More nuanced (filtering depends on entered currency vs reference) (ServiceNow)
Aggregation behavior	Based on reference currency	Can aggregate on entered or reference values (configurable) (ServiceNow)
Data model	Simple numeric + implicit currency context	Complex (backed by Currency Instance records) (ServiceNow)

GuruKrishnV · ‎04-24-2024

wrong typo