5 ms·
See, the thing is: creating an invoice is an 'accounting' event that needs to be thought out a bit. Like a double entry general ledger, receiving payments, prop
by jumby 14y ago
See, the thing is: creating an invoice is an 'accounting' event that needs to be thought out a bit. Like a double entry general ledger, receiving payments, proper audit trails, the inability to modify an invoice after 'posting' it, batches, periods, and other goodness.
Otherwise, you get this ugly term: embezzlement.
But kudos for opensourcing it and standing up to criticism from hecklers like me.
- ericingram 14y agoI disagree, as a business should think first in the broad context of product/market fit, which is a very dynamic issue, and not all markets need the kind of depth in an accounting product you describe.
- einhverfr 14y agoThe only case where that my be true is the case where you have a sole proprietor where the owner is the only one who touches the books. As soon as you have a bookkeeper who is not the owner, or multiple owners you do need that kind of depth.
- ericingram 14y agoI'd bet the OP intended it for use by sole proprietors like himself, and that he never aimed to build a product for bookkeepers. There's plenty of a market for invoicing software that targets sole proprietors. A product with as much depth would likely appeal to accountants or those that assist them directly.
- einhverfr 14y agoFirst there is an unspoken assumption in your post. Embezzlement can only happen when someone is handling someone else's money. In many sole proprietors, this is not the case. So for those, sure. But it's important to understand the limitations here. But still within the core area, I think you have to accept that I would trust your books if they were kept in pencil more than I would trust books kept with software that didn't have proper controls.