Currently, in Microsoft Dynamics 365 Business Central, there is no validation to prevent conflicts between number series used by draft documents (such as unposted Sales Orders, Purchase Orders, or other document types) and posted documents (such as Posted Sales Invoices or Posted Purchase Invoices).

This behavior can lead to unexpected blocking issues during posting when a number series overlap occurs. For example:

• A draft Sales Order or Purchase Order is created using a number from a specific number series.
• Later, when attempting to post the document, the system tries to assign a number that already exists in the posted document number series.
• Because the number already exists, the system prevents posting, resulting in an error and blocking the user.

This situation is often caused by:

• Misconfiguration or overlapping number series between draft and posted documents
• Accidental manual assignment or reuse of numbers
• Lack of system validation at the draft stage

As a result, users are only made aware of the issue at the time of posting, which can disrupt business processes and require manual correction.

Business Impact:

• Users are unable to post documents due to number conflicts discovered late in the process
• Increased operational disruption, especially in high-volume environments
• Additional time required to troubleshoot and correct number series issues
• Risk of inconsistent numbering policies and reduced data integrity
• Potential delays in financial posting and reporting

Additional Context:

This issue is commonly encountered when customers accidentally configure or reuse number series across document types, or when draft documents are created before number series are properly finalized. Early validation would significantly improve system robustness and prevent avoidable errors.