Changeset - 9f2a0cd1cc1b
[Not reviewed]
master
0 1 0
Martin Michlmayr (tbm) - 5 years ago 2019-03-29 05:40:05
tbm@cyrius.com
Define the PurchaseOrder and Contract tags
1 file changed with 30 insertions and 1 deletions:
0 comments (0 inline, 0 general)
npo-ledger-cli-tutorial.md
Show inline comments
...
 
@@ -230,24 +230,53 @@ repository to the document, [as described above](#documentation-tags).
 

	
 
Some examples of appropriate uses of the `Invoice` tag are:
 

	
 
* an actual invoice as sent by a vendor to the organization.
 

	
 
* a request for payment sent by the organization to someone else.
 

	
 
* a reimbursement request submitted by an employee, contractor, or volunteer
 
  for expenses they've already incurred and would like the organization to
 
  reimburse (e.g., an expense report, requesting for reimbursement of travel
 
  expenses).
 

	
 
#### PurchaseOrder Tag
 

	
 
The `PurchaseOrder` tag refers to a document issued by the buyer to a
 
seller of a service or product.  It is often issued before the supplier
 
can create and submit an invoice.
 

	
 
Some examples of appropriate uses of the `PurchaseOrder` tag are:
 

	
 
* A purchase order for conference sponsorship.
 

	
 
* A purchase order for sponsorship of outreach activities.
 

	
 
#### Contract Tag
 

	
 
The `Contract` tag refers to contracts that define a commercial
 
relationship.
 

	
 
Some examples of appropriate uses of the `Contract` tag are:
 

	
 
* a contract between the organization and an independent contractor
 
  providing development services.
 

	
 
* a contract with a venue for a conference.
 

	
 
* a contract with a vendor to supply food for a conference.
 

	
 
* a contract for insurance services (such as directors and officers liability
 
  insurance).
 

	
 
#### Statement Tag
 

	
 
The `Statement` tag refers to any sort of written statement received from an
 
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, [as described above](#documentation-tags).
 

	
 

	
 
Some examples of appropriate uses of the `Statement` tag are:
 

	
 
* bank statements, as received from the banking institution.
...
 
@@ -454,25 +483,25 @@ it like this:
 
        Expenses:Conservancy:Hosting            $-100.00
 

	
 
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
 
the Expense did/should occur.  This use of `NEVER CHARGED` in the payee is
 
thus deprecated.
 

	
 
#### Income Account Documentation
 

	
 
Each `Income:` account must have the following tags:
 

	
 
* One of: [`Invoice`](#invoice-tag),
 
  [`PurchaseOrder`](#purchase-order-tag),
 
  [`PurchaseOrder`](#purchaseorder-tag),
 
  [`Statement`](#statement-tag), or
 
  [`Contract`](#contract-tag).  Exceptions to this requirement are as follows:
 
     + the income generated from the transaction is less than $800, or
 
     + the `IncomeType` is `RBI` and the income is for a defined, public
 
       program (such as conference registration)
 

	
 
* An [`Entity`](#entity-tag) tag, *iff.* the Income for the transaction is
 
  for more than $800.
 

	
 
* An [`IncomeType`](#incometype-tag) tag.
 

	
 
* A [`Program`](#program-tag) tag.
0 comments (0 inline, 0 general)