web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

Journal voucher number

(0) ShareShare
ReportReport
Posted on by

Hi everyone,
I'm facing an issue where already posted voucher numbers keep reappearing in new Vendor payment journal.


Due to strict audit requirements, I cannot use the "Number allocation at posting" feature. The voucher number must be identical on the journal report both before and after posting by audit process.
Is there any other way to fix this number sequence reuse issue without enabling "Number allocation at posting"?
Thanks!

Categories:
I have the same question (0)
  • Suggested answer
    Shaluma Profile Picture
    131 on at
    Hi,

    When a number sequence is set to Continuous, D365FO maintains a Status List of reserved numbers. Numbers get "locked" in this list when a session crashes, a browser is closed unexpectedly, a journal is deleted in draft, or a customization/import issue occurs. The "Next" value on the sequence moves forward, but the locked number sits in the status list marked as "Free"  and D365FO then re-offers that already-used number to the next journal.

    Please find the below URL for
    https://experience.dynamics.com/ideas/idea/?ideaid=e1f614c8-4a88-ec11-b820-0003ff45ec21
    Please refer the below URL it's helpful for your issue
    https://community.dynamics.com/blogs/post/?postid=b67fc3a3-9741-49cc-984b-7712a013d81b

    Clean Up the Number Sequence Status List 

    This is the primary fix for your current error.
    Organization Administration > Number Sequences > Number Sequences

    Find the number sequence tied to your Vendor Payment Journal (e.g., GJ26/JP).
    Click Edit, then go to General > Cleanup.
    Run Manual Cleanup → select Current records.
    This ensures all number sequences on the status list are set to status Free / Action None.
    After cleanup, open the Status List tab and check if the problematic voucher number (GJ26/JP/00677) appears there. If it does and the number is genuinely already posted, delete it from the status list using Alt + Delete.
    Then verify the "Next" field on the number sequence is set to a value higher than your last posted voucher.

    Only delete a status list record if you've confirmed the voucher is truly already posted in the ledger. Do not delete if it was never successfully posted.

    Schedule Automatic Cleanup as a Batch Job

    To prevent this from recurring:

    You can run the cleanup process manually or automatically to recover lost numbers. It is recommended to run the cleanup as a batch job during non-peak hours
    https://community.dynamics.com/blogs/post/?postid=06145872-b397-407c-93ff-91f4fa5c4cc1
    Organization Administration > Number Sequences > Number Sequence Cleanup
    Set this as a recurring batch job

    If the issue still persists after following them, please raise a query, and we will be happy to support you further.

    Thanks,
    If you found it helpful, please consider marking it as verified â€” it may be useful for others in the future!


     

     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Abhilash Warrier Profile Picture

Abhilash Warrier 681 Super User 2026 Season 1

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 598 Super User 2026 Season 1

#3
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 579

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans