As of 2022, in the French tax mandatory requirement, il is mandatory to generate a customer prepayment invoice. When creating a prepayment from a Sales order, it is mandatory now to generate a customer invoice for this prepayment.

Currently in Dynamics 365 Finance, it is not possible to create a prepayment invoice. The prepayment invoice has the same legal data as the final customer invoice. In the standard version, a prepayment is just entered as a payment (without an invoice as justification) and then settled manually with the sales invoice.

French description from the Tax regulation : Le Code général des impôts prévoit que tout assujetti est tenu d’émettre une facture pour les acomptes qui lui sont versés avant que se produise le fait générateur qui doit normalement donner lieu à l’émission de la facture.

Facture d’acompte : les 9 mentions obligatoires en 2022 (legalplace.fr)

Settle and post sales taxes does not consider the functionality “Vat report date codes” and cause that the company pay wrong taxes.

Issue was escalated under ID 756139 but it was rejected for now due to fact that the 'vat report date codes' were never supported by the "sales tax payment"

Link to LCS: Details for issue 756139 (dynamics.com)

Configurations that we import from Microsoft repositories misses release note to find which changes have been made on data model, model mapping and format designer.

This will help user to get better overview that each KB or ID include in regards with new fields functions, changed mapping and deleted fields.

As an example, It could be added a text field as attachment regarding the changes as "Release note" or a new field on mapping model and format designer that contain information about the KB/ID changes.

As per Legal Reference: Taxation Act – Section 76A(2)

According to Section 76A(2) of the Taxation Act

"The tax payable under subsection (1) shall be deducted from the amount referred to therein upon—

(a) accrual of the amount to such person; or

(b) payment of the amount to such person whether directly to him or to his account in or outside Malawi; or

(c) remittance of the amount to such person; or

(d) crediting of the amount or of the value thereof in favour of such person…”

The use of "or" in this clause indicates that withholding tax is triggered by the earliest of the listed events — whether it is accrual, payment, remittance, or crediting of the income.

This interpretation aligns with the Malawi Revenue Authority's practice and international tax standards, where withholding obligations are typically triggered at the earliest recognition of income, to avoid deferred taxation.

Key Compliance Requirement

In practical terms:

• If a liability is accrued via an invoice, and no WHT is deducted until later payment, the organization may be seen as non-compliant.
• Therefore, our request to calculate WHT at invoice level is to ensure legal compliance and timely deduction, as required by Section 76A(2)(a).

System Expectation

However, the system currently calculates WHT only at payment, which does not satisfy the requirement for invoice/accrual-based withholding under Malawi law.

Request

We request your assistance in identifying configuration changes or hotfixes that will enable WHT to be triggered at invoice posting (accrual) for the Malawi region.

Ref:

in the current implementation of the ER configuration of the electronic invoice import 'Vendor invoice Mapping to destination', when an item cannot be identified by the external item number, the mapping uses an item called 'DEFAULT_ITEM' as a replacement.

We would like very much, that this Item can be replaced by a default procurement category since the options to assign the correct ledger account are way more comfortable using a procurement category instead of an item.

I would kindly note that fields in table CustParameters are not mapped in Data entity CustomerParametersEntity so we are unable to export/import fields via standard function "copy to legal entity", nor by export/import project in Data management.

We would appreciate that fields, which are mandatory to be used in several countries can be used as they are supposed to be used, especially in project phases such as migration.

The list of the missing fields:

MandatoryVATNum, AdvanceInvoiceCreditCorrection_W, AdvanceInvoiceReversalCorrection_W, InvoiceIdEditing_W, PercentCustomersPerBatchTask, TaxGroup_RU, TaxItemGroup_RU

Hi,

To comply with Indian legislation, it is mandatory to have a daily backup of the Indian company data on a server which is physically located in India.

Since this is part of Indian legislation and Indian company audit, the idea is that Microsoft provides such a functionality.

As a finance ERP it would be nice and preferred, they provide all parts of financial audits (or can comply with Indian legislation). That way the Indian company data can remain inside MS (architectural) boundaries.

This can be helpful for many customers since the MS process would be audited and not the company individual processes to comply to the Indian legislation.

This should also be possible for companies with 250 legal entities, where only 1 legal entity is India based. So only the data of the Indian legal entities can/should be saved on the server which is physically located in India.

Many thanks!

Currently an applied prepayment amount is not taken into account, when an imported invoice is submitted to workflow and the "Require the calculated totals to equal the imported totals for workflow submission" parameter is set to yes in accounts payable parameters (tab invoice -> invoice workflow)

For invoices an prepayment is applied to the calculated invoice amount is reduce by the prepayment amount. Based on that the calculated total differs from the imported total. For those invoices the functionality should also take the applied prepayment totals into account. Otherwise those invoices are blocked for workflow submission and the parameter must be deactivated each time to process invoices.

Idea on sales order invoice summary control

Multiple sales orders can be summarized on one invoice using the Summary update for parameter on the Posting invoice form:

In cases where a lot of sales orders are created for a customer which are delivered, this could result in an invoice with a large amount of lines.

Some customers want to avoid having such large invoices, but still want to generate these invoices in batch using the “Late selection” functionality, instead of splitting the sales orders using the query and creating multiple batch jobs manually.

The idea is to add an additional parameter to the Posting invoice form where users can specify the maximum number of invoice lines in case sales orders are grouped on one invoice.

This functionality should keep track of the amount of lines that are grouped under a single sales order header (and one invoice). Once the maximum specified number of lines is reached, the current sales order that was being added should be added in total (to avoid splitting one sales order over two invoices), and the next sales order will become the new sales order header where the next sales orders will be grouped underneath until the specified maximum of lines is reached, or until all selected sales orders are allocated under a sales order header.

Hi Microsoft,

in some cases, the business has many financial dimensions and their values. It is not unusual, that the accounting wants to exclude only one dimension value from posting on specific account. e.g. on Account Revenue EU, there should be no posting with dimension for Inland.

For now, you have to specify all allowed values for the accounts in the structure. If there is any new value created, you need to add this into the structure firstly.

With the possibility to exclude values, it will be easier to maintain Account structures, because all newly added values will be automatically allowed.

K.