-
Invoice coding ability in Invoice Capture App
The Microsoft Invoice Capture Apps can process a "Cost Type" of invoice where it can generate an invoice journal in accounts payable. The journal posts all the expense to the default expense account that is associated with the vendor.
There is is currently no ability to select another GL account (and dimension combination)
In addition expenses cannot be allocated to other legal entities especially in the case of larger organization with multiple legal entities or shared service scenarios.
Users would literally have to re-create all the necessary lines for the expense allocation to one or multiple legal entities in the journal.
A more robust invoice capture solution would allow users the ability to to allocate expense to more than one expense account (and dimensions) as well as more than one legal entity.
-
Dimension Link - Default dimension value on billing schedule line, as setup in the dimension link.
The dimension link feature allows for a selected dimension value to be defaulted from the Site anytime the latter is selected on a transaction such as a sales order or a purchase order. However, this feature is not consistent across the modules. For example, if a site (with a dimension link) is selected on a billing schedule line, the corresponding dimension value is not defaulted.
This suggestion is to request Microsoft to standardize the dimension link feature across all the modules - especially the subscription billing module.
-
Cost invoice transaction processing in Invoice Capture
Each cost invoice captured by the app is currently created as a sperate Invoice Journal in D365 Finance - i.e. a one-to-one relatonship between invoice an Invoice Journal.
This causes a lot of records on the invoice journal grid and makes it hard to navigate and search for a specific journal. In addition the description on each journal is vague which makes the task of looking for a particular journal even more difficult.
Suggestion: Group all cost invocie over a given period of time in one journal - where each invoice is a separate voucher within the journal. The attachments would be at the voucher level.