Close enough is not a financial truth
Actuals supports full multi-currency configuration. Every currency gets its own precision and rounding rules, and the FX conversion is part of the matching, not a step beside it.

It is Friday afternoon, and someone in accounting is looking up an exchange rate from six weeks ago. The order came in euros. The payout landed in dollars. The ERP books in pounds. Somewhere in between, the numbers have to meet, and they never meet exactly.
So the team settles for close enough. But close enough is not a financial truth.
Actuals now supports full multi-currency configuration, built into the platform.
Where the currency gap opens
High-volume digital businesses work across borders by default. Marketplaces collect payments in local currencies and pay out in others. Subscription businesses bill in the customer’s currency and report in one functional currency. Gaming and betting platforms process millions of micro-transactions across dozens of markets every day.
Until now, keeping those books clean meant converting currencies by hand, outside the reconciliation workflow. That led to errors, and to unexplained FX differences piling up as suspense items. It also slowed down the month-end close, because someone had to trace every mismatch back by hand.
Four settings, then it runs
- Set your functional currency. It is the anchor for consolidated reporting and the currency your P&L reflects.
- Add every currency you transact in. There is no limit, and each currency gets its own precision settings.
- Set the rounding rules per currency. Some currencies have no decimal places, others go to four. Actuals handles the precision, so a reconciliation does not fail on a technicality.
- Let Actuals match. From then on, every cross-currency transaction is matched with the same logic.
What happens to the euro order
Take the order from the opening again. The order, the payment, the settlement and the accounting entry are all matched with the same logic. They use the same rates and the same rules. The FX conversion happens automatically, as part of the matching rather than a step beside it.
If there is an FX difference, it shows up as data you can explain, not as a failed reconciliation. Every conversion leaves an audit trail. A one-cent difference no longer turns into a thirty-minute investigation.
What changes at month end
- The close gets faster, because FX differences are visible and explainable instead of buried in a suspense account.
- Audit prep gets cleaner, because every conversion decision can be traced. Auditors get answers, not approximations.
- Manual work drops. Nobody spends Friday afternoon on exchange rates from six weeks ago.
Selling in a new country or currency soon? Look at how many FX differences end up in your suspense account today. That shows how much of your close still runs on close enough. The setup itself is described in the Actuals docs, under currencies.
In practiceNew country, new PSP, new currency. Same close?


