[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: deleting draft transactions
- Subject: Re: deleting draft transactions
- From: Michael Richardson <..hidden..>
- Date: Mon, 13 Jul 2015 14:02:11 -0400
Erik Huelsmann <..hidden..> wrote:
> Heh. I'm not sure one is correlated to the other :-) . So, lets start with
> your situation: how many people are there in your business and how many are
> there in your "accounting department"?
> If the answer is - as I suspect - "I'm alone" (like me, in most of my
> businesses), then Draft versus Posted transactions are not for you. Draft and
> Posted transactions implement a principle which is called "separation of
> duties". It ensures - in companies of size "2+" - that no single person can
> cook the books (usually heavily associated with fraud).
Yeah, I thought I understood the goals --- and I agree that they generally
aren't for me. They significantly get in my way: having auto-post might be
If I could do *trial* reconciliations with drafts, and then be able to edit
them... wow that would rock.
The question is, given the state of draft/posts, it's not obvious that they
actually help companies of size 2+.
> Hmm. No, I didn't notice anything like that. To be honest, we do use draft
> transactions and we do sometimes duplicate them, but I can't remember running
> into your problems. I've logged them on SourceForge:
> That's a bug too (registered it under
> https://sourceforge.net/p/ledger-smb/bugs/1392/). No, the (draft)
> transactions aren't a work in progress, but badly suffering from the fact
> that nobody started drawing state transition diagrams and discussing the
> required state changes before writing the code that's behind it. (It'd be
> very unfortunate if all you could do with a not-acceptable draft transaction
> is to delete it.)
okay, I'd like to help with this.
> I wouldn't expect these to be bugs because you entered in 1.3 and upgraded.
> I'm expecting (although I haven't verified) the same problems with
> 1.4-created transactions.
I'm considering for a number of reasons to start a new database for 2016.
I'm considering whether I should do that for Jan 1, 2015, since I've only
gotten up to March 31, 2015 today.
What I'm thinking about now is how to best transition what data I can port
directly to a new database, and how. My chart of accounts, I think that I
can re-create just fine.
The contacts would seem to be the biggest benefit to this, and I'm thinking
also about how it might be nice to able to sync the contacts with other
systems (Gmail, bbdb.el come to *my* mind). I may work on this part.
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] ..hidden.. http://www.sandelman.ca/ | ruby on rails [
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
Ledger-smb-devel mailing list