Samruddha Medhekar CSS Engineer

As per European laws, employees are entitled to take various types of paid leaves than can extend for more than a year. In the HR Module/Leaves & Absence module of D365 F&O, if we select any employee record and try to submit a leave request, we are unable to enter the leave duration for more than a year. If we try to enter the leave duration for more than a year, the system automatically defaults the End Date to be exactly one year from the Start Date.

This is not a logical as there is no reason to assume why the system should restrict any employee from taking a leave for more than a year.

Path -

In HR module -> Select any employee. For e,g. Alicia Thornber.

Go in the Leaves tab.

Click on View Leave of absence.

Click on Request leave of absence

Select the Start Date to any date.

Try to select the End date to any date that is more than a year from the start date.

System will automatically default the end date to be one year from the start date only.

Customization is not a solution either as due to technical restrictions in the code present for the Leaves.

Because of this restriction, European customers can face legal compliance issues if they are unable to grant sufficient leaves to their employees. Remove the restriction so users can submit the leave request for as long as they like.

Standard Process

Pre-requisites -

1. Make sure to have enough transactions with sales tax amounts
2. Remove the vendor from the tax authority, keep it blank.

Process -

1. Go to Tax module -> Declarations -> Run the declaration "Settle and Post sales tax" for the required settlement period with the Sales Tax Payment version as Original.
2. When the settlement voucher is posted, go to the voucher and reverse it.
3. Now run the Declaration again, with the Sales tax payment version as Latest Corrections.
4. System will throw the error "Original sales tax settlement has already been created for the period."

Expectations -

This error is not logical, because when we reverse the settlement voucher, the settlements become effectively 0 for that period, so running the declaration again should post a new settlement voucher. Once the settlement voucher is posted, the system closes the period for any new settlement. If that voucher is reversed, system should recalculate the settlement for the periods.

This can be further seen when we fetch the Declaration reports (Tax -> Declaration -> Report Sales Tax for Settlement Period), with the option Total Corrections, where the report will now display the original settlement amount and the reversal amount. For e.g., if the tax settlement amount was 1000, and the voucher for it was reversed, then the report will show the value as 2000.

This is a tremendous pain point for customers who might reverse the tax settlement for any reasons and wish to run the settlement again.

The TSG provided for the issue is not feasible at all, as it requires the customer to create dummy settlement periods and run backend queries everytime a settlement is reversed.

Technical details - There is a flag “reversed” in table TaxReportVoucher, there is an enum-value “TaxReversed” on enum “TaxOrigin” etc. The reversal of a tax settlement was implemented but leaves inconsistent data and wrong reports.

If this feature is implemented in upcoming versions, it will help ease the pain of many customers.

Standard Process

Pre-requisites -

1. Make sure to have enough transactions with sales tax amounts
2. Remove the vendor from the tax authority, keep it blank.

Process -

1. Go to Tax module -> Declarations -> Run the declaration "Settle and Post sales tax" for the required settlement period with the Sales Tax Payment version as Original.
2. When the settlement voucher is posted, go to the voucher and reverse it.
3. Now run the Declaration again, with the Sales tax payment version as Latest Corrections.
4. System will throw the error "Original sales tax settlement has already been created for the period."

Expectations -

This error is not logical, because when we reverse the settlement voucher, the settlements become effectively 0 for that period, so running the declaration again should post a new settlement voucher. Once the settlement voucher is posted, the system closes the period for any new settlement. If that voucher is reversed, system should recalculate the settlement for the periods.

This can be further seen when we fetch the Declaration reports (Tax -> Declaration -> Report Sales Tax for Settlement Period), with the option Total Corrections, where the report will now display the original settlement amount and the reversal amount. For e.g., if the tax settlement amount was 1000, and the voucher for it was reversed, then the report will show the value as 2000.

This is a tremendous pain point for customers who might reverse the tax settlement for any reasons and wish to run the settlement again.

The TSG provided for the issue is not feasible at all, as it requires the customer to create dummy settlement periods and run backend queries everytime a settlement is reversed.

