Dynamics 365 Finance

Hi, Running the collection letter process allows generating a collection letter document that can be send out to the customer for example by email. This is a great functionality. What is missing though is that one wants to attach the invoices included in the collection letter to this email that goes out to the customer. That is because many customers call once they receive their collection letters and ask for a copy of the invoice(s). Sending them directly with the collection letter alleviates and speeds up this process. Would be great if this could be implemented with one of the next releases. Many thanks, Ludwig

Would be useful if you can change the invoice address on the sales order like the delivery address. Right now a customer has a primary invoice address and when want to you change it for a sales order, you need to change the primary invoice address on the customer and that is a bit complicated. You can manage it via separate invoice accounts, but then you need per invoice address an invoice account and in case of a big customer with multiple invoice addresses you get many accounts for one customer.

Both references are merged in Deliverable Issue:654615

Reference LCS Issue:572499 - The project ID is not copied on the line details while creating a purchase agreement from RFQ.

Reference LCS Issue:654615 - Error “You cannot specify a project after the record has been saved.” when editing project PO created from RFQ

Issue description:

When a PA (Purchase agreement) is created from a RFQ (Request for quotation), there are two possible outcomes:

1. If RFQ header did not have project ID, there is no project information from RFQ lines in PA lines (project details such as project category and activity numbers are copied to the PA lines);
2. If RFQ header has a project ID (and different project numbers in RFQ lines), PA lines have project ID from the header and not from RFQ lines;

As the current product does not accommodate the above scenarios as well, it is severely limiting the ability to purchase agreed services/material through the contract (=PA) and affects the reporting process as well as transparency of the purchasing process.

Having the possibility to make use of such case scenarios from a standard product perspective, would be of great benefit and flexibility.

From July 2021,  B2C sellers dispatching their goods from a single country will no longer be required to register for foreign VAT and complete multiple VAT filings in the countries where they are selling. Instead, they may opt to simply complete and file a new OSS filing alongside their regular domestic VAT return that will list all their pan-EU sales.

This functionality, OSS return is currently not available in Dynamics 365 Finance.

EU 2021 One Stop Shop (OSS) VAT return for e-commerce (avalara.com)

Include Portugal in D365 localization

Currently it is possible to press on "simulate posting" on the overview of the pending vendor invoices. This will validate the posting of the invoice against accounting policies and the accounting structure of the company even before the final posting is performed. This way the AP accountant knows what he/she needs to adapt.

However, as a consultant I see that this is often forgotten at my customers and thus the invoices go through the entire vendor invoice workflow. Only then to notice that the invoice cannot be posted as there are some fields missing. This means that the workflow is stopped and also creates confussion for approvers as this means that the invoice has to be recalled, adjusted and then resubmitted into the workflow.

So a great solution would be if a parameter can be enabled in the AP parameters, allowing that vendor invoices only can be submitted into a workflow if the "simulate posting" validation is without errors. The system should do this validation immediately and automatically at the moment a user presses on "submit".

When Vendor invoice workflow is used to approve a pending vendor invoice and assignment Managerial hierarchy is used, it is only possible to select either Workflow originator or Workflow owner. Workflow originator is equal to the person who submit the invoice for approval. This is often an AP clerk and not the right first approver.

The Idea is to adjust the standard functionality and workflow:

1. When Pending vendor invoice is related to a purchase order, the Orderer from the PO is inserted as Requested approver on the Pending vendor invoice. When the invoice is submitted for approval, the workflow shall submit on behalf of the Requested apporver
2. When pending vendor invoice is not related to a PO (e.g. cost invoice) the AP clerk select the first approver in the field Requested approver on the pending vendor invoice header.

This will make the approval process efficient and skib that the AP clerk must delegate the vendor invoice to the correct first approver (Requested approver.

D365 via OCR process allows to digitalise vendor invoices. But these digital documents should also be archived and have some audit trails, timestamps, ....

In France some legal requirement

Article A102 B-2 - Livre des procédures fiscales - Légifrance (legifrance.gouv.fr)

This may be requested in different countries and solution should be global and not specific

Main points

• should be exact copy of original
• Archiving solution should be documented and subject to internal audit to ensure availability, readability, integrity during the period
• regarding integrity, document should be kept on format PDF or PDF A/3 (ISO 19005-3)to have interoperability of systems and sustainability

also should have either

• stamp from server on certificate with security reference on 1 star
• digital footprint
• electronic signature from certificate with security reference on 1 star
• or any similar security device with certificate from organization listed by French Authorities (Trust-service Status List-TSL).

each file should have a timestamp to have date on different operations done.