Katie Nguyen

Invoice capture - Cost Invoice - Need to support multiple lines in Tax Invoice journal.

Currently there's no approval workflow for customer and supplier netting journal.

We request to have a workflow implemented for the netting journal.

The business impact is that we have an audit requirement that states a user should not be able to create and post a journal without approval from one or more people. For netting journals, we are unable to comply with this requirement and we will need to explain this to our auditors for our FY 2025 audit commencing in April 2025.

The issue reported pertains to the Print management destination set as SharePoint. The customer utilized the Batch invoicing feature in Accounts Receivable to process multiple sales orders and send the resulting invoices to SharePoint. However, when handling a high volume of sales invoices, some failed to export to SharePoint without any record in the system. This required significant manual effort from users to identify the missing invoices. A table or feature is needed to track this data within the system effectively.

Currently in Microsoft Dynamics 365 Finance, there isn’t a single out-of-the-box report that directly combines all the specific details such as the Withholding Tax (WHT) settlement voucher, settlement date, and WHT transactions—in one prebuilt format. We would like to have a standard report that includes all the details for improved reporting purposes.

Currently, with prebuilt invoice model, system captures vendor name from logo. However, it's not picking full logo to derive vendor name. In addition, the AI should be improved to better identify the vendor name on captured invoices, as the accurate vendor name is not always the one in the logo.

Ideally, there should be a parameter in Invoice capture that allows to use vendor name from the synced vendor master record so that the vendor name is always correct.

When an initial e-invoice submission fails, the status in the Electronic Document Submission Log remains “Failed”. Even after a successful related submission, the original log entry does not update. Users must manually navigate to Inquiries > Related submissions to find the latest status. This makes Submission status unreliable and time-consuming to use for tracking submission outcomes.

We would like to propose a design change request that involves either:

• A status override or chaining mechanism in the submission log to reflect the latest related submission.
• A visual indicator or link in the original failed submission pointing to successful related submissions.
• A consolidated view that merges submission history for the same document.

Customer adds a charge code in a sales line and proceed with posting sales invoice. After invoice posting, it’s observed that with current design, charge is recorded in voucher transactions and can be found at sales invoice line, however, it gets deleted in sales order line.

We would like to have charges remained on sales order after invoice posting so the invoice total balances to the line totals.

The ‘Approved by’ field at line level of vendor invoice journal is defaulted to the creator of the journal. The same info in Approved by field shows in Vendor open transactions report, which confuses users as it can be understood that the creator is the one approving the journal.

We request a design change to the 'Approved by' field so it can populate the correct person who approves the journal.