Skip to main content

Vote (0) Share
's profile image

on

Comments (0)
's profile image Profile Picture

Beth Jacques on 13 May 2025 22:10:32

RE:

Is it possible to see when this feature will be rolled out?

's profile image Profile Picture

Rhonda InFlorida on 13 May 2025 17:56:33

RE:

It is not available for D365 Customer Service either. Overall, Dataverse doesn't have OOTB analytics available.

's profile image Profile Picture

Henrik Jaeger on 13 May 2025 17:54:02

RE:

I am trying to understand the business scenario requiring automatic posting of penny difference. I assume these penny differences are in accounting currency (if they are in reporting currency, check out "Enable post currency realized gains/losses for ledger settlements" in GL parameters). For my understanding, what kind of ledger transactions are settled, where you need to automatically post a penny difference in accounting currency? In an AR and AP settlement scenario, it makes sense to me as payment may differ slightly from the invoice, but I would like to understand any scenarios outside of AR/AP. Thanks!

's profile image Profile Picture

Rhonda InFlorida on 13 May 2025 17:52:49

RE:

I hadn't noticed this, how odd! I upvoted.

's profile image Profile Picture

Rhonda InFlorida on 13 May 2025 17:46:21

RE:

It was a little hard to follow your write up but I voted for your idea. It is related to the need for a Persistent link method to overcome the challenge of using a GUID at the version level.(Ironically, I can add the link to my idea here) Please search - Persistent Knowledge Article link to latest published version

's profile image Profile Picture

Henrik Jaeger on 13 May 2025 17:39:36

RE:

In the General ledger parameters, you most likely have "Delete existing year-end entries when re-closing the year" enabled - this means that when you re-close a fiscal year, the original opening transactions will be deleted...but it is not possible to delete an opening balance if the transaction has been settled (as you have experienced). Instead, if you disable "Delete existing year-end entries when re-closing the year", only the differences between the previous and current year-end close will be processed as part of the re-close of the fiscal year, and therefore none of the previous opening transactions will be (or need to be) deleted. Keep in mind though that there are scenarios where this (also called "delta close") is not supported - e.g. if you change the opening account in your Chart of Accounts, change how dimensions are transferred (basically any setting int eh year end close template)

's profile image Profile Picture

Henrik Jaeger on 13 May 2025 17:31:00

RE:

I know this Idea was posted more than a year ago, but I wanted to comment that when I run a Year-end close in D365FO v10.0.43 with Advanced awareness options enabled and keep details, then the Financial tag details are copied to the detailed opening transactions created

's profile image Profile Picture

Henrik Jaeger on 13 May 2025 17:23:41

RE:

In my opinion, the partial ledger settlement is there to support the "subledger to ledger auto settlement" that can be enabled in the GL parameters - this will automatically partially settle ledger transactions based on the Customer/Vendor settlements, though not by using Process Automation for Ledger Settlement. That said, what is the business requirement you have that requires automatic partial ledge settlement? I would like to understand this, as I am concerned that having Process Automation for Ledger Settlement perform partial settlements end up being the Ledger equivalent to the automatic settlement that can be enabled in the AR/AP parameter - where it is always settled against the oldest balance. In that case, I am not sure I see the purpose of performing ledger settlement, but I may be missing aspects of this, so I encourage you to share the specific business requirement related to this. Thanks!

's profile image Profile Picture

Henrik Jaeger on 13 May 2025 16:44:26

RE:

I am not sure, I understand the improvement asked for - so, I will try to clarify:If the "Post foreign currency realized gains/losses for ledger settlement" is enabled in the GL parameters, D365FO will post a currency gain/loss transaction when settling two ledger transactions that have balancing (debit/credit) accounting currency, but where reporting currency does not balance (this can happen due to exchange rate differences between the accounting currency and the reporting currency on the days of the two ledger transactions being settled) - for example (accounting currency is USD and reporting currency in EUR):Debit 1st May 2025 USD 1000.00 EUR 885.21Credit 7th May 2025 USD 1000.00 EUR 886.33In the above example, a currency gain will be posted, when these two transactions are settled with each other. This currency gain is posted against the Main account of the transactions being settled and offset to the account set up in Accounts for currency revaluation (under General ledger -> Ledger setup -> Ledger)D365FO will not use the penny difference configuration in the General ledger parameters, as this is not a penny difference, it is a currency gain/loss, and therefore it uses the Accounts for currency revaluation.It is correct that if the above mentioned "Post foreign currency realized gains/losses for ledger settlement" is not enabled, and the two transactions from the example above are settled with each other, then you will most likely receive an error when performing the Year-end close, as you describe. Therefore, unless you want to manage the currency gain/loss in reporting currency manually (=post them using the Reporting currency adjustment journals, and include these adjustments in ledger settlements), the recommendation is to enable "Post foreign currency realized gains/losses for ledger settlement"

's profile image Profile Picture

Beth Jacques on 13 May 2025 15:24:56

RE:

This would save us a TREMENDOUS amount of time. To have social media icons built in and be able to customize the color would be amazing. Right now we have to create all of these in our brand colors, upload, create as content blocks, update links, and then save.