Dynamics 365 Finance

When attempting to reconcile a bank transaction in Dynamics 365 Finance, an accounting entry from a prior fiscal period remains pending due to minor decimal discrepancies between the original and newly entered reconciliation entries. These discrepancies typically range between $0.01 and $3.00. Please note that this fiscal period is on hold.

Upon initiating the reconciliation process via the navigation path:

Cash and bank management > Bank statement reconciliation > Bank reconciliation

the system throws the following error:

Error Message:

Voucher 6003: Fiscal period for 1/6/2025 is not open.

This indicates that the system requires the accounting period associated with the original entry to be reopened, even though the discrepancy is minimal and purely decimal-based.

Expected Behavior

Given the negligible nature of the decimal differences, the system should allow reconciliation without requiring the reopening of a fiscal period on hold. Ideally, there should be a configurable parameter within:

Cash and bank management settings or Bank reconciliation page

that permits tolerance for minor rounding differences during reconciliation.

Warning The transaction has been reversed previously and cannot be reversed again when a previous reversal exists. If you continue, the previous reversal itself will be reversed. The transaction can then be reversed again.

Business value:

To avoid previous reversals from being reversed again.

To avoid timeconsumption.

To avoid multiple transactions.

To avoid financial irregularity.

To secure data quality.

In many business scenarios, users need to cancel a customer invoice due to billing or accounting errors, but without reopening the associated packing slip.

Currently, in standard D365 Finance & Supply Chain Management, when canceling a posted invoice, the system automatically affects the packing slip — reversing the shipment — even when there is no physical change to the delivered goods.

This creates unnecessary operational complexity and confusion in logistics tracking, especially when:

• The goods were already physically delivered and must remain “Delivered”.
• The cancellation is purely financial (for example, incorrect price, wrong tax code, or invoice issued on the wrong date).

Requested enhancement:

Add an option (parameter or dialog checkbox) to:

“Cancel posted invoice only — do not reopen or reverse packing slip.”

The system should then:

• Create the reversal (credit note) for the invoice only.
• Keep the delivery status unchanged (Delivered).
• Prevent re-processing of the shipment.

Business impact:

This feature will improve audit control, simplify accounting corrections, and align with real-world logistics flows where financial and physical processes are decoupled.

Currently, when the field ‘Confirmations, delivery and invoicing on hold’ = ‘Tax Invoice’ is set on the Customer Master, sales order invoices are blocked from processing, while other transaction types such as Customer Free Text Invoices and Customer Payment Journals are allowed to process under certain conditions.

For example:

• A credit Free Text Invoice processes successfully, but a debit Free Text Invoice fails.
• A credit Customer Payment Journal processes successfully, but a debit Payment Journal fails.

This behavior makes sense as it prevents increasing the customer’s balance while allowing reductions.

However, credit Sales Order Invoices, which also reduce the customer’s balance, are currently blocked from processing. 

Suggestion: Sales Order Invoices—especially credit transactions—should be allowed to process when they reduce the customer’s balance, just like the other transaction types. This would ensure consistency across invoice and payment processing logic and reduce manual workarounds.

When a customer has the mandatory credit limit set to Yes, the system should display the Ordered, Credit Limit, and Remaining Credit Limit amounts, even if the credit limit itself is set to zero. This is because the mandatory setting enforces credit limit calculations. In this scenario, the customer is treated as prepaid, meaning orders should not proceed until payment is received. Once payment is made, the customer can place orders up to the paid amount. Since the standard functionality already checks the credit limit against the prepaid amount (as the payment creates a negative balance), it makes sense to reflect these calculations in the customer balance. This behavior differs from a case where the credit limit is not mandatory and simply left at zero.

When the customer pays the balance between an invoice and a credit note, and mention both in the payment reference of the bank statements, the credit note will not be settled .

currently It will result in a open balance of the vendor invoice for the credit note amount and an open unsettled credit note transaction.

For example

• Invoice 100
• Credit note -20
• Payment amount 80 which is the balance between invoice and credit note.

Invoice is settled for 80, open balance of 20

credit note is not settled, open balance of -20

Idea to settle the credit note and the invoice amount matching the payment amount

For example

• Invoice 100
• Credit note -20
• Payment amount 80 which is the balance between invoice and credit note.

Invoice is settled for 100, no open balance

credit note is settled, no open balance

OCR > Setup system > Manage vendors

Out-of-the box there is limitation on sync by selection - only 40 records can be chosen for a manual sync. A lot of customers do not wish to sync employees and contractors due to GDPR issues (name and personal address) as they are in D365 FO as both workers and suppliers (payment of expenses and accounts payable invoices).

This functionality should be extended to a custom automatic sync where you deselect criteria for the sync e.g. vendor groups, etc. The sync should be automatic similar to sync all option.

In addtion, pls bring functionality to delete vendors in "Manage vendors" via the Front user interface/also Excel (truncate) so unwanted suppliers can be removed.

Thanks

Thanks

In Dynamics 365, the commitment cost of a project budget currently reflects the net amount (including discounts) when the accounting configuration includes a designated account for discounts. However, when the related purchase order (PO) is consumed, the discount is excluded, and the budget consumed reflects the full amount of the PO.

For example:

A PO is confirmed with a line item of USD 1,000 and a 10% discount, resulting in a net amount of USD 900. At this point, the budget commitment is recorded for USD 900.

However, when the invoice is posted, the budget consumed is recorded for the full USD 1,000, which is the expected behavior.

The request is to align the commitment view with the consumed budget view, meaning that the commitment cost should also reflect the full amount (USD 1,000), without applying the discount.

This adjustment would ensure consistency in budget tracking and better reflect the actual financial impact of the PO throughout its lifecycle.

Issued Reminder: There is no option to select 'Show Not Due Amounts'.

When you want to send an e-mail (button: Send by Email), see also e-mail attachment

Best regards,

Daniël van den Hoek

4PS by Hilti

Under the current system design, enabling the parameter “Summarize amounts in bank account” within the journal name setup disables the Post and Transfer function, making it unavailable for user selection.

Design Change Request:

We recommend enhancing system compatibility by allowing the “Summarize amounts in bank account” parameter to function in conjunction with the Post and Transfer feature.