The report ‘Vendor balance list’ (Accounts payable > Reports > Status) display the wrong main account, if the vendor Group was changed. Then the ‘Vendor balance list’ do not display the ‘Vendor balance’ of the vendor transactions. Instead, the main account from the ‘Vendor posting profil’ will display.
The same issue arises with ‘customer balance list’ too.
Document Routing Agent as a Windows Service - Allow printing of checks and other document requiring custom margins
In the article below we learn that we have to "jump through hoops" to print documents with custom margins (such as checks). We find this to be unacceptable. Please enhance the document routing agent so that it can handle documents with custom margins (just like any other document).
Documents that require custom margins
When the Document Routing Agent runs as a Windows service, document reports, such as checks, that require custom margins can't be printed directly to network printers. Instead, the Document Routing Agent automatically routes those document to a target folder. New configuration properties in the application's Settings dialog box let you define the target location for document reports that require custom margins.
When the Document Routing Agent runs as a desktop application, it continues to take advantage of Adobe Reader to spool the document to the shared printer device that is selected in Microsoft Dynamics 365 for Finance and Operations, Enterprise edition. To handle scenarios where documents that have custom margins must be printed, we recommend that you install the Document Routing Agent in multiple locations. Then install the printers that will handle those documents only on the Document Routing Agents that will run in desktop application mode. Alternatively, use a post-execution process to pick up the files in the target directory and direct them in the appropriate manner.
Source: Run the Document Routing Agent as a Windows service (as of 9/13/2017)
On a PO invoice usually the only reference you have is a PO number, and you do not have any detailed information which is currently needed with import of PO vendor invoice lines. This results in that you have to provide the most pertinent information with data provided from operations in order to import the invoice using Vendor Invoice Automation.
There should be support for wholesale defaulting of PO lines to invoice lines or product receipt, in this way there could be minimal invoice information and you do not need to access Operations data in order to do the import of the invoice.
In addition there should also be a function where you can create a purchase order from the imported pending invoice, and also a form for vendor invoice lines that failed to import (similar to existing 'Vendor invoices that failed to import')
Similar to purchase order product receipt correction functionality. It will be nice to have a vendor invoice correction functionality. This functionality should allow adjusting qty or unit price or both at the invoice line. Such Functionality will be usefull in handling debit memo or credit memo scenarios where product return is not applicable.
Currently, vendor bank accounts and method of payments are maintained at header level for individual vendors. It would be nice to have bank accounts and method of payments assigned to individual vendor addresses. If a vendor has multiple pay sites i.e. multiple addresses with different banking and method of payment information, bank account and method of payments linked to the address can be used to create remittances. A lot of times this is a requirement from large vendors to process electronic payments. Setups defined at the address level should override header level setups.
It would be nice to have a configuration parameter to allow setting up the vendor invoices to be automatically posted to the next open period when the Posting date falls into an on hold period or a period with AP module closed. This is helpful especially when auto posting is a workflow step and workflow approval takes time. Currently the system will prompts a message to the users (some approvers may not be accounting staff and don't understand what it is) and auto posting step in the workflow will fail with stopped error.
The similar feature is already available for expense report and time sheet.
When vendor invoices are imported from data management (with OCR or scanner process), there is no automatic receipt matching.
If the purchase order has already been received and product receipt information is part of pending invoice imported, match status is not automatically updated.
Invoice has to be edited to have match status refreshed.
The idea will have an option (or batch) to automatically match the pending invoice is purchase reception.
This idea is related with unbalancing of Vendor Aging and TB balance if a prepayment functionality of PO has been used.
-AP Parameters should be removed of Prepayment posting profile.
-PO Created, Prepayment tagged with PO.
-Prepayment invoice posted via PO.
-Voucher gets DR Advance to suppliers account and CR Trade Payables account.
-Vendor aging at this stage gets negative balance too.
-Prepayment paid via payment journal journal.
-Voucher gets DR Trade Payables account and CR Cash / bank.
-Vendor aging at this stage not showing any amount however in my TB i have a advance given to vendor getting displayed.
-Query is to show this possitive amount in Vendor aging as well so it can be matched with TB.
When posting a purchase invoice in the Invoice Register it is mandatory to fill a worker in the field "Approved by". The worker has to be selected manually and it is only possible to select a worker that has a deployment in the company you are working in at that moment.
1. It is not logical to make this field mandatory as it has nothing to do with the (formal) approval process in the organisation.
2. It is not logic to limit the selection of workers only to the workers that has a deployment with that company. Suppose you have a multi-company environment where accounting / AP clerks work in multi-companies whereas they have only a (legal) deployment with one of the companies.
1. Remove the mandatory character of the field
2. Make it possible (via a parameter) to select workers only from the specific legal entity or from the complete worker table
3. Let the field "Approved by" automatically be filled with the worker related to the user.
The document routing agent requires for an Azure token to be generated every 90 days in order to remain operable according to the documentation (and subsequent follow up discussions with Microsoft Support to confirm this), to keep the service working requires several manual steps to be performed by a user -
Refresh the Azure service token
- Azure authentication tokens must be refreshed every 90 days while the Document Routing Agent is running as a Windows service. To refresh the service token, start the client, and then sign out and sign back in by using the menu items.
This is not an acceptable solution for such a business critical function, and should be resolved.