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

* bank statements, as received from the banking institution.

* written reports of travel.

* blog posts made by a contractor documenting their work.

* written organizational policies about the expense.

* just about anything that is clearly not an [invoice](#invoice-tag) nor a

  [receipt](#receipt-tag), but definitely is valid backup documentation for

  the transaction.

#### TaxReporting Tag

The `TaxReporting` tag is an optional tag for `Assets` accounts that debit to

the account.

When provided, the `TaxReporting` accompanies a `TaxImplication` information

tag.  The TaxReporting refers to a document that verifies the choice for the

`TaxImplication` tag.  For example, for individual contractors in the USA, a

links to a [W-9](https://www.irs.gov/pub/irs-pdf/fw9.pdf) for the individual

being paid.  For a individual foreign contractor, the `TaxReporting` might

link to a

[W8-BEN](https://www.irs.gov/uac/form-w-8ben-certificate-of-foreign-status-of-beneficial-owner-for-united-states-tax-withholding)

for the payee.

### Information Tags

In contrast to documentation tags, information tags can more traditionally be

considered pure "meta-data" for a ledger entry.

#### Entity Tag

The `Entity:` tag is required for many types of ledger entries.  The value of

the `Entity:` tag is a unique moniker that identifies the organization,

company, person, or legal entity that is the external party for the

transaction.

Note that there is no database of these monikers, so typos can cause

trouble.  However, you could implement checks in

`accounts/config/config-tags.ledger` using a regular expression to verify no

typos have occurred.  This would be somewhat cumbersome, since Ledger CLI

would likely require that the monikers be encoded into a regular expression.

Barring that, the