You are right, the best of available choises :).I have used sql-ledger for years and migrated to ledgersmb 1.2 in 2010.
I started to use ledgersmb 1.4 half a year ago with one company and
Thanks for using LedgerSMB all that time! Your 1.2 experience was pretty good, then, I assume. Is that correct?
We have tried also commercial bookkeeping software, but ware not able to afford any yet. I have tried to migrate to 1.3 also several times, but have not managed.
I do not remember exact cause. Was it perl errors because of wrong perl libraries or database conversion problems or both. That's why I used 1.2 so long.
Also, in case of 1.4 I still am not able to migrate. I installed new vm and got 1.4 working, but was unable to import v1.2 databases, so I started from clean database again. I also could not import chart of accounts. I managed somehow to export coa from 1.2 to csv but unable to import to 1.4.
You are right. But as I am doing bookkeeping myself, I am not so much worried about fraud :).planned to migrate others to from ledgersmb 1.2 to 1.4, but I am afraidI can not. I make mistakes quite often and as transactions and invoices
repair is not possible in 1.4. The correct way of doing reversal
transactions and invoices may be good for big companies, but I have
mostly one person companies.
Actually, the behaviour to require reversing/reposting transactions instead of overwriting them has very little to do with big versus small companies. It has to do with software that is compliant with generally accepted anti-fraud measures in the accounting process.
Right again. But the reports look much cleaner and easier to read without the old transactions and their reversals. If there would be possible to get reports without wrong invoices and their reversals it might also be the solution.I have repaired records and invoices using
directly sql prompt or with dump-modify-restore sequence, but this is
also quite frustrating.
I can imagine. May I ask why you choose to use this workflow? I make my share of errors (believe me!), but I use this workflow:
* Open the faulty transaction
* Put a minus in front of all the numbers, f it's an AR/AP transaction, add "-VOID" to the invoice number
* Post the transaction
* Reopen the faulty transaction
* Correct the mistake
* Post as a new transaction
Is there any reason why you couldn't use this workflow? It's completely compliant and probably less error prone and faster than correcting in the SQL dump/window.
Most common mistake is putting wrong account to transaction. For example in case of vendor invoice I put the cost of good to assets but later decide to change to expense. I would need to change just the number of account in vendor invoice without any mess in balance sheet and income statement (if I would need to reverse the invoice as a whole). For example in HansaWorld it is possible to change account number in transactions later.
This sounds great, but it would not resolve the mess in reports as I described above. Of course I name it "mess" but you probably name it "correct".
There is this:
I have an open request from a customer who would like me to implement the automated workflow above, but with the push of a button. The idea is that the user does not need to execute all the steps above, but instead, posts the reversal with the same push which posts the correcting transaction. Then, it will work with the same number of pushes on buttons as LedgerSMB 1.2 and SQL Ledger *and* the underlying recording stays compliant.
Would that be a solution for you too?
Another solution I have thought, would be append only auditing log, where all the changes are written, so the fraud would not be possible, but reports ware clean.
I am glad if my thoughts help to improve the program. Another problem is also my poor knowledge of English accounting terminology which makes it especially hard to learn all the possibilities of LedgerSMB.Thanks for taking the time to mail us! I hope we can learn from it and maybe we can improve the software in a way that you don't need to migrate to SQL Ledger and everybody gets to benefit? I hope we can discuss your reasons to dump/edit/restore versus the workflow I'm proposing!
Some things would be much easier if I would know which button to press :).
------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________ Ledger-smb-users mailing list ..hidden.. https://lists.sourceforge.net/lists/listinfo/ledger-smb-users