Christopher Browne writes:
> Sorry, I don't think so. If I go on vacation to Nepal for 2 months, and
> don't get around to entering information 'til I get back, the backlog
> doesn't affect the fact that the two months worth of credit card charges
> hit accounts whilst I was away.
A special situation. I don't mean to suggest that the current date should
override the one you type in. I do contend that it is quite a valuable
piece of data and often the only date you have for a transaction, though.
As you note, storing it along with the date entered by the user would be
useful for auditing.
> But when the issue is of how to allocate transactions over time, which
> will include their allocation to particular accounting periods, time of
> data entry is decidedly _not_ an acceptable measure.
Failing to post transactions until several accounting periods have passed
is also not very acceptable either (not that we don't do it).
> I could, if pressed, outline some entertaining _frauds_ that could be
> implemented via the methodology of not recognizing transactions until
> they are entered into the computer system.
If there exist business documents recording the actual dates of the
transactions, then those are the dates on which you recognized the
transactions regardless of when you got around to posting them. If there
are no such documents then the entry date is the only one there is (you
should, of course, keep up on your posting).
--
John Hasler
[EMAIL PROTECTED] (John Hasler)
Dancing Horse Hill
Elmwood, WI
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
