Martha Padilla

The “Collection Process History” on the Collection Process Automation screen does not display all the configured activities of the collection process: email, collection letter, and call activity. When the batch job is completed, the collection process history displays only the few activities,

This history should show all the activities generated, emails, calls, and collection letters, without omitting any type of activity

When a Fixed Asset is transferred with different derivative books and layers, the transfer of the financial dimensions must also be carried out in all the derivative books and layers, for their correct balance.

Since the transfer is not currently transferring for the derivative books, only the main book,

Deliverable associated: 800773

Feature Request: Option to Cancel Termination Proposals that have not been registered

Currently, the standard functionality allows for the reversal of lease termination once the proposal has been posted. However, there is no option to delete or cancel a termination proposal that has not been posted. This request is for the addition of functionality that allows users to cancel or delete an unposted termination proposal in case it has been created but not yet published.

The system presents an issue when attempting to set default addresses for a customer with multiple purposes (such as Delivery and Invoice). Even after selecting new addresses for each purpose and confirming the changes, only one of the default addresses is actually updated. This prevents multiple default addresses from being assigned simultaneously,.

Description:

When you generating new timesheet periods, the first week in the worker's period isn't updated correctly. and you must manually rerun the "Update Worker Periods" process. 

Requirement:

The period update process should happen automatically when you enable the check box corresponding to period update, which exists when new periods are being created.

When attempting to split project transactions to subprojects using 2 decimal precisions, and totaling 100.00%, receiving the error "Total quantity for all adjusted lines must equal the quantity in the original line, This is when the Qy to be distributed are values ​​with 2 decimals,

Customer manages hundreds of transactions with amounts rounded to two decimal places. It is necessary to allocate these expenses across multiple subprojects, sometimes >100 subprojects, each of which will be capitalized as Fixed Assets. 

Currently, the Subscription Billing module in Dynamics 365 Finance does not allow for a direct reversal of revenue recognition from the voucher generated by the recognition process. This creates a significant limitation when users need to correct recognition errors or reassign revenue to the correct accounts.

When the "Summarize recognition journal" option is enabled, the system consolidates multiple recognition lines into a single voucher, using the first available billing or deferral schedule number. This consolidation makes it difficult to trace and select specific transactions for reversal, as it’s not easy to identify which lines belong to which schedule.

Proposal: Introduce a feature that allows users to reverse revenue recognition directly from the voucher, without needing to filter through multiple combinations or split the process into parts. This option should:

• Be accessible from the voucher interface.
• Allow selection of the recognition period or date to reverse.
• Automatically reassign revenue to the correct accounts upon reprocessing.
• Be compatible with summarized vouchers generated by the journal summarization option

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

Actual Outcome:

Currently, when a project transaction is adjusted in Dynamics 365 Finance, the vendor's name and id from the original transaction is removed—even though the original transaction included this detail. This behavior differs between expense and item transactions, and neither case retains the vendor reference post-adjustment.

Expected Outcome:

The vendor's name and id from the original transaction should persist even after adjustment. This would ensure consistency across expense and item transactions and maintain the integrity of vendor-based reporting. Ideally, the system should retain the vendor reference in both the adjusted and reversing entries or at least provide a configuration option to preserve this metadata.