Stefani Kostadinova

Our client is having a business requirement to have end dates which some are 999 years in length.

There is currently a limit on the date to field to only allow up to 31/12/2154.

Their business process uses the dates from the Leases on the buildings they handle for reporting purposes and since there is a limit on the End date, the reports cannot reflect correctly the information, which interferes with the normal process.

We would like to ask for your vote for this Idea so we can show to the Product Team this extension is needed for the normal daily business of the client.

Start and End date are hardcoded into the system and we couldn't achieve this with customization, so we require help from Microsoft.

Hello,

We would like to ask for additional description to be added for Feature 'Date of VAT register'.

Our client faced a scenario where Pending Vendor Invoice Sales Tax combination was not valid making it 0%. If toggle 'Check sales tax code' is not enabled (General Ledger parameter > Sales tax tab) system will not inform the user that the sales tax combination is wrong.

'Date of VAT register' date field is populated by the user, but if sales tax combination is wrong system automatically deletes it during Posting, which is confusing for the users if they do not know that Tax combo they used is wrong. There are no other warning or system notifications that can point to the user what was the mistake.

We agreed that the way to avoid this is to enable 'Check sales tax code' to Warning in GL Parameters, but we would like the description of the Feature 'Date of VAT register' to include this as a warning: that if the sales tax combination is not valid, 'Date of VAT' field will be removed during posting as there is no Sales Tax on the transaction that will trigger the table.

This will avoid user confusion and will present good practice for all future clients that will use it.