Microsoft Dynamics 365
Any financial transaction batch (whether vendor/customer invoice, expense, payment, journal, etc...) should post in the same fiscal period to prevent reconciliation timing issues.
Ideally there is a built-in control to ensure this happens and prevents one expense report from being split between ...
Expense management (150)
I am unsure of the difference between Invoice and Document in the Invoice Journal (Non-PO invoice) or Vendor transactions (PO invoice) screens, but if our users forget to populate them both then some of our reports are missing this important info. We will adjust our reporting to include both colu...
Accounts Payable (386)
With the use of the GL Default Descriptions (which we LOVE), we find that some our descriptions are truncated. Can we extend to min 80 characters, or ideally to 100?
General Ledger (467)
Users often pull reports by transaction type (i.e. Purchase Order vendor invoices and product receipts are transaction type 3) but currently all Reversal vouchers post with ONE transaction type (0 in our case).
To provide a better audit trail and improve reporting, can reversal vouchers retain ...
I understand that users can drill down from a reversal voucher to the original transaction, but this is not visible in reports. Since reversals can refer to transactions many months ago, it would be super helpful to provide the original transaction/voucher within their reporting. This would also...
The current default is miles and I cannot find any place where it could be configured to kilometers for countries (like Canada) that report and claim on km's VS miles.
I understand that this was available in old AX versions and there is value in sharing account structures between legal entities. However, there are valid circumstances where the rules are just too different and it would really add value to have the option to set it up by legal entity.
This report is very useful to identify tax issues, especially with large volume of EDI invoices that are auto-matched for payment. However, it would be even more useful if the report's "Records to include" section included a vendor account filter. Thank you for the consideration.
This new feature was released as part of PU29 but is very basic with just two parameters: Number of days to retain history and Number of hours to execute the job. It would be much more useful with the following additions:
- Allow for several batches to be executed (similar to Staging cleanup)
The Data Management job history form allows filtering of all columns with exception of this one. Can you please add the filter option on Status as well?
This would add value by allowing users to filter by "Failed" and "Executing" as part of maintenance and issue resolution.
Filtering by "Ex...