Dynamics 365 Finance

At https://learn.microsoft.com/en-us/dynamics365/finance/localizations/italy/emea-ita-competence-date is stated that "On the General ledger parameters page, on the Ledger tab, set the Transaction date reference to competence date option to Yes. After the competence date functionality is turned on, you can specify Transaction date as an acknowledgment date for each journal that can be used to post the adjustment and closing transactions for the fiscal year:".

Despite the checkbox is turned off the Transaction date (AcknowledgementDate) is automatically populated and can be manually adjusted.

At the same link is also stated that "you can specify Transaction date as an acknowledgment date for each journal that can be used to post the adjustment and closing transactions for the fiscal year:

General journal (General ledger_Journal entries_General journals), Fixed assets journal (Fixed assets_Journal entries_Fixed assets journal), Bank account reconciliation (Cash and bank management_Bank accounts_Bank accounts_Reconcile_Account reconciliation), Closing period adjustments (General ledger_Period close_Closing period adjustments), Year-end close (General ledger_Period close_Year end close_Run fiscal close), Project – Post costs (Project management and accounting_Periodic_Time and Material_Post Costs_Post), Project – Accrue revenue (Project management and accounting_Periodic_Time and material_Accrue revenue), Project – Estimate post (Project management and accounting_Periodic_Estimates_Post estimates), Project – Estimate reverse (Project management and accounting_Periodic_Estimates_Reverse estimates)" but the Transaction date (AcknowledgementDate) is automatically populated and can be manually adjusted also when it comes to vendor invoices for example.

Expected results: We should not be able to use the functionality without enabling “Transaction date reference to competence date option to yes”. And use this on accounts payable as this is not listed on document.

When lines are generated from the budget plan import, the system does not automatically perform a budget check. Currently, the system runs budget checks correctly only when the lines are entered manually.

With the current system behavior, the withholding tax amount is currently deducted from the payment. However, as per legal requirement in Australia referencing Documents quoting supplier's ABN | Australian Taxation Office, withholding tax should be calculated and recorded into the system based on gross amount of payment. 

For instance, Vendor A issues an invoice for 100 AUD with a 5% WHT for Buyer B. When making the payment, Buyer B pays Vendor A the full 100 AUD and 5 AUD to the tax authority. This means the 5 AUD withholding liability is recorded as a WHT expense. The offset account for the journal should be Accounts Payable to Tax Authority, to be settled by the end of the month. 

It should be possible to import a return file that contains payments for several legal entities. This was possible until version 10.0.35 (update 831854).

Now, when importing a return file that contains payments for several legal entities, the file can be imported into one company, but fails in all the others. The file must either be split manually to be able to import it in the other companies, or the payments must be manually updated.

When printing Vendor payment advice with Use print management and Batch processing enabled, the system throws the following confusing warning message:

“A report running in batch can't print to the screen. Screen output will be automatically sent to the print archive instead”

Although the report is sent to the correct destination setup in Print management, users still receive a message that the report cannot be printing to the destination showed in the report dialog

On the header of an intercompany journal, the description always defaults to the description of the intercompany journal in the 'Journal names' screen e.g. 'Intercompany Journal' in our scenario.

It would be really useful for us to be able to use this field to give a better description of what the intercompany journal was raised for in the new legal entity e.g. if it could take the description from the general journal header that was raised in the first legal entity to create the intercompany transaction.

Thanks

With the new Customer prepayment feature it should be possible, that if the customer pays only a partial amount of the prepayment invoice, to apply this in the Sales order invoice.

What we expect:

We should have the possibility

• to correct the first prepayment invoice
• to apply the real payment in the sales order

Suggested solution 1:

When the partial Payment is settled with the prepayment invoice

• the old Prepayment Invoice should be reversed
• a new prepayment invoice will be automatically generated in the amount of the real payment.
• In all steps the tax should be corrected.
• The corrected prepayment invoice should be available in the sales order invoice

Suggested solution 2:

When we post the sales order invoice we wish to have an automatically reverse of the first prepayment invoice and creation of the new prepayment invoice with the paid amount. And in this way the tax should also be corrected.

Right now, there's only a duty available to Maintain vendor master. This includes:

• Maintaining vendor details
• Create/Update/Delete Vendor bank accounts
• Submit Vendor bank account changes for approval
• Approve Vendor bank account changes

This is not SOx compliant! Approval should be moved to a separate duty and privilege for approval of vendor bank accounts. Auditors currently indicate this risk with a high severity level, as employees are able to fill in their private bank account details, without anyone noticing or checking these modifications.

When the automatic ledger settlement is enabled, a debit transaction and a credit transaction can be automatically matched only if their amounts in the accounting currency are equal. A debit amount of $1.00 can be automatically matched to a credit amount of $1.00. However, a debit value of $1.00 can't be automatically matched to two credits, each of which is valued at $0.50.

The improvement would be that, when the total of the account is 0 (respecting the rules of the setup), the system would settle all the transactions into one.

Regarding Microsoft ticket 2401240030002949 & 2402070030003668,

We require Microsoft's assistance in developing an automated solution for extracting data from LCS user logs. Additionally, we need the ability to retain data for longer periods beyond the current 7-day limit. Alternatively, we are exploring the option of populating this data directly into Power BI.

Our aim is to find more efficient and automated methods to minimize manual tasks and reduce the risk of human error. If your team has any alternative methods for exporting data from the backend, we would appreciate hearing about them.

Thanks

Ida