|
From: Herb R. <he...@bu...> - 2001-11-04 05:12:54
|
On Sat, 3 Nov 2001, Keld J=F8rn Simonsen wrote: > Hi ! > > I talked with Dieter about a need for not being > able to change a transaction, once it has been entered. > This is a requirement by Danish law, so it is important > for Danes sql-ledger users to have that capability. > > I wonder if this is a requirement on other countries. > Does anyone out there have information on this? > > Kind regards > Keld Simonsen > I too have talked to Dieter about something like this; ie to be able to "close the books" at some point in time as after the fiscal year end. My interest is actually to contribute to sql-ledger by adding this function (along with some multi-currency function) but being new to SL, this list and to SL's coding style I thought it better to start with something easy like a phonebook (and now contact "manager"). AW, my initial look at SL's structure suggests to me that closing out a period could be done by providing an input for a "closed-as-at" dat= e that then is checked before any transactions are edited, deleted or added. This closing date would require admin or superuser privileges. If monthl= y closings are necessary then that would work also. In my mind this would preserve SL's fluid approach to accounting periods (which I like a lot) while still giving some comfort to the auditors and protecting against routine errors that could affect entries that are reconciled and considered final. If some extraordinary situation arose where a closed period's transactions do need to be changed, the admin / superuser could roll back the closed-as-at date. I doubt if there is any prohibition to reopening = a closed set of books in Canada's Income Tax Act, but I'm sure Revenue Canada (now Canada Customs and Revenue ...) would take a very long look a= t a companies activities if this was done without a *very* good reason and without refilling amended statements and tax returns. --=20 Herb Richter, Toronto, Ontario http://www.partsandservice.com |