Banxico Exchange Rate Integration for NetSuite: Eligibility and Prerequisites

Banxico exchange rate integration for NetSuite imports Banco de México (Banxico) rates through Mexico Complementary Features SuiteApp 1.8.0. NetSuite automatically applies those rates to new foreign-currency transactions in subsidiaries whose base currency is the Mexican peso (MXN). Before configuration, administrators must enable Multiple Currencies, prepare currency records, obtain Banxico credentials, and create an API secret.

The first planning decision is eligibility by subsidiary base currency—not location alone. The second is whether the intended transactions fit the documented new-transaction scope.

Key takeaways

Automatic application is documented for new foreign-currency transactions in MXN-base subsidiaries.
Imported rates express the value of currencies from outside Mexico in Mexican pesos (MXN).
Before setup, enable Multiple Currencies and create records for MXN and each currency whose rates you want to import.
Register with Banxico to obtain the exchange rates API base URL and token. Use the token to create an API secret, then record the secret’s script ID.
Do not assume retroactive updates to existing transactions or automatic application for subsidiaries with another base currency.

Which subsidiaries and transactions are in scope?

Start with the subsidiary’s base currency. The documented automatic application applies where that currency is MXN. A list of entities located in Mexico is therefore not an adequate substitute for a base-currency review.

Separate the subsidiary question from the transaction question. An MXN-base subsidiary meets the stated subsidiary condition, but the described transaction use is narrower: new transactions in currencies other than MXN. Both conditions should inform the rollout and the scenarios finance users test.

Scenario	Interpretation for this integration
MXN-base subsidiary, new foreign-currency transaction	Within the documented automatic-application scope.
MXN-base subsidiary, existing foreign-currency transaction	Do not assume a retroactive update.
Subsidiary with another base currency	Automatic application is not established for this scenario.
Subsidiary located in Mexico	Location alone does not establish eligibility; assess the base currency.
MXN-base subsidiary, transaction in MXN	Not the described foreign-currency transaction use case.

A useful planning aid is a subsidiary inventory showing base currency and intended new foreign-currency transaction scenarios. This is a recommendation, not an additional NetSuite prerequisite. It helps prevent an entity-level rollout decision from becoming an unsupported promise about every transaction that entity enters.

For example, consider an MXN-base subsidiary preparing a new transaction in a foreign currency whose rate the team intends to import. That matches the described transaction scenario. Preparation must include a record for MXN and a record for that foreign currency. The example does not establish that every possible foreign currency is supported by Banxico imports.

If the transaction already exists, the documented behavior no longer establishes what will happen. Describe the finance handoff accordingly: this project prepares Banxico rate imports for new foreign-currency transactions in MXN-base subsidiaries, not replacement of exchange rates across the entire account.

For related reading, see NetSuite Banxico exchange rates setup and scope.

What must be ready before configuration?

Complete the four documented preparation areas before configuring the integration. For each one, capture a concrete readiness result rather than a general “ready” status. The evidence column below is a recommended handoff aid, not an additional product requirement.

Prerequisite	Required preparation	Recommended readiness evidence
Multiple Currencies	Enable the feature in the NetSuite account.	Confirmation that the feature is enabled.
Currency records	Create records for Mexican Peso (MXN) and each currency whose rates you want to import from Banxico.	A comparison of intended import currencies against existing records.
Banxico registration	Obtain the exchange rates API base URL and token.	Confirmation that both have been obtained.
API secret	Create a secret using the Banxico token and note the script ID you define for it.	The secret’s script ID in implementation notes.

A practical preparation sequence is:

Identify the MXN-base subsidiaries and intended new foreign-currency transaction scenarios.
Confirm that Multiple Currencies is enabled.
Compare intended import currencies with existing currency records, including MXN, and create the required records.
Register with Banxico and obtain the exchange rates API base URL and token.
Create the API secret using that token and record its script ID.
Review the readiness evidence before beginning integration configuration.

The first and last steps are organizational recommendations. The feature, currency records, registration, and secret are the documented prerequisites. Keeping that distinction explicit avoids turning an internal checklist into an invented NetSuite requirement.

For administrators coordinating several localization projects, a separate readiness checklist for Banxico can keep these requirements visible. Broader related reading includes the Localization SuiteApps enhancements overview; it should not replace the integration-specific checks above.

How should you prepare currency records?

Start with the intended imports, not simply the presence of an MXN record. Mexican Peso (MXN) is required, but so is a currency record for each currency whose rates you want to import. Compare the intended-import list with the account’s existing currency records before setup.

For example, if the project plans imports for several foreign currencies, confirming MXN alone does not complete the prerequisite. Check every planned currency against existing records and identify which records still need to be created. This turns a broad task—“prepare currencies”—into a reviewable list.

Keep that list separate from assumptions about supported currency coverage. A business requirement to import a currency does not demonstrate that the integration supports it. The supplied material does not enumerate supported currencies, so the readiness review should distinguish records prepared from coverage confirmed.

Keep Banxico credentials and the API secret distinct

Banxico registration supplies the exchange rates API base URL and token. The token is then used to create an API secret. Obtaining the token is therefore not the same as completing the secret-creation prerequisite.

There are three distinct preparation outputs to track:

API base URL: obtained through Banxico registration.
Token: obtained through Banxico registration and used to create the API secret.
Secret script ID: the identifier you define for the API secret and record in implementation notes.

Do not substitute the token or API base URL when recording the secret’s script ID. A clear handoff should identify which preparation tasks are complete and include the recorded script ID, rather than treating all three items as interchangeable “credentials.”

Keep the Banxico checklist separate from unrelated localization reading, such as the Chile localization help and licensing preparation guide. A completed checklist for another project is not evidence that the four Banxico prerequisites have been completed.

Organize setup and verification around four topics

Once the prerequisites are ready, organize implementation around the four topics identified in the source:

Setting up the integration with Banxico.
Setting up currencies for exchange rate imports.
Deploying the Banxico Exchange Rate Import Script.
Verifying exchange rates imported from Banxico.

These topics form an implementation checklist, not a configuration procedure. Credentials being available does not, by itself, establish that configuration, deployment, or verification is complete. Give each topic its own completion check in the project plan.

The supplied material does not specify setup navigation, permissions, import frequency, supported currency coverage, or deployment parameters. Do not turn assumptions about those details into implementation commitments. This article covers eligibility and preparation rather than a click-by-click deployment guide.

Define an acceptance check within the documented scope

As an additional practitioner-recommended check, test a new foreign-currency transaction for an MXN-base subsidiary and compare its applied rate with the imported rate. This is not an additional documented prerequisite; it connects the imported result with the transaction behavior finance users expect.

Recommended test evidence includes the subsidiary, its base currency, the transaction currency, the imported rate, and the applied rate. Recording those details makes it clear whether the test actually represents the documented scenario. An existing transaction or a subsidiary with another base currency would not test the stated new-transaction use case.

Administrators and integration owners can coordinate prerequisite preparation and deployment review, while accountants and transaction users participate in acceptance checks. This division of work is a planning recommendation, not a statement of required NetSuite permissions.

FAQ

Does the integration automatically update existing transactions?

Automatic application is documented for new transactions. Do not assume that importing Banxico rates revises historical transactions, and do not promise retroactive updates in the rollout plan.

Is an MXN currency record enough to complete currency preparation?

No. The prerequisites also call for a currency record for each currency whose rates you want to import from Banxico. Compare the intended-import list with existing records rather than checking MXN alone.

What should be recorded after creating the API secret?

Record the script ID you define for the secret in implementation notes. Keep it distinct from the Banxico token used to create the secret and from the exchange rates API base URL.