Hi team.

Recently, we recently receive the ticket about concern "Prevent Skipping Numbers in Non-Continuous Number Sequences". This is a request to optimize the behavior of number sequences in Dynamics 365 for Finance and Operations. The current design for non-continuous number sequences may skip numbers when certain actions (e.g., cancellation) occur. This behavior is by design as stated in the official documentation, but it does not align with some customers’ operational expectations.

A customer has raised a concern that when using non-continuous number sequences for purchase orders, cancelling a purchase order skips the number (e.g., sequence starts at 1000, cancels the PO, and continues at 1001, skipping 1000). The customer requires that even with a non-continuous sequence, the system should not skip numbers, ensuring better traceability and compliance with their business processes.

Customer Scenario (with repro steps):

1. Configure a non-continuous number sequence starting at 1000 for Purchase Orders.
2. Create a new purchase order.
3. Cancel the purchase order.
4. Create another purchase order.

• Current result: The new purchase order is created with the next number in the sequence (1001), skipping the cancelled number.
• Expected result: The new purchase order reuses the skipped number (1000).

Expected behavior:

When using non-continuous number sequences, even if a transaction is cancelled, the same number (e.g., 1000) should be available for reuse in the next transaction, ensuring no skipped numbers.

Business Impact:

• Missing numbers in sequences affects traceability and reporting, especially in industries that require strict compliance with regulatory standards.
• Customers who prefer non-continuous sequences for performance reasons face challenges due to skipped numbers when transactions are cancelled.

We would like to suggest the enhancement for function as:

Update the functionality of non-continuous number sequences to include an option or feature that allows the reuse of numbers from cancelled transactions, ensuring no skipped numbers without switching to continuous number sequences. This should be configurable to maintain flexibility for customers who rely on the current design.

This enhancement would improve customer satisfaction by addressing a common business need for sequential numbering while retaining the benefits of non-continuous sequences. It also aligns the product with diverse operational and regulatory requirements across industries.

Kindly review and contact me if any information required. Thank you so much!