Improve ledger settlement - Settlement in transactional currency
The advanced settlement function for General ledger allows to settle transactions based on accounting currency. This design has a couple of disadvantages when it comes to settlement of sales and payment transaction in another currency than accounting currency. Preconditions. Accounting currency ...
Financial dimensions on transaction grids
Financial dimensions are visible only in the specific tab. Should be great, as in Trial Balance, to see and filter financial dimension on transaction grid, for example on Customer / Vendor / Ledger / Asset transaction. Exporting data with Excel add-in, this functional is already available for t...
Allocation rule - destination posting - keep financial dimension from source
In the ledger allocation rule, the "Destination" form does not allow to keep the financial dimension (those not allocated) according to the original value.
If you want to allocate dimension 1, you need to even though define each value of dimension 2 for destination posting. This is not ...
Thank you for your feedback. This is a great suggestion! We will consider this in our roadmap.
Sincerely,
Kristi Weekley
PM, Microsoft
Be able to change the names of the custom posting layers
7 additional posting layers have been added in Dynamics 365 for Operations - I would like to suggest that the names of these additional posting layers can be changed to reflect what the individual posting layer is used for (preferable with the ability to provide language specific descriptions)...
Thank you for your feedback. This is a great suggestion! We will consider this in our roadmap.
Sincerely,
Kristi Weekley
PM, Microsoft
Enable "Partial ledger settlements" should be possible even if cross-year settlements exist in closed fiscal years.
When trying to activate the Partial ledger settlement option, the following message appears:
You have cross-year ledger settlements. All cross-year ledger settlements must be reversed to enable partial settlements....
IFRS 18 - Categorize Profit & Loss transactions into 5 groups
IFRS 18 will be effective 01/01/2027 in the EU.
It includes legal requirements to categorize Profit & Loss transactions into 5 groups: Operating
Allocation Terms and Budget Control
Allocation terms (defined against the main account) are a great feature, as they post in real time with the original transaction. However, when using budget control, they don't work in all areas of the system. For example, I've found that while they work for sales order posting, they don't work w...
Enable using different exchange rate providers when same currency is used for accounting and reporting
Currently, when reporting currency is the same as accounting currency, selecting exchange type is disabled for reporting currency. Since the amount in reporting currency is not longer calculated from accounting amount, but from transaction amount, I do not see the need for that. For local acco...
Ledger Allocation Rules - Allow additional account types
Hi,
Ledger allocation rules can currently be used for allocating amounts between ledger accounts.
Many companies require a similar to allocate amounts from ledger accounts to projects, vendors, customer for multiple reasons (Example: indirect cost allocation, interest calculation...
Thank you for your feedback. This is a great suggestion! We will consider this in our roadmap.
Sincerely,
Kristi Weekley
PM, Microsoft
FutureFiscal period should be open to post Accrual
Description of problem: When an accrual entry is created where more than one fiscal year is involved, and the future fiscal year is not open then system does not allow to post those entries and gives error. Opening future period in advance is a risk from customer's perspective Error message: P...
Administrator
With the introduction of the GL parameter "Enable post currency realized gain/loss for ledger settlements", the matching functionality was changed to match on the transaction currency. This was required in order to determine if a gain or loss should be posted.
The feature was originally introduced on 10.0.38 in Feature management, but was later moved to a GL parameter.