-
Add Ability to apply Intercompany Projects in Travel Requisition form
D365 should allow, in Travel Requisition form, to display a list of projects from another companies. The same/similar functionality to the existing one in Expense Report form is required, where the user can change the legal entity and choose an inter-company project if necessary. • Travel requisition form (no intercompany project option) – new functionality needed • Travel expense report form (intercompany project option available) -
Add Ability to apply a specific exchange rate type for AR and AP foreign currency revaluation processes
D365 should allow to apply a specific exchange rate type for Accounts Receivable and Accounts Payable foreign currency revaluation processes. Currently, for AR and AP foreign currency revaluation processes, D365 considers only the exchange rate type setup in the General Ledger module (Ledger form).
-
Add ability to use Mobile App for D365 vendor line level WF approvals
The Mobile App for D365 vendor approvals should support line level WF approvals. Not only header level approvals as in the current design. -
(Polish localization): Improvements required for SAF Bank statements report if the Advanced bank statement reconciliation parameter is being enabled
In the current design of D365, SAF Bank statements XML file does not include detailed transactions settled on bank statements (when Advanced bank statement reconciliation feature is being used). There is a need to include the advanced bank statement reconciliation transactions (from BankDocumentTableView) within SAF Bank statements XML file. -
(POL): Free text invoice correction - link between original invoice and credit note is necessary
When using “Correct invoice” function from free text invoice form in D365, the additional tab “Credit note” (with the original invoice number presented) must be added. This is required by polish regulation to have a link between original invoice and credit note. -
(POL) Quarterly JPK_V7K report is necessary in D365
Based on the latest legal changes (https://www.podatki.gov.pl/jednolity-plik-kontrolny/jpk-vat-z-deklaracja/) there is a need to implement quarterly JPK_V7K report in D365. -
Improvements needed for Standard Audit File - Inventory (JPK_MAG) generation
Customers expect the possibility of generating Standard Audit File - Inventory (JPK_MAG) in a single run, for all warehouses in each legal entity. -
(POL) New feature for the ratio of the structure of VAT for Sales tax receivable required
New improvements in D365 are required, regarding the ratio of the structure of VAT for Sales tax receivable process: • There should the possibility to set separate accounts for non-deductible part of the VAT to be posted • Also, a new feature is needed that will allow to setup sales tax code values and Non-deductible %, based on the “Date of VAT register” from/to date range. At this moment, standard D365 for Poland only allows that setup based on the posting date • Additionally, a new control in “VAT register transactions” periodic process is required. Based on the new feature (mentioned in the previous point), it should not be possible to change “Date of VAT register” if the new date would be included in the “Date of VAT register” from/to date range, with a different sales tax code value or Non-deductible %: -
(ESP): “Date of VAT register” GL parameter should be available globally (including Spain)
There is a need to make available globally “Date of VAT register” option in GL parameters > Sales tax, which allows to do accounting (VAT settlement) by Date of VAT register. This is necessary for Spanish companies to correctly reflect VAT settlement/declaration by “Date of VAT register” in SII official tax report (for sales invoices). -
Improvements needed for changing status of sales document = Fiscal Receipt in D365 FO
In current design of D365 when using "Status change" option on customer Invoice Journal for sales document = “Fiscal receipt”, after adding/changing the data of the original customer to a new/ different one, there is no tax consequences at all. What is required is a new functionality, that will transfer the customer change information into tax transactions related tables as well.