I added the following suggestion to Bug # 570042 https://bugzilla.gnome.org/show_bug.cgi?id=570042.
I have an alternative suggestion. In short: Update the database schema to include a boolean flag at transaction (or split) level to identify the transaction as a book-closing transaction. At a minimum: * Update the database schema (sqlite, postgres, mysql) to add a column to the transactions table called "closing_entry". * Update the XML schema to add an element called "<trn:closing-entry>". * Update income/expense related reports to exclude any transactions where the closing entry flag is set to 'y'. * Update the Close Books routine to set the closing entry flag to 'y' for each transaction created by the routine. Possible addition: * Update the report customization screens to give users an option to exclude the closing entries from the report. * The default for the option would be 'exclude'. Honestly, I have a hard time envisioning a use case for the include/exclude option, but users (myself included) seem to prefer customization over the application making a choice for you. On Fri, Dec 3, 2010 at 11:38 AM, Mike or Penny Novack < stepbystepf...@mtdata.com> wrote: > > > What would be NICE would be to allow a "special date" for book closing (one > no in the real calendar). > > _______________________________________________ > gnucash-user mailing list > gnucash-u...@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-user > ----- > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. > _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
