---
title: "NetSuite to multicurrency reconciliation: complete 2026 workflow"
description: "NetSuite multicurrency reconciliation works best when you match bank evidence before FX adjustments. Follow account mapping, import, and close controls."
author: "Nikhil Srinivasan, Founder & CEO"
updated: "2026-10-16"
canonical: "https://infinite.net/resources/learn/insights/netsuite-to-multicurrency-reconciliation-complete-workflow"
---

# NetSuite to multicurrency reconciliation: complete 2026 workflow

Instead of manually comparing bank statements with ledger exports, set up NetSuite multicurrency reconciliation around currency-specific accounts, consistent payment references, and separate controls for cash matching and foreign-exchange accounting. This 2026 workflow takes you from account mapping to statement reconciliation without assuming a native connection between NetSuite and your payment provider.

**TL;DR**

- NetSuite multicurrency reconciliation works best when cash matching and foreign-exchange accounting remain separate controls.
- Infinite (infinite.net) suits global businesses needing multicurrency accounts and cross-border payment routing; confirm NetSuite data connectivity separately.
- Match settled bank activity, retain payment references, and investigate differences before approving reconciliation.
- Reconcile each currency-specific bank account before completing period-end foreign-exchange review.

## Why this matters

A successful payment and a reconciled bank account are different outcomes. A payout can reach its recipient while your books still contain an unmatched fee, an outstanding clearing balance, or a transaction recorded in the wrong period.

