Dynamics 365 Finance

Currently, the due date for credit notes is based on the payment terms defined on the customer's account. This can result in credit notes not appearing on collection or reminder letters until several weeks after they are posted, even though the credit is immediately applicable.

I propose enhancing the system to allow credit notes to be handled separately and assigned their own due date logic. This would make it possible for credit notes to appear on collection letters immediately, while invoices continue to follow standard payment terms (e.g., 30 days). This change would improve customer communication and streamline the collections process.

Select "JBA(JP) - Format A" for "Import format" in "Methods of payment".

Specify any string for "Document" in the "Journal names" setting.

After selecting the "Journal names" created in the Journal in "Customer payment journal" and importing the JBA format file in "Import payments", the "Document" field in the imported line is Blank.

The string value set in “Document” in the "Journal names" screen is not retained.

Since the "Document" field value is retained when creating records using the "New" button or when using the payment proposal, the same behavior is expected when creating records through payment import — the "Document" field should also be carried over.

Regards,

'Bulk editing in grids' is a feature On by default in 10.0.44. 

We request that this feature is never made mandatory as a user could inadvertently incorrectly mass update a grid, causing operational stop for the company and a major clean up issue. 

This feature should never be forced on clients and ideally Disabled by default, so clients have to directly opt-in.

Currently, it is not possible to recognize multiple Purchase Orders within the same invoice that is read by Invoice capture.

Within a business, it can often happen that suppliers can send one invoice combining multiple Purchase Orders.

Hence, instead of having an automated way to capture the vendor invoices, the business has to manually review the invoices and assign the right PO on each line of the PO invoice before transferring to F&O.

This has a big impact on the purpose of Invoice capture and the automation of the process to facilitate the business processes of the Finance team.

The recognization of multi PO within one invoice would be then very appreciated.

Idea Summary:

In Microsoft Dynamics 365 Finance and Operations, within the Advanced Bank Reconciliation functionality, the matching rules allow users to perform automatic actions such as "Generate Voucher." However, when using this action type, it is currently not possible to input or assign a financial tag (also known as a financial dimension tag).

Proposed Enhancement:

Extend the capabilities of the "Generate Voucher" action in reconciliation matching rules to allow users to specify a financial tag. This would ensure that vouchers generated during reconciliation are properly classified and aligned with financial reporting requirements.

Business Value:

• Improved accuracy in financial reporting through better tagging and classification of generated vouchers.
• Enhanced automation by reducing the need for manual voucher adjustments post-reconciliation.
• Consistency in financial tagging across all types of transactions, including those created automatically via reconciliation rules.

Use Case:

A company that uses financial tags extensively for internal reporting needs to ensure that all transactions, including automatically generated vouchers during bank reconciliation, carry the correct tag.

Suggested Implementation:

• Add the Financial Tag field as an editable input option when configuring the “Generate Voucher” action within the reconciliation matching rule setup.
• Ensure this tag is applied to the resulting voucher transactions.

Our business is always facing problem when trying capture invoices with more that 15 to 20 pages via Invoice Capture AI model.

The reason for this is the attached invoices are having more than 1000+ lines, which can cause time outs from Ai builder.

Recommendation is to split and try with reduced number of lines.

We are suggesting an improvement in Microsoft Invoice Capture AI builder model to read and process invoices with more than 1000+ lines so that our customers can process invoices with more that 15 to 20 pages without splitting it.

Thanks.

Description:

The customer has reported that in Budget Planning within Dynamics 365 Finance (version 10.0.43), the Forecast Position functionality is not correctly sourcing worker compensation fixed plan data from the Human Resources module.

Details:

When an existing position is added to a Forecast Position and the "Assign a compensation group" option is set to No, the system is still deriving the budget amount from a Budget cost element instead of using the employee’s compensation fixed plan.

Current Outcome:

After creating the Forecast Position and the "Assign a compensation group" option is set to No, the budget cost amount displayed is pulled from the Budget cost elements section, rather than reflecting the employee’s compensation fixed plan.

Expected Outcome:

Given that "Assign a compensation group" is set to No, the system should instead display the pay rate from the employee’s compensation fixed plan in the Human Resources module.

Deferral's logic is wrongly insisting on balancing out the total deferral's sum of lines with the amount of the invoice including VAT.

This happens in cases where the invoice has had a prepayment because the PO had to have gross amount to be prepaid in the line, and the PO Invoice had to have a line manually set in net amount with the Sales tax calculated based on the tax setup on the line.

The SUM of the deferral should be net amount of the invoice (line excluding VAT).

Each cost invoice captured by the app is currently created as a sperate Invoice Journal in D365 Finance - i.e. a one-to-one relatonship between invoice an Invoice Journal.

This causes a lot of records on the invoice journal grid and makes it hard to navigate and search for a specific journal. In addition the description on each journal is vague which makes the task of looking for a particular journal even more difficult.

Suggestion: Group all cost invocie over a given period of time in one journal - where each invoice is a separate voucher within the journal. The attachments would be at the voucher level.

When we have a tax combination " Group and group Item' with a sales tax code shared between them with a Zero Rate it throughs an error that the tax combination is not valid.

This happened because the result of the combination is Zero, so the tax code validation read the combination as a wrong one.

To resolve that we need to turn the toggle for "Check sales tax code " to None or Warning.

But this is not the best option as we need the validation when we have a wrong combination to prevent users from proceed also we need to use the Zero rate so we trace which transactions were posted using this VAT code >tracing error or missing tax transactions becomes easier.

So the suggestion would be to remove the Zero tax code form the validation as long as the setup for the sales tax code, Item and group is correct it should proceed as normal with no error.