Automating Multi-Currency Reconciliation Without a Dev Team: NetSuite, Salesforce CPQ and Month-End Close Workflows
Multi-currency reconciliation matches CPQ quotes, NetSuite invoices and payments in the billed currency, then explains FX. How to automate it without code.

Multi-currency reconciliation is the work of matching every deal, invoice and payment across your systems in the currency the customer was actually billed in, and then explaining whatever difference is left in your base currency as an exchange-rate effect rather than an error. When Salesforce CPQ quotes in euros and NetSuite books in a US dollar subsidiary, the two systems will almost never show the same dollar figure, even when every record is correct.
The fix is not a better spreadsheet. It is a fixed order of checks: transaction currency first, base currency second, reporting currency last, run on a schedule so the exceptions are known before the close starts.
Where engini fits: engini connects Salesforce and NetSuite in both directions and runs the reconciliation checks as a workflow built in Workflow Studio, a visual builder that needs no code. The workflow reads quotes, opportunities, sales orders, invoices and payments, compares them in the billed currency, writes status back where you need it, and posts mismatches to Slack or Teams for a person to resolve. Every run is recorded. Start with the NetSuite connection guide or the engini docs index.
Key Takeaways
- Reconcile in the transaction currency first. A euro quote, a euro invoice and a euro payment should match to the cent before any conversion.
- Salesforce CPQ prices a foreign-currency quote from that currency's price book entries, and a primary quote must use the opportunity's currency.
- NetSuite converts each transaction to the subsidiary's base currency and posts realized gains and losses when a payment is applied, and unrealized gains and losses at period-end revaluation.
- Differences in the base currency are expected. The job is to explain them as exchange-rate effects, not to force the totals to agree.
- A no-code workflow can run these checks daily and send only the true exceptions to the finance team.
What is multi-currency reconciliation?
Multi-currency reconciliation is the check that the same commercial event, a deal, an order, an invoice, a payment, carries the same amount in the same currency in every system that records it. It covers two questions that are easy to mix up:
- Did the right amount move? Compare the quote, the order, the invoice and the payment in the currency the customer was billed in.
- Is the conversion explained? Compare the base-currency or reporting-currency figures, and attribute each difference to a rate, a date or a revaluation.
Teams that answer only the second question spend the close chasing differences that are not errors. Teams that answer only the first miss the revaluation and gain or loss postings that auditors ask about.
Why Salesforce CPQ and NetSuite totals disagree
Salesforce CPQ and NetSuite totals disagree because each system takes its currency and its exchange rate from its own setup, at its own date. Both systems are working as designed.
Sources: Salesforce's Multi-Currency in CPQ article and NetSuite's Currency Management and Foreign Currency Revaluation topics, read November 2026.
Two consequences follow. First, the dollar value of a euro opportunity in Salesforce reports and the dollar value of the matching euro invoice in NetSuite are converted with different rates on different dates, so they differ. Second, a CPQ quote can fail to price correctly in a currency if one of its per-currency records is missing, and that shows up later as a mismatch against the order.
Note: NetSuite's Multiple Currencies feature cannot be turned off after you create transactions and records that rely on it, according to NetSuite's Currency Management topic. Plan currencies per customer and subsidiary before you migrate history.
How to reconcile multiple currencies: three layers, in order
Reconcile in three layers, and stop at the first layer that fails. This keeps exchange-rate noise from hiding real errors.
- Transaction currency. For each closed-won opportunity, match the primary quote, the NetSuite sales order, the invoice and the applied payment in the billed currency. Check the currency code, the total, and the line count. Any difference here is a real error: a wrong price book entry, a missing line, a partial payment or a wrong customer currency.
- Base currency. For each matched invoice and payment, compare the base-currency amounts in NetSuite and confirm the difference sits in the realized gain or loss account. For invoices still open at period end, confirm that revaluation ran, which NetSuite runs as part of the period close and which requires the Currency Revaluation permission.
- Reporting currency. For the consolidated view, confirm consolidated exchange rates were updated for the period, which NetSuite says you should do before you close each period. Then compare Salesforce bookings in the corporate currency with NetSuite revenue, and label the remaining gap as a rate-date difference.
Tip: Keep a single matching key across both systems, such as a Salesforce ID stored on the NetSuite customer and sales order. Matching by name or by amount fails the moment two currencies or two partial payments are involved.
What to automate, and what stays with people
Automate the data steps and the comparisons; keep the judgment calls with your team. This split works for most mid-market finance teams.
The point of the split is that a person never retypes data between Salesforce and NetSuite, and never opens a spreadsheet just to find out that everything matched.
A daily multi-currency check without a dev team
A daily check is a short workflow that any operations or finance systems person can build in a visual tool. In engini's Workflow Studio it looks like this:
- Trigger: a schedule, for example every weekday at 6:00 in your close timezone. A trigger on a changed record also works for near-real-time checks.
- Read Salesforce: get closed-won opportunities changed since the last run, with their primary quote, currency and lines.
- Read NetSuite: get the matching sales orders, invoices and customer payments by the shared key.
- Compare: loops and conditions compare currency codes, totals and line counts in the billed currency. A table lookup holds tolerances per currency if you round differently by currency.
- Stage results: write each match and mismatch to an engini Table, so the history is kept between runs and large result sets do not overload one run.
- Write back: update the Salesforce opportunity with invoice number and payment status, since every engini integration runs in both directions.
- Report exceptions: post only the mismatches to a Slack or Teams channel, with links to both records.
This is the same pattern as the Salesforce closed-won to NetSuite sales order tutorial, extended with currency checks. For how orders get into NetSuite in the first place, see creating NetSuite sales orders from Salesforce, and for keys that survive retries, Salesforce external IDs and NetSuite upserts.
Banks, payment processors and legacy ledgers
Multi-currency reconciliation rarely ends at NetSuite. Payments arrive in bank statements and processor payout files, and banks, credit unions and older subsidiaries often keep ledgers in systems that never touch Salesforce.
- Bank and processor files: a workflow can read CSV files from SFTP or FTP and match payout lines, by currency, to NetSuite payments.
- Ledgers on your own servers: engini's on-prem agent reaches databases such as SQL Server, Oracle Database and IBM DB2, and file drops in local folders and network shares, without opening inbound firewall ports.
- Databases: custom SQL and existing stored procedures can pull balances by currency from a legacy ledger for the same comparison.
If your multi-currency exposure is mostly at the bank, the order-to-cash and finance pages show where the same workflows sit in the wider process.
How engini handles multi-currency reconciliation
engini is the layer that reads and writes both systems and runs the checks; it does not replace NetSuite's currency engine or Salesforce CPQ's pricing. What it does for this problem:
- Reads and writes both systems. On Salesforce: create, update, upsert, delete and get records on any object, plus bulk jobs. On NetSuite: create, update, create or update, delete, and get one or many records. Custom fields and custom objects are read live from each system's setup.
- Starts on the right event. A schedule, a webhook, or a record created or updated in Salesforce or NetSuite, checked as often as every 15 minutes. Salesforce outbound messages give a real-time trigger.
- Needs no code. Workflow Studio has loops, conditions, data transformation, table lookups and CSV file handling. It has no code step by design, so the workflow stays readable for the next person.
- Records every run. Run history shows what each run read, compared and wrote. The audit log can be exported or streamed to a SIEM.
- Uses accounts you control. In NetSuite, your administrator sets up the integration record, the role and the tokens, and chooses which record types the connection uses. Give the role create and edit rights on the records the workflow writes, and view rights elsewhere.
- Can add an AI agent step. An AI agent step can read an exception and draft the explanation for the reviewer, for example that a difference matches a rate change between quote date and invoice date.
When you do not need engini: if you bill in one currency, or if Salesforce never sends orders to NetSuite and you reconcile only bank to ledger inside NetSuite, NetSuite's own matching and revaluation tools may be enough. engini earns its place when the same deal lives in Salesforce CPQ, NetSuite and a bank or legacy file, in more than one currency. For the full close, see AI month-end close software.
Frequently Asked Questions
How do you reconcile multiple currencies in NetSuite?
Reconcile in the transaction currency first, then confirm base-currency differences sit in realized or unrealized gain and loss. NetSuite posts realized gain or loss when a payment or credit memo is applied to an invoice, and unrealized gain or loss when you run period-end revaluation of open balances. Check both before you sign off the period.
Does Salesforce CPQ support multiple currencies?
Yes, Salesforce CPQ quotes in multiple currencies, using each currency's own price book entries. A primary quote must use the opportunity's currency, and MDQ price dimensions, cost records, consumption rates and discount tiers each need an entry for the quote's currency, or the quote may not price correctly.
Why does the Salesforce amount not match NetSuite in US dollars?
The two systems convert with different rates on different dates. Salesforce applies dated exchange rates only to opportunities and certain related objects, while NetSuite converts each transaction with its own exchange rate list and later revalues open balances, so base-currency figures rarely agree exactly.
Can you automate quote to cash between Salesforce CPQ and NetSuite without code?
Yes, a visual workflow builder can move closed-won deals into NetSuite and check them back without code. In engini's Workflow Studio, a workflow creates the customer and sales order in NetSuite, then reads invoices and payments and writes their status back to Salesforce.
What is the difference between realized and unrealized exchange gains?
Realized gains and losses come from payment application; unrealized ones come from revaluing open balances. In NetSuite, the realized amount posts when a payment is applied to an invoice, and the unrealized amount posts during period-end revaluation of open foreign-currency transactions and balances.