Dynamics 365 Business Central – Dimension set to “No Code” on GL Code but a value still posts for a exchange gain\loss adjustment

I came across an interesting situation today that I thought was worth documenting to see if there’s any known reason for this behaviour or if I’ve misunderstood something.

I’m unsure if this is a software issue, or by design, however I noticed that even though I’d set the dimension value posting to “No Code” on a GL code, a value was still posting for the dimension in a certain scenario.

The scenario is outlined below but in short the G/L entries affected were exchange gain and loss postings that were automatically created after applying a foreign currency invoice to a foreign currency payment.

The G/L account in question is the exchange gains\losses account. As you see I’ve specified this shouldn’t have any analysis to the “CUSTOMERGROUP” dimension code.

I then posted an Invoice and Payment at different exchange rates and analysed both to the Dimension Code “CUSTOMERGROUP”. (I used different value codes for each transaction as part of the test)

Then I applied the payment to the invoice to force an exchange gain\loss postings as per below.

When posting the application I expected an error however to my surprise this worked, and when I check the G/L entries the GL code 31900 has dimension code analysis posted to “CUSTOMERGROUP”. (its taken from the Payment as I used the dimension value code “MEDIUM” on the payment)

To confirm I’d set this up correctly I tried posting a standard journal to the GL code and I correctly received the error below:

While I appreciate its unlikely the system would ever be setup like this its interesting that the rule of “No Code” appears to have been bypassed in this particular scenario.

It would be interesting to know if there’s any reason for this?

Thanks for reading!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s