Changeset - 228dc22e03d6
[Not reviewed]
0 1 0
Bradley Kuhn (bkuhn) - 5 years ago 2017-07-10 15:29:36
GrantLocation: new tag to help w/ 990 Schedule I&F

This new tag, for use in Expense accounts, will assist in collecting
data for filing Form 990 Schedule I (for USA domestic grants) and
Schedule F (for foreign grants).
1 file changed with 16 insertions and 0 deletions:
0 comments (0 inline, 0 general)
Show inline comments
@@ -366,12 +366,24 @@ particular program activity an expense is toward (e.g., funding travel to
some specific conference).

The Program tag is always a string with the same format as a Ledger CLI
account (primarily for use with Ledger CLI's `--pivot` and `--group-by`,
[as described later](#testing-program-success)).

#### GrantLocation Tag

The `GrantLocation` tag is used to indicate that an expense is a grant.  The
value for the tag should indicate the geographical region.  It is recommend
that the geographical reason be identified with the
[ISO 3166-2]( two letter country
code for the country where the grant goes.

This tag is to assist in filing
Form 990, [Schedule I]( and
[Schedule F](

### Account Type Documentation Requirements

Each account type has different documentation requirements.  Based on the
type of the account, it requires a different set of tags.

When Ledger CLI's `--pedantic` option is used, these rules are enforced by
@@ -386,12 +398,16 @@ Each `Expenses:` account entry must be tagged with the following tags:
  [`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).)

* A [`Program:`](#program-tag) tag.

Expense accounts can have the following optional tag:

* A [`GrantLocation:`](#grantlocation-tag) tag.


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
historical special-case.  The solution was originally design for the
following scenario:
0 comments (0 inline, 0 general)