Dynamics 365 Finance

Bank statement lines includes amounts that are fully VAT and the tax base is in separate line. Currently it is not possible to book full sales tax amounts from bank reconciliation worksheet as there are no option to enter sales tax code or actual sales tax amount.

We'd suggest to open usage of these fields also in bank reconciliation worksheet.

We had an issue where the Sales figure of Profit and Loss report generated from the management reporter was not matched with the trial balance and we found out that a transaction was missing in the management reporter P&L report.

Going in deep, we reviewed the voucher of the transaction which was missing and found out the difference in the value of the "Project" financial dimension on sales order header as well as sales order line with the voucher.

We also validated the length of the field to try to give us a reason, but longer lengths of financial dimensions exist with the full financial dimension values.

The financial dimension value got truncated in transaction voucher and not get picked in the financial report.

We need a tool to validate the values for financial Dimension values in order financial reports showing correct data.

Currently logic processing royalty claims

• Original accrual reversed with the orginal accrual date, causing financial periods to be reopen for which monthly reporting have been completed and settled, which is not optimal
• P&L transactions created again with vendor invoice, where the invoice date in a different month
• A huge number of extra transactions created.

The currenty logic processing royalty claims is not optimal in a financial perspective following good accounting practice, therefore this idea/suggestion for optimization

• Make it options if original accural should be reversed.
• When reversal of original accrual is set to NO - the transactions related to posting vendor invoice should be done against the Accrual account linked to the Royalty agreeement.
• Make it optional to specify a invoice date for the Vendor invoice when processing Royalty claims.

If the offset account is a ledger, we can calculate TDS in the Vendor Payment Journal. (If the posting type is purchase cash for that GL). Similarly, if any of the posting types would work for customer payment journal also, it is preferable that users use bridging accounts rather than banks.

Thanks

Raju Kulla

9959000489

In the payment export XML the priority is labeled as "Norm", but ING imports this as "Urgent" because of the service level code SDVA.

As a result of the urgent label bankcharges are charged.

We need a different export protocol to meet the expectations of ING as for Rabobank the payment is not labeled as urgent.

Because of the inconsistency we need an additional report next to report 11000012 so that we can serve both banks

These items are not set in Tax adjustment general journal when Consolidated invoices for Japan is confirmed.

• Method of payment (can be deriverd from the customer)
• Terms of payment (can be deriverd from the customer)
• Invoice (can be set consolidated invoice number)
•  Due date (can be calculated using terms of payment)

Broker claims- functionality is not supported by Tax Calculation Service for multiple lines in Broker claims approval. One broker may have several customers with different tax handling, or several lines per customer. Broker claims can only be approved on line basis when Tax Calculation Service is enabled. Customers using the Tax Calculation Service are not fully able to utilize the functionality to calculate and pay out Broker claims for customers. Since there is a gap with these features, we suggest that the Tax Calculation Service would be developed to include the possibility of handling Broker claims fully as soon as possible. 

Financial reports are moved to default folder after using option “import default reports” or installing a service update.

System considers a financial report as a default one if they have at the end of the names the following segment “ - Default” (blank space, hyphen, blank space and default).

On the other hand, if the segment is not at the end of the name (for example, adding a dot after “Default”), any of the blank spaces is missing or hyphen is not the same one as in the other reports, issue will not be triggered.

Default word can be either in capital or lower case.

Example:

This triggers the issue: Test Financial Report - default

This does NOT trigger the issue: Test Financial Report- Default

This does NOT trigger the issue: Test Financial Report - Default.

This does NOT trigger the issue: Test Financial Report - Default new

Request is adding this to the public information to prevent anyone face this limitation.

Would need the Index rate (%) field to be based on Revaluation date and not on Lease start date.

The revaluation according to Index rate (%) should be reflected in the Payment schedule, with a recalculation of the instalment amounts starting from revaluation date, by the percentage specified in the index rate type schedule (whichever the book type, Cash basis/IFRS/USGAAP).

We would like to propose new feature or batch job to be implemented within F&O to clean up the one-time address from source table or to be truncated after a specific period of time