Ian Luu

In real-world business scenarios, a physical bank account often processes transactions in multiple currencies.

However, the current system only supports bank statement reconciliation when the currency of the bank statement transactions matches the default currency of the corresponding bank account in the system.

When users attempt to reconcile bank statements containing transactions in currencies different from the bank account’s default currency, the system returns the following error:

"Bank statement currency is not consistent with bank currency."

Ideally, the system should support reconciliation of bank statements containing transactions in non-default currencies, without requiring users to create and maintain separate bank accounts for each currency.

In the header section of the Purchase Order invoice within Finance and Operations (FnO), there is a Purchase Order drop-down field that enables users to select a single Purchase Order (PO).

Many organizations rely on this field containing a PO number as a condition within their invoice posting workflows. Specifically:

• If the Purchase Order field is left empty, the invoice is treated as a non-PO invoice.
• If the field contains a PO number, the invoice is processed as a PO invoice.

Currently, the system does not support the scenario where an invoice—transferred from Invoice Capture—is associated with multiple POs. In such cases, the Purchase Order drop-down field in FnO remains unpopulated, as no PO number is applied automatically.

This gap in logic presents a challenge for organizations attempting to automate PO invoice posting via workflow, as the absence of a PO number in the field prevents the system from correctly identifying the invoice type.

Proposed Design Enhancement:

To align with the manual process in FnO, the system should populate the Purchase Order drop-down with one of the associated POs—preferably the first PO in the sequence—when a multi-PO invoice is transferred from Invoice Capture. This approach reflects current user behavior during manual entry, where the first PO added to an invoice is automatically set in the drop-down field.

Implementing this enhancement will enable businesses to maintain workflow automation for PO invoices, even in multi-PO scenarios.

Currently, the Project Transaction Adjustment functionality in Dynamics 365 Finance and Operations does not support batch processing. This limitation poses challenges when users need to adjust a large volume of project transactions, as the process may be interrupted due to browser session timeouts or database connection issues.

To mitigate these risks and enhance usability, it is recommended that a batch mode option be introduced for this function. Enabling batch processing would ensure greater reliability and efficiency when handling high-volume adjustments.