Dynamics Community Forum Thread Details

Exchange Rate Adjustment Error After Upgrading to Business Central 28.3

Hello All,

When we run Exchange Rate Adjustment, we receive the error shown in the screenshot below.

I then checked the setup and found that:

Revaluation is already disabled on the G/L Account (1-1225) card.
However, the Source Currency Code is set to USD.
This G/L account is being used as the Sales Receivable Account in the Customer Posting Group for the foreign customer category.

I noticed that the Exchange Rate Adjustment posts successfully only if either:

I remove this G/L account from the Customer Posting Group, or
I clear the USD Source Currency Code from the G/L account.

However, neither option is feasible:

We cannot clear the USD Source Currency Code because Business Central validates that the account balance must be zero, and this account currently has a balance.
We also cannot change the Customer Posting Group because this account was specifically created for US Sales Receivables.

I'm wondering if this behaviour is related to the new BC 28.3 version, as my copy sandbox is running on 28.3.

Is there any other approach you would recommend?

Thanks.

Categories:

Dynamics 365 Business Central

For standard setup in BC you wouldn't be using a subledger account also as a revaluation account. The subledger posting group accounts should be only tied to specific master records (customer posting group = just customers).

Any revaluation would be done to the LCY without using the Source Currency feature and instead just use the standard subledger revaluations.

You could change the Source Currency Code field on the G/L Account if you disable validation and update that value using a configuration package or some data editor tool such as this one: Table Data Editor for Business Central - it could have downstream effects but it would let you disable that toggle for now.

For the source currency field on GL Accounts I would only use that in scenarios you have for example an investment account not in a local currency or a GL account that isn't tied to any posting group and needs to be reported in a currency different from the LCY.

As for a full fix, if disabling validation doesn't work you could also try posting an entry to that GL Account to set it as 0$, change the source currency and then reverse that entry that zeroed it out.

Best,

Teagen Boll

Work: Catapult ERP

Social: LinkedIn

Quick Links

Leaderboard > Small and medium business | Business Central, NAV, RMS