Dynamics 365 Finance

Currently financial tags given on journal header or vouchers are not copying on withholding tax transactions generated for withholding tax deducted at the time of vendor payment. It would be really helpful if financial tags are copied by default from the journals on to the withholding tax transactions too as this would help customers to have a better reporting capability and consistency across trasactions.

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.

When adding controls to a form pattern in the designer, most controls follow a consistent naming convention. For example, when adding an ActionPaneControl, the label displayed is Action Pane, and for a GroupControl, the option appears as Group. However, in the case of the QuickFilterControl, the designer displays the full control name—Quick Filter Control—instead of just Quick Filter, which breaks the naming consistency.

This inconsistency can be confusing, especially for new developers or when working quickly across multiple form patterns. Ideally, Quick Filter Control should be labeled simply as Quick Filter to match the established pattern and improve usability.

The Customer free text invoice data entity is a denormalised entity for creating Accounts Receivable/Sales Ledger invoices that doesn't provide all functionality available within the UI. Within the UI, when creating an AR invoice, it's possible to select from the customer's recorded addresses which should be used as the Invoice address (to which the invoice is sent) and/or the Delivery address (to which the product/service should be provided). The data entity would be more useful if it included fields to specify the two address fields, ideally by a user-meaningful value like Name or description, but Address location Id might be sufficient for some use cases. If these fields are blank, the current functionality to use primary address could be the default position, but if populated, DMF should change the address on the invoice header

When a retail statement is calculated, document attachments are an available option. However, when the statement is approved/posted it is deleted from the retail statement table and replaced with entries in accounting tables. What is desired is a way to attach document files to a calculated retail statement and transfer/link that document reference to the posted statement table(s).

When printing the Vendor Account Statement Report, the Assessment date is not printed in the file. Is it possible to include this field?

When printing the Vendor Account Statement Report, the Assessment date is not printed in the file. Is it possible to include this field? 

Recently we ran into an issue where a really big Journal batch(over 36000 lines) had to be reversed. Since it forces you to use batch processing we waited for over 4 hours. There was no confirmation of posting/reversal or any exception based reports. I am aware of the infolog within job history for the batch however it would save a ton of time if we have an option to print or access a report for a posted/reversed journal to access voucher by voucher success/failure report.

Many organizations require the ability to audit any user that performed read operations on certain sensitive tables like data that contains protected health information or sensitive banking data. Dynamics Finance does not have any built in read audit capabilities along this line.

You reached out requesting that audit trail attributes be included in Microsoft's SOC reports, as these are important from an annual system audit perspective.

The SOC report content is determined by Microsoft's compliance and engineering teams. Suggestions for content changes fall outside the scope of the Break/Fix support model, which is focused on resolving runtime issues and technical problems.