-
Leverage data management for import of BAI2 advanced reconciliation bank files
In Dynamics AX 2012, it was possible to assign a directory folder path that could allow placement of a BAI2 file to be swept and automatically imported upon batch job completion. It appears this functionality was deprecated in the move to D365. Users must manually import the BAI2 file through the UI in order to perform advanced reconciliation. This repetative task is discouraging for the user to have to perfrom every time, especially if the company is setup to perform reconcilation daily. Please add the ability to import BAI2 files using Data management so that batch processing can occur. -
Project contract funding limit spent details
Project management and accounting features include a committed details button to leverage when observing a project contract funding limit. It would be helpful to see the Spent details on the project contract funding limit. Currently the user only has the ability to click posted project transactions, which does not show by funding source without having to click into the details of each and every transaction and click into the Sales tab to see the funding source spent amounts.
Create new button on the project contract funding limits to see filtered results by funding source of the spent amount details.
-
Exclude year end close transactions for balance sheet accounts in budget analysis
Budget analysis includes year end transactions for balance sheet accounts. This causes budget analysis to show a debit (consumed budget) in budget analysis for the opening transaction for CWIP accounts.
Please allow the filter to exclude year end closing transactions to be extended to opening transactions as well or create a new toggle to exclude year end opening transactions.
-
History of Optimization advisor rules that have been run
Optimization advisor provides the ability to run diagnostic rules. After running the rule there is no audit history of the rule that had been run. Create a new history record of runs.
-
Project contract funding limits committed details reflect the actual commitment of a purchasing document regardless of project category transaction type
Project based purchases fail to show the committed amount and the actual spent amount for project category transaction types (All except item. Item will only show actuals). The product current is deficient in this area for charges against projects. Please resolve this for a consistent user experience and accurate reporting for the ledger to reconcile to the sub-ledger.
-
Ability to remove purchase agreement from pending vendor invoice without having to delete and create a new invoice
Currently users in Dynamics 365 must delete and create a new pending vendor invoice if a purchase agreement (that is setup as direct invoice) has been assigned on an invoice. This is currently a bad user experience and should be resolved. This idea shouldn't be necessary as its a defect in the product.
-
Resolve known defect when transacting against more than one project in accounting distributions on Purchase requisitions - ledger to sub-ledger reconciliation issue
Microsoft has determined they're unwilling (at this time) to resolve a known issue Sub-ledger reconciliation issue.
If Project is included in the ledger dimension account string, the use of accounting distributions allows multiple projects to be used, when releasing the Purchase requisition into a purchase order, there is a clear mismatch in the ledger and sub-ledger. The ledger account string only reflects the one project that was listed in the line details, leaving references to the other project dimension in the ledger account string.
The results of this will incur a mismatch between ledger and sub-ledger on the resulting vendor invoice if not caught by a user.
You’re offline. This is a read only version of the page.
