[email protected] writes:
> On Mon, Feb 8, 2010 at 8:11 AM, Derek Atkins <[email protected]> wrote:
>
> JT Morée <[email protected]> writes:
> > I realize my post was long but in short I believe the best solution is
> to have the reports be smarter. It's not difficult (almost done in fact)
> and it avoids the fiscal year problem you mention.
>
> This is only part of the solution. There isn't really enough
> information in the current data. We would really need an actual period
> indicator in order to indicate which period a transaction belongs to.
>
> Color me confused -- why couldn't GnuCash just use the transaction date? If
> an invalid or imaginary date is used as the period end, then anything before
> one such date (and after another, for past periods) would belong to a certain
> period. No?
Because the period of the date in which you post the account might not
reside in the period to which the transaction applies. This is
particularly important for things like A/R and A/P. If you perform Cash
based accounting then you need to apply your Income and Expense when the
payment happens, not when you book the invoice/bill. So in this case
the invoice/bill txn does NOT apply to the period in which it is dated.
> Cheers,
>
> -- Erik Anderson
-derek
--
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
[email protected] PGP key available
_______________________________________________
gnucash-devel mailing list
[email protected]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
