slaesvuo/hledger
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

;doc: update manuals

Browse Source
This commit is contained in:
Simon Michael 2021-12-21 10:53:19 -10:00
parent 82cd81c066
commit 4bf0d76a1f
3 changed files with 2233 additions and 1721 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

182
hledger/hledger.1
View File

@ -1529,12 +1529,171 @@ not the old one, and \f[C]amt:\f[R] matches the new quantity, and not
the old one. the old one.
Note: this changed in hledger 1.22, previously it was the reverse, see Note: this changed in hledger 1.22, previously it was the reverse, see
the discussion at #1625. the discussion at #1625.
.SH COSTING .SS CONVERSION & COST
.PP .PP
The \f[C]-B/--cost\f[R] flag converts amounts to their cost or sale This section is about converting between commodities.
amount at transaction time, if they have a transaction price specified. Some definitions:
If this flag is supplied, hledger will perform cost conversion first, .IP \[bu] 2
and will apply any market price valuations (if requested) afterwards. A \[dq]commodity conversion\[dq] is an exchange of one currency or
commodity for another.
Eg a foreign currency exchange, or a purchase or sale of stock or
cryptocurrency.
.IP \[bu] 2
A \[dq]conversion transaction\[dq] is a transaction involving one or
more such conversions.
.IP \[bu] 2
\[dq]Conversion rate\[dq] is the exchange rate in a conversion - the
cost per unit of one commodity in the other.
.IP \[bu] 2
\[dq]Cost\[dq] is how much of one commodity was paid to acquire the
other (when buying), or how much was received in exchange for the other
(when selling).
We call both of these \[dq]cost\[dq] for convenience (after all, it is
cost for one party or the other).
.SS Recording conversions
.PP
As a concrete example, let\[aq]s assume 100 EUR was converted to 120
USD.
There are several ways to record this in the journal, each with pros and
cons which will be explained in more detail below.
(Also, these examples use journal format which is properly explained
much further below; sorry about that, you may want to read some of that
first.)
.SS Implicit conversion
.PP
You can just record the outflow (100 EUR) and inflow (120 USD) in the
appropriate asset account:
.IP
.nf
\f[C]
2021-01-01
assets:cash -100 EUR
assets:cash 120 USD
\f[R]
.fi
.PP
hledger will assume this transaction is balanced, inferring that the
conversion rate must be 1 EUR = 1.20 USD.
You can see the inferred rate by using \f[C]hledger print -x\f[R].
.PP
Pro: - Easy, concise - hledger can do cost reporting
.PP
Con: - Less error checking - typos in amounts or commodity symbols may
not be detected - conversion rate is not clear - disturbs the accounting
equation
.PP
You can prevent accidental implicit conversions due to a mistyped
commodity symbol, by using \f[C]hledger check commodities\f[R].
You can prevent implicit conversions entirely, by using
\f[C]hledger check balancednoautoconversion\f[R], or
\f[C]-s/--strict\f[R].
.SS Priced conversion
.PP
You can add the conversion rate using \[at] notation:
.IP
.nf
\f[C]
2021-01-01
assets:cash -100 EUR \[at] 1.20 USD
assets:cash 120 USD
\f[R]
.fi
.PP
Now hledger will check that 100 * 1.20 = 120, and would report an error
otherwise.
.PP
Pro: - Still concise - makes the conversion rate clear - provides some
error checking - hledger can do cost reporting
.PP
Con: - Disturbs the accounting equation
.SS Equity conversion
.PP
In strict double entry bookkeeping, the above transaction is not
balanced in EUR or in USD, since some EUR disappears, and some USD
appears.
This violates the accounting equation (A+L+E=0), and prevents reports
like \f[C]balancesheetequity\f[R] from showing a zero total.
.PP
The proper way to make it balance is to add a balancing posting for each
commodity, using an equity account:
.IP
.nf
\f[C]
2021-01-01
assets:cash -100 EUR
equity:conversion 100 EUR
equity:conversion -120 USD
assets:cash 120 USD
\f[R]
.fi
.PP
Pro: - Preserves the accounting equation - keeps track of conversions
and related gains/losses in one place - works in any double entry
accounting system
.PP
Con: - More verbose - conversion rate is not clear - hledger can not do
cost reporting
.SS Priced equity conversion
.PP
Another possible notation would be to record both the conversion rate
and the equity postings:
.IP
.nf
\f[C]
2021-01-01
assets:cash -100 EUR \[at] 1.20 USD
equity:conversion 100 EUR
equity:conversion -120 USD
assets:cash 120 USD
\f[R]
.fi
.PP
hledger currently does not allow this; instead, you can record the
conversion rate as a comment.
.SS Inferring missing conversion rates
.PP
hledger will do this automatically for implicit conversions.
Currently it can not do this for equity conversions.
.SS Inferring missing equity postings
.PP
With the \f[C]--infer-equity\f[R] flag, hledger will add equity postings
to priced and implicit conversions (and move the conversion rate into a
comment).
.SS Cost reporting
.PP
With the \f[C]-B/--cost\f[R] flag, hledger will convert the amounts in
priced and implicit conversions to their cost in the other commodity.
This is useful to see a report of what you paid for things (or how much
you sold things for).
Currently \f[C]-B/--cost\f[R] does not work on equity conversions, and
it disables \f[C]--infer-equity\f[R].
.PP
These operations are transient, only affecting reports.
If you want to change the journal file permanently, you could pipe each
entry through \f[C]hledger -f- -I print [-x] [--infer-equity] [-B]\f[R]
.SS Conversion summary
.IP \[bu] 2
Recording the conversion rate is good because it makes that clear and
allows cost reporting.
.IP \[bu] 2
Recording equity postings is good because it balances the accounting
equation and is correct bookkeeping.
.IP \[bu] 2
Combining these is not yet supported, so you have to choose.
For now, priced conversions are a good compromise, so that:
.RS 2
.IP \[bu] 2
When you want to see the cost (or sale proceeds) of things, use
\f[C]-B/--cost\f[R].
.IP \[bu] 2
When you want to see a balanced balance sheet or correct journal
entries, use \f[C]--infer-equity\f[R].
.IP \[bu] 2
Combining these is not yet supported; \f[C]-B/--cost\f[R] will take
precedence.
.RE
.IP \[bu] 2
Conversion/cost operations are performed before valuation.
.SH VALUATION .SH VALUATION
.PP .PP
Instead of reporting amounts in their original commodity, hledger can Instead of reporting amounts in their original commodity, hledger can
@ -7579,9 +7738,10 @@ account ACCTNAME [ACCTTYPE] [;COMMENT]
.PP .PP
By adding a \f[C]type\f[R] tag to the account directive, with value By adding a \f[C]type\f[R] tag to the account directive, with value
\f[C]A\f[R], \f[C]L\f[R], \f[C]E\f[R], \f[C]R\f[R], \f[C]X\f[R], \f[C]A\f[R], \f[C]L\f[R], \f[C]E\f[R], \f[C]R\f[R], \f[C]X\f[R],
\f[C]C\f[R] (or if you prefer: \f[C]Asset\f[R], \f[C]Liability\f[R], \f[C]C\f[R], \f[C]V\f[R] (or if you prefer: \f[C]Asset\f[R],
\f[C]Equity\f[R], \f[C]Revenue\f[R], \f[C]Expense\f[R], \f[C]Cash\f[R]), \f[C]Liability\f[R], \f[C]Equity\f[R], \f[C]Revenue\f[R],
you can declare hledger accounts to be of a certain type: \f[C]Expense\f[R], \f[C]Cash\f[R], \f[C]Conversion\f[R]), you can
declare hledger accounts to be of a certain type:
.IP \[bu] 2 .IP \[bu] 2
\f[B]asset\f[R], \f[B]liability\f[R], \f[B]equity\f[R], \f[B]asset\f[R], \f[B]liability\f[R], \f[B]equity\f[R],
\f[B]revenue\f[R], \f[B]expense\f[R] \f[B]revenue\f[R], \f[B]expense\f[R]
@ -7595,6 +7755,12 @@ the standard types in accounting, or
.P .P
.PD .PD
a subtype of asset, used for liquid assets. a subtype of asset, used for liquid assets.
.IP \[bu] 2
\f[B]conversion\f[R]
.PD 0
.P
.PD
a subtype of equity, used for conversion postings
.PP .PP
Declaring account types is a good idea, since it helps enable the easy Declaring account types is a good idea, since it helps enable the easy
balancesheet, balancesheetequity, incomestatement and cashflow reports, balancesheet, balancesheetequity, incomestatement and cashflow reports,

