Salvador Espinosa Support engineer

To run tests and demos, you need to activate the tool called Customer Payment Predictions. This is not possible without first installing a plugin called Finance Insights. The problem is that if you have a UDE environment, this is not possible, which does not allow you to run tests or demos of the tool. Therefore, it would be great to have this plugin in the UDE environment and not just in the LCs self-service environments, which helps with more processes in the system and not just for payment predictions.

When generating electronic accounting reports, the system inverts the balances, whether debit or credit, that have a negative sign, which causes my balance to become unbalanced. This results in the information being rejected by the authority (SAT).

In budget planning, when adding the lines and selecting a revenue account, the budget class field automatically has the value of expense and not revenue. This can be modified manually, but ideally it should come by default depending on the account type in the main account configuration.

When generating an invoice proposal from project operations, it is not synchronized in d365 f&o. The characteristics of this invoice proposal are that it is "0" and is not chargeable.

This request is for the system to synchronize invoice proposals in in d365 f&o. when generating invoices from project operations with "0" as non-chargeable.

Today this would be inconsistent data between project operations and in d365 f&o.  This request is to ask the “0” invoice to be consistent with Project Operations and FSCM.

Contracted Invoices - consistent with all Invoice Proposal.

Problem Description:

Currently, when generating vendor payments using the check payment method, the system automatically voids the payment if more than 36 invoices are included. While the system can print multiple pages, starting from the second page, a “void” message appears, and the payment is invalidated.

Additionally, it causes gaps in check numbering, since voided checks are still counted in the sequence, leading to confusion and audit complications.

Customer Impact:

This behavior significantly limits the system’s functionality. Users are forced to manually split payments into batches of 36 invoices or fewer. This slows down the process, increases the risk of errors, and adds unnecessary manual effort.

Why This Should Be Changed:

• More intuitive: The system does not warn users about this limitation in advance, leading to confusion and wasted time.
• More scalable: Businesses that handle high volumes of invoices per vendor cannot automate their payment processes efficiently.
• Clear justification: If the system supports multi-page printing, it should not void payments based on an arbitrary invoice count.
• Real-world alignment: Users need the system to reflect operational realities, where settling more than 36 invoices in a single payment is common.

Proposal:

Update the system design to allow more than 36 invoices in a single check payment without triggering automatic voiding.

Description:

In the Mexican localization of Dynamics 365 Finance and Operations, the system currently requires users to manually activate the "Foreign trade" checkbox in order for the Registration Number (foreign country tax ID) to be inherited when creating a sales order for a foreign customer.

This occurs even when the registration number has already been configured in the customer record. If the checkbox is not selected, the field remains empty, which can lead to compliance issues or data inconsistencies.

Proposal:

We request that the system automatically inherit the foreign country registration number from the customer record without requiring the user to activate the "Foreign trade" checkbox. While the checkbox can still be used to enable other fields like Commodity Code or Intrastat data, it should not be a prerequisite for inheriting a value that already exists.