NPO-Accounting/npo-ledger-cli
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Perform some copy editing

Browse source
This commit is contained in:
Martin Michlmayr 2019-03-28 22:11:39 +07:00
parent 10e89248db
commit a1da18abe8
No known key found for this signature in database
GPG key ID: 3D0787AAAF6C61DD
1 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
npo-ledger-cli-tutorial.md
View file

@ -172,7 +172,7 @@ has three tags: [`Entity`](#entity-tag), [`Invoice`](#invoice-tag) and
[`IncomeType`](#income-type). The `Entity` and `Invoice` tags, since they're [`IncomeType`](#income-type). The `Entity` and `Invoice` tags, since they're
listed at the top of the transaction, propagate through and apply to both listed at the top of the transaction, propagate through and apply to both
sides. But, the `IncomeType` tag, which has no meaning for `Accrued:` sides. But, the `IncomeType` tag, which has no meaning for `Accrued:`
accounts, so it is applied only to the `Income:Main Org:Donations` part of accounts, is applied only to the `Income:Main Org:Donations` part of
the transaction. the transaction.
Below you'll find detailed descriptions of all the possible tags that are Below you'll find detailed descriptions of all the possible tags that are
@ -267,7 +267,7 @@ Some examples of appropriate uses of the `Statement:` tag are:
The `TaxReporting` tag is an optional tag for `Assets` accounts that debit to The `TaxReporting` tag is an optional tag for `Assets` accounts that debit to
the account. the account.
When provided, the `TaxReporting` accompanies a `TaxImplication` information When provided, the `TaxReporting` tag accompanies a `TaxImplication` information
tag. The TaxReporting refers to a document that verifies the choice for the tag. The TaxReporting refers to a document that verifies the choice for the
`TaxImplication` tag. For example, for individual contractors in the USA, a `TaxImplication` tag. For example, for individual contractors in the USA, a
`TaxImplication` of `1099` would be well served by a `TaxReporting` that `TaxImplication` of `1099` would be well served by a `TaxReporting` that
@ -340,8 +340,8 @@ The possible values for this field are:
* `Accountant-Advises-No-1099`, indicating that the circumstances and rules * `Accountant-Advises-No-1099`, indicating that the circumstances and rules
seem to indicate a USA Federal Form 1099 should be issued for the `Entity` seem to indicate a USA Federal Form 1099 should be issued for the `Entity`
involved, but an outside accountant advised that no 1099 need be issues for involved, but an outside accountant advised that no 1099 needs be issued
this `Entity`. for this `Entity`.
* `Bank-Transfer`, indicating that the amount is a transfer between two * `Bank-Transfer`, indicating that the amount is a transfer between two
banking accounts under the control of the NPO itself. banking accounts under the control of the NPO itself.
@ -427,8 +427,8 @@ Expense accounts can have the following optional tag:
#### NEVER CHARGED Payee #### NEVER CHARGED Payee
The only exception to the standard tagging requirement is when the payee has The only exception to the standard tagging requirement is when the payee has
been modified to indicate that the expense was `NEVER CHARGED`. This is an been modified to indicate that the expense was `NEVER CHARGED`. This is a
historical special-case. The solution was originally design for the historical special-case. The solution was originally designed for the
following scenario: following scenario:
Suppose an expense was expected — for example, a situation where you Suppose an expense was expected — for example, a situation where you
@ -453,7 +453,7 @@ it like this:
Liabilities:Credit Card:Visa $100.00 Liabilities:Credit Card:Visa $100.00
Expenses:Conservancy:Hosting $-100.00 Expenses:Conservancy:Hosting $-100.00
However, going forward, you'd likely never enter anything the ledger However, going forward, you'd likely never enter anything into the ledger
**until** you had real proof via an Invoice, Receipt or Statement that showed **until** you had real proof via an Invoice, Receipt or Statement that showed
the Expense did/should occur. This use of `NEVER CHARGED` in the payee is the Expense did/should occur. This use of `NEVER CHARGED` in the payee is
thus deprecated. thus deprecated.