Changeset - 01013ec96c78
[Not reviewed]
0 1 0
Bradley Kuhn (bkuhn) - 8 years ago 2013-04-21 19:41:32
bkuhn@ebb.org
Beginning of general description of using Ledger CLI for fiscal sponsorship accounts.
1 file changed with 31 insertions and 0 deletions:
0 comments (0 inline, 0 general)
npo-ledger-cli-tutorial.md
Show inline comments
...
 
@@ -110,2 +110,33 @@ longer used.)
 

	
 
Handling Fiscal Sponsorship
 
---------------------------
 

	
 
NPOs that do not provide fiscal sponsorship services will find this section
 
somewhat useless.  One of the biggest benefits of Ledger CLI is its
 
incredible flexibility that just does not exist in other accounting systems.
 
This section describes how to exploit that flexibility to provide a
 
separation in your books and reporting to handle earmarked accounts for
 
fiscally sponsored projects.
 

	
 
NPOs that don't need this feature can, in most cases, use the methods
 
described herein to deploy Ledger CLI, but should leave out the `:General:`
 
and `:ProjectNAME:` parts of the account hierarchy, since these are the
 
primary mechanisms used herein to handle the fiscal sponsorship structure.
 

	
 
### Earmarked Accounts
 

	
 
Many fiscal sponsor NPOs keep earmarked accounts for their member/affiliated
 
projects.  Furthermore, these projects often may either (a) terminate their
 
agreement with the NPO, and thus deserve a copy of their books that they can
 
"take away" with them, or (b) might be affiliated with *other* NPOs that also
 
hold accounts.  This system of earmarked accounts is designed to make it easy
 
for projects to have a copy of their own accounts, but not interfere with nor
 
even be aware of (a) the books of other member/affiliated projects, and (b)
 
the overall books of the entire NPO.
 

	
 
On the latter point, this system utilizes a directory structure and separate
 
`.ledger` files to separate out the different projects into different
 
structures.  This allows member/affiliated projects to take their data and
 
run `ledger` commands against it, separately and without access to the other
 
`.ledger` files of the NPO.
 

	
0 comments (0 inline, 0 general)