Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

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

Voucher already exist in AP

(0) ShareShare
ReportReport
Posted on by 142

Hi all

We have upgraded to version 21. Recently noticing that we always get voucher already exist error whenever users validate the invoice vendor journal. I am not sure the reason for the same. I am always clearing the status list. But we are getting the error again.  Please let me know if there is any relation because of upgrade. 

Thanks

  • Suggested answer
    Alireza Eshaghzadeh Profile Picture
    13,585 Super User 2025 Season 1 on at
    RE: Voucher already exist in AP

    Hi Sundhu,

    You can also try the provided workaround by deleting the journal and then status list of the number sequence associating to the journal. You can try it to check if it resolve the issue.

    PS. You can export the journal via data management and import again after cleaning the status list.

  • Suggested answer
    Vamsa Profile Picture
    142 on at
    RE: Voucher already exist in AP

    Ok Thank Anh. Yes I saw the same hotfix from my lcs. We are doing the patch in uat. We will confirm in uat and do the same in production.

  • Alex VN Profile Picture
    1,994 on at
    RE: Voucher already exist in AP

    Hi,

    We have encounter the same issue and it seems to be a bug confirmed by MS. Please check this KB 4648893 from LCS Issue Search or your Quality Update and try to update and test the issue again.

    Annotation-2021_2D00_11_2D00_23-141111.png

    Hope this helps.


    Regards,

    Anh Ong

  • Suggested answer
    André Arnaud de Calavon Profile Picture
    292,892 Super User 2025 Season 1 on at
    RE: Voucher already exist in AP

    Hi Sindhu,

    Can you tell how you are entering or importing the invoices in the journal? If you have a customization for e.g. import or generate lines then review the coding which was used. If a next number from a number sequence is retrieved with the option 'makeDecisionLater', also a statement with numberSeq.used() should be called. Otherwise it will leave records in the status list which shouldn't be there.

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

Daivat Vartak – Community Spotlight

We are honored to recognize Daivat Vartak as our March 2025 Community…

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Kudos to the February Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,892 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,772 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156 Moderator

Leaderboard

Product updates

Dynamics 365 release plans