[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Reposting invoices
- Subject: Re: Reposting invoices
- From: Erik Huelsmann <..hidden..>
- Date: Thu, 29 Mar 2012 14:19:51 +0200
On Thu, Mar 29, 2012 at 2:10 PM, Erik Huelsmann <..hidden..>
On Thu, Mar 29, 2012 at 1:50 PM, Andrew Rowland <..hidden..>
After upgrading from 1.2 LedgerSMB 1.3 is now working well for me, however I find that I'm unable to alter or delete an invoice when I make even a minor error.Â Common mistakes are getting the date wrong of forgetting to change the drop-down for the customer which by default comes pre-popupated with the first entry in the debtor list (maybe this could be empty by default instead).
Anyway under 1.2 with audit trails turned off, I could edit the invoice and re-post to correct this. It wold give a warning but that's fine. This seems to be not possible in 1.3.Â There is no POST button for an existing invoice and whilst there is a delete button it gives a permission error when I try to use it.
ERROR: permission denied for relation acc_trans
I know this is possibly by design and that I probably should be voiding invoices and re-creating them but I'm not an accountant and I don't want this and all the clutter that this involves. The LSMB Manual suggests that this should still be possible
LedgerSMB has a capability to require such reversals if the business deems this to be necessary. When this option is enabled, existing transactions cannot be modiïed and one will need to post reversing transactions to void existing transactions before posting corrected ones.
Could someone please point me at some settings or failing that DB permissions that will allow this to work
As a matter of coincidence, I've just covered the setting in the book I'm writing. CheckÂhttp://book.ledgersmb.org/1.3/ledgersmb.pdf
Âsection 18.3.1 "Audit control". It says there's a setting called "Enforce transaction reversal for all dates". Try setting it to "No". It should do what you want.
Be sure to read the explanation in the section quoted though.
(Just checked the Invoice screen.) The process that I'd use instead of the one you propose is "Copy to New" on the incorrect invoice, correct the fields you entered incorrectly and post the corrected invoice. The incorrect invoice can then be voided, without requiring posted invoices to be edited. This would allow you to get a correct invoice without overwriting the existing invoice - which is strongly recommended not to be done by the LedgerSMB authors.
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
Ledger-smb-users mailing list