Solution for closing year.

Phenno

What do you prefer when you are closing year (fiscal)?

I would surely like to have all data from past years so i could make analysis but, i do not need all the item ledgers, value entries, g/ls.... (from past years, ofcourse).


100 of invoices with 100 of sales lines by day, it is a lot of staff and Navision seems slow with sales reports allready. Not to mention how it will be in few years.

So, what are your suggestions ?

To close year, compress data by date (is this a safe solution in 3.6?) and move old year as another company or to another DB, to have all the data availible in one way?


What i am concerned about is speed of reports and work, and also some technical details. Our accountants have to look at data from past years all the time which they didn't use to..... They want only one year to see

nofirm

hello,

i'm currently facing the same problem! And, I think the solution to follow will be:
- define a date;
- at that date copy DB (production) to another DB with a name like NavisionFiscalYear;
- compress data per date on production DB.

I tried once to compress data over a test DB and it worked fine!

Best regards,
SS

Phenno

nofirm wrote:

hello,

i'm currently facing the same problem! And, I think the solution to follow will be:
- define a date;
- at that date copy DB (production) to another DB with a name like NavisionFiscalYear;
- compress data per date on production DB.

I tried once to compress data over a test DB and it worked fine!

Best regards,
SS

Does MS has some official guide or procedure advice on this topic?

For me, this is only logic action at the end of year.
Question for you:

When you tested data compress: what did you compress? (there are few modules with that options. All?)

What was result? exmpl, you now have 1 g/l entry per account, 1 per customer ledger entry?

Is it like a start balance on 01.01.xxxx or kind of last entry on 31.12.xxxx-1