Changeset - a5f212dc71a3
[Not reviewed]
0 1 0
Martin Michlmayr (tbm) - 7 years ago 2014-05-18 13:14:58
tbm@cyrius.com
Typo fixes
1 file changed with 2 insertions and 2 deletions:
0 comments (0 inline, 0 general)
npo-ledger-cli-tutorial.md
Show inline comments
...
 
@@ -382,13 +382,13 @@ ledger itself via the configurations found in `config-tags.ledger` and
 

	
 
Each `Expense:` account entry must be tagged with the following tags:
 

	
 
* 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 was never charged](#never-charged-payee).)
 

	
 
* A [`Program:`] tag.
 

	
 
#### NEVER CHARGED Payee
 

	
 
The only exception to the standard tagging requirement is when the payee has
...
 
@@ -453,13 +453,13 @@ data for the organization.
 
If you use the [`Program`](#program-tag) tag effectively, you can easily test
 
the successes of various fundraising programs with a command like this:
 

	
 
    $ ledger -f accounts/books.ledger --pivot Program bal '/^Income/'
 

	
 
Meanwhile, using the  [`Program`](#program-tag) tag for Expenses can help
 
track what programs are costing with commands like hese:
 
track what programs are costing with commands like these:
 

	
 
    $ ledger -f accounts/books.ledger --group-by 'tag("Program")' reg '/^Expense/'
 

	
 
FIXME: example output
 

	
 
### Checking Integrity of a Tag
0 comments (0 inline, 0 general)