NetSuite 2026.2 Adds Currency Context to Currency Custom Fields

Currency Context is a new setting in NetSuite 2026.2 for custom currency-type fields that controls whether the field displays amounts in the subsidiary's base currency or the transaction's transaction currency. Before this setting, custom currency fields did not have a predictable way to specify which currency context should apply.

If your NetSuite account uses custom fields that store currency amounts, 2026.2 adds a new option called Currency Context to the field definition.

What Does Currency Context Control on NetSuite Custom Fields?

A currency custom field stores a monetary value. In a multi-currency NetSuite account, that value needs a context: which currency does it represent, and how should it convert when displayed or used in transactions involving a different currency?

Currency context is the setting that answers this question. It tells NetSuite how to treat the stored value when the transaction or record is operating in a different currency than the one the value was entered in.

What Is New for Currency Context in NetSuite 2026.2?

NetSuite 2026.2 adds a new Currency Context option to currency custom fields. This gives administrators more explicit control over currency behavior at the field level, rather than relying on account-wide or transaction-level defaults.

Where Do You Find the Currency Context Setting?

Currency Context is a field-level setting. To access it:

Go to Customization > Lists, Records, & Fields and select the type of field you want to configure (Transaction Body Field, Transaction Column Field, Entity Field, etc.).

Open the currency custom field you want to update. The Currency Context option is in the field definition.

When creating a new currency custom field, the Currency Context option is available during setup.

Who Should Review Currency Context Settings?

• Administrators who manage custom fields that store currency amounts on transactions, records, or entities
• Accounts with multi-currency setups where custom currency fields need consistent behavior across different transaction currencies
• Developers building customizations that involve currency amounts on custom records or transaction lines

If your account uses single-currency only, or if your existing currency custom fields behave correctly already, this update may have no immediate impact. But it is worth reviewing if you have noticed inconsistent currency behavior on custom fields in a multi-currency environment.

How Does Currency Context Affect Multi-Currency Transactions?

When a NetSuite account operates across multiple currencies, the same custom field may store values entered in euros on one transaction and dollars on another. Without clear context, NetSuite has to make assumptions about how to interpret, display, or aggregate those values. Currency Context makes that behavior explicit at the field level.

This matters most in scenarios such as: a currency custom field on a vendor record that stores an amount in the vendor's native currency; a transaction body field that holds a pre-negotiated price that should not be converted; or a custom field used in reports that aggregates monetary values across transactions in different currencies.

Before 2026.2, currency fields relied on account-level or transaction-level behavior for these interpretations. The new field-level setting gives administrators the ability to define this behavior per field, which reduces inconsistencies when the same field is used in different multi-currency contexts.

Frequently asked questions

Q: Which field types support Currency Context? A: Currency Context is available on currency-type custom fields including Transaction Body Fields, Transaction Column Fields, and Entity Fields.

Q: Does Currency Context affect existing records that already have values stored in a currency custom field? A: Field definition changes in NetSuite typically affect how values are displayed and used going forward. Review any reports or searches that use the affected field after changing Currency Context to confirm the output matches expectations.

Q: Do single-currency accounts need to review this setting? A: Not in most cases. Currency Context is primarily relevant for multi-currency accounts where the same field is used on transactions in different currencies.

Q: Where exactly is the Currency Context option in the field editor? A: It is in the field definition when editing a currency-type custom field under Customization > Lists, Records, and Fields.

Q: Is Currency Context available on all subtypes of currency custom field? A: NetSuite 2026.2 added it to Transaction Body Fields, Transaction Column Fields, and Entity Fields. Check the field editor for the specific field type you are working with to confirm the setting is available.

Q: What is the best way to audit existing currency custom fields in an account? A: Open each currency-type custom field under Customization > Lists, Records, and Fields and review the Currency Context setting. Accounts with large numbers of custom fields may want to prioritize fields that appear on transaction sublists or entity records used in multi-currency transactions.

For step-by-step instructions on configuring the Currency Context setting on a custom field, see How to Set Currency Context on NetSuite Currency Custom Fields.

For help auditing or configuring custom fields in your NetSuite account, see SuitePacific's NetSuite administrator support service.