A confirmation code will be emailed when setting up your account or resetting your password—check spam if needed.no-reply@dynamicscommunities.com

Next Journal Entry number jumping

  • Dynamics GP

    Next Journal Entry number jumping

    Posted by David Morinello@mttsvc.com on October 7, 2025 at 4:14 pm

    Does anyone have a solution similar the PSTL PO numbering fix?

    Next purchase order number jumping or wrong

    We have implemented Wipfli ExpenseConnect and have started seeing Journal Entry numbers jump back to 5-digit numbers, then back to 7-digit numbers again. We have other processes generating JE numbers and all are staying a 7-digits except for the ExpenseConnect generated ones.

    Symptoms aside, Wipfli says it is in GP settings. So, I am hoping I can adapt a variation on the PSTL PO solution into a JE version and lock these down.

    Dynamics GP 18.3

    David Morinello@mttsvc.com replied 3 weeks, 3 days ago 3 Members · 5 Replies
  • 5 Replies

  • Deborah A Bergman

    Member
    October 7, 2025 at 4:25 pm
    Up
    0
    Down
    ::

    Is it the PO number or the next GL number? The next GL number is set in the GL setup.

    • David Morinello@mttsvc.com

      Member
      October 8, 2025 at 12:59 pm
      Up
      0
      Down
      ::

      Yes, the issue is with jumping JE numbers. It is set correctly (7 digits) in the GL40000 Table. 1187586 is the next at this moment.

      Some, not all Wipfli ExpenseConnect processed records jump back to JEs in the 12445 to 12669 (so far) range.

  • David david@winthropdc.com

    Member
    October 7, 2025 at 9:46 pm
    Up
    0
    Down
    ::

    Hi David

    We would be able to use GP Power Tools to debug this and find out when the next GL Journal number is being returned and is less than the previous value.

    We can then add a trigger to prevent that from happening.

    Kind regards

    David

    • David Morinello@mttsvc.com

      Member
      October 8, 2025 at 1:04 pm
      Up
      0
      Down
      ::

      Thanks David!

      If I can narrow enough of the issue to reproduce it, then I will try a trace.

      Wipfli ExpenseConnect, I believe, makes eConnect calls as part of their processing.

  • David Morinello@mttsvc.com

    Member
    October 15, 2025 at 8:48 am
    Up
    0
    Down
    ::

    This turned out to be a mapping and value transformation issue with Wipfli ExpenseConnect. We are in the process of fixing the configuration with the help of Wipfli Support.

    We have this implemented in multiple GP companies and ExpenseConnect was incorrectly selecting one of the other companies and using the next available Journal number from that smaller company.

Log in to reply.

Start of Discussion
0 of 0 replies June 2018
Now

Report

Harassment or bullying behavior
Contains mature or sensitive content
Contains misleading or false information
Contains abusive or derogatory content
Contains spam, fake content or potential malware

Block Member?

Please confirm you want to block this member.

You will no longer be able to:

  • See blocked member's posts
  • Mention this member in posts
  • Invite this member to groups
  • Message this member
  • Add this member as a connection

Please note: This action will also remove this member from your connections and send a report to the site admin. Please allow a few minutes for this process to complete.

Report

You have already reported this .

Welcome to our new site!

Here you will find a wealth of information created for people  that are on a mission to redefine business models with cloud techinologies, AI, automation, low code / no code applications, data, security & more to compete in the Acceleration Economy!