Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Payment Voucher Number...
Microsoft Dynamics GP (Archived)

Payment Voucher Number Sequence Gap

(0) ShareShare
ReportReport
Posted on by Community Member Microsoft Employee

Hi,

I have this client who encountered the a Sequence Number gap issue in AP Cheque Voucher Number.

The scenario goes as below:-

1. Use Select Cheque to build a payment cheque batch, for multiple vendors.

2. When the batch of vouchers got created, there are several "jumps" in the vouchers numbering sequence.

Voucher Number Vendor ID Document Type Document Date
KPV140167 CZB0002MYR Payment 17/05/2014
KPV140168 CZC0009MYR Payment 17/05/2014
KPV140169 CZC0008MYR Payment 17/05/2014
KPV140170 CZL0004MYR Payment 17/05/2014
KPV140171 CZL0002MYR Payment 17/05/2014
KPV140173 CZM0004MYR Payment 17/05/2014
KPV140174 CZP0003MYR Payment 17/05/2014
KPV140176 CZT0004MYR Payment 17/05/2014
KPV140177 CZM0002MYR Payment 17/05/2014

3. As shown above, there are 2 missing numbers in the sequence.

4. Checking the records in PM00400 table, the gaps are indeed present.

------------------------------------------------------------------------

CNTRLNUM CNTRLTYP DCSTATUS DOCTYPE VENDORID
KPV140167             1 3 6 CZB0002MYR     
KPV140168             1 3 6 CZC0009MYR     
KPV140169             1 3 6 CZC0008MYR     
KPV140170             1 3 6 CZL0004MYR     
KPV140171             1 3 6 CZL0002MYR     
KPV140173             1 3 6 CZM0004MYR     
KPV140174             1 3 6 CZP0003MYR     
KPV140176             1 3 6 CZT0004MYR     
KPV140177             1 3 6 CZM0002MYR     

------------------------------------------------------------------------

Hence in this case, we'd need to answer the 2 questions from the client.

A. How / What caused such numbering gap to happen?

B. How to fix the numbers that are already posted and have gaps?

*This post is locked for comments

  • soma Profile Picture
    soma 24,408 on at
    RE: Payment Voucher Number Sequence Gap

    I am wondering why this is working with un-sequencial order of the payment numbers.

    Better contact your GP partner or Microsoft support team to look into this issue.

    Hope this helps!!!

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Payment Voucher Number Sequence Gap

    Hi Soma,

    Thanks for the suggestion.

    However before i could test as you've suggested, there's another new batch encountering the same issue.

    This time, there are only 3 payments in total, and the numbers skipped by 2 (83, 84, then 87). Similar to the earlier cases, there are only 1 user doing payment, there are no other payment window nor setup window opened.

    I'm out of answers to explain to my user now. Is there any other areas or possibilities i could look at?

  • Suggested answer
    soma Profile Picture
    soma 24,408 on at
    RE: Payment Voucher Number Sequence Gap

    Ivan,

    Once you entered and posted the transaction for the payment number KPV140167, then you can't use the same number for any other transactions even though it has been voided.

    Better void the posted payment and then rebuild the batch without changing the starting payment number. Then check whether the payment number gab is available for the new build batch(This batch will build with new range of Payment Number rather than the voided transactions).

    Note: It would be better if you try above suggestion in test server.

    Hope this helps!!!

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Payment Voucher Number Sequence Gap

    Hi Soma,

    If not mistaken the batch is already posted.

    This test of yours is basically just to confirm if system is able to generate the correct series of numbers without the gaps, correct?

    What if i try to void the posted payments, then rebuild the batch with payment number starting from KPV140167, would it be relevant ?

  • soma Profile Picture
    soma 24,408 on at
    RE: Payment Voucher Number Sequence Gap

    Did you print/post the batch? If not, backup the company database and stored it to test company, delete the batch and set the next payment number to KPV140167 then try to build the batch again. Then verify the Control Number from the table PM00400.

    Hope this helps!!!

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Payment Voucher Number Sequence Gap

    No Soma. This user was the only one in Payables during the check batch building process, therefore no Manual Payment screen was open at that time.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Payment Voucher Number Sequence Gap

    No Richard. The check batch building process got initiated and completed all the way through remittance and posting, without Edit Check / Edit Check Batch.

  • soma Profile Picture
    soma 24,408 on at
    RE: Payment Voucher Number Sequence Gap

    May be someone was opening on the Manual Payment screen while the check batch was being built. Please confirm. This is possible to lock the payment number(CNTRLNUM for DOCTYPE=6 from PM00400) while the build was in process.

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,730 on at
    RE: Payment Voucher Number Sequence Gap

    After this person selected the checks for the check batch, did he/she then edit the batch and delete two checks before printing?

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Payment Voucher Number Sequence Gap

    Hi Soma,

    Thanks for the explanations.

    Do correct me if i'm wrong, i thought the CNTRLNUM for DOCTYPE=6 is in fact the numbers for the payment documents, which in this case are for the checks generated from the check batch building process, not the invoices applied to.

    I've also checked through the PM30300 table, and confirmed that the CNTRLNUM numbers shown in my first post are the check payment numbers; while the invoices these checks are applied to, had a separate number series of 'KPV14*****'.

    The tricky part in this issue is that there was only one user working on the check batch building process when the issue surfaced.

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

Congratulations 2024 Spotlight Honorees

Kudos to all of our 2024 community stars! 🎉

Meet the Top 10 leaders for December

Congratulations to our December super stars! 🥳

Start Your Super User Journey

Join the ranks of our community heros! 🦹

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,711 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,458 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans