Managing the bankreconciliationhistorydetails Table
We propose an enhancement to the current data management capabilities within the bank reconciliation module. We need for more granular control over historical data, specifically the ability to remove subsets of data from the bankreconciliationhistorydetails table once it is deemed no longer n...
Cash flow sales order and purchase order (by delivery line date)
Now D365 for sales order and purchase order take the delivery header date to calculate the cash flow forecast.
The suggestion is to use the delivery date (requested or confirmed if we have the confirmed delivery date) in sales and purhcase order line in order ...
Vendor bank account validation in the Vendor Payment proposal lines
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 ...
Inventory Value Storage report date is incorrect
Inventory Value Storage Report has incorrect date in header and does not match with the data inside report.
In our project, we create Inventory Value Storage Report through Batch jobs.
We update batchjob parameters with dates to extract monthly report.
Although ...
Advanced Bank Reconciliation Statements lack the level of detail that manual bank reconciliation statements had
When printing a bank reconciliation statement after reconciling via the Advanced Bank Reconciliation - the statement only shows transactions that were auto-generated by the ABR model as well as unreconciled items. However, it does not give you any insight into the transactions that were able t...
Transfer Bank statement number to Document Number to improve visability
Advanced bank reconciliation: transferring the bank statement number into Document number (LedgerJournalTrans.DocumentNum) of the automatically generated and posted journal line (e.g. if you process reconciliation matching rule "Settle customer invoice", generating a customer payment journal) ...
NACHA Format does not meet bank standards
NACHA US format doesn't meet bank standard.
For position 80 – 94 the 8 digits should be as outlined by NACHA.org, but it is currently formatting as 0 + part of the journal number + line numbers.
• Field: 11
• Length: 15
Linking a Letter of credit for more than one PO and One Po to have more than one Letter of credit
Linking a Letter of credit for more than one PO and One PO to have more than one Letter of credit. In general business scenario, it is a possible scenario to make the LC for multiple PO's with the same vendor and also for one purchase order there is a chance of having more than one LC.
Reverse a Bank Account reconciliation for the Bank which is not enabled for "Advanced bank reconciliation"
Provide the Bank Account reconciliation reversal future for the bank account which is not enabled for "Advanced bank reconciliation".
Human errors are common, and this avoids lot of corrections that need to be made at t...
Ability To Be Able Delete Banks That Have No Transactions Recorded
Hi There,
We are seeking a solution whereby banks created on Dynamics but have no transaction recorded can be deleted. We have a current scenario where this happened on our Golden Environment; and we do not want these invalid banks to go on Production during the copy to Produc...