Feedback / Enhancement Request

In Microsoft Dynamics 365 Business Central, the system currently allows users to post multiple transactions using the same Document No., even when the transactions relate to different entries, amounts, or posting dates.

From a financial control and audit perspective, this can create challenges in maintaining data integrity and transaction traceability. Many organizations consider the Document No. to be a key transaction identifier, and the ability to post multiple entries with the same document number may lead to accidental duplicate postings, especially in payment journals, general journals, and other financial transactions.

We recently encountered a scenario where multiple payment entries were posted using the same document number. To address this concern and strengthen user confidence in the system, we had to implement a custom validation to prevent such occurrences.

We believe Business Central should provide a standard configuration option to validate document number uniqueness during posting. Ideally, when a document or journal is posted, the system should verify whether the same Document No. has already been used for a previously posted transaction and either:

• Prevent posting of duplicate document numbers, or
• Provide a configurable warning/blocking mechanism based on business requirements.

Such validation could be configurable by transaction type, document type, or posting group to accommodate different business scenarios while maintaining flexibility.

Additionally, during financial reviews and audits, users frequently analyze General Ledger Entries, Vendor Ledger Entries, Customer Ledger Entries, Bank Ledger Entries, and related posted transactions using the Document No. as a primary reference. When the same document number appears multiple times across different postings or dates, it becomes difficult to determine which transaction is the original entry and which may be an unintended duplicate.

Since the Document No. is widely used as a key reference for reconciliation, reporting, audit trails, and transaction tracing across organizations globally, introducing a standard duplicate document number validation feature would significantly improve financial controls, data accuracy, and overall user confidence in the system.

We request Microsoft to consider this enhancement as a configurable standard feature within Business Central.