-
Change of payment status when importing a camt 054 file to a customer payment journal
Suggested by Emma Stanley – New – 2 Comments
When importing a customer payment file with file format Camt.054 to a customer payment journal it would be preferable if the payment status would be set to "Approved" on the payments that are fully settled against an invoice. Currently all payments get payment status "Received" regardless of finding an invoice match or if the payment amount is not correct. It would also be a nice feature to get an import report when the import of the payments has finished. This report should display which payments that were OK (i.e settled) and which payments that were not OK (ex not finding the invoice or wrong amount). A short description of why the settlement against an invoice failed shold be displayed on all lines that are not OK. Today most swedish customers are importing customer payments with the file format BGMax. When importing this format you both get a import report once the import is finished (displaying whats suggested above). Additionaly, payments that successfully settles against an invoice gets payment status approved while payments that do not settle (fully or at all) gets status received. This makes it easy to see which payments you need to take a look at and manually handle. However, this payment format (BGMax) will no longer be supported by the banks as of 2022, and the new recomendation will be to use the camt.054 format. Therefore many swedish customer will be effected by this and will most likely miss the functionality that comes with BGMax format that the camt.054 format does not support today. -
Revaluation report from AP and AR is not generated when D365 session expires
Suggested by Veronika Hoskova – New – 1 Comments
There is a functionality of Revaluation in Accounts Receivable and Accounts Payable. The people from Business need to know from the auditor reasons which Exchange rate was used when revaluating. The only possibility how to get this information is to generate revaluation report which can be set up within Revaluation setting form by activating the toggle "Print". There is NO POSSIBILTY TO REPRINT the report in case the user forgot to switch on that Print toggle. And there is also no possibility to pull out that Exchange rate additionally by adding it as a new field within the list of transactions generated afterward. So there is only one option to get that report.
You first have to set the parameters within Revaluation setting form, you switch on the toggle Print and afterward there is a new window/form where you can set the parameters for printing revaluation report. Once this printing parameters are set up and confirmed, the revaluation is taken place and the report is generated.
BUT - if you set up parameters for revaluation and then you let the D365 session expire without setting up the parameters for report printing (the second setup form required), because for example there is a lot of data, it´s taking a long time and you are paying attention to other tasks, then the system skips the printing option form and performs the revaluation without generating the revaluation report (and the report can´t be reprinted again).
In our company there are dozens of LEs and for some of them the revaluation is taking even more than one hour because of the big volume of data. And users can´t be paying attention to one open D365 page so it doesn´t expire. We would strongly need to have a possibility of RE-PRINTING the report.
-
Mass Update the option "Show Task list on default dashboard" on User level
Suggested by Veronika Hegyi – New – 1 Comments
Mass Update the option "Show Task list on default dashboard" on User level. Currently it is not possible to add this field to the 'User information' Data entity.
-
LATAM localization: Personalize localized fields and enable filter/sorting capabilities
Suggested by Michael Huber – New – 0 Comments
Many standard D365 Finance tables have additional fields for the LATAM localization, e.g. vendors and customers. On the vendor/customer card the LATAM fields are accessible via a FastTab "LATAM". Technically, those LATAM fields are not integrated in the standard VendTabl/CustTable but are separate tables.
Our customer in Chile would like to personalize those LATAM fields, esp. moving the fields to e.g. the "General" FastTab on vendors/customers. If you open the Personalize bar and try to move those fields, they do not appear in the list of available fields.
Additionally, it is not possible to filter by the LATAM fields, not even using Advanced sorting/filtering.
This is a downside for Chilean customer since they would like to filter by the "RUT" number that is included in the LATAM field "Country identification number". This is impossible since the field (among all the other LATAM fields) is not filterable and cannot moved to the General FastTab in order to at least have the number at first glance.
This is valid especially for but not limited to customer and vendor cards.
Summary of the idea:
- Enable personalization of LATAM fields (esp. moving them to other FastTabs)
- Make the LATAM fields filterable and sortable
-
Blocking rule Days overdue exclusion rule for amount should look at the total balance on the customer
Suggested by Pernille Busk Sørensen – New – 0 Comments
Hi, Could you make a change to the current Days overdue rule? So the exclusion rule for amount could look at the customer's total balance amount and not just the overdue balance?
Or maybe you could create a new blocking rule/exclusion rule for this customer total balance?
Many thanks, Pernille
-
Intrastat - fix for incorrect VAT numbers
Suggested by Henrika Petäjä – New – 0 Comments
In some cases tax exempt numbers is wrong on Intrastat report which should be fixed.
There is a bug where sometimes two first characters are missing in Tax exempt number -field on Intrastat report even the tax exempt number is correctly inserted to customer and is also correct on the sales order setup.
This bug causes manual work every month to correct the Intrastat report.
Please see issue number 859557 for this case.
-
Dynamic update of payment note in vendor payment journal
Suggested by Kim Melton – New – 1 Comments
If you, after creating a payment propoal in a vendor payment journal, wants to add another invoice to the payment using Settlement for the journal line, then the payment note should automatacally be updated with the additional text according to the setup in default descriptions. Also if an invoice is removed from settlement, te payment not should update automatically.
This was the functionality until approx version 10.0.26 and it should be reinstated
-
After doing Customer settlement form the settlement window has been closed
Suggested by Nirmal Kumar Gandhi – New – 1 Comments
In AX2012, the Customer settlement form allowed to settle multiple transactions at once by clicking on "Update" and without getting the form closed.
The same thing does not happen in D365 F&O. After settling customer transactions and clicking on Post, the Customer settlement form gets closed. The expectation is that the customer settlement form should not get closed even when we have settled multiple transactions and an "Update" option should be provided as it was in AX2012.
-
Belgium : Enterprise number deducted from VAT ID
Suggested by Marie Warnier – New – 0 Comments
In Belgium, for the Belgian customers, the enterprise number must be filled in in addition to the Tax exempt number.
The enterprise number contains text and a ten-digit number.
The idea is to deduce the Enterprise number from the VAT ID (as the ten-digit number is the same) for the Belgian customers.
Because as there are 2 registrations ID to create (Enterprise number & VAT number) for Belgian customers, it's a risk to forget to create the enterprise number.
Furthermore, in AX2012, the Tax exempt number was deducted from the Enterprise number.
-
Vendor bank account validation in the Vendor Payment proposal lines
Suggested by Neil Catubig – New – 3 Comments
SCENARIO/ISSUE:
Let's say, User #1 created a new vendor bank account and set to expired the existing ones.
User #2 then generates a payment proposal and tries to settle an invoice that is previously tagged with the old, expired vendor bank account.
At this point, there is no warning if the vendor bank account on the transaction is already expired. User #2 then went ahead and generate the payment, not knowing that it had the incorrect vendor bank account details.
RESOLUTION:
With the current design, users need to set the new/valid vendor bank account into the 'Alternate account' field in the payment proposal lines.
FEATURE REQUEST:
To make User #2 aware that expired vendor bank accounts are being used in the vendor payment proposal lines (before they generate and send out the payment file), it would be best to add into the Payment proposal lines form the same vendor bank account validation that now exists on the vendor transactions, where it is currently throwing the following message where applicable: 'The
bank account is inactive. Select an active bank account’ The desired warning/error message is similar to it with a slight variation: 'The
bank account on the line is inactive. Select an active bank account as an Alternate account’