-
Option to allow automatic financial settlement of $0.00 purchase upon receipt
We receive raw materials provided at no cost by our customers. We follow the purchase order process to place orders and receive customer supplied materials into inventory at no cost. The inventory transactions are not financially settled until an invoice is processed, but in this scenario, there is no invoice to process. We currently have to process $0.00 invoices to settle these transactions, which is burdensome. Having an option, perhaps set per vendor, to automatically financially settle purchase order lines upon receipt if the line value is $0.00 would be an enormous time saver. It could either happen automatically upon receipt of the materials, or it could be run as a batch process with a review step to help prevent erroneous posting. -
Add support for addenda lines to NACHA CCD+ and CTX file formats
The current implementation of CCD and CTX NACHA payments does not allow remittance details (i.e. invoice and detail amount paid) to be transmitted as part of the file. Instead, the current implementation only supports only a single detail record containing the total paid for that payee and generation of a separate remittance advice which must be sent to the payee via other means. NACHA file standards already support these addenda records, and it is becoming increasingly common as more vendors request electronic payments that they want payment details sent as part of the payment record, to support automatic settlement on their end.
-
Support Date Interval Date Ranges On Currency rate import Recurring Batch Jobs
The current functionality for importing foreign currency exchange rates allows you to select either Today or a Date Range, defined by a start and end date defined in the job parameters. In order to pull single average rate for a period, you enter the start date and end date of the range, select the Single Rate for Date Range button and run it.
Unfortunately, there is no way to set up a recurring batch job to run on the 1st day of a month and pull rates for the preceding month automatically, as the original data parameters are hard coded. It would be very helpful if the Date Interval functionality used in other areas of the system. Batch jobs for running reports, for example the Ledger Transaction List, support Date Intervals in the Parameters. This functionality should be available across all batch jobs where a date range is an option. If the selection of choices between Today and a Date Range is what prevents that from being implemented, I'd suggest going to purely a date interval method, and Today can be easily defined as a date interval choice.
-
Standardize the Use of Date Interval Supporting Date Range Parameters On All Reports
Currently some of the standard system reports, for example Gross Margin By Customer, only support filtering to a specific date range by entering a date range to the "Records to Include" filter prior to running the report. This prevents using recurring batch functionality, as there is no mechanism to specify a new date interval on the Recurrence.
A better method would be to move the date range selection to the report Parameters and support selection of a Date Interval definition there. This would allow the date range to dynamically update every time a recurring report is run, for example a report that is run routinely on the first day of the work week or the first day of a month.
-
Allow Different Legal Entities on Purchase Order Lines and Accounting Distributions
In many businesses, each physical location will be set up in D365 as a separate legal entity. There needs to be a method by which a centralized purchasing agency (at the headquarters, for example) can create a Purchase Order and then on the PO Lines, specify per line which legal entity the accounting (expense) needs to be posted to in General Ledger. This should be possible via two methods:
- Switching a PO line to a different legal entity switches Item Numbers and Product Categories available to those of the target entity, driving the correct GL and inventory posting. This allows centralized purchasing of both stocked and non-stocked items.
- Using Distribute Amounts to ONLY modify the accounting posting allows posting to different legal entity. This should only be allowed on non-stocked items, so that inventory cannot be posted to one entity while accounting posts to a different one. This would also allow accounting, by individual line, to be split across multiple legal entities by percentages.
In AP, it is possible on invoice journal invoices to make the Company field available on lines and the system automatically switches to the target company's account structure and chart of accounts, and assuming intercompany accounting is set up correctly, the system will automatically post the needed due to/from intercompany transactions. This is basically to add similar functionality to invoices created through purchase orders.
You’re offline. This is a read only version of the page.
