FrontAccounting forum — Opening Year - 2017

Re: Opening Year - 2017

null@example.com (MacKenzie) — Mon, 20 Feb 2023 21:25:41 +0000

It's not a problem. Once I create a new company, and then run a mysql script that updates gl_classes, gl_coa, quick_entries, fiscal years and other things. Take less than 5 seconds. ;-)

rafat wrote:

I think @joe was very clear with this and I quote him:
joe wrote:
Hello Sir,
I guess you are referring to an external COA. In the FA core there are 2 COAs, en_US_demo.sql and en_US_new.sql. These 2 COAs only contains two fiscal years, Currently these are 2020 and 2021.
In the next minor release these will be updated to 2021 and 2022.
All the COAs in the Extension repository are maintained by various users and some are probably not updated.
Joe

Re: Opening Year - 2017

null@example.com (joe) — Tue, 14 Feb 2023 10:49:21 +0000

FYI, itronics has updated the Fiscal Years in the Repo COAs (not included in core). He has found a smart way to automatically always use the current year and previous year for Fiscal Years.

Joe

Re: Opening Year - 2017

null@example.com (rafat) — Tue, 14 Feb 2023 09:59:11 +0000

I think @joe was very clear with this and I quote him:

joe wrote:

Hello Sir,
I guess you are referring to an external COA. In the FA core there are 2 COAs, en_US_demo.sql and en_US_new.sql. These 2 COAs only contains two fiscal years, Currently these are 2020 and 2021.
In the next minor release these will be updated to 2021 and 2022.
All the COAs in the Extension repository are maintained by various users and some are probably not updated.
Joe

Re: Opening Year - 2017

null@example.com (PatJr) — Mon, 13 Feb 2023 22:25:23 +0000

yes, looks like it takes some massaging, adding years, changing the active year, deleting unused years, to get were the year is fiscal and active with the year after 2017

seems to be an annoyance but still works

Re: Opening Year - 2017

null@example.com (MacKenzie) — Mon, 13 Feb 2023 18:54:46 +0000

I think I was referring to something else.

My new company installations still default to 2017/2018. This is a brand new company setup (today 02132023), and clearly it doesn't really likes 2017/18. Must have been a great year! ;-) - - Not sure it matter but I got this after selecting 5-digit coa.

rafat wrote:

what did you find and how you solved it?

Re: Opening Year - 2017

null@example.com (rafat) — Sun, 05 Feb 2023 10:30:39 +0000

what did you find and how you solved it?

Re: Opening Year - 2017

null@example.com (MacKenzie) — Sun, 05 Feb 2023 04:53:54 +0000

**************************
I found this. SOLVED!
**************************

Re: Opening Year - 2017

null@example.com (MacKenzie) — Sun, 29 Jan 2023 19:39:15 +0000

This is what I'm seeing for setting up a new company. I basically do not want to start at 2017 or 2018 or 2019, etc. But it defaults to earlier years. Where can I tell it I want a 2023 fiscal year??

Please see this screenshot.

https://imgflip.com/i/797l9v

Re: Opening Year - 2017

null@example.com (MacKenzie) — Sun, 29 Jan 2023 19:25:33 +0000

I'm going to try that right now. Thanks.

Re: Opening Year - 2017

null@example.com (apmuthu) — Sun, 29 Jan 2023 18:01:26 +0000

Check the defaults for fiscal years in the CoA used for creating the new company. If no data is entered, then change the fiscal years in the database directly.

Opening Year - 2017

null@example.com (MacKenzie) — Sun, 29 Jan 2023 14:48:37 +0000

Upon setting up a new company, one is defaulted to 2017. This should be updated to at least 2021. Can I get an Amen? Thank you.