Dynamics 365 Finance

When the asset is terminated at the end of lease period, the accumulated depreciation value left in the account is not being reversed. And the value is being carry word to every year.

Hence user is manually posting an adjustment entry to Knock off the value present under the accumulated depreciation account.

In most European countries ECO participation is requested. This is a contribution to help recycling.

This is a trend all over European countries.

Eco participation is mostly based on unit and should be printed on invoice.

• Eco participation is based on unit
• the rate can be based on 3 digits even rounded to 2 digits on invoice
• VAT total will be calculated on total invoice lines included Eco participation.

There is no full solution in the system. But so far workaround will be to adapt Charge for sales order.

Some example.

• BEBAT (tax on battery)
• Plastic
• Carbon

 When two registration numbers exist in one legal entity (Germany) and transferring the Intrastat for Transfer orders of the two registration numbers, the Transaction code, statistics procedure Country/region and State/Province are not defaulting the correct values for the e.g. Arrival.

As per the legal requirement, the referenced fields must be transferred and populated for the Transfer order Shipping and Receiving, when the Intrastat is generated and reported.

It would be of great benefit to reconsider the current design of the product as such to more efficiently incorporate the fields to be available in the Transfer order line form for easier processing and avoiding manual rework during the Intrastat preparation as well as accommodate the current legal requirement.

Our client is having a business requirement to have end dates which some are 999 years in length.

There is currently a limit on the date to field to only allow up to 31/12/2154.

Their business process uses the dates from the Leases on the buildings they handle for reporting purposes and since there is a limit on the End date, the reports cannot reflect correctly the information, which interferes with the normal process.

We would like to ask for your vote for this Idea so we can show to the Product Team this extension is needed for the normal daily business of the client.

Start and End date are hardcoded into the system and we couldn't achieve this with customization, so we require help from Microsoft.

When having a Procurement category-based purchase agreement which is associated to a Project.

upon creating Purchase order (non-Project related) and purchase agreement mentioned while creation of Purchase order. System allows user to link the Purchase agreement with purchase line. This should not be allowed as the Purchase order is not related to any Project. Also, after linking the purchase line system will assign project ID to the purchase order line.

This behavior is not same when we have Purchase agreements of Product quantity agreement. system does not allow users to link them with purchase order line.

If purchase agreement line is related to a project it should not be available for linking with PO line without project (as it works for items), regardless of whether there’s an item or a procurement category on PO line. 

It can take months of effort to train the custom invoice model. This must first be done in a UAT/test environment so that we can ensure proper functionality before bringing to production. However, when our testing is completed there isn't a way to move the model and it's training to our production environment. This significantly limits our ability to implement custom models due to the time needed to invest in the training. The model and it's training should be able to be promoted to production and also copied to other environments.

When adding a Ledger accruals to a vendor invoice, the description of the accrual line vouchers is taken from the accrual scheme. There is no concrete link between the vendor invoice number and the related accrual transactions. For (year-end) audits and month end closing it can be important to have a link between the accrual lines in the ledger and the original invoice where they are based on.

Therefore my idea would be to be able to add a direct link between the vendor invoice number and the related created accrual lines in the ledger. For example via:

• A parameter in AP where you can decide that the vendor invoice number is automatically added in the field ‘Description’ on each related accrual line instead of using the description from the accrual scheme or in addition to the description from the accrual scheme.
• And / or being able to create a Default description for this accrual postings to add information like vendor invoice number.
• And / or being able to find the link between all postings via the option ‘Related vouchers’ in the created voucher transactions. 

My Client receives a high volume of zero valued invoices relating to the scenario where faulty/damaged stock is replaced by a supplier and they issue zero value invoices for the replacement of the stock that is faulty or damaged instead of issuing a credit note and re-invoicing for the new stock at the normal cost. 

When a PO is created for the zero value stock, It is possible to process an invoice directly against the PO, however it is not possible to post the invoice to the invoice register to be matched later to the PO 

When attempting to add the invoice to the invoice register, and then match the invoice to the PO, it is not possible to post the invoice on the invoice register, you receive the error message "Posting without amount cannot be made"

My client needs to be able to raise these invoices on the invoice register so that they have a consistent process for their staff for processing purchase invoices.

If it is possible to post the invoice against the PO it should be possible to post the invoice on the invoice register as well.

Please can this be fixed so that these invoices can be processed via the Invoice register?

As per below regulations all description elements in SAF-t (LT) should be automatically truncated to 256 characteds (purchase/sales invoice, invoice lines description, GL and FA desctiptions and Payment descritpions):

SAF-T legislation in Lithuania

• Article 16 of the Law on Accounting;
• Resolution No 699 of 01 July 2015 of the Government of the Republic of Lithuania;
• Order No VA-49 of 21 July 2015 of the Head of the State Tax Inspectorate under the Ministry of Finance;
• Specification of XSD description of the XML scheme of SAF-T, as prepared by the State Tax Inspectorate under the Ministry of Finance.

Schema in english:

https://www.vmi.lt/evmi/documents/20142/725548/SAF-T_XSD_specifikacija_v2.1_F+en.pdf/23775a8a-0ba7-6b9c-1fc9-cfceb4ba8bd0?t=1606462594737

Reg ticket number 2502051420001009.

Becasue of missing limitations such errors appears and XML for SAF-t (LT) is not accepted:

ERROR: Element '{https://www.vmi.lt/cms/saf-t}Description': [facet 'maxLength'] The value has a length of '267'; this exceeds the allowed maximum length of '256'.

Please have a dark mode within the app. A black/dark grey background with white/light grey text will be highly appreciated.