Earlier quoted context omitted.
> I mean, this is just....wrong. It's beyond wrong. The developer here is redefining established accounting terms because he doesn't like their inconsistencies.
> It's beyond wrong. How so? > The developer here is redefining established accounting terms because he doesn't like their inconsistencies. Yes. What's wrong with fixing inconsistencies? Established accounting terms are from 500 years ago when people had trouble with subtraction.
Double Entry Accounting for Developers
51–60 of 237 posts
Re: Double Entry Accounting for Developers
#52Earlier quoted context omitted.
Transaction: Income > Work: $200 (or $200CR) Assets > Bank Account: -$200 (or $200DB) This is exactly how it would be stored in any software system behind-the-scenes, and how it would be submitted in statutory accounts. The only thing that makes this look weird is that you are used to seeing your bank account statement with 'credit'. But that's only because the bank account statement is from their accounting perspect…
I don't understand where the negative comes from. I just gained $200. Why would my bank balance go down by $200?! If you're talking about the bank's perspective, why is that relevant to me? I'm just asking about how to do my own accounting.
I am not inventing this. Money in your bank is debit in _your_ accounting.
You are very welcome to treat it as positive and add. As long as you keep track of where every positive number is a credit or a debit, and you learn all the rules about which accounts to add and which ones need taking away.
Or you can just treat credits as positive numbers and debits as negative.
Literally the only 'weirdness' is that money you have put somewhere for future use (like a bank) is negative.
Your initial reaction might be "that's just nonsense and ridiculous!" But I guarantee that is how your accountant and accountancy software is storing it. Your bank balance is debit from your accounts. Legally and intuitively. The only reason it is weird is because you receive statements from the bank from their perspective (a credit because they received the money from you).
If you have made it to junior high school you are quite capable of the math. Treat debits as negative and credits as positive. No accountancy ed / special rules needed.
If you want to get it more intuitive you can think of it as: Negative numbers are money that you put somewhere and is now owed to you. If you have $1000 in 'your' account, legally that means you are $1000 down because you are owed that money by the bank. It is your debit. You have given them credit.
It may not feel like a loan because it feels like you can get the money any time you want. But loans you have given and bank accounts are both assets in your accounting. They are both debit. They are both money you have put somewhere.
Re: Double Entry Accounting for Developers
#53Note to people looking for job security: there is a HUGE need for developers who understand finance. The fundamental problem is that most finance people can't speak the language of software development (the biggest problem I've seen is that finance people tend to be very poor at writing out a spec of what the software should do - they're much better at looking at a set of examples and then telling you if the calculat…
Aside from the obvious PayPal, SQ, and Stripe, would you (and other folks) please share some companies one should look into?
Re: Double Entry Accounting for Developers
#54Earlier quoted context omitted.
I don't understand where the negative comes from. I just gained $200. Why would my bank balance go down by $200?! If you're talking about the bank's perspective, why is that relevant to me? I'm just asking about how to do my own accounting.
Debit is where you put money. Credit is where it came from. I am not inventing this. Money in your bank is debit in _your_ accounting. You are very welcome to treat it as positive and add. As long as you keep track of where every positive number is a credit or a debit, and you learn all the rules about which accounts to add and which ones need taking away. Or you can just treat credits as positive numbers and debits…
> Literally the only 'weirdness' is that money you have put somewhere for future use (like a bank) is negative.
But that is literally what I'm talking about. Whether the sign is positive or negative isn't the issue. It just makes no sense for this to be a zero-sum game, is all I'm saying. You're telling me if I get $200 out of the blue I suddenly owe someone that $200 instantly? How does that work?
Re: Double Entry Accounting for Developers
#55Note to people looking for job security: there is a HUGE need for developers who understand finance. The fundamental problem is that most finance people can't speak the language of software development (the biggest problem I've seen is that finance people tend to be very poor at writing out a spec of what the software should do - they're much better at looking at a set of examples and then telling you if the calculat…
Aside from the obvious PayPal, SQ, and Stripe, would you (and other folks) please share some companies one should look into?
Re: Double Entry Accounting for Developers
#56One thing I really appreciate about YNAB is that they ditched the obscure words with murky Latin roots and rules to memorize about flipping signs and whatnot, and just used the words "inflow" and "outflow". They don't mean anything different in this context than "debit" and "credit." But still, somehow, when you use the traditional words, the topic seems to be as difficult to explain as monads, while with the YNAB te…
Re: Double Entry Accounting for Developers
#57[1] https://beancount.github.io/docs/the_double_entry_counting_m...
Re: Double Entry Accounting for Developers
#58One thing I really appreciate about YNAB is that they ditched the obscure words with murky Latin roots and rules to memorize about flipping signs and whatnot, and just used the words "inflow" and "outflow". They don't mean anything different in this context than "debit" and "credit." But still, somehow, when you use the traditional words, the topic seems to be as difficult to explain as monads, while with the YNAB te…
Re: Double Entry Accounting for Developers
#59Oh wow, I posted this earlier and assumed it hadn't been picked up. From people's comments here it sounds like I may have missed the mark on some of this. Pull requests always gratefully received. None the less, the result has been some software which seems to have worked well for those that have used it. I certainly haven't received any angry issues. I'll link to this thread from that page.
I checked out the GitHub repo. I’m a CPA who’s getting into web development and has some Django experience. Would definitely be interested in contributing.
Re: Double Entry Accounting for Developers
#60Earlier quoted context omitted.
Aside from the obvious PayPal, SQ, and Stripe, would you (and other folks) please share some companies one should look into?
I would look at finance companies and banks directly.