Sage 100

 View Only
Expand all | Collapse all

Client on 4.5.2 (or maybe 3, I'd have to look) rer

  • 1.  Client on 4.5.2 (or maybe 3, I'd have to look) rer

    Posted 05-29-2012 10:36
    Client on 4.5.2 (or maybe 3, I'd have to look) reran an aging for the prior month end. Had an invoice in there with a date from April but a payment date of May. Transaction dates were April for invoice and May for check. Now hasn't it always been that if I run the aging dated April 30, the invoice will show up because it wasn't paid until May? Says No Data Selected. I've tried checking and unchecking the Future Trans check box, etc, but this sounds to me like a new bug.


  • 2.  RE: Client on 4.5.2 (or maybe 3, I'd have to look) rer

    Posted 05-29-2012 10:47
    Does it show up on the Trial Balance?


  • 3.  RE: Client on 4.5.2 (or maybe 3, I'd have to look) rer

    Posted 05-29-2012 11:19
    No. OK, I'm not still on vacation, am I? The invoice was dated 4/24 and the transaction date was 4/24. The check was dated 5/4 and the transaction date was 5/4. The invoice should show up on both the Aging and the TB dated 4/30, correct? And this is happening on more than just this vendor, so it's not something flukey here with just this vendor.


  • 4.  RE: Client on 4.5.2 (or maybe 3, I'd have to look) rer

    Posted 05-29-2012 11:21
    Could the year be wrong on the invoices? Were they all part of the same batch? Try running the TB with 12/31/9999 and see if they show up. Sounds like a date problem to me.


  • 5.  RE: Client on 4.5.2 (or maybe 3, I'd have to look) rer

    Posted 05-29-2012 11:36
    I actually went into AP_Open and AP_TransactionWhatever and looked at the records and the date was correct on both records in every place there was a date. Maybe I'll rebuild sort files...


  • 6.  RE: Client on 4.5.2 (or maybe 3, I'd have to look) rer

    Posted 05-29-2012 11:45
    When 4.X came out, they said we were supposed to be able to use the aging for balancing to the g/l for the first time ever, NOT TRUE. I've proved this wrong many times. I still use the a/p trial balance to tie out to the g/l at month end. The aging still drops off the invoices if paid but the trial balance will keep them on if they were still not paid at the end of the month.


  • 7.  RE: Client on 4.5.2 (or maybe 3, I'd have to look) rer

    Posted 05-29-2012 11:47
    Hmph. I'd just like the dang things to show up SOMEWHERE they are supposed to... But both the Aging and the TB say ""No data selected"". Seems to be working in my 4.5...


  • 8.  RE: Client on 4.5.2 (or maybe 3, I'd have to look) rer

    Posted 05-29-2012 11:48
    Did you select the open field when running the report? Just checking something obvious that I have overlooked when running.


  • 9.  RE: Client on 4.5.2 (or maybe 3, I'd have to look) rer

    Posted 05-29-2012 11:50
    BB, you find the darndest things......................


  • 10.  RE: Client on 4.5.2 (or maybe 3, I'd have to look) rer

    Posted 05-29-2012 11:51
    @JeffSchwenk , thank you. I try. @KathyPurkiss I even tried ALL and nothing came up for this vendor. Not good at all.


  • 11.  RE: Client on 4.5.2 (or maybe 3, I'd have to look) rer

    Posted 05-29-2012 11:52
    Is it only invoices that have been paid since 4/30 that don't show up? What if you run the aging with a date the same as one that doesn't show up - 4/24?


  • 12.  RE: Client on 4.5.2 (or maybe 3, I'd have to look) rer

    Posted 05-29-2012 11:52
    Try going in through g/l and drilling into that payment to make sure they didn't use a funky date. I just had one post a big batch of checks to Dec, 2012, hosed up ap, bankrec and g/l.


  • 13.  RE: Client on 4.5.2 (or maybe 3, I'd have to look) rer

    Posted 05-29-2012 12:03
    I give up. I went back in to check these things and the only thing I did differently was to run the aging for ALL vendors for 4/24 before running it for just this one vendor. Now it shows up on 4/24, 4/30 and on the Trial Balance, too. Maybe running it for all refreshes some file that running for just one doesn't? *sigh*