status of accounting periods support

[Derek Atkins]

The real solution is to complete the implementation of Periods.  In
the meantime, the only thing to do is to create separate files and
hand-edit the opening/closing transactions.

If you handle periods via separate files, then you can use Dec 31 as
your _opening_ date and Jan 1 as your _closing_ date, and everything
"just works" (assuming calandar year Periods).  Considering all the
reports assume "year to date", this works fine :)

If your periods are not calendar years, you've got MANY OTHER problems
trying to use GnuCash....

-derek

Ian Pilcher <pilchman at attbi.com> writes:

> Hendrik Boom wrote:
> > Looks like we need a January 0, and a December 32.
> > This might be the easiest hack, depending on how dates are stored.
> >
> 
> Don't forget that business may have fiscal years that end on dates other
> than December 31.
> 
> The other approach that I can think of (and I'm not a GnuCash developer)
> is to add a "closing transaction" flag and ignore any transactions with
> this flag set when calculating income and expense totals for reports.
> 
> I don't *think* that anything else would be necessary.
> 
> IANAA (I am not an accountant), but the second approach feels more
> "right" to me.  (Of course, since I'm neither an accountant nor a
> developer, I should probably just shut up!)
> 
> -- 
> ========================================================================
> Ian Pilcher                                           pilchman at attbi.com
> ========================================================================
> 
> 
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at lists.gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available