4.4 Accounting & Reporting Currencies (Dual-Currency Architecture)

4.4 Accounting & Reporting Currencies (Dual-Currency Architecture)

Quick Summary: Multinational enterprises operating in Microsoft Dynamics 365 Finance leverage a native Dual-Currency Architecture that tracks financial values simultaneously in both an Accounting Currency (functional currency) and a Reporting Currency (secondary corporate currency) for every transaction line. At the close of each financial period, organizations execute Foreign Currency Revaluation (General ledger > Periodic tasks > Foreign currency revaluation) to restate foreign-denominated monetary assets and liabilities to current spot exchange rates, recognizing Unrealized Gains and Losses in compliance with IAS 21 and US GAAP ASC 830.

---

1. The Dual-Currency Architecture (Triple-Amount Model)

In Dynamics 365 Finance, every journal entry and subledger voucher stores three discrete currency amounts on every line of the GeneralJournalAccountEntry table:

+-----------------------------------------------------------------------------+
|                     THE TRIPLE-AMOUNT RECORDING MODEL                       |
+-----------------------------------------------------------------------------+
|                                                                             |
|  1. Transaction Amount (AmountCur)                                          |
|     - The original denomination currency of the source document             |
|     - Example: 10,000.00 EUR (Invoice Currency)                             |
|                                                                             |
|  2. Accounting Currency Amount (AmountMST)                                  |
|     - The primary functional currency of the legal entity                   |
|     - Calculated at posting using Default Exchange Rate Type                |
|     - Example: 10,800.00 USD (1 EUR = 1.08 USD)                             |
|                                                                             |
|  3. Reporting Currency Amount (AmountReportingCurrency)                     |
|     - The secondary corporate reporting currency of the legal entity        |
|     - Calculated at posting using Reporting Currency Exchange Rate Type     |
|     - Example: 8,640.00 GBP (1 USD = 0.80 GBP)                              |
+-----------------------------------------------------------------------------+

Core Currency Definitions

Calculation Rules for Reporting Currency Amounts

When a voucher is posted, the reporting currency amount is calculated using one of two deterministic paths based on the Ledger configuration:

• Direct Conversion from Transaction Currency: $\text{Reporting Amount} = \text{Transaction Amount} \times \text{Exchange Rate (Trans } \to \text{ Rep)}$
• Triangulated Conversion via Accounting Currency: $\text{Reporting Amount} = \text{Accounting Amount} \times \text{Exchange Rate (Acct } \to \text{ Rep)}$

[!NOTE] Penny Difference in Reporting Currency Due to fractional rounding between tripartite exchange rate calculations, minute rounding differences (e.g., $0.01) can occur between accounting and reporting currency balancing. Dynamics 365 Finance automatically balances reporting currency entries using the Penny difference in reporting currency account configured in General ledger > Posting setup > Accounts for automatic transactions.

---

2. Configuring the Two Ledger Currencies

Both currencies are set once, on General ledger > Ledger setup > Ledger, and each is paired with its own exchange rate type.

If the reporting currency is left equal to the accounting currency, the reporting amount is simply a copy — there is no separate translation and no separate revaluation.

The Irreversibility Rule

Exam trap: As soon as one transaction has posted in a legal entity, the Accounting currency and Reporting currency fields become read-only. There is no configuration, security role, or period reopening that unlocks them.

Correcting a wrong accounting currency after go-live is not a setup task — it requires a new legal entity and a full data migration. This is why currency selection is a Solution Blueprint decision in the Initiate phase rather than a configuration decision made during Build. On a case study, a requirement to "change the accounting currency of DEMF from EUR to USD" is a trap: the correct answer is always to create a new legal entity, never to edit the Ledger page.

Which Amount Is Used Where

• Subledger balances and statutory statements — accounting currency.
• Consolidation into a parent that uses a different currency — either the reporting currency or a consolidation legal entity with its own accounting currency, depending on the group's design.
• Customer and vendor invoices — the transaction currency prints on the document; the accounting and reporting amounts exist only on the accounting entry.
• Foreign currency revaluation — runs separately for the accounting currency and the reporting currency, because the two can drift at different rates.

Because all three amounts sit on the same GeneralJournalAccountEntry row, Financial Reporting can render a full trial balance in either the accounting or the reporting currency without any translation step at report time.