|
|
|
|
|
by EvanAnderson
1406 days ago
|
|
> > Without the context of the specific accounts being debited or credited the terms themselves mean nothing." > This seems incorrect to me. You can't derive the change in assests, liabilities, or equity without know which accounts are being debited and credited. The terms "debit" and "credit" themselves don't tell you anything by themselves. Without the context of accounts the terms are meaningless. I think programmers get hung-up on thinking that they have meaning in isolation (i.e. thinking that "a debit means somebody owes us money"). > I think of it as 'owing' (liability) or 'owning' (asset). > When you credit an account, you either increase what you 'owe' on that account OR decrease what you 'own' on that account. That's my point. When you know they type of account being debited or credited you can reason about how it affects the balance of the account and the managerial context of the transaction (i.e. "somebody owes us money because the debit was to a receivable account"). |
|
This is true, but it doesn't negate my point (that debit and credit have meaning independent of the type of account).
I know this because I have used the principle many times in practice, to define charts of accounts, to define rules for posting different types of transactions etc.