Dynamics 365 Finance

The Spanish electronic invoice management providers want the prefix ES mandatory in the VAT number of the xml sent to them. For the management of the SII instead, the Spanish customs agency does not require the prefix in the VAT number.

By design there is only one field to manage the company's VAT number.

It requires the management of the two cases, currently managed manually.

When we use the ledger settlement functionality, it should be possible to configure an automatic account ledger that will post automatically the penny difference when we try to settle ledger account. This business process is very critical for our customers and it will be extremely helpful the Ledger settlement Module.

When the Date of VAT Register functionality turned on which allows user to change the date of VAT transactions already settled, without creating a contra entry to ensure the net movement is zero.

Due to this same transaction could be settled multiple times to the VAT authorities, which is incorrect.

Expectation: System should give validation such as any notification which alerts the user when they try to change the data of VAT register for already settled and paid transactions.

WIth the "Reject duplicate" invoice number setup in the accounts payable parameters, we expected to forbide the creation of two pending invoices with the same number.

But it is not the current behaviour while one of this two invoices is not posted but on going into the workflow

So I suggested to extend the feature "Prohibit submission to workflow when the invoice number already exists on a posted invoice", to un-posted invoice also,

Thank you for taking into account this idea and voting for it,

Bests regards

Update data entities for Party, Vendor, Customer Postal addresses to include VAT Registration ID and the General section of the Manage Address form.

When using registration ID to maintain VAT numbers, migration of customer/vendor master data becomes extremely cumbersome to have to merge 3 or sometimes even 4 data entities using party ID and location ID to get the information imported.

Currently migrating customer master data with multiple delivery addresses and VAT numbers attached, consist of the following;

1. Customer V3
2. Customer Postal Address
3. Registration Number

These must all be linked by party ID and Location ID.

In all master data cards, we are able to add default financial dimensions, however, in the petty cash feature, when we create a cash account, we are not able to add default financial dimensions. This should be a basic feature functionality since in all other master data cards we have this possibility.

Without this feature basic development, customers need to have a lot of additional manual work and it can cause several posting errors that need to be corrected later.

Petty cash feature is very poor in terms of options and need some development in order to be usefull for F&O users.

Please take this in consideration and think on developing this default financial dimensions in the petty cash feature (cash accounts master cards).

Thank you.

Purchase order prepayment is missing in Cash Flow Forecast

Without proper visibility into PO prepayments, finance teams may inadvertently misjudge available liquidity or overlook potential cash shortages. This lack of transparency can hinder decision-making, delay critical investments, and increase the risk of financial missteps. By ensuring comprehensive reporting of all PO-related cash movements, organizations can gain clearer insight into their financial position and make more informed, agile decisions.

This is not a new idea for the product, but it is necessary because the current cash flow report is ineffective.

New Feature process automation for accounts receivable and accounts payable foreign currency revaluation (and coming Bank revaluation for process automation in ver 10.0.44) looks very promissing to optimize processes within companies. Unfortunately I am missing option in the setup of these process automation - checkbox to mark of printing report - which is available with standard process. I fully understand that still end users could print report for simulation - but simulation report cannot be used for audit purposes. Revaluation report is a reflection of posted transactions - it is easy to check calculations and see what exactly has been revaluated. It is impossible to see it on the transaction level, as there are thousands of vouchers. Most companies are saving Revaluation reports for audit purposes (internal and external) - which is impossible within new Feature.

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.

We discovered that some users have been removed from the User Group in Financial Reporting Designer without any changes to the configuration. Therefore, it would be beneficial to have a method or feature to track changes made in Financial Reporting Designer.