3 ms·
I suspect the misconception might be that you think individual accounts must balance (Or think that what I'm saying). Transactions always balance, companies alw
by sago 6y ago
I suspect the misconception might be that you think individual accounts must balance (Or think that what I'm saying). Transactions always balance, companies always balance.
In double entry accounting you track where money came from to you. You are right in not having to worry where they get their money from. But you do have to track how/why it came to you.
You will have an account in your accounting of 'income' (it's usually called 'Revenue'). If you have even the slightest complexity in your business, you will have many income accounts. Some businesses will definitely track at the level of detail where they have accounts for each customer, so they can see who purchased how much.
Each transaction balances.
Each line in a transaction is associated with an account.
So if you have done 50 weekly transactions of:
Revenue>Consulting $1,000CR
Assets>Bank $1,000DB
Each one balances.
But in total you will have $50,000CR in Revenue>Consulting and $50,000DB in Assets>Bank, but your company will still balance.
If you pay yourself $45,000 in salary from that, let's say in one go at the end of the year (to save me typing) you would have a transaction:
Assets>Bank $45,000CR (it came from your bank account)
Expenses>Salary $45,000DB (it went to your salary)
So at the end, your accounts are:
Assets>Bank $5,000DB
Revenue>Consulting $50,000CR
Expenses>Salary $45,000DB
This still balances. Double accounting always balances companies and transactions.
Historically it balances credits and debits. All I'm saying is it makes more sense to think of debits as negative and credits as positive, and all the math becomes much much simpler. Which is how accounting software is written.
- mehrdadn 6y agoAh okay thanks a ton! I think that clears it up. So basically: - The idea is that every source/destination ("node") of funds keeps their own account for every node they deal with. And every transaction ("directed edge") necessarily needs to be tracked by both accounts in an equal and opposite manner. - This is mainly only useful for businesses, as they generally have multiple sources of income (and/or multiple creditors) and need to be able to explain/track them. (At least as far I can see, I don't really see much of a point in doing this for the average person.)
- sago 6y agoYes on both fronts. Thanks for continuing until we've got on the same page. The only slight curve ball in your part one is that transactions are not always between two accounts. The joke is that 'double entry' sometimes has more than two. The classic example is sales tax. E.g. a transaction: Revenue>Product $100CR Liability>Sales tax $5CR Asset>Bank $105DB (Although the specific form/standard categories will massively depend on how sales tax works in your jurisdiction.) There are plenty of other examples (in my consulting: the customer paid some their bill in advance, or I pay a bill in a different currency and have to pay a fee). So I like the idea of making it a topology question, but it would be nice if it were only two.
- mehrdadn 6y agoYeah I almost mentioned multiparty transactions too, but thought I'd keep it simple since I got the crux of it :) thanks!