AP Invoice Register updated in wrong month but caught before GL posting

Hello Sage Community,

We have a situation where an AP Invoice Register for entire batch was updated in the wrong period, but the date error was caught before the Daily Transaction Register was updated.  Is there a clean method to correct the AP module without mucking up the GL by posting then adjusting each invoice or recording a GJE with a reverse for the GLs hit?  Is there away to recall the whole batch without entering all the invoice data individually?  The only previous forum posts i could find addressed the case where the GL was already updated.

If not, is there ever an advantage to not posting the Daily Transaction Register immediately after the registers?  Why would SAGE bake it into their system to post the register and the daily transaction register to the GL separately? 

Thanks,

Joe

  • 0
    You have a bullet laying around? Time to bite the bullet. Only way to do this is to go ahead and post to the GL. Print out the DTL that comes up and then go into the GL and do a reversal entry using the date you had wanted to post it to. Or you could go into AP Invoice Entry and reverse and then re-enter in correct month.
  • 0 in reply to BigLouie
    "If not, is there ever an advantage to not posting the Daily Transaction Register immediately after the registers? Why would SAGE bake it into their system to post the register and the daily transaction register to the GL separately?"

    This isn't the official line, but here is my take. Sage 100 is a modular system. Not everyone has all modules thus the separation of the invoice journal and the daily transaction register.

    Now you are saying, but the g/l module is required! This is true. But oddly enough I had a client that didn't integrate to the g/l. Seems strange but they had their reason which I no longer remember.

    Many years ago, I used to do the a/p invoice register and not post the daily transaction register. Then I would do the check run immediately and update it. Then I would do the daily transaction register and get both the a/p register and check register DTRs on the same piece of paper. I thought that was great.

    However, that caused a problem in larger companies where sometime one person would print/update the DTR and get someone else's transactions on their printout/update. Solution was to make it so that if you didn't do it immediately you then had to go to g/l daily transaction register. So, my original reason for not printing immediately kind of went out the window.

    Currently, I don't think there really is a reason for not posting the daily transaction register immediately.

    How's that for a history lesson?

    I believe that the idea's site has a suggestion for rolling the journals and daily transaction registers up into a single step. I think I even voted for it.