Skip to content

Jonathan Allard

My feedback

1 result found

  1. 23 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Jonathan Allard commented  · 

    I happily second this proposal. It seems to be related to [#493789](https://bugs.gnucash.org/show_bug.cgi?id=493789) in Bugzilla.

    Copying my comment there:

    ## Problem statement

    * As a business user of Gnucash, I need to manage at least one organization with a different year-end
    * Prevents Gnucash from knowing the right year-end for my book
    * Produces reports for the wrong periods

    * workaround: I need to set the date manually for each {report,period} I want to see
    * workaround: I leave the tab open definitely to keep a {report,period} pair

    * I can not change the accounting period globally which is fixed (2019-04-01 to 2020-03-31; instead of each year ends on -03-31.) – eg viewing last year does this does not help me

    => Current issue disincentivizes organizations to use Gnucash, unfortunately

    ## Solution
    A book-specific year-end date:

    * allows me to manage different entities in Gnucash
    * encourages non-individuals/organizations to use Gnucash

    ## Next steps

    * Define 'year-end' option in book schema (location and type), and load/save logic. (Seeing a year-end date is year-agnostic, datum could be set in 1970 eg. 1970-03-31)
    * Add setting UI in book properties
    * Make reports use this data
    * (?) Remove current global accounting period option

    Jonathan Allard supported this idea  · 

Feedback and Knowledge Base