web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Unanswered

Exchange rate gain does not exist" on EUR vendor payment — all FX/auto accounts configured

(0) ShareShare
ReportReport
Posted on by 25

Environment: Dynamics 365 Finance & Operations, version 10.0.48. Single legal entity "TM". Accounting currency MXN, reporting currency also MXN (identical). Accounting-currency exchange rate type = REGULATORIO; reporting-currency exchange rate type is blank.

Scenario: I'm posting a Vendor payment journal (Accounts payable > Payments) with a single line — vendor account, debit 100.00 EUR, offset account type = Bank. On validate/post the journal cancels with:

  • "The account number for the transaction type Exchange rate gain does not exist." (ES: "El número de cuenta para el tipo de transacción Ganancias por tipo de cambio no existe")

  • The message appears twice, each preceded by "Posted from company account tm"

  • Followed by "The posting has been cancelled"

The interesting part is that the message fires twice for a single-line payment, and the reporting currency equals the accounting currency (both MXN), so I wouldn't expect a reporting-currency conversion leg.

What I've already verified and ruled out:

  1. Currency revaluation accounts (General ledger > Currencies): EUR row for company TM has all four accounts populated — realized gain, realized loss, unrealized gain, unrealized loss.

  2. Ledger page > Accounts for currency revaluation FastTab: same four accounts populated for TM (the fallback layer).

  3. Accounts for automatic transactions (General ledger > Posting setup): the "Exchange rate gain" (ExchRateGain) and "Exchange rate loss" posting types are present and now point to valid postable detail accounts (I initially had them on a non-postable total account and corrected that — no change, still errors).

  4. Account structure: the target gain/loss main accounts post cleanly through a manual General journal line, so they're active and pass the active account structure.

  5. Bank account currency: I reproduced the identical error paying from both an MXN-denominated bank account and a EUR-denominated bank account. Same error both ways, so it's not the bank leg.

  6. Reporting currency = accounting currency, so no reporting-currency revaluation setup should be in play.

My question: with the currency revaluation accounts, Ledger page, and Accounts for automatic transactions (Exchange rate gain/loss) all populated and confirmed postable, where else does F&O resolve the ExchRateGain posting type during a vendor payment settlement? What would make "Exchange rate gain does not exist" fire twice on a single EUR line when the mapped account is valid and postable?

Things I suspect but haven't confirmed: (a) whether EUR↔MXN under the REGULATORIO type is a direct rate or triangulates through a bridge/pivot currency, which might spin off an extra exchange-difference leg; (b) whether the blank reporting-currency exchange rate type is triggering a second resolution path even though both currencies are MXN. Any pointers on either — or on other hidden account resolutions for this posting type — would be appreciated. Happy to share screenshots of any setup page.

Evidence 2.png
Evidence 1.png
Categories:
I have the same question (0)
  • SajeedMullaji Profile Picture
    61 on at

    The double firing on a single payment line points to two distinct settlement calculation passes running independently within the subledger-to-GL engine.
     

    The first pass handles the realized gain or loss from settling the EUR invoice — calculating the variance between the invoice date exchange rate and the payment date exchange rate via VendSettlement.
     

    The second pass is triggered by your blank Reporting Currency Exchange Rate Type. Even though your reporting currency equals your accounting currency (both MXN), when a foreign currency transaction (EUR) is settled, D365 F&O still attempts to run a secondary conversion pass for the reporting currency layer. With the exchange rate type field blank on the Ledger form, the secondary resolution path cannot complete and queries the automatic transaction engine for ExchRateGain a second time — producing the duplicate error.
     

    The most likely fix: populate the Reporting Currency Exchange Rate Type field on General Ledger → Ledger → Reporting Currency tab with your REGULATORIO type or an equivalent valid rate type. This closes the secondary conversion pass cleanly.
     

    Two additional things to verify: confirm the EUR row under General Ledger → Currencies → Currency Revaluation Accounts has all four accounts mapped specifically for EUR in company TM — not just at the Ledger fallback level. Also check that the main accounts mapped in Accounts for Automatic Transactions for ExchRateGain are included in the active account structure for the current posting date and are not suspended.
     

    The double message is a strong indicator of the blank reporting currency exchange rate type creating a second resolution loop — address that first.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the July Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 265 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 261 Super User 2026 Season 2

#3
Subra Profile Picture

Subra 229 Super User 2026 Season 2

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans