Sage 100

All Versions - Ah, New Years. That joyous time of the year when you get phones to correct data posted sometime during 12/**2018**. And yet, even with the new release of v2018, this annual PITA bug STILL has not been fixed! Just received confirmation from Tech Support that users again have to be vigilant when entering 12/30 and expecting 2017 to be the default year. This happens EVEN if you change the default module date.

I had to have someone restore from a backup this morning for this issue. I know there is a setting to only allow posting to one future period which would be helpful, but would not stop a posting in a future year when you are in December.

All the inventory from the sales journal posting had a 12/2018 transaction date. Of course it was a huge end of year invoicing batch.

Hard to get Sage to prioritize this when it is only extremely painful a couple weeks every year. And of course, when client returned these items to the vendor and rereceived, the tier for 12/2018 remained. So now I have to get rid of it via inventory transactions

We should all charge our time to resolve these errors and to deal with the phone calls back to Sage. Perhaps that will encourage them to fix this.

Or just tar and feather whoever shows up at the MOTM 2018 conference. Should we start with Rob and Kerry?

Sage simply does not understand how much time they waste of ours due to non-existent procedures, inferior infrastructure and software design issues. If we don't respond to our customers, they will eventually no longer be customers of us or Sage. I constantly tell Rob and Kerry that all of these time wasters take me away from selling software, which is all they are interested in.

This issue that is big to the customers and consultants could be resolved with small changes to the software.

The problem seems to be that there are functions and responsibilities that are unassigned or unknown, so they drop through the cracks at Sage. Part of this is the elimination of experienced people and positions over the years. The other part is very bad management.

Would be nice if they would create a WAD fix department. They wouldn't have to create any NEW features, just fix the broken code. They could call it the ""quick win"" team.

You get what you incentivize for. If the CEOs were hired under terms that paid most of their money in stock that couldn't be sold for ten years you would see very different behavior. Hit your 6% growth target? Great! Had to raise prices at ten time the inflation rate to do it? You'd better hope the next CEO has a better plan or your stock is worthless...

@PhilMcIntosh That is spot on. I would love to know how organic growth is calculated. If 6% growth is the target and prices are raised by 10% and reported actual is 3% organic and 6% total then there is a huge issue and the company is sinking. Ahem... 1. losing customers because the perceived value doesn't justify the price. 2. Emphasizing large business partners because they require less overall staff to manage. (even though the target market is small and mid-sized businesses.).

Just had a customer call saying they can't select AP invoices for payment. I connect, go through the selection process and sure enough, only a handful of invoices. So I run an aging and same invoices appear. ""That's all you have out there. Are you sure you have more?"" ""Yes, I just entered a bunch."" ""Did you update the register?"" I check and there is nothing to post. ""What's is one you just entered?"" Pull up the vendor and sure enough, the invoice is dated 12/18/2018 and not due until 12/18/2018. ""Oh..."" Told her it happens to everyone. She now has ~35 invoices to back out and re-enter.

I agree that Sage should ""fix"" this, but we as consultants stress how important dates are during training and periodically (like, all the time). Users must take some responsibility for checking what they are entering. At least they should review the register before they post it, but I know most don't.

Couldn't agree more @JohnHoyt the whole premise of batch processing is to allow a REVIEW before posting.

I know this does not help with incorrect invoice dates, but what about that Company Preference of ""Restrict Accounting Date to Current and One Future Period?"" Is that not checked for most customers? Perhaps the ""fix"" for Sage is to add another preference to look at invoice dates and warn or restrict.

I think the restrict accounting date would probably work but that would require instilling some discipline on the clients to run their departments like professional accountants..... The issue is that the default code for supplying the year based on the MMDD user key entry looks at the system date, NOT the module date. Many clients are trained to change the module date to prevent period posting errors through out the year. This falls apart when your system year is different than your module year. The fix should be the root cause, not the symptom.

The date validation (oh wait, there isn't any) in Sage 100 just sucks. If you look closely at any installation you can probably find at least once transaction from the Middle Ages and one beyond Captain Picard's birthday.

In reading all the posts, I thought there must be an easier way to fix the invoice date besides reversing and re-entering the invoice. So, I tried adjusting the invoice with a zero dollar adjustment and changing the invoice date. It seems to fix the date of the invoice in AP, however, you would need to manually adjust the GL. Am I missing something or does this seem like it would work?

@JaneCavanaugh I would be concerned with the transaction date of the inventory items.

@JohnHoyt @MoiraGoggin - Yes, I agree. Users should be watchful in data entry. BUTTTTTTTT, ( a big but), this has happened to me in the past numerous times in numerous years. I coach my users to be alert on dates. I also coach my users to minimize their keys strokes. MMDD is my mantra. Let the system default the year for them. When posting to a prior month, change the module date to the prior month and enter all prior month invoices in that batch. Then change your date back. When I key dates (for the past 21 years) I use the FEATURE relentlessly. I have sent Diane Coffman emails for the past 4 years asking that this get fixed. She proposes it, her bosses dispose it as not important for the near future. Not a happy situation when it happens to you when you try VERY hard for the first two weeks being careful!

With the current Sage culture I'd expect this to get attention with about 100k votes on the ideas site. Seems like an opportunity for an enhancement to be developed. Pop-up warnings when saving any transaction with any date type field (UDF's included) more than 2 months in the future / past (from the module date). Similar warning when choosing a posting date during an update. How to handle VI imported data would be tricky. Smart exclusion settings (so things like edits to Master SO's don't cause desensitization to the warning), and it could be an easy sell to anyone feeling such pain in January.

Require a password to post to a period that is more than ""x"" into the future for any module. Make it a setup option under Company Maintenance. Skip the current and one future period, it's a hold over from legacy days. The simple extra password step would get the second look that's needed.

I think it might be helpful to highlight somewhere in the first page of the Journal in screaming red that some dates are outside of 'reasonable' parameters. When a customer has a 100+ page Journal, it's ridiculous to expect they will/can check every invoice.