weaken our claim to do "double entry accounting"
We (h/ledger, anyway) don't distinguish types of posting amounts (debit, credit) and accounts (balance sheet, income statement), so in some sense we do "less type-checking" than traditional double-entry accounting. Changed it to say "double-entry-style", though stopped short of linking the relevant comment.
This commit is contained in:
@@ -49,7 +49,7 @@ Plain Text Accounting
|
||||
</div>
|
||||
<div class="four columns">
|
||||
<h3 id="with-text">… with text</h3>
|
||||
<p><strong><a href="#ledger-likes">Ledger</a></strong> and the other <strong><a href="#ledger-likes">Ledger-likes</a></strong> inspired by it are minimalist software tools for efficient double-entry accounting. This site introduces them and their way of doing things.</p>
|
||||
<p><strong><a href="#ledger-likes">Ledger</a></strong> and the other <strong><a href="#ledger-likes">Ledger-likes</a></strong> inspired by it are minimalist software tools for efficient double-entry-style accounting. <!-- **[double-entry-style](https://news.ycombinator.com/item?id=10512418)** accounting. --> This site introduces them and their way of doing things.</p>
|
||||
<p>Accounting data is valuable; we want to know that it will be accessible for ever - even without software. We want to know when it changes, and revision-control it. We want to search and manipulate it efficiently. So, we store it as human-readable <strong><a href="http://ledger-cli.org/3.0/doc/ledger3.html#The-Most-Basic-Entry">plain</a> <a href="http://hledger.org/manual.html#journal">text</a></strong>.</p>
|
||||
<p>We simplify debits and credits by using <strong><a href="http://ledger-cli.org/3.0/doc/ledger3.html#Stating-where-money-goes">signed numbers</a></strong> instead - positive for inflows to an account, negative for outflows from an account.</p>
|
||||
<p>We define arbitrary <strong><a href="http://ledger-cli.org/3.0/doc/ledger3.html#Structuring-your-Accounts">account</a> <a href="http://hledger.org/manual.html#account-names">hierarchy</a></strong> to suit our needs. This scales smoothly from simple to complex scenarios, and from high-level overview to fine detail.</p>
|
||||
|
||||
Reference in New Issue
Block a user