Dynamics 365 Finance

Currently after posting invoice approval journal is approved in another period then system is not showing the "Invoice number" for the new voucher id lines (Accounting source explorer report), this is creating issue while referring the report of "Accounting source explorer" it needs to be added manually.

When a company within EU sell to a customer who does not have a valid VAT registration, the transactions cannot use intracommunity VAT calculation. Domestic VAT must be calculated instead.

In principle a company must validate that the VAT registration is valid every time the company sell to an EU customer to avoid calculating domestic VAT.

Since this is a manual procedure, this is often not done. Instead we need this to be automated,

The European Commission have create a website where it is possible manually to validate if a VAT registration is valid or not.

Wen site is called "VIES VAT number validation"

Idea: a functionality in D365FO that can be set up to on a daily basis to make that check for all VAT registrations in the Tax exempt number table.

When a credit note is posted and transferred to intrastat, looking at the general tab, the data should be automatically filled in with the correct data of the original invoice (month. correction year, original Intrastat record/original invoice number). We do not have to manually impute the details.

This idea is created by Tax Calculation service product team to understand the market requirements for Microsoft to build formulas (operators such as 'NOT', '*',) in tax group applicability tables to simplify the creation & maintenance of applicability rules.

Please vote for this idea if you need this feature in your

project.

It will be much appreciated if you can post a comment to share

why you need this feature and what the current pain points are in your business

in this area.

Thanks,

Kai

Current Scenario: The generated report achieved by running the Report VAT for a settlement period process in combination with the SPECIAL REPORT is displaying VAT from 'Original’ settled and posted VAT Payment only not from the ‘Total list’. (Total List : Original + Latest Corrections)

Expected Scenario: The generated report achieved by running the Report VAT for a settlement period process in combination with the SPECIAL REPORT should display VAT from all the Settled and posted VAT Payments i.e. the ‘Total list’, not just from the ‘Original’ settled and posted VAT Payment.

Path: Accounts Receivable > Intent letters

In the customer intent letters form the field "Name" is missing. There is only the customer account code.

The name should be included in order to enhance the standard functionality and to align the behaviour to the form on the passive part (vendor intent letters)

Users have the ability to put Vendors and Invoices on hold but if these are already in a Payment Batch and get submitted it causes major issues as it gets processed to bank and paid and then it does not post. Need a warning message either to user placing invoice on hold that the Invoice has been added to a Payment Batch or to Batch owner that an invoice has been changed before it's submitted. It would be great if the message was setup for both sides. We have different teams who did this and sometimes the communication does not get relayed. I can't imagine this company is the only company that has had this issue. We use TAS and once it's submitted for approval, approved it goes automatically to the bank. If we have to correct this, we have to create to a new batch and grab it before it reaches the bank which sometimes can't be done then we have to work with the bank to back out. A lot time and resources to fix when a warning would alleviate this. Thanks!

The inclusion of invoices created in the Project Management and Accounting module in the Collection Process Automation feature is necessary, as currently, only invoices originating from sales orders and tax-free invoices are being considered.

According to the SEPA Credit Transfer rulebook 2019 V1.0. The structured remittance info for extended remittance info occurrences mustn't exceed 280 characters in length.

However, in the payment model for ISO20022 for credit transfer, in the case of bundling a credit note with and a payment, along with using long Payment IDs, as in Finland (the RF number could be up to 25 character), the STRD tag for the payment file will exceed the mentioned 280 characters in total, which results the rejection by the bank.

In that case, some banks would suggest removing the referenced document number represented in the tag.

We suggest handling the document in the way you see fits to avoid the rejection of the bank in such cases and make it easier for the D365 ER users to handle these cases.