NetSuite Banxico Exchange Rates Setup and Scope

The Mexico Complementary Features SuiteApp integrates NetSuite with Banxico to import foreign-currency exchange rates expressed in Mexican pesos (MXN). NetSuite applies these rates to foreign-currency transactions for MXN-base subsidiaries. Before configuration, prepare Multiple Currencies, the required currency records, Banxico credentials, and an API secret.

How Do Banxico Rates Apply to MXN-Base Subsidiaries?

The Mexico Complementary Features SuiteApp connects NetSuite with Banco de México, known as Banxico, to import exchange rates. These rates express the value of currencies outside Mexico in MXN. The documented transaction application is specifically for subsidiaries with the Mexican peso as their base currency.

For implementation planning, distinguish a subsidiary's base currency from a transaction's currency. Having an MXN currency record alone does not establish the documented scope: the subsidiary must use MXN as its base currency, and the transaction must be in another currency. The supplied documentation does not describe application of these rates for subsidiaries with another base currency.

For related coverage, see the Banxico exchange rate integration overview.

What Must Be Ready Before Configuration?

Complete these four prerequisites before setting up the integration:

1. Enable Multiple Currencies in the account.
2. Create currency records for MXN and every currency whose rates you want to import from Banxico.
3. Register with Banxico to obtain the exchange rates API base URL and token.
4. Create an API secret using that token, and record the script ID you define for the secret.

Keep the Banxico token and the API secret's script ID as separate checklist items. The source requires the token to create the secret and explicitly tells implementers to note the secret's script ID. Recording only the Banxico registration details leaves that prerequisite incomplete.

The supplied documentation does not specify a Banxico import frequency, API quota, historical-rate window, or complete permission matrix. Treat these as unresolved deployment questions rather than assuming defaults.

How Should You Prepare Currency Records?

Multiple Currencies provides these currencies by default:

MXN is not in that default list. Check whether an MXN record already exists before creating one, and prepare any additional records needed for the currencies you intend to import. NetSuite supports all ISO 4217 standard currencies; that statement does not establish which currencies Banxico supplies through this integration.

To create a currency, go to Lists > Accounting > Currencies > New. Each currency requires a name, default locale, ISO code, and default exchange rate.

Currency names become selectable on customer, vendor, and other records, so naming affects users beyond the integration administrator. Review names for clarity, particularly when several countries' currencies share the same name.

NetSuite warns when an ISO code is changed to an unsupported value. The currency-record documentation states that nonstandard ISO codes significantly slow exchange rate updates. Verify codes rather than relying only on a familiar currency name or symbol; a recognizable label is not a substitute for the required code.

What Is the Setup and Verification Sequence?

After completing the prerequisites, the overview points to four implementation topics:

1. Setting up the integration with Banxico.
2. Setting up currencies for the exchange rates import.
3. Deploying the Banxico exchange rate import script.
4. Verifying the exchange rates imported from Banxico.

These topics establish the implementation stages, but the supplied material does not include their configuration fields or deployment settings. Use the detailed help topics to complete those stages rather than treating the prerequisite checklist as the full setup procedure.

For acceptance planning, include checks of the intended currencies, imported rates, and foreign-currency transaction behavior in an MXN-base subsidiary. These are recommended validation steps based on the documented scope, not a substitute for Oracle's detailed verification instructions.

Does the Currency Reference Include Separate Role Guidance?

The accompanying currency-enablement reference describes a Costed Bill of Materials role adjustment when Multiple Currencies is enabled after the SuiteApp is installed. It does not identify this adjustment as a Banxico-specific permission requirement. For that separate scenario, the reference instructs administrators to:

1. Go to Setup > User/Roles > Manage Roles and customize Costed_BOM_Role.
2. Optionally change the custom role's Name.
3. Under Permissions > Lists, add Currency at View level, then save.
4. Go to Customization > Scripting > Scripts, open Deployments for Costed Bill of Materials, and edit the deployment.
5. Set Execute As Role to the custom role and save.
6. Repeat the deployment change for Costed BOM DataService.

Keep this manufacturing-related adjustment separate from the Banxico prerequisite checklist. The reference does not establish a Banxico execution role or permission matrix.

Who This Affects

• Administrators: Prepare Multiple Currencies, currency records, and the API secret.
• Integration implementers: Coordinate Banxico registration and follow the configuration, deployment, and verification topics.
• Accounting teams: Plan validation around foreign-currency transactions in MXN-base subsidiaries.
• Manufacturing administrators: Review the separate Costed BOM role scenario where applicable.

Key Takeaways

• Banxico imports express foreign-currency values in MXN; documented transaction use applies to MXN-base subsidiaries.
• Prepare Multiple Currencies, currency records, Banxico credentials, and an API secret before configuration.
• Record the secret's script ID as well as the Banxico registration details.
• General currency-record support does not establish Banxico's available currency coverage.
• Follow configuration and script deployment with verification of imported rates.
• Do not treat the separate Costed BOM role guidance as a Banxico permission requirement.