Dynamics 365 Finance

There is currently a limit of 20 files that can be uploaded simultaneously in invoice capture. It would be useful to increase this limit to at least 50.

Currently, in the Invoice Capture functionality of Dynamics 365 Finance, the main invoice list view only displays the vendor number, requiring users to drill down into each invoice to verify the vendor name. This limitation creates operational friction, especially when handling multiple invoices from vendors with similar codes or when quick validation is needed.

Proposal: Add a visible column in the main Invoice Capture view to display the Vendor Name alongside the vendor number. This information is already available in the system and can be retrieved from master data or OCR results, but it is not currently shown directly in the list view.

justification:

• Improves efficiency for accounts payable teams by reducing unnecessary clicks.
• Minimizes errors in invoice-to-vendor assignments.
• Enables faster visual validation during bulk invoice reviews.
• Aligns the user experience with other areas of the system where vendor names are shown by default

Many customers ONLY want their customer payments to be automatically settled IF the amount on the bank statement line = to the (sum) of amounts of the referenced invoice(s). Same as with SKG isv. However, current functionality does not support this idea. It can only automatically settle based on amount if only 1 invoice is referenced by the customer, but this is not common as most customers pays multiple invoiced at once. Theoretically, you want to use the following logic in the matching rules

• Invoice IN Reference No
• Invoice amount in transaction currency = Amount in transaction currency

The second bullet point is the logic that does not fully work in the current bank module. Current logic will only work if the customer references 1 invoice. When 2(+) invoices are referenced, the rule will not work as it will only look at the first invoice referenced. Meaning, this rule will never correctly settle if customers reference multiple invoices. I want to be able to use this logic for customers who pay multiple invoices at once, as this happens more often. Many clients ask for this functionality.

I would like to see an update in this functionality as I believe this is a flaw in the design.

It should be possible to view accounting entries (vouchers) on the bank reconciliation worksheet screen.

Today, it is necessary to go to other tables and manually search for the corresponding voucher, which consumes a lot of time for accountants.

Title: CRITICAL: Support Intermediary Concept for Malaysian e-Invoicing - Current Limitation Defeats Globalization Studio Purpose

Severity: High - Major Business Impact

Description: The current requirement for each legal entity to maintain separate Client ID, Client Secret, and Digital Certificate for Malaysian e-Invoicing integration directly contradicts the purpose of Globalization Studio and creates unsustainable costs for multi-entity organizations.

Critical Business Impact:

• Cost Impact: With digital certificates costing RM1,500 per year per entity, organizations with 20-50 entities face annual costs of RM30,000 - RM75,000 just for certificates
• Defeats Globalization Studio Purpose: Globalization Studio is designed to centralize and streamline compliance processes, but this limitation forces decentralization
• Administrative Burden: Managing 20-50 separate certificates, renewals, and credentials creates unnecessary complexity
• Competitive Disadvantage: Other ERP systems and the Malaysian e-invoicing system itself support intermediary concepts

Current Limitation:

• Forces each legal entity to acquire separate digital certificates (RM1,500/year each)
• No support for intermediary/shared service center model
• Contradicts the centralization benefits of Globalization Studio
• Creates unsustainable costs for multi-entity organizations

Proposed Solution: Urgently enhance Malaysian e-Invoicing integration to support:

1. Intermediary entity configuration allowing one set of credentials for multiple legal entities
2. Alignment with Malaysian LHDN's support for intermediary submissions
3. Leveraging Globalization Studio's centralization capabilities
4. Single digital certificate usage across multiple legal entities

Financial Impact: For an organization with 30 legal entities:

• Current approach: RM45,000/year in certificate costs alone
• With intermediary support: RM1,500/year
• Potential savings: RM43,500/year

Risk of Not Implementing:

• Organizations may seek alternative ERP solutions that support intermediary concepts
• Defeats the value proposition of Dynamics 365's Globalization Studio
• Creates barrier to adoption for larger organizations
• Inconsistent with Microsoft's cloud-first, centralization strategy

Regulatory Alignment: The Malaysian LHDN (tax authority) already supports and recognizes the intermediary concept for e-invoicing. This enhancement would align D365 with existing regulatory frameworks.

Currently, when transferring to a Pending Vendor Invoice in D365, the Invoice will be created using the Due Date that was read in Invoice Capture.

We need the Invoice's Due Date in D365 to be calculated based on the Payment Terms which were negotiated with the Vendor, so either taking them from the PO or from the Vendor itself in case of non-PO.

It could be a configurable option.

Thank you!

At the moment if you pay the second schedule line payment of the leasing and also the second line of the lease liability amortization schedule and then update the book version, the new book version shows a mismatch between the two schedules. The logic of the Lease Liability Amortization schedule will have to replicate the same logic of Payment Schedule.

When trying to post cost invoice in invoice approval journal where are two project type of lines (credit and debit) and two different sales tax codes used (VAT25,5 and VAT0). Only the amount of VAT will be paid for the vendor. Posting will end up in error: Tax direction must be specified on ledger account . No specific ledger account is mentioned in the warning. VS debugger shows that validation try to find sales tax direction for "empty" ledger account. Posting will passthrough when GL Sales Tax parameter Tax direction requirement is switched off. All needed ledger accounts have tax direction. SingUp Software's ExFlow AP automation is used. Posting of approval journal is standard functionality. Tax direction validation in this case was working in version 10.0.36 but not anymore.

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.

When a Project PO is created, it includes the tax amount. However, upon confirming the PO, only the net amount is committed to the project budget, and the tax amount is not. The total amount, including tax, is updated in the consumed budget once the invoice is posted based on the project line property.

The expectation is that the tax amount should be included in the committed budget along with the net amount once the PO is confirmed project line property.

This is to prevent budget overlap if another user creates a different PO in the same project.