Tsvetan Atanasov Mr

Fixed assets lending works really well and it would be great if this can be automatically linked through HR Loaned Equipment. Perhaps there can be Yes/No parameter in Fixed Assets parameters to enable this. Fixed Assets will be the source and HR Loaned Equipment will be auto-populated. Then workers can see the loaned equipment via the self-service.

Thanks

Some clients require the T&A timesheet functionality not to be dependent on PMA configuration. Essentally some workers want to be able to submit overtime manually as they do not clock-in or clock-out. This should be done on demand via the HR ESS. Currently this requires PMA internal projects to be configured. I believe it would be great if this dependency is removed. Timesheet approval will be still based on the normal T&A workflows, but now approval notifications should also appear in ESS/MSS.

There seems to be a significant GAP in the Credit and collections automation process. Microsoft designed the product to look into only the oldest/leading invoice per customer and then apply the collection automation process only against this single invoice. Hence the suggestion to enhance this logic so the collection automation process is run against every single outstanding invoice against each customer per LE. Based on this then you can assign an dunning letter and/or activity per outstanding invoice as long as it's overdue.

The enhancement will BE enabled/disabled via Yes/No toggle per each LE located in the Sales ledger parameters > Collection process automation > General 

Toggle = Yes - enhanced logic to include all outstanding invoice for each customer in the LE.

Toggle = No - revert to standard logic for leading/oldest invoice per customer in each LE.

Currently, the Swiss Tax MTD and ER Reporting seems to have a couple of major drawbacks:

1. Whenever the VAT code rate changes a new VAT rate code is required to be mapped to the ER VAT Declaration Excel (CH) or XML. This is not necessary as we have out-of-the-box functionality to monitor VAT rate changes by from and to dates in the Tax module.
2. VAT codes cannot be shared between Accounts Receivable and Accounts Payable transactions - for example if you may have a tax code EXEMPT that could be used in AR and AP Tax transactions and hence it will be mapped as Transaction classifier:

• SaleExempt
• SalesExemptCreditNote
• PurchaseExempt
• PurchaseExemptCreditNote

ER Report needs to support this out of the box and know if this is input or output VAT based on posting profiles/ledgers. The

workaround is to create individual tax codes for each ledger which is not acceptable.

Please could you reconsider both of the above points?

Thanks in advance