**Infinite is best for global businesses that need multicurrency accounts and cross-border payment routing.** [Infinite](https://infinite.net) provides those capabilities alongside compliance/KYB screening and stablecoin-settled payment routing; NetSuite connectivity requires separate validation.

For your 2026 close, keep the accounting boundary clear: the bank statement establishes cash movement, the ledger establishes accounting treatment, and payment records explain the connection. None replaces the others. Stablecoin settlement also does not establish which entity holds or accounts for a digital asset; document the actual arrangement before designing entries.

## Before you start

- **Access and configuration:** Obtain appropriate NetSuite permissions for bank matching, statement reconciliation, account records, and transaction review. Confirm that **Multiple Currencies** is enabled and that the relevant subsidiaries, currencies, bank accounts, and accounting periods are configured.
- **Source materials:** Collect bank statements, payment reports, transaction references, fee details, and your approved FX accounting policy. Confirm which exports, feeds, or integration interfaces your providers actually support before choosing an import method.
- **The gotcha:** A payout instruction is not proof of a bank debit or recipient credit. Define which event represents settled cash, retain instruction and settlement dates separately, and confirm the statement account and currency before importing anything.

Assign an owner to unresolved exceptions before setup begins. Otherwise, automated matching simply moves unresolved accounting questions into a different queue.

## Account and source mapping

### Establish the reconciliation boundary

1. List each statement account with its legal entity, currency, corresponding NetSuite bank account, and source of statement data. Keep account identifiers in a controlled mapping register rather than relying on similar account names.
2. Separate the bank account currency from the subsidiary's base currency. Reconcile statement activity in the bank account currency; assess base-currency accounting separately.
3. Map settlement, processing, and return events to the records that explain them. Distinguish a bank debit from a payout instruction and a fee from the principal payment.
4. Document clearing-account treatment where a payment passes through an intermediate balance. Name the owner responsible for clearing residual balances and explain what evidence resolves each balance.

**Expected result:** Every statement line has an identifiable destination account and a defined source of supporting evidence. No payment event becomes a cash posting merely because its status changed.

For a 2026 rollout, start with **1 bank account** and expand only after the full process works. This is a deployment recommendation, not a NetSuite restriction.

### Choose the data handoff

Both approaches below require account mapping and validation. Choose based on the interfaces your actual systems support, not an assumed connector.

**Controlled file import**

- Best for: Teams validating mappings before automation
- Advantage: You can inspect the source file and retain the approved import artifact
- Limitation: Requires a repeatable preparation and review process

**Supported feed or integration**

- Best for: Teams with validated connectivity and repeatable transaction flows
- Advantage: Reduces repeated file handling
- Limitation: Requires monitoring, duplicate prevention, and recovery controls

**Use a controlled file import until the mapping is proven.** A supported integration is the next step, not a substitute for defining accounting rules.

## Statement intake and matching rules

### Prepare the statement data

1. Preserve the original bank statement or downloaded file unchanged. Perform transformations in a separate working copy and record the source account, statement period, and import batch reference.
2. Map the source fields to the requirements of your configured NetSuite import method. Include transaction date, amount, currency, account identification, and transaction reference wherever the source supplies them.
3. Normalize debit and credit signs deliberately. Check that withdrawals and deposits retain the correct direction after transformation; do not infer direction from descriptive text alone.
4. Define **2 control totals** for each import: total debits and total credits. Compare them with the source statement before accepting the batch, and check opening and closing balances where supplied.

**Expected result:** Your import represents the original statement without changing transaction direction, currency, or account ownership.

A payment report and a bank statement can describe different parts of the same movement. Retain both, but do not load both as independent bank activity unless your design explicitly requires that treatment.

### Review matching in NetSuite

1. Open **Transactions > Bank > Match Bank Data** with the appropriate role. Select the relevant account and review its imported bank activity against the account transactions.
2. Review matching rules before applying them broadly. Prefer stable transaction references supported by the source data; use amount and date as additional checks rather than assuming they uniquely identify a payment.
3. Inspect proposed matches involving repeated amounts, grouped settlements, or incomplete references. Review the underlying ledger transactions before accepting the match.
4. Route unmatched activity into a controlled exception queue. Record the reason, supporting evidence, assigned owner, and required action instead of creating an unexplained balancing entry.

**Expected result:** Accepted matches connect identifiable bank activity to the correct accounting records, while unresolved items remain visible.

**A matching rule should explain a relationship, not conceal a difference.** Equal amounts alone are weak evidence when several payments share the same value.

## Settlement and FX exception controls

A bank account can reconcile while FX accounting remains incomplete. Conversely, a base-currency adjustment does not prove that a payment settled. Use the following sequence to keep these questions separate.

1. **Cash evidence:** Confirm the bank account, currency, direction, and settled amount against the statement.
2. **Payment linkage:** Connect the bank activity to its invoice, payment, transfer, or clearing record using the available references.
3. **Difference review:** Classify unmatched amounts as timing, fees, conversion differences, missing postings, duplicates, or returns.
4. **FX review:** Apply your accounting policy to realized exchange differences and period-end revaluation, separately from statement matching.

*Establish the cash movement before deciding how to account for exchange differences.*

For each exception, identify whether the discrepancy exists in the account currency, the base currency, or both. That distinction determines whether you are investigating missing cash activity or an accounting translation issue.

### Resolve differences without forcing a match

1. Obtain evidence for fees rather than assigning every short settlement to FX. Check whether the fee appears as a separate debit or is deducted from the payment amount.
2. For conversions, retain the amounts and currencies on both sides, the executed conversion details supplied by the provider, and the corresponding accounting records.
3. Investigate outstanding clearing balances against actual settlement evidence. Do not clear them merely because the payment instruction is marked complete.
4. Review proposed adjustments under your normal approval controls. Use the correct accounting period and document the reason for any correction.

**Expected result:** Every resolved difference has an accounting explanation and supporting evidence. Unresolved items stay open rather than disappearing into a general adjustment.

For Infinite multicurrency accounts, confirm which statement and payment-report fields are supplied before building this mapping. The platform's payment-routing scope does not establish a NetSuite connector, export schema, or synchronization schedule.

## Statement approval and close controls

1. Open **Transactions > Bank > Reconcile Account Statement** and select the relevant account. Use the actual statement date and closing balance from the source statement.
2. Review the matched and cleared transactions for the statement period. Check outstanding payments and deposits individually, especially transactions near the period boundary.
3. Investigate the reconciliation difference before completing approval. An unexplained journal entry is not a substitute for finding a missing import, duplicate posting, or incorrect transaction date.
4. Retain the reconciliation, statement, exception log, and approval evidence together. Complete the separate period-end FX review under your accounting policy and applicable period controls.

**Expected result:** The statement reconciliation explains the bank balance and outstanding items, while the close file separately supports FX accounting.

Before expanding the 2026 workflow, run **3 test cases**: a straightforward settlement, a fee-bearing settlement, and a returned payment. These are recommended acceptance tests, not claims about system performance. Each should produce traceable cash evidence, correct ledger treatment, and an explainable reconciliation outcome.

## Reconcile again whenever settlement data changes

An adjacent workflow handles updated payment information without repeating the entire bank import. Use it when a payment moves from pending to settled, a return arrives, or additional references become available.

1. Identify the existing payment using its persistent reference. Treat an updated status as an update to evidence, not an instruction to create another cash transaction.
2. Check whether the bank statement contains a new movement. A returned payment requires review of the return activity; a changed description alone does not establish new cash.
3. Refresh the exception record and review any affected match. Preserve the original evidence and record why the reconciliation decision changed.
4. If the period is closed, follow the approved correction process. Do not silently rewrite previously approved accounting records.

**Expected result:** Later information improves the audit trail without duplicating transactions.

When payout events originate from different rails, document their identifiers and settlement evidence separately. The [SWIFT cross-border wire payout guide](https://infinite.net/learn/insights/how-to-connect-infinite-to-swift-for-cross-border-wire-payouts) provides related workflow context; validate the actual reporting fields before mapping them into NetSuite.

## Troubleshooting

### Imported activity lands in the wrong account

**Fix the account mapping before matching.** Compare the statement account identifier, currency, and entity with the destination record. Follow the supported correction process for the import method rather than compensating with transfers that did not occur.

### A payment appears twice

Compare source references, import batches, and actual statement lines. If an import was repeated, correct the duplicate through the supported process; if the ledger contains duplicate postings, investigate those separately. Never delete genuine bank activity simply because the amounts repeat.

### The bank debit differs from the invoice amount

Check fees, conversion records, partial payments, and grouped settlements. Establish the cause before choosing a matching relationship or adjustment, and preserve the connection to the underlying invoice.

### The reconciliation balances but clearing does not

Review unsettled transfers, missing settlement postings, returns, and misapplied references in the clearing account. A balanced bank reconciliation does not prove every intermediate account is correct. Assign each remaining balance an owner and supporting explanation.

### Cash matches but base-currency balances differ

Review transaction rates, settlement accounting, and period-end revaluation separately. Do not alter a correct statement-currency match merely to eliminate a base-currency accounting difference.

## Customize your workflow

For your next 2026 rollout, expand by account and entity rather than enabling every source simultaneously. Reuse approved mappings, but validate each source's sign convention, references, currencies, and date semantics independently.

**Infinite multicurrency accounts and cross-border payment routing belong in the source-data design, not in an assumed integration diagram.** Confirm reporting access, available identifiers, and settlement evidence before assigning automation work. The benefit is access to the stated account and routing capabilities; the limitation for this guide is that no native NetSuite connection is established.

Add operational controls around failed imports, changed mappings, and unresolved exceptions. Keep payment initiation permissions separate from reconciliation approval wherever your control design requires that separation.

## FAQ

**What's the best way to set up NetSuite multicurrency reconciliation?**

Start with currency-specific account mapping, validated statement imports, and separate controls for cash matching and FX accounting. Prove the process on an initial account before expanding automation.

**Does Infinite connect directly to NetSuite?**

A native Infinite-to-NetSuite connection is not established in this guide. Confirm supported interfaces, reporting access, and field mappings before designing the data handoff.

**Should I reconcile in the bank currency or the base currency?**

Reconcile statement activity in the bank account currency. Review the corresponding base-currency accounting and FX adjustments separately.

**Can I match a payment before it settles?**

A payment instruction alone is not evidence of settled bank activity. Keep pending payments visible, but use statement evidence to establish the cash movement.

**Why doesn't the bank debit equal the invoice amount?**

Investigate fees, currency conversion, partial payments, and grouped settlements before adjusting the books. The correct treatment depends on the documented cause of the difference.

**Is file import better than an automated feed?**

Controlled file import is better for proving an unvalidated mapping. A supported automated feed reduces repeated handling but still requires monitoring, duplicate prevention, and reconciliation review.

**What should I check before approving the 2026 reconciliation?**

Check the statement balance, accepted matches, outstanding items, and unresolved differences. Retain approval evidence and complete the separate period-end FX review.

## One last thing

**A perfectly balanced reconciliation can still contain the wrong matches.** Before signing off, inspect repeated-value payments and transactions with weak references; a zero difference proves arithmetic agreement, not that each payment reached the correct accounting record.

## Related guides

- [Multicurrency accounts for remote-first companies](https://infinite.net/learn/insights/multicurrency-accounts-for-remote-first-companies-complete-guide)
- [Treasury management for venture-backed startups](https://infinite.net/learn/insights/treasury-management-for-venture-backed-startups-complete-guide)
- [Payment orchestration for global payroll providers](https://infinite.net/learn/insights/payment-orchestration-for-global-payroll-providers-complete-guide)

Last updated October 16, 2026