Changeset - 1e2c39d3cd8c
[Not reviewed]
0 1 0
Bradley Kuhn (bkuhn) - 8 years ago 2013-04-30 18:36:23
bkuhn@ebb.org
Fix awkward descriptions: details on the tags were under the account tag requirements.

Thus, I factored the text regarding the linking to documents that was in the
Expense account section into the section on describing the tags themselves,
and then merely linked back to that.
1 file changed with 37 insertions and 20 deletions:
0 comments (0 inline, 0 general)
npo-ledger-cli-tutorial.md
Show inline comments
...
 
@@ -176,6 +176,24 @@ the transaction.
 

	
 
### Tags Used In This System
 
Below you'll find detailed descriptions of all the possible tags that are
 
used in this system.  The actual declarations and enforcement of rules of
 
these tags can be found in the file `accounts/config/config-tags.ledger` in
 
this project.
 

	
 
A list of tags can be found in the file `accounts/config/config-tags.ledger`
 
in this project.
 

	
 
### Documentation Tags
 

	
 
Documentation tags are tags that link to other backup documents that provide
 
evidence and details that justify a particular ledger entry.  The value of
 
the tag is a relative path name of a file elsewhere in the same repository
 
that documents the specific expense.  For example, an entry like this:
 

	
 
     2012-02-05 Office Supply Galore - Online Order
 
         Expense:Main Org:Office Supplies      $35.00
 
             ;Receipt: accounts/documentation/org/receipts/2012-02-05_office-supply-galore.txt
 
         Liabilities:Credit Card:Visa         -$35.00
 

	
 
shows that a purchase was made at Office Supply Galore's online store for
 
$35.00, and the file
 
`accounts/documentation/org/receipts/2012-02-05_office-supply-galore.txt`
 
contains the receipt from that purchase.
 

	
...
 
@@ -186,3 +204,3 @@ document that shows clear confirmation that the transaction has already
 
occurred.  The value of the `Receipt:` tag is always a valid pathname in the
 
repository to the document.
 
repository to the document, [as described above](#documentation-tags).
 

	
...
 
@@ -209,3 +227,3 @@ that is a request for payment, rather than documenting an actual payment that
 
has occurred.  The value of the `Invoice:` tag is always a valid pathname in
 
the repository to the document.
 
repository to the document, [as described above](#documentation-tags).
 

	
...
 
@@ -227,3 +245,5 @@ external party (or even perhaps generated internally) that provides document,
 
insight, or other information about the transaction.  The value of the
 
`Statement:` tag is always a valid pathname in the repository to the document.
 
`Statement:` tag is always a valid pathname in the repository to the
 
document, [as described above](#documentation-tags).
 

	
 

	
...
 
@@ -243,2 +263,7 @@ Some examples of appropriate uses of the `Statement:` tag are:
 

	
 
### Information Tags
 

	
 
In contrast to documentation tags, information tags can more traditionally be
 
considered pure "meta-data" for a ledger entry.
 

	
 
#### IncomeType Tag
...
 
@@ -277,18 +302,10 @@ account (primarily for use with Ledger CLI's `--pivot` and `--group-by`,
 

	
 
Each Expense account entries need to be tagged with an
 
[`Invoice`](#invoice-tag), [`Receipt`](#receipt-tag), or
 
[`Statement`](#statement-tag) tag.  The value of the tag is a relative path
 
name of a file elsewhere in the same repository that documents the specific
 
expense.  For example, an entry like this:
 

	
 
     2012-02-05 Office Supply Galore - Online Order
 
         Expense:Main Org:Office Supplies      $35.00
 
             ;Receipt: accounts/documentation/org/receipts/2012-02-05_office-supply-galore.txt
 
         Liabilities:Credit Card:Visa         -$35.00
 
Each `Expense:` account entry must be tagged with the following tags:
 

	
 
shows that a purchase was made at Office Supply Galore's online store for
 
$35.00, and the file `accounts/documentation/org/receipts/2012-02-05_office-supply-galore.txt`
 
contains the receipt from that purchase.
 
* One of: [`Invoice:`](#invoice-tag) [`Receipt:`](#receipt-tag), or
 
  [`Statement`](#statement-tag).  (The only exception to this rule: an entry
 
  does not need an `Invoice:`, `Receipt`, nor a `Statement` tag if the
 
  [payee was never charged](#never-charged-payee).
 

	
 
#### payee with "NEVER CHARGED"
 
#### NEVER CHARGED Payee
 

	
0 comments (0 inline, 0 general)