Jarrett Parr is a Financial Systems Implementer for SuiteDynamics, a NetSuite solutions provider. He enjoys analyzing and improving processes for both our company and clients. He also loves solving accounting and financial problems for growing businesses. Jarrett lives in Madison, WI, with his wife, Abbie, and their golden retriever, Clark.
The NetSuite Multi-Currency Feature: What You Need to Know About Exchange Rates and ERPs
Every international business must handle multi-currency transactions. Here's how to do it with minimum fuss.
If your company is large enough to need a NetSuite Cloud ERP, you might be large enough to operate in international markets—and multi-currency transactions complicate business operations to no end.
For example, you might have to maintain financial records in one currency while accepting invoices and purchase orders in another. You might also manage international subsidiaries that use various types of legal tender. Fortunately, you can simplify financial operations using the NetSuite multi-currency feature.
Key Takeaways
- Global Business Management - NetSuite's multi-currency feature, part of the OneWorld solution, supports over 190 currencies and exchange rates. Businesses can easily transact with international vendors and customers while managing various tax structures.
- Automated Currency Exchange - The system automatically converts transactions between currencies at current exchange rates without manual intervention. It also offers the option to set fixed rates during monthly close periods.
- Flexible Currency Assignment - Businesses can assign multiple currencies to the same customer or vendor, accepting any legal tender they use. However, payments must be applied in the transaction's specific currency.
- Multi-Book Accounting Capabilities - NetSuite allows users to maintain parallel financial records in different currencies. It keeps primary books in the base currency and secondary books in other currencies to meet varying regulatory standards, automatically updating all books from a single transaction entry.
- Comprehensive Revaluation System - The platform handles currency fluctuations through various revaluation transaction types, including Unrealized Gain/Loss (month-end revaluations), Realized Gain/Loss (upon payment/closure), and Base Currency Adjustments, to ensure accurate financial reporting.
Why is the NetSuite multi-currency feature important?
The NetSuite multi-currency feature is a part of the OneWorld global business management solution. It supports more than 190 currencies and exchange rates and a range of payment options.
This functionality allows your business to easily transact with vendors and customers worldwide. It also helps manage a variety of international tax structures.
What can the NetSuite currency exchange rate tool do?
Automate currency exchange rate updates - Perhaps, the best part of NetSuite’s currency exchange rate integration is its automation. For instance, you can maintain your financials in USD but enter invoices that use euros. The system automatically converts the expenses into USD at the day’s exchange rate. You don’t even have to click a button.
You also have the option to set the exchange rate, so conversions won’t adjust to rate fluctuations. This feature comes in handy during the monthly close.
Work with customers and vendors using more than one currency - Or you may work with customers or vendors using multiple currencies. That’s not a problem with NetSuite multi-currency capabilities. You can assign various currencies to a customer or vendor and accept any legal tender they use. Note, however, that you must apply payment in the transaction’s specific currency.
Generate and update consolidated exchange rates - Your business may have an international network of parent and child subsidiaries. If so, NetSuite can generate consolidated exchange rates each accounting period so currencies translate correctly from one subsidiary to another. It also regularly updates these exchange rates to keep your financial reports accurate.
Allow for multi-book accounting with various currencies – NetSuite OneWorld allows users to keep multiple sets of parallel financial records, each in a different currency. So, you can keep primary book in your base currency and secondary books in other legal tenders to fulfill varying regulatory standards by country or industry. You can also include Fixed Assets in multiple books with separate currencies and varying depreciation methods. And best of all, the system automatically updates all books from one source of transaction entry. No duplicate data entry or adjustments required.
And, of course, NetSuite multi-currency tools are user-friendly, so your accountants don’t need IT specialists to set exchange rates or automate conversions. Instead, they can program the automation within minutes, saving your business time, money, and headaches.
How to set up a NetSuite currency exchange rate
NetSuite calculates currency conversions using two currency exchange rate API providers, Xignite and HSBC.
To enable NetSuite currency conversion, click the Currency Exchange Rate Integration checkbox. Find it by navigating to Setup > Company > Enable Features under the company subtab. (Note: Multiple currencies must be selected first.)
Then, you can select the rate provider. Find it by navigating to Setup > Accounting > Accounting Preferences.
How to select an API provider in NetSuite
Xignite and HSBC support different currency pairs. You can see which pairs your system supports by navigating to Lists > Accounting > Currency Exchange Rates.
You have two options if your current provider doesn’t support a needed pairing. First, select the other currency provider to see if they have the pairing or enable the NetSuite multi-currency feature’s triangulation calculation.
Triangulation calculation uses a third “matchmaker” currency to convert the pair. For example, suppose you need to convert the United States Dollar to the Icelandic Krona, but the pair is unavailable. Instead, you can use triangulation, which would use a dollar-to-euro pair and a euro-to-krona pair to perform the task.
You can enable triangulation underneath the Rate Provider dropdown.
How the NetSuite multi-currency feature handles revaluation transactions
Exchange rates fluctuate constantly, impacting the values of all financial transactions in a NetSuite multi-currency environment. Currency revaluation accounts for those fluctuations by measuring the change in valuation and posting it as a loss or gain. NetSuite features a variety of currency revaluation transactions based on the process type.
Unrealized Gain/Loss – The month-end currency revaluation process produces this revaluation transaction. Open balance sheet accounts are revalued based on current exchange rates if the account uses a foreign currency. This requires you to enable the Currency Revaluation permission in NetSuite.
The system doesn’t delete these transactions if you rerun the revaluation in the same period. Instead, it creates additional currency revaluation transactions to reflect any changes.
Reversal of Unrealized Gain/Loss – As the name suggests, this type of transaction reverses the Unrealized Gain/Loss from the previous month-end close. The system will post the reversal on the first day in the period following the Unrealized Gain/Loss transaction.
You can’t edit or delete this transaction type. But if you edit or delete an associated month-end revaluation, the system automatically updates or deletes the reversal.
Realized Gain/Loss – This transaction records exchange rate variances between currencies upon closure or payment. As the name suggests, it records differences that have occurred or are “realized” because payment in a foreign currency is being transacted. Conversely, think of an “unrealized” gain/loss as a value difference that would occur if a transaction took place.
Like “reversal of Unrealized Gain/Loss,” you can’t delete these transactions. However, a source transaction adjustment may change a previously posted gain or loss. In that case, NetSuite automatically deletes the associated currency revaluation transaction.
Rounding Gain/Loss – This transaction occurs when a realized gain/loss is recorded but it doesn’t balance due to using two decimal places in accounting. These transactions typically display +/- $.01 values because that’s all the system should need to balance the account.
These transactions can’t be deleted. Still, NetSuite will eliminate previous currency revaluations if source transaction alterations change previously posted gain or loss.
Base Currency Adjustment – The month-end currency revaluation process creates this type of revaluation. This transaction zeros out accounts that may otherwise have residual balances caused by fluctuations in exchange rates. This is done by posting an adjustment to a currency gain/loss account and the account with the residual balance.
The transaction also gets rid of amount reversals and continuous revaluation for that account. Additionally, the system will automatically delete and recreate the transactions if you perform the revaluation again in the same period.
If you’re interested in the NetSuite OneWorld global business management system, you’ll need a competent consulting firm to set it up. SuiteDynamics employs several experts who understand NetSuite multi-currency features and the complex accounting they use. As a result, we can evaluate your company, identify your pain points, and guide you through a smooth OneWorld implementation. Call today to learn more.
Disclosure: This article was developed with the assistance of Claude, an AI created by Anthropic. Our editorial team used Claude as a collaborative writing tool, carefully reviewing, editing, and fact-checking all AI-generated content. The final text has been thoroughly vetted to ensure accuracy, clarity, and alignment with SuiteDynamics' editorial standards. We take full responsibility for the content presented in this article, maintaining our commitment to providing reliable and informative insights to our readers.
Spreadsheets built modern business. For decades they served as the unofficial operating system of job shops and custom manufacturers everywhere. They are flexible, familiar, and just comfortable enough to feel like a real solution. In the early days of a growing shop, they genuinely work. But as make-to-order complexity increases, as custom BOMs multiply, lead times tighten, and engineering revisions pile up, spreadsheets strain under the pressure. Every job is different, but spreadsheets want everything to be the same. In make-to-order environments, no two jobs are identical. Unique BOMs, custom routings, variable material costs, different setup requirements, customer-specific specs. Spreadsheets, though, thrive on repetition and standardized rows. So the more variation you introduce, the more tabs you create. The more exceptions you add, the more manual overrides appear. The more formulas you patch together, the more fragile the whole thing becomes. Eventually, the file turns into something only one person truly understands. That’s a liability, not a system. Capacity becomes a guessing game. In make-to-order shops, capacity isn’t theoretical. It’s constrained by reality. Machines go down. Operators vary in skill. Setup time fluctuates from job to job. Rush orders blow up carefully planned weeks. Spreadsheets struggle here because they’re built on static inputs. You can build a beautiful planning sheet with machine-hour allocations, but unless it dynamically adjusts for real-time job status, operator availability, overlapping resource conflicts, and maintenance downtime, you’re not really planning. You’re forecasting best-case scenarios. And that’s exactly how shops overpromise delivery dates and end up paying for it later in overtime and expediting costs. Engineering changes don’t cascade cleanly. Change is a constant in make-to-order manufacturing. A customer tweaks a dimension, a material substitution becomes necessary, or a tolerance tightens halfway through production. In an integrated system, that change automatically updates BOMs, routings, cost projections, and scheduling impact all at once. In a spreadsheet environment, it depends entirely on who remembers to update which tab. A routing might change without adjusting the labor estimate. A material substitution might never feed into the margin calculation. A lead-time adjustment might not reach the production schedule until it’s too late. These small disconnects multiply quickly, and because spreadsheets have no enforced relationships between data sets, the errors don’t announce themselves. Institutional knowledge becomes a single point of failure. Ask most growing job shops who owns the master spreadsheet and you’ll get a name. One estimator, planner, or operations manager who has become the living interpreter of years’ worth of embedded formulas, assumptions, and logic that nobody else fully understands. This works fine until it doesn’t. When that person goes on vacation, gets sick, or leaves, the shop loses operational clarity. In an environment already defined by complexity, having critical knowledge live inside one person’s mental model of a file is an inefficient bottleneck. Visibility stops at the file boundary. Spreadsheets are static snapshots. Make-to-order manufacturing is anything but. Without real-time feedback loops, shops find themselves unable to answer questions that should be simple: Are we actually on track this week? Which jobs are consuming more labor than quoted? Where is the bottleneck right now? Which customers consistently drive margin compression? When performance data doesn’t flow automatically from the floor back into quoting and planning, improvement stalls. You can’t refine what you can’t see. Here’s the thing about spreadsheet failure in manufacturing… it’s not dramatic. It’s gradual. First the files get slow, then fragile, then opaque. By the time leadership feels the real pain through late shipments, squeezed margins, and rising overtime, the architectural issues are widespread. Make-to-order manufacturing demands systems that understand relationships: how a routing affects capacity, how a BOM revision affects cost, how a delayed job cascades through the rest of the schedule. The question most shops ask is whether they can make the spreadsheets work. The better question is what it’s actually costing to keep them. The most resilient make-to-order manufacturers are building systems that preserve flexibility without sacrificing the visibility needed to actually run the business. Adaptability is the advantage.
In custom manufacturing , when systems break down, profit rarely disappears all at once. It leaks. Quietly, repeatedly, and often in ways that never show up clearly on any report. Walk into almost any fabrication shop and you’ll hear some version of the same story: the backlog is strong, revenue looks good, we’re staying busy. And yet the margin feels thinner than it should. For job shops running custom work, profitability doesn’t usually collapse because of one bad decision. It erodes through small, daily inefficiencies buried inside quoting, scheduling, engineering changes, and the gap between what was planned and what actually happened on the floor. Here’s where shops most commonly lose efficiency, and how to get it back. The quote that was almost right. For custom orders, every quote is a prediction, and predictions are dangerous when they’re disconnected from real shop-floor data. Outdated labor standards, underestimated setup time, material prices that changed since the template was built, and capacity assumptions based on average weeks instead of current reality. These errors are each small on their own, but a 4% underestimate on labor here, a missed secondary operation there, add up across hundreds of jobs. Small errors compound into real margin loss. The best-performing shops treat quoting as a living system fed by actual job performance data, not static spreadsheets that nobody updates. Capacity that looks available but isn’t. On paper, there’s open space on the schedule. In practice, that open week includes a machine down for maintenance, a senior operator on vacation, two complex jobs already competing for the same bottleneck, and a rush order someone verbally committed to last Thursday. Without finite capacity planning, shops routinely overcommit based on theoretical machine hours rather than real-world constraints. The fallout is predictable: overtime spikes, expedited shipping costs, re-sequencing chaos, and exhausted operators. Margin shrinks not because the shop is incapable, but because it’s planning in averages. Engineering changes that never get repriced. Designs evolve. A hole moves, a weld spec changes, or a tolerance tightens. Each adjustment has a cost. But many shops hesitate to reprice midstream, worried about damaging the customer relationship, and end up absorbing the extra labor and rework time instead. Do this enough times and it becomes a cultural norm: “we’ll just take care of it.” That’s margin erosion disguised as good service. High-performing job shops track engineering change impact in real time and make repricing decisions based on data rather than discomfort. Setup time hiding in plain sight. In low-volume, high-mix environments, setup time is often the silent killer. When shops don’t track setup separately from run time, assume it’ll all come out in the wash, and never refine their routings based on what actually happened, they end up underpricing complexity. In job shops producing one to fifty unit runs, setup can represent a disproportionate share of total labor. If it isn’t measured accurately, it can’t be priced accurately. The spreadsheet layer nobody talks about. Most shops run a hybrid environment where the ERP handles transactions and spreadsheets handle reality. Capacity lives in one file, quoting assumptions in another, and actual job performance in someone’s head. This creates invisible disconnects. Quotes not aligned with current routing, schedules that don’t reflect real constraints, and historical performance that never feeds forward into better decisions. Each disconnect feels manageable in isolation. Collectively, they create margin leakage that leadership can feel but can’t quite locate. What makes all of this so frustrating isn’t that shop owners don’t care. It’s that they can’t see clearly enough to act decisively. Without integrated visibility across quoting, routing, capacity, and quality, operators run on instinct. And instinct works remarkably well until scale and complexity outpace it. The shops that consistently outperform aren’t necessarily the biggest or the busiest. They operate with clarity and consistency. Fewer assumptions and more decisions based on reality. In a manufacturing landscape where lead times keep shrinking and customers expect speed and precision at the same time, margin won’t be protected by effort alone.
Every manufacturing leader has lived this moment: The schedule looks perfect. Orders are slotted. Commitments are made. And then reality shows up. A machine goes down. A key operator calls out. Setup times balloon. One late job cascades into five. Suddenly the plan (built meticulously inside your ERP) falls apart. Not because your team failed, but because the plan was never grounded in reality to begin with. The Hidden Lie Inside Most ERP Schedules
NetSuite’s Model Context Protocol (MCP) , built in partnership with Anthropic, helps users leverage AI to ask simple, natural-language questions and get back complex, structured analysis, all powered by live NetSuite data. This practical use of AI can be used to generate reports, create or update records, perform queries, analyze reports, automate workflows, or make predictions based on real-time data. Here's how you can get started and connect AI to NetSuite using MCP: 1. Login to NetSuite and navigate to Customization → SuiteCloud Development → SuiteApp Marketplace. 2. Search “MCP Tools” > Click on the icon and install the MCP Tools SuiteApp
Job shop manufacturing is a production method where small batches of 1-100 units of customized or unique products are made to meet specific customer requirements. Unlike mass production, each order typically requires unique setups, specialized processes, and custom routing through the facility. In this comprehensive guide, you'll learn: The complete definition of job shop manufacturing How job shops differ from other manufacturing types Industries that rely on job shop methods Technology solutions that optimize job shop operations When to consider implementing specialized ERP systems What is Job Shop Manufacturing? (Definition) Job shop manufacturing is a production strategy focused on customization over volume . Instead of producing thousands of identical items, job shops create small quantities of unique products tailored to specific customer specifications. Key defining characteristics: Small batch sizes - Typically 1-100 units per order High product variety - Hundreds or thousands of different products Custom specifications - Each order has unique requirements Project-based workflow - Work orders last days to weeks Skilled labor - Requires specialized expertise and flexibility Job Shop is a powerful, fully integrated solution built for custom manufacturers, combining quoting, configuration, production, and fabrication workflows inside NetSuite. Learn more about SuiteDynamics' NetSuite Job Shop for Manufacturing.
Uncover the challenges of data quality affecting DIO accuracy, from ghost inventory to inconsistent formats. Find out how to tackle these issues effectively with a NetSuite ERP.
In the world of private equity, creating operational value has become increasingly critical as the market evolves. With exit timelines extending and competition for deals intensifying, PE firms are looking beyond financial engineering to drive returns. One emerging strategy that's gaining traction is the consolidation of NetSuite instances across portfolio companies. The Hidden Challenge of System Fragmentation As PE portfolios grow through acquisition, a common pattern emerges: multiple portfolio companies operating on separate NetSuite instances. While each system may work effectively in isolation, the fragmentation creates significant operational inefficiencies at the portfolio level: Redundant Licensing Costs: Each separate instance requires its own licensing structure , creating unnecessary expenses that directly impact EBITDA. Manual Consolidation Effort: Finance teams spend countless hours extracting, transforming, and manually consolidating data from disparate systems. Inconsistent Processes: Basic business functions are handled differently across portfolio companies, limiting standardization efforts. Limited Portfolio-Wide Visibility: Gaining insight across the entire portfolio requires extensive manual effort, delaying strategic decision-making. Integration Challenges: Onboarding new acquisitions becomes increasingly complex when each company maintains its own environment.
Explore Esusu's partnership with SuiteDynamics to enhance financial processes. Schedule a consultation to see how your business can thrive with NetSuite solutions.
Discover how to effectively set up and configure case statuses, rules, types, priorities, and more in NetSuite's case management system. Streamline your workflow and improve customer support with this comprehensive guide.
Backorders disrupt revenue and frustrate customers. Learn what "backordered" means, how backorders happen, their impact on businesses, and how NetSuite ERP can minimize the issues.
