Contact Info
What should an ERP for multi-currency accounting handle?
An ERP for multi-currency accounting should record each transaction in its original currency and your base currency, apply the right exchange rate on the right date, calculate realized gains and losses on payment and revalue open balances at period-end. It should also report clearly in more than one currency, so finance does not rebuild the numbers in a spreadsheet every month.
Last reviewed by Vikas Saroj
Once you buy, sell or hold bank accounts in more than one currency, accounting gets harder fast. Rates change between invoice and payment, bank charges appear in a different currency from the invoice, and open balances need revaluing at month-end. Many businesses handle this with manual journals and a currency spreadsheet that only one person understands.
An ERP for multi-currency accounting can take most of that work away, but the setup decisions matter: which rate source to use, when rates are applied, how gains and losses are posted and which balances are revalued.
I help finance teams make those decisions and test them before they become a month-end problem.
Multi-currency issues are rarely about whether the ERP supports currencies. They are about how it is set up and used.
A written policy covering base currency, reporting currency, rate source, rate timing and rounding, agreed with finance and auditors before anyone configures the system or migrates a single balance.
Process maps for foreign sales, purchases, advances, partial payments and refunds, showing which rate applies at each step and where differences should post in the ledger.
Rules for revaluing open receivables, payables and foreign bank balances at period-end, including which accounts are revalued, how reversals work and what the auditors expect to see.
Design for foreign currency bank accounts, cross-currency payments, bank charges and reconciliation, so the bank statement and the ledger agree every month without manual adjustments or suspense entries.
Decisions on foreign currency price lists, landed costs on imported goods and how purchase currency affects inventory valuation, cost of sales and margin reporting by product and customer.
Scenario tests on shortlisted platforms: invoice in one currency, pay in another, revalue, reverse and report. Gaps found here are cheap; gaps found at year-end are not.
Agree the currency rules
Prove the rules in the system
Make month-end routine
Multi-currency problems are easy to live with until month-end, when they all arrive at once. The usual symptoms:
These issues compound as the business adds currencies, bank accounts and countries. An ERP for multi-currency accounting can automate most of this, but only when the underlying rules are clear.
When finance teams tell me their system cannot handle currencies, the cause is usually one of these:
Only the last cause needs new software. The others need a decision and a proper configuration. That distinction matters: replacing a system because of a setup problem just moves the problem. I check which causes apply through a focused gap analysis of your currency scenarios before recommending anything bigger.
Depending on the root causes, the fix can be small or structural:
| Option | When it fits |
|---|---|
| Policy and process change | The system supports currencies, but rates, timing and ownership are not defined. A written currency policy and a month-end checklist solve most of it. |
| Reconfiguration | Rate feeds, gain and loss accounts, customer and supplier currencies or revaluation settings are wrong or missing. |
| Reporting layer | Transactions are fine, but management needs group-currency reporting the ERP does not produce well. |
| New or upgraded ERP | The current tool cannot revalue, cannot hold foreign bank accounts or cannot report in more than one currency. |
If you also run several legal entities, the currency design and the group structure have to be decided together, because consolidation adds currency translation on top of transaction currency. The companion page on ERP for multi-company operations covers that side. Whatever the option, I document the currency rules in the ERP solution design so the implementer configures your policy, not their default.
The mainstream mid-market platforms all handle foreign currency transactions. The differences show up in revaluation, bank handling, rate automation and reporting, and in how much configuration is needed to get them right:
Fit also depends on your sector. Trading companies importing in one currency and selling in another, logistics firms billing international customers and ecommerce businesses selling across borders each stress different parts of the currency setup. I test those exact scenarios before recommending a platform.
The effort of setting up an ERP for multi-currency accounting depends on:
A realistic timeline runs in phases. First, inventory currencies, accounts and payment patterns, and agree the currency policy with finance and, ideally, the auditors. Second, configure and test the core scenarios: foreign invoice, payment at a different rate, partial payment, bank charge and revaluation. Third, migrate open items with their original currency values, which is where many projects slip, so I plan it with the data migration work. Finally, run the first close in the new system with a checklist and a review, and adjust before it becomes routine.
Currency problems are worth fixing before they reach year-end. The first step is a short review of how currencies flow through your business today and how your current system handles them.
To start, I usually ask for:
From that I can tell you whether you have a setup problem, a process problem or a system limitation, and what the lightest fix looks like. If a new ERP is the answer, the currency rules become part of your requirements, and every shortlisted vendor is tested against them.
As an independent consultant, I am not tied to any platform, so I can tell you plainly when your current system is capable and just needs configuring properly. Contact me to review your multi-currency setup.
Tell me about your business and current systems. I’ll suggest the most sensible first step.
Book a Consultation
Not sure which ERP you need?
Share your business requirements with me and I will help you understand the right process, architecture and platform before implementation.
A realized gain or loss arises when a foreign currency invoice is paid at a different rate from the one used when it was recorded. An unrealized gain or loss arises when open balances are revalued at period-end at the current rate. An ERP should post both automatically to separate accounts, with the unrealized entry reversing in the next period.
That is a policy decision, usually agreed with your auditors: a central bank rate, a commercial feed or a bank's rate, applied on the transaction date. What matters is consistency. The ERP should pull rates from one agreed source and apply them the same way every time, with manual overrides controlled.
Many ERPs support a reporting or additional currency, and others rely on a reporting layer for translation. The right approach depends on whether you need the second currency for management only or for statutory reporting. I check how each shortlisted platform handles this against your actual reporting needs.
Open invoices and bills should migrate with their original currency amount and the rate at which they were recorded, so payments and revaluation work correctly afterwards. Migrating only base currency totals creates differences that surface as soon as the first payment arrives.
Every business is different. Share where you are today and what you want to fix, and I’ll tell you honestly whether and how I can help.
Book a Consultation
Book a consultation to talk through your processes, systems and goals. I’ll reply with practical next steps - no obligation.