Technical details - There is a flag “reversed” in table TaxReportVoucher, there is an enum-value “TaxReversed” on enum “TaxOrigin” etc. The reversal of a tax settlement was implemented but leaves inconsistent data and wrong reports.

If this feature is implemented in upcoming versions, it will help ease the pain of many customers.

Summary of the problem - In the deferral defaults, a main account can be linked against a single customer only. There is no way to link the main account on the basis of STG, which is much simpler and more practical. Due to this, cx will have to link deferral accounts for individual customers, which will be a time consuming and error prone process.

Expectations - A column for STG should be added in the Deferral Defaults to link main accounts based on grouping the STG.

Issue details -

Path – Subscription Billing -> Revenue & Expense Deferrals -> Setup -> Deferral Defaults.

In the column account code, select the grouping as Table. Then link a main account. You will notice that you can only link a main account against individual customer only.

If a user has to link main accounts for all customers, it will be a tedious process. It would be much simpler to have a provision to add a column for STG. Based on this, the system will check the customer selected in the billing schedule, and search for the STG of that customer in the deferral defaults. Once it finds it, it will use the main account linked to it in the Deferrals of the Billing Schedule.

If there are 10 customers linked to a single STG, then it will be easier to link the main account against the STG in the deferral defaults, instead of adding 10 lines for each customer for the same main account.

This requirement is further supported by the fact that there are columns for STG in other modules, for e.g., in Cost Management -> Ledger integration policies setup -> Posting, one can find a column for STG. (Even if it is not there, it can still be activated from the Posting setup for the same).

Hence, consider this idea as crucial from the standpoint of European customers who are missing out on an important feature which can reduce time, efforts and errors.

Issue statement –

In Purchase requisition, the customer selects a procurement category (PC). This PC is linked to Business rules for FA determinations where the threshold amount is 0. They enter the quantity and unit but leave the unit price blank. In the FA tab of Line Details, the Asset group does not get populated. If the user goes to Unit Price field and manually enters a 0, only then it gets populated.

This is an issue because the user cannot manually keep entering the price field every time. If the FA group is not populated, the Purchase request gets processed further to Purchase order and invoice without the FA group, which defeats the purpose of FA acquisition. 

Setup -

 Define a Business Rule for FA determination, link a Procurement category to it and set the Capitalization threshold is 0.

Process -

1. Create a Purchase request.
2. Select the Procurement category and leave the unit price field blank.
3. In the Fixed Asset details tab, the asset group will display blank values.
4. Click on the unit price field and enter a 0 manually and move to the next field.
5. The fixed asset details will be populated with the asset group defined in the business rules.

This is a product defect, and though the obvious work around is to enter a 0 manually, this is not a feasible process and will not work for any purchase request where the number of lines is huge, exceeding 10s or 100s. This defect should be resolved by linking the asset group for those business rules where the cap threshold is 0.

For all employee records, it is critical to attach important documents like passports, driving licenses, etc.

The feature to attach documents for employees exists only for the following path -

HR module -> employees -> Person -> Identification Numbers.

But if we try to access the same through the Employees Self Service -> Edit Personal Details -> Identification numbers, the attachment icon does not exist.

This leads to an inconvenience as the users cannot attach files and have to rely on the HR manager or someone with the permissions to the employees form to attach all documents for every individual employee. This causes time consumption and chances of attaching wrong documents as one person might have to attach individual documents for each employee, rather than every employee doing it for themselves.

Currently, financial reports can be generated only on month end dates. There should be a provision to fetch reports for any date of the month. Not all reports are fetched on a month end basis. Some reports can be fetched for data on a daily basis.

In D365 F&O for HR and Leave & Absence modules, we have the functionality to buy and sell leave requests.

The user can buy a leave or sell a leave from a pre-defined balance. But there is no option to cancel the bought or sold requests. Once the leaves are bought or sold, it's final and the balance changes permanently.

Since there is a functionality to cancel time off/leave requests in the regular leaves, there should be an option to cancel the Bought/Sold Leave requests also.