NPO-Accounting/npo-ledger-cli Changeset - 18a4125ff756

Changeset - 18a4125ff756

Parent rev.

Child rev.

[Not reviewed]

0 2 0

Bradley Kuhn (bkuhn) - 11 years ago 2013-05-10 21:04:15
bkuhn@ebb.org

Initial documentation for Income accounts, including tagging requirements.

Implemented in the config-accounts.ledger is an incomeChecker() function that
matches the documentation requirements.

2 files changed with 22 insertions and 1 deletions:

accounts/config/config-accounts.ledger

npo-ledger-cli-tutorial.md

0 comments (0 inline, 0 general)

accounts/config/config-accounts.ledger

➞

Show inline comments

@@ ... / @@ -60,27 +60,29 @@ account Expense:Main Org:Payroll:Salary @@
     note Main Organization's Staff Salaries
 account Expense:Main Org:Payroll:Benefits
     assert expenseChecker() or payee =~ /NEVER CHARGED/
     note Main Organization's Staff Benefits
 account Expense:Main Org:Phones
     assert expenseChecker() or payee =~ /NEVER CHARGED/
     note Main Organization's Phone Expenses
 account Expense:Main Org:Hosting
     assert expenseChecker() or payee =~ /NEVER CHARGED/
     note Main Organization's Network Hosting Provider services
 account Expense:Main Org:Development
     assert expenseChecker() or payee =~ /NEVER CHARGED/
     note Main Organization's software development expenses
 account Expense:Main Org:Occupancy
     assert expenseChecker() or payee =~ /NEVER CHARGED/
     note Main Organization's Occupancy for Office Space and the like
 ; Organizational Income Accounts
 define incomeChecker(amt) = (tag("Entity") !~ /^\s*$/ or (amt > -800.00 and amt < 800.00)) and tag("IncomeType") !~ /^\s*$/ and tag("Program") !~ /^\s*$/
 account Income:Main Org:Donations
     assert tag("IncomeType") =~ /^Donations$/
+    assert incomeChecker(amount) and tag("IncomeType") =~ /^Donations$/
     note Donation income to the Main Org.

npo-ledger-cli-tutorial.md

➞

Show inline comments

@@ ... / @@ -399,48 +399,67 @@ through — but it turns out the charge never happened. @@
 The recommended way to resolve this problem in the system is to just delete
 the entry entirely from the Ledger file, and allow the VCS to log the fact
 that the charge was expected, but the vendor never billed the credit card.
 The reason the `NEVER CHARGED` payee text was added was to handle the
 situation where the books included this charge, but the books were already
 closed for the financial period (e.g., the books had already been audited).
 Changing the payee was a method for documenting the expense.  You might use
 it like this:
 /05/28 My Bad Billing Hosting - NEVER CHARGED
         Liabilities:Credit Card:Visa            $-100.00
         Expenses:Conservancy:Hosting             $100.00
 /01/01 My Bad Billing Hosting - REVERSAL - NEVER CHARGED
         Liabilities:Credit Card:Visa             $100.00
         Expenses:Conservancy:Hosting            $-100.00
 However, going forward, you'd likely never enter anything 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),
   [`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.
 Analysis of the Data
 --------------------
 If this methodology is followed, Ledger can be used to analyze the financial
 data for the organization.
 ### Testing Program Success
 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:
     $ ledger -f accounts/books.ledger --group-by 'tag("Program")' reg '/^Expense/'
 FIXME: example output
 ### Checking Integrity of a Tag
 [As mentioned](#entity-tag), the `Entity:` tag is one example among many
 where the value is a wide range, but since Ledger CLI isn't backed by a more

0 comments (0 inline, 0 general)