These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Multi-currency Accounting
- Implementation
How a Multi-currency Accounting rollout works
Build the rollout around your reporting calendar and the quality of the data coming from your current systems. Configuration, integrations and acceptance testing are part of implementation. Timing depends on the number of entities, migration history and the work needed to reconcile opening balances.
Map the group
Agree the functional and reporting currencies, ownership and group consolidation unit. Map each entity’s calendar to group reporting periods. Review the chart, monetary-account flags, rate policies and historical equity rates. Assign owners for tax configuration, approval limits, bank controls and the close checklist. Record which local reporting requirements need additional configuration or external specialist review.
Configure roles and masters
Set entity access, approval limits in each person’s limit currency, delegation rules and separation of duties. Load currencies, accounts and entity references in dependency order, followed by periods, rates, bank accounts and contacts. Verify vendor bank details and supported bank formats. Test missing-rate handling and approved rate overrides before loading transactions.
Rehearse the close
Use representative invoices, bills, partial settlements and bank movements. Exercise a receipt awaiting allocation, a returned payment and a corrected application. Reconcile the banks before revaluation, then review postings and consolidation. Check that Delta and reversing revaluation methods clear settlements without counting prior exchange differences twice. Each role rehearses its approvals and exceptions.
Reconcile the migration
Load the approved opening trial balance and imported open documents against a documented cutover schedule. Load imported open items without posting and include their reconciled control balances in the opening journal. Link each item to that journal and its migration batch. Do not post the same balances again when importing the documents. Reconcile original foreign amounts, current carrying values, accumulated revaluation, unapplied cash, assets and intercompany balances to the old ledger before any live posting.
Go live by entity
Launch each entity after its finance owner signs off the rehearsal and reconciled opening balances. Define the reporting bridge for entities still in the old system and prove it before the first group consolidation. Freeze the old ledger at the agreed cutover and retain its evidence for audit access.
Stabilise the process
Review the first close, rate-feed exceptions and bank acknowledgements with the users who handle them. Tune matching rules against reviewed outcomes, verify each additional integration and update the close checklist through change control.
What the customer provides
Name a process owner for each finance area and provide source-system extracts, approved rate history and reconciled trial balances. The team also supplies decisions on posting policies, approval limits, calendars, bank formats and reporting requirements, plus time for migration review and rehearsal.
Changing it afterwards
Use Proto to configure changes on a branch for review before release. Adding an entity or currency requires validated account mappings, rates, permissions and opening balances. A new jurisdiction can also require tax, filing and reporting work; confirm that scope before launch.
Set up Multi-currency Accounting your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.