Topic Options
#42309 - 07/10/14 08:43 AM Year End Best Practices
Hugh Offline
Adagio Maven

Registered: 09/25/13
Posts: 186
Loc: Victoria, BC Canada
The file structure I inherited has a separate folder for each year. eg:

N:\ASP\Company\DATA\2012
N:\ASP\Company\DATA\2013
N:\ASP\Company\DATA\2014

So each year users must redirect to the new path to ensure they are opening the current year, and if any late adjustment journals arrive they must be posted in both copies.

Q1. Does the year end process spawn these new folders automatically?
Q2. If not, is this a good practice to continue with and does it add anything to the party such as improved access to older data?

Thanks for any input!

Top
#42310 - 07/10/14 08:55 AM Re: Year End Best Practices [Re: Hugh]
Warren Karges Online   content


Registered: 08/04/11
Posts: 461
Loc: Waterloo, Ontario
Hi Hugh, the answer to your first question is no, it's all manually done. The answer to your second is that this is an old practice inherited from Accpac, I believe. With the newer versions of ledger, there isn't a common cause to do this anymore since it can retain many years worth of account information instead of just a couple. Late adjustments can be dealt with using the post to prior year function, or by keeping both years open simultaneously until the older one is finished. It's still generally good practice to keep a year end back-up copy of the data, but you should only ever need it in an emergency.

That said, everyone is unique in some way and you may want to review your expectations with your consultant before changing the practice.
_________________________
Warren
Stief Group

Top
#42311 - 07/10/14 09:10 AM Re: Year End Best Practices [Re: Warren Karges]
Hugh Offline
Adagio Maven

Registered: 09/25/13
Posts: 186
Loc: Victoria, BC Canada
Warren,

Thanks for that. It makes sense to hear that it's a historical norm rather than a requirement of the current version of the software.

I see the value in a clearly identified year end backup, but when rolling my year end bouncing around from directory to directory doesn't seem like a great idea... It means I have to ensure that all users are going to the correct file set which seems like an extra step and an opportunity for error.

Top
#42312 - 07/10/14 09:28 AM Re: Year End Best Practices [Re: Hugh]
Warren Karges Online   content


Registered: 08/04/11
Posts: 461
Loc: Waterloo, Ontario
Agreed, having separated databases just for that purpose is a bad idea as people could be doing work in the wrong database without knowing it and the practice necessitates duplicating all the prior year entries with no discernible benefit.

The backup is really only there if you somehow manage to completely lose everything in the live dataset and need a reference, or need to start the year end over again (something you wouldn't consider after a day or two has passed). It wouldn't ever get unzipped under normal circumstances.
_________________________
Warren
Stief Group

Top


Moderator:  Softrak Support 
Who's Online
0 registered (), 78 Guests and 0 Spiders online.
Key: Admin, Global Mod, Mod
Forum Stats
1865 Members
5 Forums
14448 Topics
70593 Posts

Max Online: 432 @ 01/20/25 10:17 PM
April
Su M Tu W Th F Sa
1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30