It is common for our clients to request the ability to enter vendor invoices against projects using the Open in Excel experience. This is because a vendor invoice can have hundreds of lines which all need to be coded to different projects. However, this functionality is not available in the product. Consider these facts: • The Vendor Invoice Journal (standard UI) does not support Intercompany Project Transactions at all • The Vendor Invoice Journal OData template does not support use of the Account Type = Project • The Project Expense Journal (standard UI) does not support Intercompany Project Transactions at all • The Project Expense Journal OData template does not support Intercompany Project Transactions because of the point above • The Vendor Invoice OData template does not support Projects because it does not include the related table VendInvoiceInfoLine_Project just like it doesn’t support Fixed Assets because it does not include the related table VendInvoiceInfoLine_Asset. So, in conclusion, • The customer cannot NOT use the Vendor Invoice Journal for any vendor invoice data entry (AP > Invoices > Invoice Journal). • The customer must use the Vendor Invoice (AP > Invoices > Pending vendor invoices) for all project expenses that originate from a vendor invoice, however, these must be entered manually. • The customer can use the Project Expense Journal if they desire for non-intercompany project expenses when there is a benefit due to large volumes of data. We would simply like to ask Microsoft to add the VendInvoiceInfoLine_Project to the datasource in the Vendor Invoice Line data entity. Ideally, this data entity should support all related child tables including the VendInvoiceInfoLine_Asset table as well.