1743
hledger/hledger.info
View File

File diff suppressed because it is too large Load Diff

161
hledger/hledger.txt
View File

@ -1033,11 +1033,145 @@ QUERIES
this changed in hledger 1.22, previously it was the reverse, see the this changed in hledger 1.22, previously it was the reverse, see the
discussion at #1625. discussion at #1625.
COSTING CONVERSION & COST
The -B/--cost flag converts amounts to their cost or sale amount at This section is about converting between commodities. Some defini-
transaction time, if they have a transaction price specified. If this tions:
flag is supplied, hledger will perform cost conversion first, and will
apply any market price valuations (if requested) afterwards. o A "commodity conversion" is an exchange of one currency or commodity
for another. Eg a foreign currency exchange, or a purchase or sale
of stock or cryptocurrency.
o A "conversion transaction" is a transaction involving one or more
such conversions.
o "Conversion rate" is the exchange rate in a conversion - the cost per
unit of one commodity in the other.
o "Cost" is how much of one commodity was paid to acquire the other
(when buying), or how much was received in exchange for the other
(when selling). We call both of these "cost" for convenience (after
all, it is cost for one party or the other).
Recording conversions
As a concrete example, let's assume 100 EUR was converted to 120 USD.
There are several ways to record this in the journal, each with pros
and cons which will be explained in more detail below. (Also, these
examples use journal format which is properly explained much further
below; sorry about that, you may want to read some of that first.)
Implicit conversion
You can just record the outflow (100 EUR) and inflow (120 USD) in the
appropriate asset account:
2021-01-01
assets:cash -100 EUR
assets:cash 120 USD
hledger will assume this transaction is balanced, inferring that the
conversion rate must be 1 EUR = 1.20 USD. You can see the inferred
rate by using hledger print -x.
Pro: - Easy, concise - hledger can do cost reporting
Con: - Less error checking - typos in amounts or commodity symbols may
not be detected - conversion rate is not clear - disturbs the account-
ing equation
You can prevent accidental implicit conversions due to a mistyped com-
modity symbol, by using hledger check commodities. You can prevent
implicit conversions entirely, by using hledger check balancednoauto-
conversion, or -s/--strict.
Priced conversion
You can add the conversion rate using @ notation:
2021-01-01
assets:cash -100 EUR @ 1.20 USD
assets:cash 120 USD
Now hledger will check that 100 * 1.20 = 120, and would report an error
otherwise.
Pro: - Still concise - makes the conversion rate clear - provides some
error checking - hledger can do cost reporting
Con: - Disturbs the accounting equation
Equity conversion
In strict double entry bookkeeping, the above transaction is not bal-
anced in EUR or in USD, since some EUR disappears, and some USD
appears. This violates the accounting equation (A+L+E=0), and prevents
reports like balancesheetequity from showing a zero total.
The proper way to make it balance is to add a balancing posting for
each commodity, using an equity account:
2021-01-01
assets:cash -100 EUR
equity:conversion 100 EUR
equity:conversion -120 USD
assets:cash 120 USD
Pro: - Preserves the accounting equation - keeps track of conversions
and related gains/losses in one place - works in any double entry
accounting system
Con: - More verbose - conversion rate is not clear - hledger can not do
cost reporting
Priced equity conversion
Another possible notation would be to record both the conversion rate
and the equity postings:
2021-01-01
assets:cash -100 EUR @ 1.20 USD
equity:conversion 100 EUR
equity:conversion -120 USD
assets:cash 120 USD
hledger currently does not allow this; instead, you can record the con-
version rate as a comment.
Inferring missing conversion rates
hledger will do this automatically for implicit conversions. Currently
it can not do this for equity conversions.
Inferring missing equity postings
With the --infer-equity flag, hledger will add equity postings to
priced and implicit conversions (and move the conversion rate into a
comment).
Cost reporting
With the -B/--cost flag, hledger will convert the amounts in priced and
implicit conversions to their cost in the other commodity. This is
useful to see a report of what you paid for things (or how much you
sold things for). Currently -B/--cost does not work on equity conver-
sions, and it disables --infer-equity.
These operations are transient, only affecting reports. If you want to
change the journal file permanently, you could pipe each entry through
hledger -f- -I print [-x] [--infer-equity] [-B]
Conversion summary
o Recording the conversion rate is good because it makes that clear and
allows cost reporting.
o Recording equity postings is good because it balances the accounting
equation and is correct bookkeeping.
o Combining these is not yet supported, so you have to choose. For
now, priced conversions are a good compromise, so that:
o When you want to see the cost (or sale proceeds) of things, use
-B/--cost.
o When you want to see a balanced balance sheet or correct journal
entries, use --infer-equity.
o Combining these is not yet supported; -B/--cost will take prece-
dence.
o Conversion/cost operations are performed before valuation.
VALUATION VALUATION
Instead of reporting amounts in their original commodity, hledger can Instead of reporting amounts in their original commodity, hledger can
@ -1378,9 +1512,6 @@ VALUATION
starting bal- cost value at valued at day value at value at starting bal- cost value at valued at day value at value at
ance (-H) report or each historical report or DATE/today ance (-H) report or each historical report or DATE/today
journal end posting was made journal end journal end posting was made journal end
starting bal- cost value at day valued at day value at day value at starting bal- cost value at day valued at day value at day value at
ance (-H) before each historical before DATE/today ance (-H) before each historical before DATE/today
with report report or posting was made report or with report report or posting was made report or
@ -1389,6 +1520,10 @@ VALUATION
posting cost value at value at posting value at value at posting cost value at value at posting value at value at
amounts report or date report or DATE/today amounts report or date report or DATE/today
journal end journal end journal end journal end
summary post- summarised value at sum of postings value at value at summary post- summarised value at sum of postings value at value at
ing amounts cost period ends in interval, val- period ends DATE/today ing amounts cost period ends in interval, val- period ends DATE/today
with report ued at interval with report ued at interval
@ -2247,7 +2382,6 @@ COMMANDS
wide Y Y Y wide Y Y Y
tall Y Y Y tall Y Y Y
bare Y Y Y bare Y Y Y
tidy Y tidy Y
Examples: Examples:
@ -5006,7 +5140,6 @@ JOURNAL FORMAT
And here are all the directives and their precise effects: And here are all the directives and their precise effects:
direc- effects ends direc- effects ends
tive at tive at
file file
@ -5351,8 +5484,9 @@ JOURNAL FORMAT
Account types Account types
By adding a type tag to the account directive, with value A, L, E, R, By adding a type tag to the account directive, with value A, L, E, R,
X, C (or if you prefer: Asset, Liability, Equity, Revenue, Expense, X, C, V (or if you prefer: Asset, Liability, Equity, Revenue, Expense,
Cash), you can declare hledger accounts to be of a certain type: Cash, Conversion), you can declare hledger accounts to be of a certain
type:
o asset, liability, equity, revenue, expense o asset, liability, equity, revenue, expense
the standard types in accounting, or the standard types in accounting, or
@ -5360,6 +5494,9 @@ JOURNAL FORMAT
o cash o cash
a subtype of asset, used for liquid assets. a subtype of asset, used for liquid assets.
o conversion
a subtype of equity, used for conversion postings
Declaring account types is a good idea, since it helps enable the easy Declaring account types is a good idea, since it helps enable the easy
balancesheet, balancesheetequity, incomestatement and cashflow reports, balancesheet, balancesheetequity, incomestatement and cashflow reports,
and probably other things in future. As a convenience, when account and probably other things in future. As a convenience, when account