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