Rui Zhong SUPPORT ESCAL ENG

From the end user’s perspective, there is a column in the Purchase Order line (as well as in some other documents) called “Budget Check Results.” This is a very important field that displays the budget validation status, with data resources being ProjBudgetStatus and budgetSource. However, after partial invoicing, the Budget Check Result field becomes blank, leading to inconsistency and confusion for the user.

Need to maintain the budget status.

Need a standard report or inquiry to compare the total amount of a Purchase Order with the Invoice amount for a Closed Purchase Order.

There is no standard report or inquiry available to compare the total amount of a Purchase Order with the Invoice amount for a Closed Purchase Order. This is a key point for the internal audit team to ensure that the procurement procedure has been properly enforced. Without this report, the end user would need to perform many manual tasks to double-check each transaction.

As it stands, the information provided by the current AP/AR foreign currency revaluation is somewhat limited. For a more comprehensive and supportive client operation, it would be ideal if the simulation could include the 'Invoice Reference' field. Additionally, incorporating details on the 'Voucher & Transaction' that will be posted would significantly improve the utility and accuracy of our financial reporting and analysis.

The requirement is for a comprehensive solution that facilitates project-based manufacturing for organizations engaging in intercompany trade, with a specific focus on tracking actual costs within the manufacturing entity or across all entities involved in a project.

The current off-the-shelf solution does not adequately cater to the needs of businesses involved in intercompany transactions, especially those seeking to precisely monitor actual costs at the manufacturing level or aggregate cost data across all participating entities in a project.

Consider the following practical scenario:

• The client manages two distinct entities: a Sales Entity and a Manufacturing Entity.
• The Sales Entity launches a Project and places an intercompany Purchase Order with the Manufacturing Entity.
• Subsequently, the Manufacturing Entity issues an Intercompany Sales Order and undertakes the creation of one or more Production Orders to fulfill the product requirements.

Unfortunately, the existing solution is not equipped to effectively track the actual costs generated by the manufacturing entity or to compile a comprehensive cost analysis for all entities participating in the project.

In real-world business contexts, particularly in countries such as India and Poland, vendor invoices frequently have multiple sales tax lines. To effectively manage this, the Invoice Capture feature needs to be upgraded to have the capability of combining these diverse sales tax lines into a single, unified tax amount.

Currently, the budget control statistic inquiry offers two options for 'Carry-forward amounts.'

1) Not included,

2) Included,

However, for a more targeted financial analysis, there is a need to implement a feature that allows for the only display of 'Carry-forward amounts'.

The Subscription Billing-Revenue Allocation needs to support combining Non-Revenue Allocation Sales Orders (SO) and Revenue Allocation Sales Orders into a single SO Invoice.

Currently, the Subscription Billing-Revenue Allocation does not support this functionality. The system will display an error message in the following scenario:

1. Create two sales orders, one with Revenue Allocation and the other without.
2. Create a single invoice that includes both sales orders and set the Summary update for the Invoice Account.

We need the ability to add workflow comments when submitting an expense report in the Expense Management PowerAPP. Currently, there is no pop-up field for submitting an expense report, which differs from the behavior in the D365FO UI. Workflow comments are crucial for the "Approver" to review and validate the expenses.

We need the ability to add expenses directly when creating an Expense Report in the Expense Management PowerAPP. Currently, the functionality only supports creating an expense first and then selecting it to create the expense report. This behavior differs from the D365FO UI and the old mobile app.

We need the ability to automate Partial Ledger Settlement. As the current functionality stands in the build 10.0.43, Process Automation for Ledger Settlement does not support Partial Ledger Settlement. Implementing automatic Partial Ledger Settlement could significantly enhance the efficiency of customers' daily operations.