-
Validation tool if the tax payer is active in EU VIES system and/or in National Tax portal.
This is a wide need to check in EU system - VIES or in national tax portal (Poland) Such functionality would need to: validate in government/EU tool if the supplier is an active tax payer (for one selected or group) Check or validate before/after posting if the Vendor/Customer is a active tax payer (receive goods, deliver goods, post invoice) Store the history of checking (in case of tax control) – by adding the screen shoot from tax/ EU portal for a specific date. Create a report which could validate if existing documents (invoices) for specific vendor are OK (status of suppliers is Active) -
Vendor invoice number – the field is too short, there is only 20 signs (digits) available.
It would be nice to extend the Invoice Id to at least 30 length. It's not country specific, but world wide need. Unfortunately, Shorter number (what means wrong number of the invoice) will be reflected in bookings and in SAF-T file (XML files required by the Authority in Poland). Manual workaround exists, to manually correct the SAF-T file before sending to government, but this is not a good approach because still the wrong number is in the system and is not the same like on reports send to tax authority which can effect on penalties as well. From July 2019 there is an addition to the regulations of the information reported in SAF-T files, stating that if information is incorrect there is a charge of 500 PLN for each mistake.
-
Sales order credit note for Poland
In Poland we have a requirment to show on invoice what was before and after credit note. With than in polish legal entity, we are creating credit notes with negative and positive lines for each item. This kind of design require to involve inventory movement which should not be done if there is price change (or discount was granted) only. In such scenario this is only a price credit note without item return. With current design the items are returned to stock and taken back to sales order, but it's not necessary. Customers are using partial numbers and serial numbers with the automatic reservation, so for the retail industry it makes very difficult to accept current design. It would be good to change current design and do not involve inventory/stock in case of sales price correction.
-
Add a feature to disable checking of remmittance address durign settlement
When user try to settle invoice and payment with different remittance address, getting an error: The remittance address on the selected transaction line does not match the remittance address on the selected payment journal line. Change one of the addresses to mark the lines for settlement. We would like to get a possibility to disable this validation. Maybe in next releases it can be taken as a feature which give Companies possibility to decide if it's important to check remittance address or not. -
Duplicates accounts report do not include accounts without transactions and there is no info about occurrence and row code
User would like to make sure that the report does not include duplicates, so mark the check box @report duplicates accounts' on the report definition. Generate the report and export to excel, check the duplicates report and the results. The report shows only account number without occurrence and row code. Next, there is no account if there is no transaction on this account in current period. -
Add localization fields in data entites
Missing fields from Polish/ Eastern Europe localization in the data entities within D365 F&O. Customer cannot prepare the Excel import files or data packages to prepare the golden configuration and the go-live. The implementation includes several legal entities, they need to be able to import the setup and copy it into other legal entities using the data management platform. Missing fields in below data entities: Vendor parameters - Exchange rate date Vendors V2 - VAT date is required Customers V3 – VAT date is required Fixed asset parameters – Depreciation percent level Fixed Asset Book V2 - Percent Basically all localization fields should be there out-of-the-box. -
Configurable hierarchies workflow assignment does not work if the workflow batch jobs processed in context of legal entity other than the buying legal entity
The customer is using configurable hierarchy workflow assignment to process the purchase requisitions approval , the workflow is failing if the workflow batch jobs processed in context of legal entity other than the buying legal entity e.g. the workflow batch job generated from DEMF while the buying legal entity is USMF It was raised under, but rejected to change: https://fix.lcs.dynamics.com/Issue/Details?bugId=506237&dbType=3&qc=d710d6e64a23b245ea72e7988980e318a69040ba64277cbad50ab559a2fb2fd0 -
Possibility to reverse PO-related invoices
Currently there is no option to reverse PO-related invoices even if for non-stocked items or procurement categories. There should be a possibility to reverse transaction connected to purchase orders invoices with non-stocked items/ procurement categories. -
[POL] New report/ feature about delayed/late payments
Since 01.01.2020 Companies need to deliver year report about delayed or late payments with below structure: 1. company (name) and tax identification number; 2. value of cash received in the previous calendar year within: • not exceeding 30 days, • from 31 to 60 days, • from 61 to 120 days, • exceeding 120 days - from the date of issuing the invoice or bill confirming the delivery of goods or the performance of the service; 3. the value of cash provided in the previous calendar year within: • not exceeding 30 days, • from 31 to 60 days, • from 61 to 120 days, • exceeding 120 days - from the date of issuing the invoice or bill confirming the delivery of goods or the performance of the service; 4. value of cash not received in the previous calendar year by the date specified in the contract and the percentage share of these benefits in the total value of cash due to this entity in that year; 5. the value of unfulfilled cash in the previous calendar year by the deadline specified in the contract and the percentage share of these benefits in the total value of cash benefits that the entity is required to perform this year. It was raised by Customers, but rejected to develop under alert: https://support.lcs.dynamics.com/RegulatoryAlertDetails/Index?aid=41417 More details here: https://www.gov.pl/web/rozwoj-praca-technologia/walka-z-zatorami-platniczymi https://tax.kpmg.us/taxnewsflash/taxnewsflash-europe/tnf-poland-tax-treatment-of-bad-debts-and-delayed-or-late-payments-in-commercial-transactions.html Still, we believe that similar requirements exist in different countries, so it would be good to develop it in Dynamics 365 F&O. -
[POL] SAF Bank statements (JPK_WB)
Currently there is no way to run the reports in one run for all Bank accounts. User need to generate this one by one. Expectation is to have an option to generate several xml files for several (all) bank accounts by one click. There should be a multi-select option for Bank accounts in the dialog, but still xml should be done per Bank account.
You’re offline. This is a read only version of the page.
