Requirements · Accounting software
Accounting software requirements for multi-currency books and audit readiness
Last updated 25 October 2026 · 2 sources listed · Reading time about 3 minutes
Short answer
Multi-currency accounting needs a defined base currency, transaction-date exchange rates, revaluation of foreign balances, realized and unrealized gain tracking, and consistent reporting. Audit readiness needs immutable audit logs, period locking, approval workflows, supporting document attachment, and accessible reports reconciling to the ledger. Specify these as testable scenarios and verify the software supports your jurisdiction's reporting framework.
Who this is for: A finance manager of a company trading internationally who must specify what accounting software needs to support foreign currency and external audit.
What to evaluate
Exchange rate management
Rates must be sourced consistently, dated correctly and traceable, since they drive gains, losses and reported balances.
How to check: Ask how rates are loaded, whether manual overrides are logged, and how historical rates are preserved.
Revaluation and gain tracking
Foreign balances such as receivables and cash need periodic revaluation, with realized and unrealized differences separated.
How to check: Run a revaluation on a sample foreign invoice and trace the journal entries.
Foreign currency bank accounts
Holding balances in foreign currency requires reconciliation in that currency and in base currency.
How to check: Reconcile a foreign bank statement and review both currency views.
Audit log integrity
Auditors need to see who created, changed or deleted entries, and logs should not be editable by users.
How to check: Edit a posted entry in a trial and inspect what the log records and who can alter it.
Period locking and approvals
Closed periods must be protected, and payments and journals often need approval.
How to check: Attempt to post into a locked period and test an approval workflow.
Supporting documents
Evidence for transactions should be linked to the entry for sampling during audit.
How to check: Attach a document to a bill and confirm it appears from the ledger drill-down.
Reporting framework support
Statutory reporting may require particular layouts, disclosures or accounting standards.
How to check: Confirm with your auditor which reports and formats they require and test their production.
Comparison
| Requirement | Capability to look for | Common gap |
|---|---|---|
| Foreign currency invoicing | Rate at transaction date and separate currency fields | Single manual rate applied to all items |
| Period-end revaluation | Automated journal with reversal option | Revaluation done outside the system in spreadsheets |
| Audit trail | Read-only log of every change | Logs that omit deleted or edited entries |
| Segregation of duties | Role-based approvals | Everyone can enter and approve payments |
| Auditor access | Read-only auditor role and exportable reports | Audit requests handled by exporting files |
Decision worksheet
Rate up to three options against this guide’s own criteria. It runs in your browser and saves only on this device. It is a thinking aid, not a recommendation.
1. Have you checked each criterion?
0 of 7 criteria checked.
2. Compare options (0 = fails or unknown, 3 = meets it well)
| Criterion | |||
|---|---|---|---|
| Exchange rate management | |||
| Revaluation and gain tracking | |||
| Foreign currency bank accounts | |||
| Audit log integrity | |||
| Period locking and approvals | |||
| Supporting documents | |||
| Reporting framework support | |||
| Total (max 21) | 0 | 0 | 0 |
Questions to ask before you commit
- Which exchange rate sources are supported and can we lock rates after close?
- How does the system calculate and post realized and unrealized differences?
- Can users edit or delete posted entries, and how is that logged?
- How do we provide auditors with read-only access?
- Which reports reconcile subledgers to the general ledger?
- How are attachments stored and retained?
- Is there a limit on currencies, entities or dimensions?
- How does the product support our accounting framework and statutory outputs?
Typical trade-offs
Automated rate feeds versus manual rates
- Upside
- Automation is consistent and quick.
- Downside
- Rate sources may differ from the ones your auditor or tax authority expects.
Strict approval controls versus speed
- Upside
- Controls reduce error and fraud.
- Downside
- They slow routine work and need maintenance.
Keeping documents in the ledger versus in a document store
- Upside
- Linked evidence simplifies audits.
- Downside
- Storage and retention policies may constrain volume.
Common mistakes
- Using a single average rate for all transactions. Define a policy and have the software apply it consistently.
- Revaluing outside the system. Keep journals in the ledger to preserve the audit trail.
- Granting broad edit rights. Restrict who can change posted data and lock closed periods.
- Waiting for auditors to request access. Create an auditor role early and test it.
- Overlooking tax implications of currency gains. Check with a qualified adviser.
Related questions
What is the difference between realized and unrealized currency differences?
A realized difference arises when a foreign currency transaction is settled and the amount received or paid in base currency differs from the amount recorded. An unrealized difference arises when open balances are revalued at period end but remain unsettled. Software should post them to distinct accounts so reports and tax treatment are clear.
What will auditors typically ask the software to show?
They sample transactions and trace them to support, test controls over approvals and access, and review journals, especially manual ones near period end. They also test that closed periods were not altered. Software that provides filtered journal reports, document links and change logs shortens this work.
Can we meet these needs with an entry-level product?
Sometimes, if the volume of foreign transactions is small and controls are managed procedurally. Check the specific features rather than the product tier: rate handling, revaluation, logs and roles. If workarounds rely on spreadsheets, evaluate whether the control risk is acceptable to your auditor.
Which accounting standards does the software need to support?
Software generally records transactions; the framework determines presentation and disclosure. Confirm with your auditor and local regulator which framework applies, then check whether the software provides the required report structures or needs export to a reporting tool.
Sources and further reading
These pages were reachable when we last checked. They informed definitions and rules referred to above; they do not endorse this guide. Where rules differ by country, check the authority for your location.
- IFRS Foundation — IFRS Foundation, retrieved 27 October 2026
- Business guide — U.S. Small Business Administration, retrieved 27 October 2026
Related guides
How to choose · Accounting software
How to choose accounting software for a growing business
Choose accounting software by the work it must carry: invoicing and collections, bills and approvals, bank feeds and reconciliation, inventory or project tracking, tax handling, and reporting your accountant needs. Check how it handles your chart of accounts, user permissions and audit trail, how easily your accountant can collaborate, and how well data exports. Fit to your business model matters more than a long feature list.
Comparison · Accounting software
Accounting software versus spreadsheets for company books
Spreadsheets offer flexibility and low upfront friction, but they leave integrity checks, reconciliation, version control and audit evidence to the user. Accounting software enforces double-entry structure, automates bank matching and tax reports, and logs changes, at the cost of learning and sometimes rigid structure. The switch becomes compelling when errors, handover risk or outside scrutiny begin to cost more than the discipline the software requires.
Problems & fixes · Accounting software
Problems to expect when switching accounting software
Switching accounting software commonly exposes opening balance mismatches, orphaned open invoices and bills, chart of accounts mapping gaps, bank feed reconnection issues, lost attachments and history, and tax code differences. Plan the cutover at a period boundary, reconcile balances to a trial balance, migrate open items rather than all history where practical, and keep the old system accessible for audit and reference.
Requirements · ERP
ERP requirements for multi-entity and multi-country finance
Multi-entity finance needs more than a chart of accounts. Specify intercompany transactions and eliminations, multiple currencies and revaluation, parallel ledgers for different accounting frameworks, local tax and statutory reporting, entity-level security, and consolidation. Define each in terms of a close process you must complete, and verify that local statutory needs are covered by the product or by a supported localization.
Requirements · HR and payroll software
Payroll software requirements for employees in several jurisdictions
Multi-jurisdiction payroll requires software or services that apply the right tax, social contribution, leave and reporting rules for each location, maintain accurate rate tables, handle currency and statutory payslip formats, and produce the filings each authority expects. Specify coverage per place, update responsibility, audit trails and data protection, and confirm with advisers or regulators because rules vary and change.
How to choose · Business operations
How to choose expense management software
Pick expense software by how it handles receipt capture, policy enforcement, approval routing, accounting integration, reimbursement, tax and audit needs, and employee experience. Adoption determines the value, so test with real users. Compare how each tool treats multiple entities, currencies, card feeds and exports, and what happens to your data if you leave.
How to choose · Business operations
How to choose a business bank account
Judge a business account on how it fits your payment flows, not only on its monthly charges. Look at fee structure, payment methods and international capability, integration with accounting software, user permissions, deposit protection, lending relationship potential and service quality. Compare a full month of your expected activity against each fee schedule, and confirm what happens if you outgrow the account.