Sage 100

 View Only
  • 1.  Greetings :) I have a client on 4.40.3: AP Invoice

    Posted 09-09-2011 08:19
    Greetings :) I have a client on 4.40.3: AP Invoice dated 10/13/10. client made an adjustment to the invoice, dated the adjustment 7/31/11. Aged Invoice report was affected as of the original invoice date, not the adjustment date. Trial balance is correct. Sage says that is the correct way the program should work......GAAP says differently. Anyone else experience anything like this? Client is not pleased since this now changes what she gave her auditors for year end @ 12/31/10.


  • 2.  RE: Greetings :) I have a client on 4.40.3: AP Invoice

    Posted 09-09-2011 08:24
    Is the Aged Invoice Report being printed with the ""Exclude Future Dated Transactions"" checked?


  • 3.  RE: Greetings :) I have a client on 4.40.3: AP Invoice

    Posted 09-09-2011 08:30
    Don't use adjustments. People swear they're the greatest thing ever but I find they lead to these types of issues.


  • 4.  RE: Greetings :) I have a client on 4.40.3: AP Invoice

    Posted 09-09-2011 08:33
    At least in AP, I agree with Wayne. Have someone with an invoice dated 2010 but mistakenly posted to 2011 (don't you just hate December and January?). Again, TB is correct, aging is not. I did give her the good news that as of Jan 1, 2012, all would be OK again...


  • 5.  RE: Greetings :) I have a client on 4.40.3: AP Invoice

    Posted 09-09-2011 08:33
    Oh, and they adjusted it in 2011.


  • 6.  RE: Greetings :) I have a client on 4.40.3: AP Invoice

    Posted 09-09-2011 08:43
    @Mark - We printed the report both ways to see if it made any difference in the results, it did not. @Wayne - I agree, credit and debit memos are not likely to cause things like this. But I do not understand why this program cannot meet basic standards.


  • 7.  RE: Greetings :) I have a client on 4.40.3: AP Invoice

    Posted 09-09-2011 08:51
    Well, if Sage thinks that's the way the program should work, ask them to explain why they have this check box on the report selection screen... which specifically states ""Exclude Future Dated Transactions - Select this check box to exclude future-based transactions (for example, payments and adjustments) from the invoice balance.


  • 8.  RE: Greetings :) I have a client on 4.40.3: AP Invoice

    Posted 09-09-2011 09:03
    While this doesn't solve the issue, it may shed some light on to what is happening (or may not). I have a client that has a bunch of pizza hut restaurants. AP is processed as one division. But every once in a while, the controller likes to see an AP Aging by store. So we wrote and access/crystal report that pulls the data from AP Open invoice table and the AP Invoice HIstory tables. We use a GL segment in the AP Invoice History Detail file to determine the store number to develop the aging by store. Long story short, this works as long as the client has not ADJUSTED any ap invoices. For some strange reason, MAS does not write the adjustment line to the AP Invoice History Detail table. So we advised the client to NEVER adjust an invoice, process a new invoice. So to finish off this sad tale, I will bet this is the issue in your situation also.


  • 9.  RE: Greetings :) I have a client on 4.40.3: AP Invoice

    Posted 09-09-2011 10:12
    That's just crazy :) But I did instruct my client to avoid using the adjustment function in the future, and use debit and credit memos instead. As long as it works, she will be a happy camper. Thanks to @Wayne and @Jeff for your help.