AI, in your work.

What the change introduces

Microsoft has merged two settings into BCApps that control whether specified credit memo and invoice correction flows restore quantities on originating orders in Microsoft Dynamics 365 Business Central. The work was merged into main on November 6, 2026, through pull request #11256, associated with commit 3452841.

Sales & Receivables Setup covers sales credit memos and sales return orders. Purchases & Payables Setup covers purchase credit memos. Each area has its own independent setting.

When enabled, the settings preserve existing restoration behaviour: shipped or received, invoiced and pending quantities are updated according to the reversed quantity. When disabled, the covered flows leave shipped or received and invoiced quantities unchanged on the originating order.

Enabled by default, with differences between operations

Both setup tables initialise the setting as enabled. The upgrade routine also enables it on existing records. The change is designed to retain previous behaviour until the configuration is changed.

The scope described in the commit distinguishes these operations:

Prompts and prepayments are also involved

The setting governs confirmations and warnings specific to restoration. The sales correction and purchase correction routines check the configuration before certain confirmations. Other checks for the operation remain in place.

Updating quantities requires locating the originating order line from the invoice. In the reviewed paths, reconciliation of deducted prepayments and recalculation of the prepayment amount to deduct continue even when restoration is disabled. The prepayment tests include cancellations with quantities preserved and checks on the released prepayment deduction.

The choice also retains the prerequisites for correcting or cancelling an invoice. For example, Microsoft's sales documentation maintains restrictions on the direct actions when an invoice is partially or fully paid.

Synthetic example: an order for ten units

Consider a sales order for ten units, with four shipped and invoiced and six remaining to ship. The invoice for those four units is cancelled, and the originating order still exists. To isolate the effect, this example excludes prepayments, advanced warehousing and extensions.

The table shows the expected order quantities according to the reviewed logic. Nexo supplied the numbers; they are not runtime results. The partial sales invoice correction tests check that shipped and invoiced quantities remain unchanged when restoration is disabled. The purchase tests contain an equivalent scenario for receipt and invoicing.

Nexo's interpretation and functional checks

Our interpretation is that this configuration makes a process decision explicit: whether correcting an invoice should make quantities pending again on the order. One team may need to continue the transaction from the originating document; another may want to preserve its quantities after the correction.

To evaluate that decision once a version containing the change is available, we suggest these checks in a test environment:

• Repeat a partial invoice correction and cancellation with the setting enabled and disabled, comparing order quantities and the documents created.
• Test sales and purchase return orders and the Undo Shipment or Undo Receipt actions separately, respecting their differences in scope.
• Include prepayments and installed extensions, checking quantities, deducted amounts and the ability to continue invoicing.

Availability and limits of this review

As of November 8, 2026, the merged pull request carries the Version 30.0 milestone. This identifies a development target, but the consulted sources do not establish a distributed build, a general availability date or the setting's presence in a particular tenant.

Nexo has reviewed published code and test assertions. It has not compiled the application or run the scenarios in Business Central. Those tests document the behaviour intended for verification; their outcome in a particular installation and interaction with extensions are outside this review.