Small and medium business | Business Central, N...

General Journal - Document No. Duplications

(4) Share

Report

Posted on by CU15100730-0

Hi,

When multiple users create a line at the same time. Sometimes what happens is that document No. becomes Duplicated. Which causes the issue in approval and unique number tracking.

Solutions I tried:

1- Changing the No. Series and Posting No. Series Seperate

2- Manual Check is disable in No. series for document no.

3- Tried Renumber Document Number

What could be the Solution?

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (8)

Answers (0)

Gerardo Rentería Ga... 25,555 Most Valuable Professional on at

Like (2)

Report
Copy link

Link copied!

Hi

Why are users using the same batch journal? Could you create multiple batch journals for each user?

Best

GR

Was this reply helpful? Yes No
Suggested answer

Pallavi Phade 5,420 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Namaste @CU15100730-0

This is common problem observed for our several customers. I would recommend userwise Batches then there will be no discrepances in no series .

Create Seperate Userwise batches and instruct users to select the said batch . As all batches will be visible

or

You can customize user wise filter view while selecting General Journal Batch . Create USerid column and put filter

If you this helped , Please mark as "Verified"

Regards

Pallavi Phade

Was this reply helpful? Yes No
Suggested answer

Aman Kakkar 2,977 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!

Hi,

The standard practice is to create a separate batch for each user and ask them to use their assigned batch only. If possible, assign a different No. Series to each batch as well.

This way you can avoid the duplication of Document No.

Hope this helps.

Aman K

Was this reply helpful? Yes No
Ahmad Subhani 618 on at

Like (2)

Report
Copy link

Link copied!

They are using Seperate Batches
Still Issue is Coming

Was this reply helpful? Yes No
Suggested answer

Sumit Singh 11,757 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!
Hi,
Turning off Manual Nos. reduces, but doesn’t eliminate, conflicts—because collisions can still occur before posting if several users are fed the “next” number at about the same time.

Even if posting catches duplicates and errors out, it’s still friction for users and leads to rework.

Suggestion:- One batch per user + dedicated No. Series per batch

Keeps number allocation isolated per user

Even with separate batches, if they share the same No. Series , collisions may occur,.

Was this reply helpful? Yes No
Suggested answer

Jainam M. Kothari 15,732 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hello,

You can consider enabling "Allow Gaps in Number Series" to reduce locking conflicts, OR create a separate batch for each user with different No. Series to ensure uniqueness.

Alternatively, a custom number assignment extension using AL code can enforce atomic number generation, ensuring that each document gets a unique number even under high concurrency.

Was this reply helpful? Yes No
Suggested answer

Rishabh Kanaskar 6,219 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi,

Can you confirm if you are using the standard No. Series assignment without any integrations or background processes? Also, does the No. Series have Allow Gaps in Nos. enabled?

Thanks

Rishabh

Was this reply helpful? Yes No
Suggested answer

Valentin Castravet 32,152 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Best practice is for each user to have their own batch, and each batch to have unique document numbers.

Valentin Castravet
Work: Zander ERP Services
Blog: Dynamics 365 Business Central Insights
LinkedIn: www.linkedin.com/in/valentin-c-0500a247/

Was this reply helpful? Yes No