On Wed, 21 Apr 2021 at 01:15, Derek Atkins <de...@ihtfp.com> wrote: > That is not how GnuCash does it. GnuCash uses a real calendar and has no > "special" dates in there. > > How it *did* it, initially, was to take the "default timestamp" of Dec 31 > and add one second to it. This was because all posted times have a > default timestamp of approximately noon. So setting the closing > transaction to one second later would assure it was the "last" transaction > of the period. This is how it was originally implemented, but it's > probably been changed since then. >
Now the timestamp is 10:59am the same as any other regular transaction[*] but has an invisible CLOSING flag which ensures the xaccTransOrder will always sort closing splits after regular splits in the register and reports. The other rub is some reports (e.g. P & L) will filter out these closing splits via description search for "Closing Entries" as well and I wish to remove[**] this feature because all closing entries created in the past 10 years or so will have the closing flag. [*] which can be deleted, amended etc as desired [**] I wonder if anyone objects? https://github.com/Gnucash/gnucash/pull/909 _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
