Re: Error updating an old transaction

[Lyle <..hidden..>]

On 10/04/2014 18:03, Pongrácz István wrote:

 

The Correct Way:

 

The correct way to handle this is to void and re-enter the invoice.  We have a void button at the bottom for this.

That's ok if you know what you are doing and don't make many mistakes. It's just not workable for a casual user from my experience.


Lyle

 

Hi,

Unfortunately the government doesn't care about how comfortable using account books and guarantee the integrity. Without these kind of restrictions, business administrator (director/owner/accountant etc.) easily could mess up the books and impossible to track back any modification, you cannot trust your books anymore.

I'd be more the happy to lock each month after it's been validated. That way the chances of someone messing it up is greatly reduced.

The bad news, one cannot proof the integrity of the books, so, the end could be a big penalty from the government.

If the books are wrong anyway they wont be happy. As long as the books are accurate they cannot complain.

I also created some mistakes in my books (sales invoices usually, with wrong dates for example), I also did void and recreate with correct data.

In any case, regarding these principles, one can consult with a professional accountant to get fresh and exact information about local rules and regulations.

I fully understand the need for banks and big business to operate in this way. But not small business.


Lyle

Cheers,

István

------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment 
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees

_______________________________________________
Ledger-smb-devel mailing list
..hidden..
https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel