diff --git a/hledger/hledger.1 b/hledger/hledger.1 index 2ccac782a..6ba253df6 100644 --- a/hledger/hledger.1 +++ b/hledger/hledger.1 @@ -1529,7 +1529,7 @@ not the old one, and \f[C]amt:\f[R] matches the new quantity, and not the old one. Note: this changed in hledger 1.22, previously it was the reverse, see the discussion at #1625. -.SS CONVERSION & COST +.SH CONVERSION & COST .PP This section is about converting between commodities. Some definitions: diff --git a/hledger/hledger.info b/hledger/hledger.info index 6cbd3d455..381aa0a33 100644 --- a/hledger/hledger.info +++ b/hledger/hledger.info @@ -66,6 +66,7 @@ try some commands like 'hledger print' or 'hledger balance'. Run * TIME PERIODS:: * DEPTH:: * QUERIES:: +* CONVERSION & COST:: * VALUATION:: * PIVOTING:: * OUTPUT:: @@ -1026,7 +1027,7 @@ with less detail. This flag has the same effect as a 'depth:' query argument: 'depth:2', '--depth=2' or '-2' are equivalent.  -File: hledger.info, Node: QUERIES, Next: VALUATION, Prev: DEPTH, Up: Top +File: hledger.info, Node: QUERIES, Next: CONVERSION & COST, Prev: DEPTH, Up: Top 6 QUERIES ********* @@ -1066,7 +1067,6 @@ arguments to restrict their scope. The syntax is as follows: * Queries and valuation:: * Querying with account aliases:: * Querying with cost or value:: -* CONVERSION & COST::  File: hledger.info, Node: Query types, Next: Combining query terms, Up: QUERIES @@ -1214,7 +1214,7 @@ When account names are rewritten with '--alias' or 'alias', note that 'acct:' will match either the old or the new account name.  -File: hledger.info, Node: Querying with cost or value, Next: CONVERSION & COST, Prev: Querying with account aliases, Up: QUERIES +File: hledger.info, Node: Querying with cost or value, Prev: Querying with account aliases, Up: QUERIES 6.7 Querying with cost or value =============================== @@ -1226,10 +1226,10 @@ Note: this changed in hledger 1.22, previously it was the reverse, see the discussion at #1625.  -File: hledger.info, Node: CONVERSION & COST, Prev: Querying with cost or value, Up: QUERIES +File: hledger.info, Node: CONVERSION & COST, Next: VALUATION, Prev: QUERIES, Up: Top -6.8 CONVERSION & COST -===================== +7 CONVERSION & COST +******************* This section is about converting between commodities. Some definitions: @@ -1259,8 +1259,8 @@ This section is about converting between commodities. Some definitions:  File: hledger.info, Node: Recording conversions, Next: Inferring missing conversion rates, Up: CONVERSION & COST -6.8.1 Recording conversions ---------------------------- +7.1 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 @@ -1278,8 +1278,8 @@ below; sorry about that, you may want to read some of that first.)  File: hledger.info, Node: Implicit conversion, Next: Priced conversion, Up: Recording conversions -6.8.1.1 Implicit conversion -........................... +7.1.1 Implicit conversion +------------------------- You can just record the outflow (100 EUR) and inflow (120 USD) in the appropriate asset account: @@ -1306,8 +1306,8 @@ balancednoautoconversion', or '-s/--strict'.  File: hledger.info, Node: Priced conversion, Next: Equity conversion, Prev: Implicit conversion, Up: Recording conversions -6.8.1.2 Priced conversion -......................... +7.1.2 Priced conversion +----------------------- You can add the conversion rate using @ notation: @@ -1326,8 +1326,8 @@ some error checking - hledger can do cost reporting  File: hledger.info, Node: Equity conversion, Next: Priced equity conversion, Prev: Priced conversion, Up: Recording conversions -6.8.1.3 Equity conversion -......................... +7.1.3 Equity conversion +----------------------- In strict double entry bookkeeping, the above transaction is not balanced in EUR or in USD, since some EUR disappears, and some USD @@ -1353,8 +1353,8 @@ do cost reporting  File: hledger.info, Node: Priced equity conversion, Prev: Equity conversion, Up: Recording conversions -6.8.1.4 Priced equity conversion -................................ +7.1.4 Priced equity conversion +------------------------------ Another possible notation would be to record both the conversion rate and the equity postings: @@ -1371,8 +1371,8 @@ conversion rate as a comment.  File: hledger.info, Node: Inferring missing conversion rates, Next: Inferring missing equity postings, Prev: Recording conversions, Up: CONVERSION & COST -6.8.2 Inferring missing conversion rates ----------------------------------------- +7.2 Inferring missing conversion rates +====================================== hledger will do this automatically for implicit conversions. Currently it can not do this for equity conversions. @@ -1380,8 +1380,8 @@ it can not do this for equity conversions.  File: hledger.info, Node: Inferring missing equity postings, Next: Cost reporting, Prev: Inferring missing conversion rates, Up: CONVERSION & COST -6.8.3 Inferring missing equity postings ---------------------------------------- +7.3 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 @@ -1390,8 +1390,8 @@ comment).  File: hledger.info, Node: Cost reporting, Next: Conversion summary, Prev: Inferring missing equity postings, Up: CONVERSION & COST -6.8.4 Cost reporting --------------------- +7.4 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 @@ -1406,8 +1406,8 @@ through 'hledger -f- -I print [-x] [--infer-equity] [-B]'  File: hledger.info, Node: Conversion summary, Prev: Cost reporting, Up: CONVERSION & COST -6.8.5 Conversion summary ------------------------- +7.5 Conversion summary +====================== * Recording the conversion rate is good because it makes that clear and allows cost reporting. @@ -1425,9 +1425,9 @@ File: hledger.info, Node: Conversion summary, Prev: Cost reporting, Up: CONVE * Conversion/cost operations are performed before valuation.  -File: hledger.info, Node: VALUATION, Next: PIVOTING, Prev: QUERIES, Up: Top +File: hledger.info, Node: VALUATION, Next: PIVOTING, Prev: CONVERSION & COST, Up: Top -7 VALUATION +8 VALUATION *********** Instead of reporting amounts in their original commodity, hledger can @@ -1454,7 +1454,7 @@ and '-X COMMODITY' options, and often one of these is all you need:  File: hledger.info, Node: -V Value, Next: -X Value in specified commodity, Up: VALUATION -7.1 -V: Value +8.1 -V: Value ============= The '-V/--market' flag converts amounts to market value in their default @@ -1464,7 +1464,7 @@ _valuation date(s)_, if any. More on these in a minute.  File: hledger.info, Node: -X Value in specified commodity, Next: Valuation date, Prev: -V Value, Up: VALUATION -7.2 -X: Value in specified commodity +8.2 -X: Value in specified commodity ==================================== The '-X/--exchange=COMM' option is like '-V', except you tell it which @@ -1474,7 +1474,7 @@ that.  File: hledger.info, Node: Valuation date, Next: Market prices, Prev: -X Value in specified commodity, Up: VALUATION -7.3 Valuation date +8.3 Valuation date ================== Since market prices can change from day to day, market value reports @@ -1491,7 +1491,7 @@ of the period, by default.  File: hledger.info, Node: Market prices, Next: --infer-market-prices market prices from transactions, Prev: Valuation date, Up: VALUATION -7.4 Market prices +8.4 Market prices ================= To convert a commodity A to its market value in another commodity B, @@ -1525,7 +1525,7 @@ converted.  File: hledger.info, Node: --infer-market-prices market prices from transactions, Next: Valuation commodity, Prev: Market prices, Up: VALUATION -7.5 -infer-market-prices: market prices from transactions +8.5 -infer-market-prices: market prices from transactions ========================================================= Normally, market value in hledger is fully controlled by, and requires, @@ -1559,7 +1559,7 @@ you, read all of this Valuation section carefully, and try adding  File: hledger.info, Node: Valuation commodity, Next: Simple valuation examples, Prev: --infer-market-prices market prices from transactions, Up: VALUATION -7.6 Valuation commodity +8.6 Valuation commodity ======================= *When you specify a valuation commodity ('-X COMM' or '--value @@ -1598,7 +1598,7 @@ converted.  File: hledger.info, Node: Simple valuation examples, Next: --value Flexible valuation, Prev: Valuation commodity, Up: VALUATION -7.7 Simple valuation examples +8.7 Simple valuation examples ============================= Here are some quick examples of '-V': @@ -1633,7 +1633,7 @@ $ hledger -f t.j bal -N euros -V  File: hledger.info, Node: --value Flexible valuation, Next: More valuation examples, Prev: Simple valuation examples, Up: VALUATION -7.8 -value: Flexible valuation +8.8 -value: Flexible valuation ============================== '-V' and '-X' are special cases of the more general '--value' option: @@ -1675,7 +1675,7 @@ this commodity, deducing market prices as described above.  File: hledger.info, Node: More valuation examples, Next: Interaction of valuation and queries, Prev: --value Flexible valuation, Up: VALUATION -7.9 More valuation examples +8.9 More valuation examples =========================== Here are some examples showing the effect of '--value', as seen with @@ -1789,7 +1789,7 @@ $ hledger print -X A  File: hledger.info, Node: Interaction of valuation and queries, Next: Effect of valuation on reports, Prev: More valuation examples, Up: VALUATION -7.10 Interaction of valuation and queries +8.10 Interaction of valuation and queries ========================================= When matching postings based on queries in the presence of valuation, @@ -1810,7 +1810,7 @@ the following happens.  File: hledger.info, Node: Effect of valuation on reports, Prev: Interaction of valuation and queries, Up: VALUATION -7.11 Effect of valuation on reports +8.11 Effect of valuation on reports =================================== Here is a reference for how valuation is supposed to affect each part of @@ -1959,7 +1959,7 @@ _report interval_  File: hledger.info, Node: PIVOTING, Next: OUTPUT, Prev: VALUATION, Up: Top -8 PIVOTING +9 PIVOTING ********** Normally hledger sums amounts, and organizes them in a hierarchy, based @@ -2016,8 +2016,8 @@ $ hledger balance --pivot member acct:.  File: hledger.info, Node: OUTPUT, Next: COMMANDS, Prev: PIVOTING, Up: Top -9 OUTPUT -******** +10 OUTPUT +********* * Menu: @@ -2029,8 +2029,8 @@ File: hledger.info, Node: OUTPUT, Next: COMMANDS, Prev: PIVOTING, Up: Top  File: hledger.info, Node: Output destination, Next: Output styling, Up: OUTPUT -9.1 Output destination -====================== +10.1 Output destination +======================= hledger commands send their output to the terminal by default. You can of course redirect this, eg into a file, using standard shell syntax: @@ -2052,8 +2052,8 @@ $ hledger print -o - # write to stdout (the default)  File: hledger.info, Node: Output styling, Next: Output format, Prev: Output destination, Up: OUTPUT -9.2 Output styling -================== +10.2 Output styling +=================== hledger commands can produce colour output when the terminal supports it. This is controlled by the '--color/--colour' option: - if the @@ -2072,8 +2072,8 @@ be used; - otherwise, unicode characters will not be used.  File: hledger.info, Node: Output format, Next: Commodity styles, Prev: Output styling, Up: OUTPUT -9.3 Output format -================= +10.3 Output format +================== Some commands offer additional output formats, other than the usual plain text terminal output. Here are those commands and the formats @@ -2118,8 +2118,8 @@ $ hledger balancesheet -o foo.txt -O csv # write CSV to foo.txt  File: hledger.info, Node: CSV output, Next: HTML output, Up: Output format -9.3.1 CSV output ----------------- +10.3.1 CSV output +----------------- * In CSV output, digit group marks (such as thousands separators) are disabled automatically. @@ -2127,8 +2127,8 @@ File: hledger.info, Node: CSV output, Next: HTML output, Up: Output format  File: hledger.info, Node: HTML output, Next: JSON output, Prev: CSV output, Up: Output format -9.3.2 HTML output ------------------ +10.3.2 HTML output +------------------ * HTML output can be styled by an optional 'hledger.css' file in the same directory. @@ -2136,8 +2136,8 @@ File: hledger.info, Node: HTML output, Next: JSON output, Prev: CSV output,  File: hledger.info, Node: JSON output, Next: SQL output, Prev: HTML output, Up: Output format -9.3.3 JSON output ------------------ +10.3.3 JSON output +------------------ * Not yet much used; real-world feedback is welcome. @@ -2158,8 +2158,8 @@ File: hledger.info, Node: JSON output, Next: SQL output, Prev: HTML output,  File: hledger.info, Node: SQL output, Prev: JSON output, Up: Output format -9.3.4 SQL output ----------------- +10.3.4 SQL output +----------------- * Not yet much used; real-world feedback is welcome. @@ -2175,8 +2175,8 @@ File: hledger.info, Node: SQL output, Prev: JSON output, Up: Output format  File: hledger.info, Node: Commodity styles, Prev: Output format, Up: OUTPUT -9.4 Commodity styles -==================== +10.4 Commodity styles +===================== The display style of a commodity/currency is inferred according to the rules described in Commodity display style. The inferred display style @@ -2196,7 +2196,7 @@ multiple commodity/currency symbols.  File: hledger.info, Node: COMMANDS, Next: JOURNAL FORMAT, Prev: OUTPUT, Up: Top -10 COMMANDS +11 COMMANDS *********** hledger provides a number of commands for producing reports and managing @@ -2311,7 +2311,7 @@ these are maintained and released with hledger:  File: hledger.info, Node: accounts, Next: activity, Up: COMMANDS -10.1 accounts +11.1 accounts ============= accounts @@ -2341,7 +2341,7 @@ liabilities:debts  File: hledger.info, Node: activity, Next: add, Prev: accounts, Up: COMMANDS -10.2 activity +11.2 activity ============= activity @@ -2362,7 +2362,7 @@ $ hledger activity --quarterly  File: hledger.info, Node: add, Next: aregister, Prev: activity, Up: COMMANDS -10.3 add +11.3 add ======== add @@ -2433,7 +2433,7 @@ file path ends with a period, as that would cause problems (#1056).  File: hledger.info, Node: aregister, Next: balance, Prev: add, Up: COMMANDS -10.4 aregister +11.4 aregister ============== aregister, areg @@ -2497,7 +2497,7 @@ options. The output formats supported are 'txt', 'csv', and 'json'.  File: hledger.info, Node: aregister and custom posting dates, Up: aregister -10.4.1 aregister and custom posting dates +11.4.1 aregister and custom posting dates ----------------------------------------- Transactions whose date is outside the report period can still be shown, @@ -2513,7 +2513,7 @@ it's probably best to assume the running balance is wrong.  File: hledger.info, Node: balance, Next: balancesheet, Prev: aregister, Up: COMMANDS -10.5 balance +11.5 balance ============ balance, bal @@ -2551,7 +2551,7 @@ more control, then use 'balance'.  File: hledger.info, Node: balance features, Next: Simple balance report, Up: balance -10.5.1 balance features +11.5.1 balance features ----------------------- Here's a quick overview of the 'balance' command's features, followed by @@ -2613,7 +2613,7 @@ in the transactions of the postings which would normally be shown.  File: hledger.info, Node: Simple balance report, Next: Filtered balance report, Prev: balance features, Up: balance -10.5.2 Simple balance report +11.5.2 Simple balance report ---------------------------- With no arguments, 'balance' shows a list of all accounts and their @@ -2659,7 +2659,7 @@ $ hledger -f examples/sample.journal bal -E  File: hledger.info, Node: Filtered balance report, Next: List or tree mode, Prev: Simple balance report, Up: balance -10.5.3 Filtered balance report +11.5.3 Filtered balance report ------------------------------ You can show fewer accounts, a different time period, totals from @@ -2674,7 +2674,7 @@ $ hledger -f examples/sample.journal bal --cleared assets date:200806  File: hledger.info, Node: List or tree mode, Next: Depth limiting, Prev: Filtered balance report, Up: balance -10.5.4 List or tree mode +11.5.4 List or tree mode ------------------------ By default, or with '-l/--flat', accounts are shown as a flat list with @@ -2717,7 +2717,7 @@ $ hledger -f examples/sample.journal balance  File: hledger.info, Node: Depth limiting, Next: Dropping top-level accounts, Prev: List or tree mode, Up: balance -10.5.5 Depth limiting +11.5.5 Depth limiting --------------------- With a 'depth:NUM' query, or '--depth NUM' option, or just '-NUM' (eg: @@ -2739,7 +2739,7 @@ $ hledger -f examples/sample.journal balance -1  File: hledger.info, Node: Dropping top-level accounts, Next: Multi-period balance report, Prev: Depth limiting, Up: balance -10.5.6 Dropping top-level accounts +11.5.6 Dropping top-level accounts ---------------------------------- You can also hide one or more top-level account name parts, using @@ -2755,7 +2755,7 @@ $ hledger -f examples/sample.journal bal expenses --drop 1  File: hledger.info, Node: Multi-period balance report, Next: Showing declared accounts, Prev: Dropping top-level accounts, Up: balance -10.5.7 Multi-period balance report +11.5.7 Multi-period balance report ---------------------------------- With a report interval (set by the '-D/--daily', '-W/--weekly', @@ -2810,7 +2810,7 @@ viewing in the terminal. Here are some ways to handle that:  File: hledger.info, Node: Showing declared accounts, Next: Data layout, Prev: Multi-period balance report, Up: balance -10.5.8 Showing declared accounts +11.5.8 Showing declared accounts -------------------------------- With '--declared', accounts which have been declared with an account @@ -2828,7 +2828,7 @@ accounts yet.  File: hledger.info, Node: Data layout, Next: Sorting by amount, Prev: Showing declared accounts, Up: balance -10.5.9 Data layout +11.5.9 Data layout ------------------ The '--layout' option affects how multi-commodity amounts are displayed, @@ -2962,7 +2962,7 @@ tidy Y  File: hledger.info, Node: Sorting by amount, Next: Percentages, Prev: Data layout, Up: balance -10.5.10 Sorting by amount +11.5.10 Sorting by amount ------------------------- With '-S/--sort-amount', accounts with the largest (most positive) @@ -2980,7 +2980,7 @@ which flip the sign automatically. Eg: 'hledger incomestatement -MAS').  File: hledger.info, Node: Percentages, Next: Balance change end balance, Prev: Sorting by amount, Up: balance -10.5.11 Percentages +11.5.11 Percentages ------------------- With '-%/--percent', balance reports show each account's value expressed @@ -3013,7 +3013,7 @@ $ hledger bal -% cur:€  File: hledger.info, Node: Balance change end balance, Next: Balance report types, Prev: Percentages, Up: balance -10.5.12 Balance change, end balance +11.5.12 Balance change, end balance ----------------------------------- It's important to be clear on the meaning of the numbers shown in @@ -3050,7 +3050,7 @@ historical end balances:  File: hledger.info, Node: Balance report types, Next: Useful balance reports, Prev: Balance change end balance, Up: balance -10.5.13 Balance report types +11.5.13 Balance report types ---------------------------- For more flexible reporting, there are three important option groups: @@ -3147,7 +3147,7 @@ v /now'  File: hledger.info, Node: Useful balance reports, Next: Budget report, Prev: Balance report types, Up: balance -10.5.14 Useful balance reports +11.5.14 Useful balance reports ------------------------------ Some frequently used 'balance' options/reports are: @@ -3187,7 +3187,7 @@ Some frequently used 'balance' options/reports are:  File: hledger.info, Node: Budget report, Next: Customising single-period balance reports, Prev: Useful balance reports, Up: balance -10.5.15 Budget report +11.5.15 Budget report --------------------- The '--budget' report type activates extra columns showing any budget @@ -3311,7 +3311,7 @@ Budget performance in 2017/11/01-2017/12/31:  File: hledger.info, Node: Budget report start date, Next: Budgets and subaccounts, Up: Budget report -10.5.15.1 Budget report start date +11.5.15.1 Budget report start date .................................. This might be a bug, but for now: when making budget reports, it's a @@ -3355,7 +3355,7 @@ Budget performance in 2020-01-01..2020-01-15:  File: hledger.info, Node: Budgets and subaccounts, Next: Selecting budget goals, Prev: Budget report start date, Up: Budget report -10.5.15.2 Budgets and subaccounts +11.5.15.2 Budgets and subaccounts ................................. You can add budgets to any account in your account hierarchy. If you @@ -3443,7 +3443,7 @@ Budget performance in 2019/01:  File: hledger.info, Node: Selecting budget goals, Prev: Budgets and subaccounts, Up: Budget report -10.5.15.3 Selecting budget goals +11.5.15.3 Selecting budget goals ................................ The budget report evaluates periodic transaction rules to generate @@ -3469,7 +3469,7 @@ select from multiple budgets defined in your journal.  File: hledger.info, Node: Customising single-period balance reports, Prev: Budget report, Up: balance -10.5.16 Customising single-period balance reports +11.5.16 Customising single-period balance reports ------------------------------------------------- For single-period balance reports displayed in the terminal (only), you @@ -3532,7 +3532,7 @@ may be needed to get pleasing results.  File: hledger.info, Node: balancesheet, Next: balancesheetequity, Prev: balance, Up: COMMANDS -10.6 balancesheet +11.6 balancesheet ================= balancesheet, bs @@ -3580,7 +3580,7 @@ options The output formats supported are 'txt', 'csv', 'html', and  File: hledger.info, Node: balancesheetequity, Next: cashflow, Prev: balancesheet, Up: COMMANDS -10.7 balancesheetequity +11.7 balancesheetequity ======================= balancesheetequity, bse @@ -3632,7 +3632,7 @@ options The output formats supported are 'txt', 'csv', 'html', and  File: hledger.info, Node: cashflow, Next: check, Prev: balancesheetequity, Up: COMMANDS -10.8 cashflow +11.8 cashflow ============= cashflow, cf @@ -3673,7 +3673,7 @@ options The output formats supported are 'txt', 'csv', 'html', and  File: hledger.info, Node: check, Next: close, Prev: cashflow, Up: COMMANDS -10.9 check +11.9 check ========== check @@ -3703,7 +3703,7 @@ hledger check ordereddates payees # basic + two other checks  File: hledger.info, Node: Basic checks, Next: Strict checks, Up: check -10.9.1 Basic checks +11.9.1 Basic checks ------------------- These checks are always run automatically, by (almost) all hledger @@ -3723,7 +3723,7 @@ commands, including 'check':  File: hledger.info, Node: Strict checks, Next: Other checks, Prev: Basic checks, Up: check -10.9.2 Strict checks +11.9.2 Strict checks -------------------- These additional checks are run when the '-s'/'--strict' (strict mode) @@ -3741,7 +3741,7 @@ flag is used. Or, they can be run by giving their names as arguments to  File: hledger.info, Node: Other checks, Next: Custom checks, Prev: Strict checks, Up: check -10.9.3 Other checks +11.9.3 Other checks ------------------- These checks can be run only by giving their names as arguments to @@ -3757,7 +3757,7 @@ therefore optional:  File: hledger.info, Node: Custom checks, Prev: Other checks, Up: check -10.9.4 Custom checks +11.9.4 Custom checks -------------------- A few more checks are are available as separate add-on commands, in @@ -3775,7 +3775,7 @@ See: Cookbook -> Scripting.  File: hledger.info, Node: close, Next: codes, Prev: check, Up: COMMANDS -10.10 close +11.10 close =========== close, equity @@ -3829,7 +3829,7 @@ posting it balances (good for troubleshooting).  File: hledger.info, Node: close and prices, Next: close date, Up: close -10.10.1 close and prices +11.10.1 close and prices ------------------------ Transaction prices are ignored (and discarded) by closing/opening @@ -3842,7 +3842,7 @@ will generate very large journal entries.  File: hledger.info, Node: close date, Next: Example close asset/liability accounts for file transition, Prev: close and prices, Up: close -10.10.2 close date +11.10.2 close date ------------------ The default closing date is yesterday, or the journal's end date, @@ -3866,7 +3866,7 @@ argument  File: hledger.info, Node: Example close asset/liability accounts for file transition, Next: Hiding opening/closing transactions, Prev: close date, Up: close -10.10.3 Example: close asset/liability accounts for file transition +11.10.3 Example: close asset/liability accounts for file transition ------------------------------------------------------------------- Carrying asset/liability balances from 2020.journal into a new file for @@ -3891,7 +3891,7 @@ $ hledger bs -f 2020.journal # just old files - balances are z  File: hledger.info, Node: Hiding opening/closing transactions, Next: close and balance assertions, Prev: Example close asset/liability accounts for file transition, Up: close -10.10.4 Hiding opening/closing transactions +11.10.4 Hiding opening/closing transactions ------------------------------------------- Although the closing/opening transactions cancel out, they will be @@ -3942,7 +3942,7 @@ $ hledger -f all.journal bs -p 2020 not:tag:clopen=2020  File: hledger.info, Node: close and balance assertions, Next: Example close revenue/expense accounts to retained earnings, Prev: Hiding opening/closing transactions, Up: close -10.10.5 close and balance assertions +11.10.5 close and balance assertions ------------------------------------ The closing and opening transactions will include balance assertions, @@ -3981,7 +3981,7 @@ single-day transactions):  File: hledger.info, Node: Example close revenue/expense accounts to retained earnings, Prev: close and balance assertions, Up: close -10.10.6 Example: close revenue/expense accounts to retained earnings +11.10.6 Example: close revenue/expense accounts to retained earnings -------------------------------------------------------------------- For this, use '--close' to suppress the opening transaction, as it's not @@ -4012,7 +4012,7 @@ $ hledger is -p Q1 not:desc:'closing balances'  File: hledger.info, Node: codes, Next: commodities, Prev: close, Up: COMMANDS -10.11 codes +11.11 codes =========== codes @@ -4058,7 +4058,7 @@ $ hledger codes -E  File: hledger.info, Node: commodities, Next: descriptions, Prev: codes, Up: COMMANDS -10.12 commodities +11.12 commodities ================= commodities @@ -4067,7 +4067,7 @@ List all commodity/currency symbols used or declared in the journal.  File: hledger.info, Node: descriptions, Next: diff, Prev: commodities, Up: COMMANDS -10.13 descriptions +11.13 descriptions ================== descriptions @@ -4087,7 +4087,7 @@ Person A  File: hledger.info, Node: diff, Next: files, Prev: descriptions, Up: COMMANDS -10.14 diff +11.14 diff ========== diff @@ -4122,7 +4122,7 @@ These transactions are in the second file only:  File: hledger.info, Node: files, Next: help, Prev: diff, Up: COMMANDS -10.15 files +11.15 files =========== files @@ -4132,7 +4132,7 @@ file names matching the regular expression (case sensitive) are shown.  File: hledger.info, Node: help, Next: import, Prev: files, Up: COMMANDS -10.16 help +11.16 help ========== help @@ -4158,7 +4158,7 @@ select a particular viewer with the '-i' (info), '-m' (man), or '-p'  File: hledger.info, Node: import, Next: incomestatement, Prev: help, Up: COMMANDS -10.17 import +11.17 import ============ import @@ -4186,7 +4186,7 @@ most common import source, and these docs focus on that case.  File: hledger.info, Node: Deduplication, Next: Import testing, Up: import -10.17.1 Deduplication +11.17.1 Deduplication --------------------- As a convenience 'import' does _deduplication_ while reading @@ -4230,7 +4230,7 @@ certain date.  File: hledger.info, Node: Import testing, Next: Importing balance assignments, Prev: Deduplication, Up: import -10.17.2 Import testing +11.17.2 Import testing ---------------------- With '--dry-run', the transactions that will be imported are printed to @@ -4248,7 +4248,7 @@ $ ls bank.csv* | entr bash -c 'echo ====; hledger import --dry bank.csv | hledge  File: hledger.info, Node: Importing balance assignments, Next: Commodity display styles, Prev: Import testing, Up: import -10.17.3 Importing balance assignments +11.17.3 Importing balance assignments ------------------------------------- Entries added by import will have their posting amounts made explicit @@ -4267,7 +4267,7 @@ please test it and send a pull request.)  File: hledger.info, Node: Commodity display styles, Prev: Importing balance assignments, Up: import -10.17.4 Commodity display styles +11.17.4 Commodity display styles -------------------------------- Imported amounts will be formatted according to the canonical commodity @@ -4276,7 +4276,7 @@ styles (declared or inferred) in the main journal file.  File: hledger.info, Node: incomestatement, Next: notes, Prev: import, Up: COMMANDS -10.18 incomestatement +11.18 incomestatement ===================== incomestatement, is @@ -4326,7 +4326,7 @@ options The output formats supported are 'txt', 'csv', 'html', and  File: hledger.info, Node: notes, Next: payees, Prev: incomestatement, Up: COMMANDS -10.19 notes +11.19 notes =========== notes @@ -4346,7 +4346,7 @@ Snacks  File: hledger.info, Node: payees, Next: prices, Prev: notes, Up: COMMANDS -10.20 payees +11.20 payees ============ payees @@ -4372,7 +4372,7 @@ Person A  File: hledger.info, Node: prices, Next: print, Prev: payees, Up: COMMANDS -10.21 prices +11.21 prices ============ prices @@ -4386,7 +4386,7 @@ displayed with their full precision.  File: hledger.info, Node: print, Next: print-unique, Prev: prices, Up: COMMANDS -10.22 print +11.22 print =========== print @@ -4509,7 +4509,7 @@ $ hledger print -Ocsv  File: hledger.info, Node: print-unique, Next: register, Prev: print, Up: COMMANDS -10.23 print-unique +11.23 print-unique ================== print-unique @@ -4530,7 +4530,7 @@ $ LEDGER_FILE=unique.journal hledger print-unique  File: hledger.info, Node: register, Next: register-match, Prev: print-unique, Up: COMMANDS -10.24 register +11.24 register ============== register, reg @@ -4628,7 +4628,7 @@ length and comparable to the others in the report.  File: hledger.info, Node: Custom register output, Up: register -10.24.1 Custom register output +11.24.1 Custom register output ------------------------------ register uses the full terminal width by default, except on windows. @@ -4660,7 +4660,7 @@ options The output formats supported are 'txt', 'csv', and  File: hledger.info, Node: register-match, Next: rewrite, Prev: register, Up: COMMANDS -10.25 register-match +11.25 register-match ==================== register-match @@ -4673,7 +4673,7 @@ ledger-autosync detect already-seen transactions when importing.  File: hledger.info, Node: rewrite, Next: roi, Prev: register-match, Up: COMMANDS -10.26 rewrite +11.26 rewrite ============= rewrite @@ -4727,7 +4727,7 @@ commodity.  File: hledger.info, Node: Re-write rules in a file, Next: Diff output format, Up: rewrite -10.26.1 Re-write rules in a file +11.26.1 Re-write rules in a file -------------------------------- During the run this tool will execute so called "Automated Transactions" @@ -4765,7 +4765,7 @@ postings.  File: hledger.info, Node: Diff output format, Next: rewrite vs print --auto, Prev: Re-write rules in a file, Up: rewrite -10.26.2 Diff output format +11.26.2 Diff output format -------------------------- To use this tool for batch modification of your journal files you may @@ -4806,7 +4806,7 @@ output from 'hledger print'.  File: hledger.info, Node: rewrite vs print --auto, Prev: Diff output format, Up: rewrite -10.26.3 rewrite vs. print -auto +11.26.3 rewrite vs. print -auto ------------------------------- This command predates print -auto, and currently does much the same @@ -4826,7 +4826,7 @@ thing, but with these differences:  File: hledger.info, Node: roi, Next: stats, Prev: rewrite, Up: COMMANDS -10.27 roi +11.27 roi ========= roi @@ -4875,7 +4875,7 @@ display, regardless of the length of reporting interval.  File: hledger.info, Node: Spaces and special characters in --inv and --pnl, Next: Semantics of --inv and --pnl, Up: roi -10.27.1 Spaces and special characters in '--inv' and +11.27.1 Spaces and special characters in '--inv' and ---------------------------------------------------- '--pnl' Note that '--inv' and '--pnl''s argument is a query, and queries @@ -4894,7 +4894,7 @@ $ hledger roi --inv="'Assets:Test 1'" --pnl="'Equity:Unrealized Profit and Loss'  File: hledger.info, Node: Semantics of --inv and --pnl, Next: IRR and TWR explained, Prev: Spaces and special characters in --inv and --pnl, Up: roi -10.27.2 Semantics of '--inv' and '--pnl' +11.27.2 Semantics of '--inv' and '--pnl' ---------------------------------------- Query supplied to '--inv' has to match all transactions that are related @@ -4948,7 +4948,7 @@ postings in the example below would be classifed as:  File: hledger.info, Node: IRR and TWR explained, Prev: Semantics of --inv and --pnl, Up: roi -10.27.3 IRR and TWR explained +11.27.3 IRR and TWR explained ----------------------------- "ROI" stands for "return on investment". Traditionally this was @@ -5011,7 +5011,7 @@ the limitations of both metrics  File: hledger.info, Node: stats, Next: tags, Prev: roi, Up: COMMANDS -10.28 stats +11.28 stats =========== stats @@ -5052,7 +5052,7 @@ selection.  File: hledger.info, Node: tags, Next: test, Prev: stats, Up: COMMANDS -10.29 tags +11.29 tags ========== tags @@ -5072,7 +5072,7 @@ they are omitted.  File: hledger.info, Node: test, Next: About add-on commands, Prev: tags, Up: COMMANDS -10.30 test +11.30 test ========== test @@ -5099,7 +5099,7 @@ $ hledger test -- -pData.Amount --color=never  File: hledger.info, Node: About add-on commands, Prev: test, Up: COMMANDS -10.31 About add-on commands +11.31 About add-on commands =========================== Add-on commands are programs or scripts in your PATH @@ -5138,7 +5138,7 @@ $ hledger-web --serve  File: hledger.info, Node: JOURNAL FORMAT, Next: CSV FORMAT, Prev: COMMANDS, Up: Top -11 JOURNAL FORMAT +12 JOURNAL FORMAT ***************** hledger's default file format, representing a General Journal. @@ -5207,7 +5207,7 @@ that looks unnecessary right now.  File: hledger.info, Node: Transactions, Next: Dates, Up: JOURNAL FORMAT -11.1 Transactions +12.1 Transactions ================= Transactions are the main unit of information in a journal file. They @@ -5236,7 +5236,7 @@ optional fields, separated by spaces:  File: hledger.info, Node: Dates, Next: Status, Prev: Transactions, Up: JOURNAL FORMAT -11.2 Dates +12.2 Dates ========== * Menu: @@ -5248,7 +5248,7 @@ File: hledger.info, Node: Dates, Next: Status, Prev: Transactions, Up: JOURN  File: hledger.info, Node: Simple dates, Next: Secondary dates, Up: Dates -11.2.1 Simple dates +12.2.1 Simple dates ------------------- Dates in the journal file use _simple dates_ format: 'YYYY-MM-DD' or @@ -5264,7 +5264,7 @@ dates documented in the hledger manual.)  File: hledger.info, Node: Secondary dates, Next: Posting dates, Prev: Simple dates, Up: Dates -11.2.2 Secondary dates +12.2.2 Secondary dates ---------------------- Real-life transactions sometimes involve more than one date - eg the @@ -5300,7 +5300,7 @@ $ hledger register checking --date2  File: hledger.info, Node: Posting dates, Prev: Secondary dates, Up: Dates -11.2.3 Posting dates +12.2.3 Posting dates -------------------- You can give individual postings a different date from their parent @@ -5335,7 +5335,7 @@ transaction and DATE2 infers its year from DATE.  File: hledger.info, Node: Status, Next: Code, Prev: Dates, Up: JOURNAL FORMAT -11.3 Status +12.3 Status =========== Transactions, or individual postings within a transaction, can have a @@ -5385,7 +5385,7 @@ your finances.  File: hledger.info, Node: Code, Next: Description, Prev: Status, Up: JOURNAL FORMAT -11.4 Code +12.4 Code ========= After the status mark, but before the description, you can optionally @@ -5396,7 +5396,7 @@ or reference number.  File: hledger.info, Node: Description, Next: Comments, Prev: Code, Up: JOURNAL FORMAT -11.5 Description +12.5 Description ================ A transaction's description is the rest of the line following the date @@ -5412,7 +5412,7 @@ comments.  File: hledger.info, Node: Payee and note, Up: Description -11.5.1 Payee and note +12.5.1 Payee and note --------------------- You can optionally include a '|' (pipe) character in descriptions to @@ -5424,7 +5424,7 @@ precise querying and pivoting by payee or by note.  File: hledger.info, Node: Comments, Next: Tags, Prev: Description, Up: JOURNAL FORMAT -11.6 Comments +12.6 Comments ============= Lines in the journal beginning with a semicolon (';') or hash ('#') or @@ -5464,7 +5464,7 @@ end comment  File: hledger.info, Node: Tags, Next: Postings, Prev: Comments, Up: JOURNAL FORMAT -11.7 Tags +12.7 Tags ========= Tags are a way to add extra labels or labelled data to postings and @@ -5507,7 +5507,7 @@ are simple strings.  File: hledger.info, Node: Postings, Next: Account names, Prev: Tags, Up: JOURNAL FORMAT -11.8 Postings +12.8 Postings ============= A posting is an addition of some amount to, or removal of some amount @@ -5539,7 +5539,7 @@ the amount, the amount will be considered part of the account name.  File: hledger.info, Node: Virtual postings, Up: Postings -11.8.1 Virtual postings +12.8.1 Virtual postings ----------------------- A posting with a parenthesised account name is called a _virtual @@ -5574,7 +5574,7 @@ postings_. You can exclude virtual postings from reports with the  File: hledger.info, Node: Account names, Next: Amounts, Prev: Postings, Up: JOURNAL FORMAT -11.9 Account names +12.9 Account names ================== Account names typically have several parts separated by a full colon, @@ -5592,7 +5592,7 @@ more spaces* (or newline).  File: hledger.info, Node: Amounts, Next: Transaction prices, Prev: Account names, Up: JOURNAL FORMAT -11.10 Amounts +12.10 Amounts ============= After the account name, there is usually an amount. (Important: between @@ -5641,7 +5641,7 @@ EUR 1E3  File: hledger.info, Node: Decimal marks digit group marks, Next: Commodity, Up: Amounts -11.10.1 Decimal marks, digit group marks +12.10.1 Decimal marks, digit group marks ---------------------------------------- A _decimal mark_ can be written as a period or a comma: @@ -5677,7 +5677,7 @@ directives will also work. These are described detail below.  File: hledger.info, Node: Commodity, Next: Directives influencing number parsing and display, Prev: Decimal marks digit group marks, Up: Amounts -11.10.2 Commodity +12.10.2 Commodity ----------------- Amounts in hledger have both a "quantity", which is a signed decimal @@ -5703,7 +5703,7 @@ these are the 'Amount' and 'MixedAmount' types.)  File: hledger.info, Node: Directives influencing number parsing and display, Next: Commodity display style, Prev: Commodity, Up: Amounts -11.10.3 Directives influencing number parsing and display +12.10.3 Directives influencing number parsing and display --------------------------------------------------------- You can add 'decimal-mark' and 'commodity' directives to the journal, to @@ -5723,7 +5723,7 @@ commodity 1 000 000.9455  File: hledger.info, Node: Commodity display style, Next: Rounding, Prev: Directives influencing number parsing and display, Up: Amounts -11.10.4 Commodity display style +12.10.4 Commodity display style ------------------------------- For the amounts in each commodity, hledger chooses a consistent display @@ -5781,7 +5781,7 @@ line option.  File: hledger.info, Node: Rounding, Prev: Commodity display style, Up: Amounts -11.10.5 Rounding +12.10.5 Rounding ---------------- Amounts are stored internally as decimal numbers with up to 255 decimal @@ -5794,7 +5794,7 @@ this could vary if hledger was built with Decimal < 0.5.1.)  File: hledger.info, Node: Transaction prices, Next: Lot prices lot dates, Prev: Amounts, Up: JOURNAL FORMAT -11.11 Transaction prices +12.11 Transaction prices ======================== Within a transaction, you can note an amount's price in another @@ -5861,7 +5861,7 @@ $ hledger bal -N --flat -B  File: hledger.info, Node: Lot prices lot dates, Next: Balance assertions, Prev: Transaction prices, Up: JOURNAL FORMAT -11.12 Lot prices, lot dates +12.12 Lot prices, lot dates =========================== Ledger allows another kind of price, lot price (four variants: @@ -5876,7 +5876,7 @@ assertion if any.  File: hledger.info, Node: Balance assertions, Next: Balance assignments, Prev: Lot prices lot dates, Up: JOURNAL FORMAT -11.13 Balance assertions +12.13 Balance assertions ======================== hledger supports Ledger-style balance assertions in journal files. @@ -5914,7 +5914,7 @@ does not disable balance assignments, below).  File: hledger.info, Node: Assertions and ordering, Next: Assertions and included files, Up: Balance assertions -11.13.1 Assertions and ordering +12.13.1 Assertions and ordering ------------------------------- hledger sorts an account's postings and assertions first by date and @@ -5933,7 +5933,7 @@ can assert intra-day balances.  File: hledger.info, Node: Assertions and included files, Next: Assertions and multiple -f options, Prev: Assertions and ordering, Up: Balance assertions -11.13.2 Assertions and included files +12.13.2 Assertions and included files ------------------------------------- With included files, things are a little more complicated. Including @@ -5945,7 +5945,7 @@ you'll have to put the assertion in the right file.  File: hledger.info, Node: Assertions and multiple -f options, Next: Assertions and commodities, Prev: Assertions and included files, Up: Balance assertions -11.13.3 Assertions and multiple -f options +12.13.3 Assertions and multiple -f options ------------------------------------------ Balance assertions don't work well across files specified with multiple @@ -5954,7 +5954,7 @@ Balance assertions don't work well across files specified with multiple  File: hledger.info, Node: Assertions and commodities, Next: Assertions and prices, Prev: Assertions and multiple -f options, Up: Balance assertions -11.13.4 Assertions and commodities +12.13.4 Assertions and commodities ---------------------------------- The asserted balance must be a simple single-commodity amount, and in @@ -6002,7 +6002,7 @@ commodity into its own subaccount:  File: hledger.info, Node: Assertions and prices, Next: Assertions and subaccounts, Prev: Assertions and commodities, Up: Balance assertions -11.13.5 Assertions and prices +12.13.5 Assertions and prices ----------------------------- Balance assertions ignore transaction prices, and should normally be @@ -6020,7 +6020,7 @@ _assignments_ do use them (see below).  File: hledger.info, Node: Assertions and subaccounts, Next: Assertions and virtual postings, Prev: Assertions and prices, Up: Balance assertions -11.13.6 Assertions and subaccounts +12.13.6 Assertions and subaccounts ---------------------------------- The balance assertions above ('=' and '==') do not count the balance @@ -6037,7 +6037,7 @@ eg:  File: hledger.info, Node: Assertions and virtual postings, Next: Assertions and precision, Prev: Assertions and subaccounts, Up: Balance assertions -11.13.7 Assertions and virtual postings +12.13.7 Assertions and virtual postings --------------------------------------- Balance assertions are checked against all postings, both real and @@ -6047,7 +6047,7 @@ query.  File: hledger.info, Node: Assertions and precision, Prev: Assertions and virtual postings, Up: Balance assertions -11.13.8 Assertions and precision +12.13.8 Assertions and precision -------------------------------- Balance assertions compare the exactly calculated amounts, which are not @@ -6058,7 +6058,7 @@ assertion failure messages show exact amounts.  File: hledger.info, Node: Balance assignments, Next: Directives, Prev: Balance assertions, Up: JOURNAL FORMAT -11.14 Balance assignments +12.14 Balance assignments ========================= Ledger-style balance assignments are also supported. These are like @@ -6095,7 +6095,7 @@ hledger or do the calculations yourself, instead of just reading it.  File: hledger.info, Node: Balance assignments and prices, Up: Balance assignments -11.14.1 Balance assignments and prices +12.14.1 Balance assignments and prices -------------------------------------- A transaction price in a balance assignment will cause the calculated @@ -6111,7 +6111,7 @@ $ hledger print --explicit  File: hledger.info, Node: Directives, Next: Directives and multiple files, Prev: Balance assignments, Up: JOURNAL FORMAT -11.15 Directives +12.15 Directives ================ A directive is a line in the journal beginning with a special keyword, @@ -6206,7 +6206,7 @@ account'*following entries until end of current file or 'end apply  File: hledger.info, Node: Directives and multiple files, Next: Comment blocks, Prev: Directives, Up: JOURNAL FORMAT -11.16 Directives and multiple files +12.16 Directives and multiple files =================================== If you use multiple '-f'/'--file' options, or the 'include' directive, @@ -6226,7 +6226,7 @@ directives do not affect parent or sibling files (see below).  File: hledger.info, Node: Comment blocks, Next: Including other files, Prev: Directives and multiple files, Up: JOURNAL FORMAT -11.17 Comment blocks +12.17 Comment blocks ==================== A line containing just 'comment' starts a commented region of the file, @@ -6236,7 +6236,7 @@ file) ends it. See also comments.  File: hledger.info, Node: Including other files, Next: Default year, Prev: Comment blocks, Up: JOURNAL FORMAT -11.18 Including other files +12.18 Including other files =========================== You can pull in the content of additional files by writing an include @@ -6267,7 +6267,7 @@ files): 'include timedot:~/notes/2020*.md'.  File: hledger.info, Node: Default year, Next: Declaring payees, Prev: Including other files, Up: JOURNAL FORMAT -11.19 Default year +12.19 Default year ================== You can set a default year to be used for subsequent dates which don't @@ -6293,7 +6293,7 @@ Y2010 ; change default year to 2010  File: hledger.info, Node: Declaring payees, Next: Declaring the decimal mark, Prev: Default year, Up: JOURNAL FORMAT -11.20 Declaring payees +12.20 Declaring payees ====================== The 'payee' directive can be used to declare a limited set of payees @@ -6306,7 +6306,7 @@ payee Whole Foods  File: hledger.info, Node: Declaring the decimal mark, Next: Declaring commodities, Prev: Declaring payees, Up: JOURNAL FORMAT -11.21 Declaring the decimal mark +12.21 Declaring the decimal mark ================================ You can use a 'decimal-mark' directive - usually one per file, at the @@ -6326,7 +6326,7 @@ thousands separators).  File: hledger.info, Node: Declaring commodities, Next: Default commodity, Prev: Declaring the decimal mark, Up: JOURNAL FORMAT -11.22 Declaring commodities +12.22 Declaring commodities =========================== You can use 'commodity' directives to declare your commodities. In fact @@ -6402,7 +6402,7 @@ style can still be overridden by supplying a command line option.  File: hledger.info, Node: Commodity error checking, Up: Declaring commodities -11.22.1 Commodity error checking +12.22.1 Commodity error checking -------------------------------- In strict mode, enabled with the '-s'/'--strict' flag, hledger will @@ -6413,7 +6413,7 @@ checking, see the notes there for more details.  File: hledger.info, Node: Default commodity, Next: Declaring market prices, Prev: Declaring commodities, Up: JOURNAL FORMAT -11.23 Default commodity +12.23 Default commodity ======================= The 'D' directive sets a default commodity, to be used for any @@ -6446,7 +6446,7 @@ commodities' command expects 'commodity' directives, and ignores 'D').  File: hledger.info, Node: Declaring market prices, Next: Declaring accounts, Prev: Default commodity, Up: JOURNAL FORMAT -11.24 Declaring market prices +12.24 Declaring market prices ============================= The 'P' directive declares a market price, which is an exchange rate @@ -6475,7 +6475,7 @@ amount values in another commodity. See Valuation.  File: hledger.info, Node: Declaring accounts, Next: Rewriting accounts, Prev: Declaring market prices, Up: JOURNAL FORMAT -11.25 Declaring accounts +12.25 Declaring accounts ======================== 'account' directives can be used to declare accounts (ie, the places @@ -6513,7 +6513,7 @@ account assets:bank:checking  File: hledger.info, Node: Account error checking, Next: Account comments, Up: Declaring accounts -11.25.1 Account error checking +12.25.1 Account error checking ------------------------------ By default, accounts come into existence when a transaction references @@ -6541,7 +6541,7 @@ been declared by an account directive. Some notes:  File: hledger.info, Node: Account comments, Next: Account subdirectives, Prev: Account error checking, Up: Declaring accounts -11.25.2 Account comments +12.25.2 Account comments ------------------------ Comments, beginning with a semicolon, can be added: @@ -6561,7 +6561,7 @@ account assets:bank:checking ; same-line comment, note 2+ spaces before ;  File: hledger.info, Node: Account subdirectives, Next: Account types, Prev: Account comments, Up: Declaring accounts -11.25.3 Account subdirectives +12.25.3 Account subdirectives ----------------------------- We also allow (and ignore) Ledger-style indented subdirectives, just for @@ -6579,7 +6579,7 @@ account ACCTNAME [ACCTTYPE] [;COMMENT]  File: hledger.info, Node: Account types, Next: Account display order, Prev: Account subdirectives, Up: Declaring accounts -11.25.4 Account types +12.25.4 Account types --------------------- By adding a 'type' tag to the account directive, with value 'A', 'L', @@ -6626,7 +6626,7 @@ they are different from the parent, but this is not common.)  File: hledger.info, Node: Auto-detected account types, Up: Account types -11.25.4.1 Auto-detected account types +12.25.4.1 Auto-detected account types ..................................... More about "guessing" account types: hledger tries to find at least one @@ -6652,7 +6652,7 @@ a mix of declared and auto-detected types can cause confusing results.  File: hledger.info, Node: Account display order, Prev: Account types, Up: Declaring accounts -11.25.5 Account display order +12.25.5 Account display order ----------------------------- Account directives also set the order in which accounts are displayed, @@ -6698,7 +6698,7 @@ means:  File: hledger.info, Node: Rewriting accounts, Next: Default parent account, Prev: Declaring accounts, Up: JOURNAL FORMAT -11.26 Rewriting accounts +12.26 Rewriting accounts ======================== You can define account alias rules which rewrite your account names, or @@ -6728,7 +6728,7 @@ hledger-web.  File: hledger.info, Node: Basic aliases, Next: Regex aliases, Up: Rewriting accounts -11.26.1 Basic aliases +12.26.1 Basic aliases --------------------- To set an account alias, use the 'alias' directive in your journal file. @@ -6752,7 +6752,7 @@ alias checking = assets:bank:wells fargo:checking  File: hledger.info, Node: Regex aliases, Next: Combining aliases, Prev: Basic aliases, Up: Rewriting accounts -11.26.2 Regex aliases +12.26.2 Regex aliases --------------------- There is also a more powerful variant that uses a regular expression, @@ -6777,7 +6777,7 @@ whitespace.  File: hledger.info, Node: Combining aliases, Next: Aliases and multiple files, Prev: Regex aliases, Up: Rewriting accounts -11.26.3 Combining aliases +12.26.3 Combining aliases ------------------------- You can define as many aliases as you like, using journal directives @@ -6814,7 +6814,7 @@ which aliases are being applied when.  File: hledger.info, Node: Aliases and multiple files, Next: end aliases, Prev: Combining aliases, Up: Rewriting accounts -11.26.4 Aliases and multiple files +12.26.4 Aliases and multiple files ---------------------------------- As explained at Directives and multiple files, 'alias' directives do not @@ -6846,7 +6846,7 @@ include c.journal ; also affected  File: hledger.info, Node: end aliases, Prev: Aliases and multiple files, Up: Rewriting accounts -11.26.5 'end aliases' +12.26.5 'end aliases' --------------------- You can clear (forget) all currently defined aliases (seen in the @@ -6857,7 +6857,7 @@ end aliases  File: hledger.info, Node: Default parent account, Next: Periodic transactions, Prev: Rewriting accounts, Up: JOURNAL FORMAT -11.27 Default parent account +12.27 Default parent account ============================ You can specify a parent account which will be prepended to all accounts @@ -6898,7 +6898,7 @@ parent account.  File: hledger.info, Node: Periodic transactions, Next: Auto postings, Prev: Default parent account, Up: JOURNAL FORMAT -11.28 Periodic transactions +12.28 Periodic transactions =========================== Periodic transaction rules describe transactions that recur. They allow @@ -6945,7 +6945,7 @@ to define budget goals, shown in budget reports.  File: hledger.info, Node: Periodic rule syntax, Next: Two spaces between period expression and description!, Up: Periodic transactions -11.28.1 Periodic rule syntax +12.28.1 Periodic rule syntax ---------------------------- A periodic transaction rule looks like a normal journal entry, with the @@ -6968,7 +6968,7 @@ will be relative to Y/1/1.  File: hledger.info, Node: Two spaces between period expression and description!, Next: Forecasting with periodic transactions, Prev: Periodic rule syntax, Up: Periodic transactions -11.28.2 Two spaces between period expression and description! +12.28.2 Two spaces between period expression and description! ------------------------------------------------------------- If the period expression is followed by a transaction description, these @@ -6993,7 +6993,7 @@ accidentally alter their meaning, as in this example:  File: hledger.info, Node: Forecasting with periodic transactions, Next: Budgeting with periodic transactions, Prev: Two spaces between period expression and description!, Up: Periodic transactions -11.28.3 Forecasting with periodic transactions +12.28.3 Forecasting with periodic transactions ---------------------------------------------- The '--forecast' flag activates any periodic transaction rules in the @@ -7061,7 +7061,7 @@ you can get around it in two ways:  File: hledger.info, Node: Budgeting with periodic transactions, Prev: Forecasting with periodic transactions, Up: Periodic transactions -11.28.4 Budgeting with periodic transactions +12.28.4 Budgeting with periodic transactions -------------------------------------------- With the '--budget' flag, currently supported by the balance command, @@ -7076,7 +7076,7 @@ compared in budget reports.  File: hledger.info, Node: Auto postings, Prev: Periodic transactions, Up: JOURNAL FORMAT -11.29 Auto postings +12.29 Auto postings =================== "Automated postings" or "auto postings" are extra postings which get @@ -7154,7 +7154,7 @@ $ hledger print --auto  File: hledger.info, Node: Auto postings and multiple files, Next: Auto postings and dates, Up: Auto postings -11.29.1 Auto postings and multiple files +12.29.1 Auto postings and multiple files ---------------------------------------- An auto posting rule can affect any transaction in the current file, or @@ -7164,7 +7164,7 @@ sibling files (when multiple '-f'/'--file' are used - see #1212).  File: hledger.info, Node: Auto postings and dates, Next: Auto postings and transaction balancing / inferred amounts / balance assertions, Prev: Auto postings and multiple files, Up: Auto postings -11.29.2 Auto postings and dates +12.29.2 Auto postings and dates ------------------------------- A posting date (or secondary date) in the matched posting, or (taking @@ -7174,7 +7174,7 @@ used in the generated posting.  File: hledger.info, Node: Auto postings and transaction balancing / inferred amounts / balance assertions, Next: Auto posting tags, Prev: Auto postings and dates, Up: Auto postings -11.29.3 Auto postings and transaction balancing / inferred amounts / +12.29.3 Auto postings and transaction balancing / inferred amounts / -------------------------------------------------------------------- balance assertions Currently, auto postings are added: @@ -7194,7 +7194,7 @@ infer amounts.  File: hledger.info, Node: Auto posting tags, Prev: Auto postings and transaction balancing / inferred amounts / balance assertions, Up: Auto postings -11.29.4 Auto posting tags +12.29.4 Auto posting tags ------------------------- Automated postings will have some extra tags: @@ -7216,7 +7216,7 @@ will have these tags added:  File: hledger.info, Node: CSV FORMAT, Next: TIMECLOCK FORMAT, Prev: JOURNAL FORMAT, Up: Top -12 CSV FORMAT +13 CSV FORMAT ************* How hledger reads CSV data, and the CSV rules file format. @@ -7281,7 +7281,7 @@ below.  File: hledger.info, Node: Examples, Next: CSV rules, Up: CSV FORMAT -12.1 Examples +13.1 Examples ============= Here are some sample hledger CSV rules files. See also the full @@ -7298,7 +7298,7 @@ https://github.com/simonmichael/hledger/tree/master/examples/csv  File: hledger.info, Node: Basic, Next: Bank of Ireland, Up: Examples -12.1.1 Basic +13.1.1 Basic ------------ At minimum, the rules file must identify the date and amount fields, and @@ -7323,7 +7323,7 @@ $ hledger print -f basic.csv  File: hledger.info, Node: Bank of Ireland, Next: Amazon, Prev: Basic, Up: Examples -12.1.2 Bank of Ireland +13.1.2 Bank of Ireland ---------------------- Here's a CSV with two amount fields (Debit and Credit), and a balance @@ -7376,7 +7376,7 @@ imported into a journal file.  File: hledger.info, Node: Amazon, Next: Paypal, Prev: Bank of Ireland, Up: Examples -12.1.3 Amazon +13.1.3 Amazon ------------- Here we convert amazon.com order history, and use an if block to @@ -7434,7 +7434,7 @@ $ hledger -f amazon-orders.csv print  File: hledger.info, Node: Paypal, Prev: Amazon, Up: Examples -12.1.4 Paypal +13.1.4 Paypal ------------- Here's a real-world rules file for (customised) Paypal CSV, with some @@ -7588,7 +7588,7 @@ $ hledger -f paypal-custom.csv print  File: hledger.info, Node: CSV rules, Next: Tips, Prev: Examples, Up: CSV FORMAT -12.2 CSV rules +13.2 CSV rules ============== The following kinds of rule can appear in the rules file, in any order. @@ -7613,7 +7613,7 @@ Blank lines and lines beginning with '#' or ';' are ignored.  File: hledger.info, Node: skip, Next: fields list, Up: CSV rules -12.2.1 'skip' +13.2.1 'skip' ------------- skip N @@ -7629,7 +7629,7 @@ ignore certain CSV records (described below).  File: hledger.info, Node: fields list, Next: field assignment, Prev: skip, Up: CSV rules -12.2.2 'fields' list +13.2.2 'fields' list -------------------- fields FIELDNAME1, FIELDNAME2, ... @@ -7672,7 +7672,7 @@ fields date, description, , amount, , , somefield, anotherfield  File: hledger.info, Node: field assignment, Next: Field names, Prev: fields list, Up: CSV rules -12.2.3 field assignment +13.2.3 field assignment ----------------------- HLEDGERFIELDNAME FIELDVALUE @@ -7706,7 +7706,7 @@ comment note: %somefield - %anotherfield, date: %1  File: hledger.info, Node: Field names, Next: separator, Prev: field assignment, Up: CSV rules -12.2.4 Field names +13.2.4 Field names ------------------ Here are the standard hledger field (and pseudo-field) names, which you @@ -7729,7 +7729,7 @@ transaction parts they refer to, see Transactions.  File: hledger.info, Node: date field, Next: date2 field, Up: Field names -12.2.4.1 date field +13.2.4.1 date field ................... Assigning to 'date' sets the transaction date. @@ -7737,7 +7737,7 @@ Assigning to 'date' sets the transaction date.  File: hledger.info, Node: date2 field, Next: status field, Prev: date field, Up: Field names -12.2.4.2 date2 field +13.2.4.2 date2 field .................... 'date2' sets the transaction's secondary date, if any. @@ -7745,7 +7745,7 @@ File: hledger.info, Node: date2 field, Next: status field, Prev: date field,  File: hledger.info, Node: status field, Next: code field, Prev: date2 field, Up: Field names -12.2.4.3 status field +13.2.4.3 status field ..................... 'status' sets the transaction's status, if any. @@ -7753,7 +7753,7 @@ File: hledger.info, Node: status field, Next: code field, Prev: date2 field,  File: hledger.info, Node: code field, Next: description field, Prev: status field, Up: Field names -12.2.4.4 code field +13.2.4.4 code field ................... 'code' sets the transaction's code, if any. @@ -7761,7 +7761,7 @@ File: hledger.info, Node: code field, Next: description field, Prev: status f  File: hledger.info, Node: description field, Next: comment field, Prev: code field, Up: Field names -12.2.4.5 description field +13.2.4.5 description field .......................... 'description' sets the transaction's description, if any. @@ -7769,7 +7769,7 @@ File: hledger.info, Node: description field, Next: comment field, Prev: code  File: hledger.info, Node: comment field, Next: account field, Prev: description field, Up: Field names -12.2.4.6 comment field +13.2.4.6 comment field ...................... 'comment' sets the transaction's comment, if any. @@ -7785,7 +7785,7 @@ File: hledger.info, Node: comment field, Next: account field, Prev: descripti  File: hledger.info, Node: account field, Next: amount field, Prev: comment field, Up: Field names -12.2.4.7 account field +13.2.4.7 account field ...................... Assigning to 'accountN', where N is 1 to 99, sets the account name of @@ -7803,7 +7803,7 @@ or "income:unknown").  File: hledger.info, Node: amount field, Next: currency field, Prev: account field, Up: Field names -12.2.4.8 amount field +13.2.4.8 amount field ..................... 'amountN' sets the amount of the Nth posting, and causes that posting to @@ -7833,7 +7833,7 @@ avoiding conflicts.  File: hledger.info, Node: currency field, Next: balance field, Prev: amount field, Up: Field names -12.2.4.9 currency field +13.2.4.9 currency field ....................... 'currency' sets a currency symbol, to be prepended to all postings' @@ -7846,7 +7846,7 @@ amount.  File: hledger.info, Node: balance field, Prev: currency field, Up: Field names -12.2.4.10 balance field +13.2.4.10 balance field ....................... 'balanceN' sets a balance assertion amount (or if the posting amount is @@ -7863,7 +7863,7 @@ equivalent to 'balance1'.  File: hledger.info, Node: separator, Next: if block, Prev: Field names, Up: CSV rules -12.2.5 'separator' +13.2.5 'separator' ------------------ You can use the 'separator' rule to read other kinds of @@ -7888,7 +7888,7 @@ inferred automatically, and you won't need this rule.  File: hledger.info, Node: if block, Next: if table, Prev: separator, Up: CSV rules -12.2.6 'if' block +13.2.6 'if' block ----------------- if MATCHER @@ -7916,7 +7916,7 @@ descriptions.  File: hledger.info, Node: Matching the whole record, Next: Matching individual fields, Up: if block -12.2.6.1 Matching the whole record +13.2.6.1 Matching the whole record .................................. Each MATCHER can be a record matcher, which looks like this: @@ -7939,7 +7939,7 @@ actually see '2020-01-01,Acme, Inc., 1,000').  File: hledger.info, Node: Matching individual fields, Next: Combining matchers, Prev: Matching the whole record, Up: if block -12.2.6.2 Matching individual fields +13.2.6.2 Matching individual fields ................................... Or, MATCHER can be a field matcher, like this: @@ -7953,7 +7953,7 @@ is a percent sign followed by the field's name or column number, like  File: hledger.info, Node: Combining matchers, Next: Rules applied on successful match, Prev: Matching individual fields, Up: if block -12.2.6.3 Combining matchers +13.2.6.3 Combining matchers ........................... A single matcher can be written on the same line as the "if"; or @@ -7970,7 +7970,7 @@ MATCHER  File: hledger.info, Node: Rules applied on successful match, Prev: Combining matchers, Up: if block -12.2.6.4 Rules applied on successful match +13.2.6.4 Rules applied on successful match .......................................... After the patterns there should be one or more rules to apply, all @@ -7998,7 +7998,7 @@ banking thru software  File: hledger.info, Node: if table, Next: end, Prev: if block, Up: CSV rules -12.2.7 'if' table +13.2.7 'if' table ----------------- if,CSVFIELDNAME1,CSVFIELDNAME2,...,CSVFIELDNAMEn @@ -8059,7 +8059,7 @@ atm transaction fee,expenses:business:banking,deductible? check it  File: hledger.info, Node: end, Next: date-format, Prev: if table, Up: CSV rules -12.2.8 'end' +13.2.8 'end' ------------ This rule can be used inside if blocks (only), to make hledger stop @@ -8073,7 +8073,7 @@ if ,,,,  File: hledger.info, Node: date-format, Next: decimal-mark, Prev: end, Up: CSV rules -12.2.9 'date-format' +13.2.9 'date-format' -------------------- date-format DATEFMT @@ -8109,7 +8109,7 @@ time zone, dates can be "off by one".  File: hledger.info, Node: decimal-mark, Next: newest-first, Prev: date-format, Up: CSV rules -12.2.10 'decimal-mark' +13.2.10 'decimal-mark' ---------------------- decimal-mark . @@ -8127,7 +8127,7 @@ misparsed numbers.  File: hledger.info, Node: newest-first, Next: include, Prev: decimal-mark, Up: CSV rules -12.2.11 'newest-first' +13.2.11 'newest-first' ---------------------- hledger always sorts the generated transactions by date. Transactions @@ -8149,7 +8149,7 @@ newest-first  File: hledger.info, Node: include, Next: balance-type, Prev: newest-first, Up: CSV rules -12.2.12 'include' +13.2.12 'include' ----------------- include RULESFILE @@ -8172,7 +8172,7 @@ include categorisation.rules  File: hledger.info, Node: balance-type, Prev: include, Up: CSV rules -12.2.13 'balance-type' +13.2.13 'balance-type' ---------------------- Balance assertions generated by assigning to balanceN are of the simple @@ -8195,7 +8195,7 @@ balance-type ==*  File: hledger.info, Node: Tips, Prev: CSV rules, Up: CSV FORMAT -12.3 Tips +13.3 Tips ========= * Menu: @@ -8216,7 +8216,7 @@ File: hledger.info, Node: Tips, Prev: CSV rules, Up: CSV FORMAT  File: hledger.info, Node: Rapid feedback, Next: Valid CSV, Up: Tips -12.3.1 Rapid feedback +13.3.1 Rapid feedback --------------------- It's a good idea to get rapid feedback while creating/troubleshooting @@ -8232,7 +8232,7 @@ output.  File: hledger.info, Node: Valid CSV, Next: File Extension, Prev: Rapid feedback, Up: Tips -12.3.2 Valid CSV +13.3.2 Valid CSV ---------------- hledger accepts CSV conforming to RFC 4180. When CSV values are @@ -8244,7 +8244,7 @@ enclosed in quotes, note:  File: hledger.info, Node: File Extension, Next: Reading multiple CSV files, Prev: Valid CSV, Up: Tips -12.3.3 File Extension +13.3.3 File Extension --------------------- To help hledger identify the format and show the right error messages, @@ -8264,7 +8264,7 @@ See also: Input files in the hledger manual.  File: hledger.info, Node: Reading multiple CSV files, Next: Valid transactions, Prev: File Extension, Up: Tips -12.3.4 Reading multiple CSV files +13.3.4 Reading multiple CSV files --------------------------------- If you use multiple '-f' options to read multiple CSV files at once, @@ -8275,7 +8275,7 @@ used for all the CSV files.  File: hledger.info, Node: Valid transactions, Next: Deduplicating importing, Prev: Reading multiple CSV files, Up: Tips -12.3.5 Valid transactions +13.3.5 Valid transactions ------------------------- After reading a CSV file, hledger post-processes and validates the @@ -8294,7 +8294,7 @@ $ hledger -f file.csv print | hledger -f- print  File: hledger.info, Node: Deduplicating importing, Next: Setting amounts, Prev: Valid transactions, Up: Tips -12.3.6 Deduplicating, importing +13.3.6 Deduplicating, importing ------------------------------- When you download a CSV file periodically, eg to get your latest bank @@ -8324,7 +8324,7 @@ CSV data. See:  File: hledger.info, Node: Setting amounts, Next: Amount signs, Prev: Deduplicating importing, Up: Tips -12.3.7 Setting amounts +13.3.7 Setting amounts ---------------------- Some tips on using the amount-setting rules discussed above. @@ -8395,7 +8395,7 @@ Some tips on using the amount-setting rules discussed above.  File: hledger.info, Node: Amount signs, Next: Setting currency/commodity, Prev: Setting amounts, Up: Tips -12.3.8 Amount signs +13.3.8 Amount signs ------------------- There is some special handling for amount signs, to simplify parsing and @@ -8421,7 +8421,7 @@ sign-flipping:  File: hledger.info, Node: Setting currency/commodity, Next: Amount decimal places, Prev: Amount signs, Up: Tips -12.3.9 Setting currency/commodity +13.3.9 Setting currency/commodity --------------------------------- If the currency/commodity symbol is included in the CSV's amount @@ -8469,7 +8469,7 @@ that would trigger the prepending effect, which we don't want here.  File: hledger.info, Node: Amount decimal places, Next: Referencing other fields, Prev: Setting currency/commodity, Up: Tips -12.3.10 Amount decimal places +13.3.10 Amount decimal places ----------------------------- Like amounts in a journal file, the amounts generated by CSV rules like @@ -8482,7 +8482,7 @@ style (because we don't yet reliably know their commodity).  File: hledger.info, Node: Referencing other fields, Next: How CSV rules are evaluated, Prev: Amount decimal places, Up: Tips -12.3.11 Referencing other fields +13.3.11 Referencing other fields -------------------------------- In field assignments, you can interpolate only CSV fields, not hledger @@ -8519,7 +8519,7 @@ if something  File: hledger.info, Node: How CSV rules are evaluated, Prev: Referencing other fields, Up: Tips -12.3.12 How CSV rules are evaluated +13.3.12 How CSV rules are evaluated ----------------------------------- Here's how to think of CSV rules being evaluated (if you really need @@ -8560,7 +8560,7 @@ command the user specified.  File: hledger.info, Node: TIMECLOCK FORMAT, Next: TIMEDOT FORMAT, Prev: CSV FORMAT, Up: Top -13 TIMECLOCK FORMAT +14 TIMECLOCK FORMAT ******************* The time logging format of timeclock.el, as read by hledger. @@ -8614,7 +8614,7 @@ $ hledger -f sample.timeclock register -p weekly --depth 1 --empty # time summa  File: hledger.info, Node: TIMEDOT FORMAT, Next: COMMON TASKS, Prev: TIMECLOCK FORMAT, Up: Top -14 TIMEDOT FORMAT +15 TIMEDOT FORMAT ***************** 'timedot' format is hledger's human-friendly time logging format. @@ -8776,7 +8776,7 @@ $ hledger -f a.timedot --alias /\\./=: bal --tree  File: hledger.info, Node: COMMON TASKS, Next: LIMITATIONS, Prev: TIMEDOT FORMAT, Up: Top -15 COMMON TASKS +16 COMMON TASKS *************** Here are some quick examples of how to do some basic tasks with hledger. @@ -8798,7 +8798,7 @@ https://hledger.org.  File: hledger.info, Node: Getting help, Next: Constructing command lines, Up: COMMON TASKS -15.1 Getting help +16.1 Getting help ================= $ hledger # show available commands @@ -8815,7 +8815,7 @@ https://hledger.org#help-feedback  File: hledger.info, Node: Constructing command lines, Next: Starting a journal file, Prev: Getting help, Up: COMMON TASKS -15.2 Constructing command lines +16.2 Constructing command lines =============================== hledger has an extensive and powerful command line interface. We strive @@ -8835,7 +8835,7 @@ happens, here are some tips that may help:  File: hledger.info, Node: Starting a journal file, Next: Setting opening balances, Prev: Constructing command lines, Up: COMMON TASKS -15.3 Starting a journal file +16.3 Starting a journal file ============================ hledger looks for your accounting data in a journal file, @@ -8874,7 +8874,7 @@ Market prices : 0 ()  File: hledger.info, Node: Setting opening balances, Next: Recording transactions, Prev: Starting a journal file, Up: COMMON TASKS -15.4 Setting opening balances +16.4 Setting opening balances ============================= Pick a starting date for which you can look up the balances of some @@ -8957,7 +8957,7 @@ $ git commit -m 'initial balances' 2020.journal  File: hledger.info, Node: Recording transactions, Next: Reconciling, Prev: Setting opening balances, Up: COMMON TASKS -15.5 Recording transactions +16.5 Recording transactions =========================== As you spend or receive money, you can record these transactions using @@ -8983,7 +8983,7 @@ and hledger.org for more ideas:  File: hledger.info, Node: Reconciling, Next: Reporting, Prev: Recording transactions, Up: COMMON TASKS -15.6 Reconciling +16.6 Reconciling ================ Periodically you should reconcile - compare your hledger-reported @@ -9038,7 +9038,7 @@ $ git commit -m 'txns' 2020.journal  File: hledger.info, Node: Reporting, Next: Migrating to a new file, Prev: Reconciling, Up: COMMON TASKS -15.7 Reporting +16.7 Reporting ============== Here are some basic reports. @@ -9186,7 +9186,7 @@ $ hledger activity -W  File: hledger.info, Node: Migrating to a new file, Prev: Reporting, Up: COMMON TASKS -15.8 Migrating to a new file +16.8 Migrating to a new file ============================ At the end of the year, you may want to continue your journal in a new @@ -9199,7 +9199,7 @@ close command.  File: hledger.info, Node: LIMITATIONS, Next: TROUBLESHOOTING, Prev: COMMON TASKS, Up: Top -16 LIMITATIONS +17 LIMITATIONS ************** The need to precede add-on command options with '--' when invoked from @@ -9227,7 +9227,7 @@ Ledger.  File: hledger.info, Node: TROUBLESHOOTING, Prev: LIMITATIONS, Up: Top -17 TROUBLESHOOTING +18 TROUBLESHOOTING ****************** Here are some issues you might encounter when you run hledger (and @@ -9300,544 +9300,544 @@ $ LANG=en_US.UTF-8 hledger -f my.journal print  Tag Table: Node: Top208 -Node: OPTIONS2593 -Ref: #options2694 -Node: General options2836 -Ref: #general-options2961 -Node: Command options7174 -Ref: #command-options7325 -Node: Command arguments7725 -Ref: #command-arguments7883 -Node: Special characters8763 -Ref: #special-characters8926 -Node: Single escaping shell metacharacters9089 -Ref: #single-escaping-shell-metacharacters9330 -Node: Double escaping regular expression metacharacters9933 -Ref: #double-escaping-regular-expression-metacharacters10244 -Node: Triple escaping for add-on commands10770 -Ref: #triple-escaping-for-add-on-commands11030 -Node: Less escaping11674 -Ref: #less-escaping11828 -Node: Unicode characters12152 -Ref: #unicode-characters12317 -Node: Regular expressions13729 -Ref: #regular-expressions13869 -Node: ENVIRONMENT15605 -Ref: #environment15721 -Node: DATA FILES17213 -Ref: #data-files17332 -Node: Data formats17871 -Ref: #data-formats17989 -Node: Multiple files19383 -Ref: #multiple-files19525 -Node: Strict mode19994 -Ref: #strict-mode20109 -Node: TIME PERIODS20815 -Ref: #time-periods20932 -Node: Smart dates21030 -Ref: #smart-dates21156 -Node: Report start & end date22693 -Ref: #report-start-end-date22868 -Node: Report intervals24535 -Ref: #report-intervals24703 -Node: Period expressions26442 -Ref: #period-expressions26582 -Node: Period expressions with a report interval28313 -Ref: #period-expressions-with-a-report-interval28545 -Node: More complex report intervals29626 -Ref: #more-complex-report-intervals29875 -Node: Intervals with custom start date30510 -Ref: #intervals-with-custom-start-date30742 -Node: Periods or dates ?32316 -Ref: #periods-or-dates32518 -Node: Events on multiple weekdays32960 -Ref: #events-on-multiple-weekdays33139 -Node: DEPTH34002 -Ref: #depth34102 -Node: QUERIES34436 -Ref: #queries34537 -Node: Query types35500 -Ref: #query-types35619 -Node: Combining query terms38291 -Ref: #combining-query-terms38466 -Node: Queries and command options39269 -Ref: #queries-and-command-options39472 -Node: Queries and account aliases39721 -Ref: #queries-and-account-aliases39924 -Node: Queries and valuation40044 -Ref: #queries-and-valuation40237 -Node: Querying with account aliases40466 -Ref: #querying-with-account-aliases40675 -Node: Querying with cost or value40805 -Ref: #querying-with-cost-or-value41006 -Node: CONVERSION & COST41307 -Ref: #conversion-cost41450 -Node: Recording conversions42339 -Ref: #recording-conversions42515 -Node: Implicit conversion42967 -Ref: #implicit-conversion43128 -Node: Priced conversion43925 -Ref: #priced-conversion44108 -Node: Equity conversion44499 -Ref: #equity-conversion44687 -Node: Priced equity conversion45455 -Ref: #priced-equity-conversion45631 -Node: Inferring missing conversion rates45979 -Ref: #inferring-missing-conversion-rates46223 -Node: Inferring missing equity postings46339 -Ref: #inferring-missing-equity-postings46574 -Node: Cost reporting46722 -Ref: #cost-reporting46903 -Node: Conversion summary47423 -Ref: #conversion-summary47570 -Node: VALUATION48292 -Ref: #valuation48400 -Node: -V Value49167 -Ref: #v-value49291 -Node: -X Value in specified commodity49486 -Ref: #x-value-in-specified-commodity49679 -Node: Valuation date49828 -Ref: #valuation-date49990 -Node: Market prices50427 -Ref: #market-prices50609 -Node: --infer-market-prices market prices from transactions51792 -Ref: #infer-market-prices-market-prices-from-transactions52059 -Node: Valuation commodity53415 -Ref: #valuation-commodity53626 -Node: Simple valuation examples54852 -Ref: #simple-valuation-examples55048 -Node: --value Flexible valuation55707 -Ref: #value-flexible-valuation55909 -Node: More valuation examples57553 -Ref: #more-valuation-examples57760 -Node: Interaction of valuation and queries59759 -Ref: #interaction-of-valuation-and-queries59998 -Node: Effect of valuation on reports60470 -Ref: #effect-of-valuation-on-reports60665 -Node: PIVOTING68362 -Ref: #pivoting68467 -Node: OUTPUT70143 -Ref: #output70243 -Node: Output destination70334 -Ref: #output-destination70466 -Node: Output styling71123 -Ref: #output-styling71269 -Node: Output format72026 -Ref: #output-format72168 -Node: CSV output73532 -Ref: #csv-output73648 -Node: HTML output73751 -Ref: #html-output73889 -Node: JSON output73983 -Ref: #json-output74121 -Node: SQL output75038 -Ref: #sql-output75154 -Node: Commodity styles75655 -Ref: #commodity-styles75780 -Node: COMMANDS76556 -Ref: #commands76668 -Node: accounts80033 -Ref: #accounts80133 -Node: activity80829 -Ref: #activity80941 -Node: add81324 -Ref: #add81427 -Node: aregister84220 -Ref: #aregister84334 -Node: aregister and custom posting dates86699 -Ref: #aregister-and-custom-posting-dates86865 -Node: balance87417 -Ref: #balance87536 -Node: balance features88529 -Ref: #balance-features88669 -Node: Simple balance report90593 -Ref: #simple-balance-report90775 -Node: Filtered balance report92255 -Ref: #filtered-balance-report92442 -Node: List or tree mode92769 -Ref: #list-or-tree-mode92937 -Node: Depth limiting94282 -Ref: #depth-limiting94448 -Node: Dropping top-level accounts95049 -Ref: #dropping-top-level-accounts95251 -Node: Multi-period balance report95561 -Ref: #multi-period-balance-report95774 -Node: Showing declared accounts98049 -Ref: #showing-declared-accounts98242 -Node: Data layout98773 -Ref: #data-layout98928 -Node: Sorting by amount106868 -Ref: #sorting-by-amount107023 -Node: Percentages107693 -Ref: #percentages107851 -Node: Balance change end balance108812 -Ref: #balance-change-end-balance109005 -Node: Balance report types110433 -Ref: #balance-report-types110623 -Node: Useful balance reports114902 -Ref: #useful-balance-reports115083 -Node: Budget report116168 -Ref: #budget-report116352 -Node: Budget report start date121627 -Ref: #budget-report-start-date121805 -Node: Budgets and subaccounts123137 -Ref: #budgets-and-subaccounts123344 -Node: Selecting budget goals126784 -Ref: #selecting-budget-goals126956 -Node: Customising single-period balance reports127990 -Ref: #customising-single-period-balance-reports128199 -Node: balancesheet130374 -Ref: #balancesheet130512 -Node: balancesheetequity131811 -Ref: #balancesheetequity131962 -Node: cashflow133342 -Ref: #cashflow133466 -Node: check134612 -Ref: #check134717 -Node: Basic checks135351 -Ref: #basic-checks135469 -Node: Strict checks136020 -Ref: #strict-checks136161 -Node: Other checks136597 -Ref: #other-checks136737 -Node: Custom checks137094 -Ref: #custom-checks137214 -Node: close137631 -Ref: #close137735 -Node: close and prices139826 -Ref: #close-and-prices139955 -Node: close date140350 -Ref: #close-date140534 -Node: Example close asset/liability accounts for file transition141291 -Ref: #example-close-assetliability-accounts-for-file-transition141592 -Node: Hiding opening/closing transactions142451 -Ref: #hiding-openingclosing-transactions142722 -Node: close and balance assertions144099 -Ref: #close-and-balance-assertions144357 -Node: Example close revenue/expense accounts to retained earnings145711 -Ref: #example-close-revenueexpense-accounts-to-retained-earnings145989 -Node: codes146879 -Ref: #codes146989 -Node: commodities147701 -Ref: #commodities147830 -Node: descriptions147912 -Ref: #descriptions148042 -Node: diff148346 -Ref: #diff148454 -Node: files149501 -Ref: #files149603 -Node: help149750 -Ref: #help149852 -Node: import150670 -Ref: #import150786 -Node: Deduplication151651 -Ref: #deduplication151776 -Node: Import testing153670 -Ref: #import-testing153835 -Node: Importing balance assignments154323 -Ref: #importing-balance-assignments154529 -Node: Commodity display styles155178 -Ref: #commodity-display-styles155351 -Node: incomestatement155480 -Ref: #incomestatement155615 -Node: notes156920 -Ref: #notes157035 -Node: payees157403 -Ref: #payees157511 -Node: prices158037 -Ref: #prices158145 -Node: print158514 -Ref: #print158626 -Node: print-unique163941 -Ref: #print-unique164069 -Node: register164354 -Ref: #register164483 -Node: Custom register output168929 -Ref: #custom-register-output169060 -Node: register-match170397 -Ref: #register-match170533 -Node: rewrite170884 -Ref: #rewrite171001 -Node: Re-write rules in a file172907 -Ref: #re-write-rules-in-a-file173070 -Node: Diff output format174219 -Ref: #diff-output-format174402 -Node: rewrite vs print --auto175494 -Ref: #rewrite-vs.-print---auto175654 -Node: roi176210 -Ref: #roi176310 -Node: Spaces and special characters in --inv and --pnl177996 -Ref: #spaces-and-special-characters-in---inv-and---pnl178236 -Node: Semantics of --inv and --pnl178724 -Ref: #semantics-of---inv-and---pnl178963 -Node: IRR and TWR explained180813 -Ref: #irr-and-twr-explained180973 -Node: stats184041 -Ref: #stats184142 -Node: tags185522 -Ref: #tags185622 -Node: test186141 -Ref: #test186257 -Node: About add-on commands187004 -Ref: #about-add-on-commands187141 -Node: JOURNAL FORMAT188272 -Ref: #journal-format188400 -Node: Transactions190627 -Ref: #transactions190742 -Node: Dates191756 -Ref: #dates191872 -Node: Simple dates191937 -Ref: #simple-dates192057 -Node: Secondary dates192566 -Ref: #secondary-dates192714 -Node: Posting dates194050 -Ref: #posting-dates194173 -Node: Status195545 -Ref: #status195655 -Node: Code197363 -Ref: #code197475 -Node: Description197707 -Ref: #description197835 -Node: Payee and note198155 -Ref: #payee-and-note198263 -Node: Comments198598 -Ref: #comments198720 -Node: Tags199914 -Ref: #tags-1200025 -Node: Postings201418 -Ref: #postings201542 -Node: Virtual postings202568 -Ref: #virtual-postings202679 -Node: Account names203984 -Ref: #account-names204121 -Node: Amounts204609 -Ref: #amounts204746 -Node: Decimal marks digit group marks205731 -Ref: #decimal-marks-digit-group-marks205908 -Node: Commodity206929 -Ref: #commodity207118 -Node: Directives influencing number parsing and display208070 -Ref: #directives-influencing-number-parsing-and-display208331 -Node: Commodity display style208824 -Ref: #commodity-display-style209032 -Node: Rounding211227 -Ref: #rounding211347 -Node: Transaction prices211759 -Ref: #transaction-prices211925 -Node: Lot prices lot dates214356 -Ref: #lot-prices-lot-dates214539 -Node: Balance assertions215027 -Ref: #balance-assertions215205 -Node: Assertions and ordering216238 -Ref: #assertions-and-ordering216420 -Node: Assertions and included files217120 -Ref: #assertions-and-included-files217357 -Node: Assertions and multiple -f options217690 -Ref: #assertions-and-multiple--f-options217940 -Node: Assertions and commodities218072 -Ref: #assertions-and-commodities218298 -Node: Assertions and prices219455 -Ref: #assertions-and-prices219663 -Node: Assertions and subaccounts220103 -Ref: #assertions-and-subaccounts220326 -Node: Assertions and virtual postings220650 -Ref: #assertions-and-virtual-postings220886 -Node: Assertions and precision221028 -Ref: #assertions-and-precision221215 -Node: Balance assignments221482 -Ref: #balance-assignments221652 -Node: Balance assignments and prices222816 -Ref: #balance-assignments-and-prices222982 -Node: Directives223206 -Ref: #directives223369 -Node: Directives and multiple files227861 -Ref: #directives-and-multiple-files228057 -Node: Comment blocks228749 -Ref: #comment-blocks228926 -Node: Including other files229102 -Ref: #including-other-files229276 -Node: Default year230200 -Ref: #default-year230358 -Node: Declaring payees230765 -Ref: #declaring-payees230936 -Node: Declaring the decimal mark231182 -Ref: #declaring-the-decimal-mark231382 -Node: Declaring commodities231779 -Ref: #declaring-commodities231970 -Node: Commodity error checking234488 -Ref: #commodity-error-checking234638 -Node: Default commodity234895 -Ref: #default-commodity235075 -Node: Declaring market prices236191 -Ref: #declaring-market-prices236380 -Node: Declaring accounts237193 -Ref: #declaring-accounts237373 -Node: Account error checking238575 -Ref: #account-error-checking238741 -Node: Account comments239920 -Ref: #account-comments240104 -Node: Account subdirectives240528 -Ref: #account-subdirectives240713 -Node: Account types241026 -Ref: #account-types241200 -Node: Auto-detected account types242616 -Ref: #auto-detected-account-types242771 -Node: Account display order244006 -Ref: #account-display-order244166 -Node: Rewriting accounts245317 -Ref: #rewriting-accounts245496 -Node: Basic aliases246253 -Ref: #basic-aliases246389 -Node: Regex aliases247133 -Ref: #regex-aliases247295 -Node: Combining aliases248014 -Ref: #combining-aliases248197 -Node: Aliases and multiple files249473 -Ref: #aliases-and-multiple-files249672 -Node: end aliases250251 -Ref: #end-aliases250398 -Node: Default parent account250547 -Ref: #default-parent-account250737 -Node: Periodic transactions251621 -Ref: #periodic-transactions251804 -Node: Periodic rule syntax253721 -Ref: #periodic-rule-syntax253921 -Node: Two spaces between period expression and description!254625 -Ref: #two-spaces-between-period-expression-and-description254938 -Node: Forecasting with periodic transactions255622 -Ref: #forecasting-with-periodic-transactions255921 -Node: Budgeting with periodic transactions258692 -Ref: #budgeting-with-periodic-transactions258925 -Node: Auto postings259334 -Ref: #auto-postings259470 -Node: Auto postings and multiple files261649 -Ref: #auto-postings-and-multiple-files261847 -Node: Auto postings and dates262056 -Ref: #auto-postings-and-dates262324 -Node: Auto postings and transaction balancing / inferred amounts / balance assertions262499 -Ref: #auto-postings-and-transaction-balancing-inferred-amounts-balance-assertions262844 -Node: Auto posting tags263347 -Ref: #auto-posting-tags263556 -Node: CSV FORMAT264192 -Ref: #csv-format264320 -Node: Examples266949 -Ref: #examples267052 -Node: Basic267260 -Ref: #basic267362 -Node: Bank of Ireland267904 -Ref: #bank-of-ireland268041 -Node: Amazon269503 -Ref: #amazon269623 -Node: Paypal271342 -Ref: #paypal271438 -Node: CSV rules279082 -Ref: #csv-rules279200 -Node: skip279533 -Ref: #skip279633 -Node: fields list280008 -Ref: #fields-list280147 -Node: field assignment281713 -Ref: #field-assignment281865 -Node: Field names282900 -Ref: #field-names283040 -Node: date field283420 -Ref: #date-field283540 -Node: date2 field283588 -Ref: #date2-field283731 -Node: status field283787 -Ref: #status-field283932 -Node: code field283981 -Ref: #code-field284128 -Node: description field284173 -Ref: #description-field284335 -Node: comment field284394 -Ref: #comment-field284551 -Node: account field284862 -Ref: #account-field285014 -Node: amount field285589 -Ref: #amount-field285740 -Node: currency field286985 -Ref: #currency-field287140 -Node: balance field287397 -Ref: #balance-field287531 -Node: separator287903 -Ref: #separator288035 -Node: if block288575 -Ref: #if-block288702 -Node: Matching the whole record289103 -Ref: #matching-the-whole-record289280 -Node: Matching individual fields290083 -Ref: #matching-individual-fields290289 -Node: Combining matchers290513 -Ref: #combining-matchers290711 -Node: Rules applied on successful match291024 -Ref: #rules-applied-on-successful-match291217 -Node: if table291871 -Ref: #if-table291992 -Node: end293730 -Ref: #end293844 -Node: date-format294068 -Ref: #date-format294202 -Node: decimal-mark295198 -Ref: #decimal-mark295345 -Node: newest-first295684 -Ref: #newest-first295827 -Node: include296510 -Ref: #include296643 -Node: balance-type297087 -Ref: #balance-type297209 -Node: Tips297909 -Ref: #tips298000 -Node: Rapid feedback298299 -Ref: #rapid-feedback298418 -Node: Valid CSV298870 -Ref: #valid-csv299002 -Node: File Extension299194 -Ref: #file-extension299348 -Node: Reading multiple CSV files299777 -Ref: #reading-multiple-csv-files299964 -Node: Valid transactions300205 -Ref: #valid-transactions300385 -Node: Deduplicating importing301013 -Ref: #deduplicating-importing301194 -Node: Setting amounts302227 -Ref: #setting-amounts302384 -Node: Amount signs304825 -Ref: #amount-signs304979 -Node: Setting currency/commodity305666 -Ref: #setting-currencycommodity305854 -Node: Amount decimal places307028 -Ref: #amount-decimal-places307220 -Node: Referencing other fields307532 -Ref: #referencing-other-fields307731 -Node: How CSV rules are evaluated308628 -Ref: #how-csv-rules-are-evaluated308803 -Node: TIMECLOCK FORMAT310254 -Ref: #timeclock-format310394 -Node: TIMEDOT FORMAT312455 -Ref: #timedot-format312593 -Node: COMMON TASKS317155 -Ref: #common-tasks317284 -Node: Getting help317691 -Ref: #getting-help317825 -Node: Constructing command lines318378 -Ref: #constructing-command-lines318572 -Node: Starting a journal file319269 -Ref: #starting-a-journal-file319469 -Node: Setting opening balances320657 -Ref: #setting-opening-balances320855 -Node: Recording transactions323996 -Ref: #recording-transactions324178 -Node: Reconciling324734 -Ref: #reconciling324879 -Node: Reporting327136 -Ref: #reporting327278 -Node: Migrating to a new file331277 -Ref: #migrating-to-a-new-file331427 -Node: LIMITATIONS331726 -Ref: #limitations331854 -Node: TROUBLESHOOTING332597 -Ref: #troubleshooting332712 +Node: OPTIONS2615 +Ref: #options2716 +Node: General options2858 +Ref: #general-options2983 +Node: Command options7196 +Ref: #command-options7347 +Node: Command arguments7747 +Ref: #command-arguments7905 +Node: Special characters8785 +Ref: #special-characters8948 +Node: Single escaping shell metacharacters9111 +Ref: #single-escaping-shell-metacharacters9352 +Node: Double escaping regular expression metacharacters9955 +Ref: #double-escaping-regular-expression-metacharacters10266 +Node: Triple escaping for add-on commands10792 +Ref: #triple-escaping-for-add-on-commands11052 +Node: Less escaping11696 +Ref: #less-escaping11850 +Node: Unicode characters12174 +Ref: #unicode-characters12339 +Node: Regular expressions13751 +Ref: #regular-expressions13891 +Node: ENVIRONMENT15627 +Ref: #environment15743 +Node: DATA FILES17235 +Ref: #data-files17354 +Node: Data formats17893 +Ref: #data-formats18011 +Node: Multiple files19405 +Ref: #multiple-files19547 +Node: Strict mode20016 +Ref: #strict-mode20131 +Node: TIME PERIODS20837 +Ref: #time-periods20954 +Node: Smart dates21052 +Ref: #smart-dates21178 +Node: Report start & end date22715 +Ref: #report-start-end-date22890 +Node: Report intervals24557 +Ref: #report-intervals24725 +Node: Period expressions26464 +Ref: #period-expressions26604 +Node: Period expressions with a report interval28335 +Ref: #period-expressions-with-a-report-interval28567 +Node: More complex report intervals29648 +Ref: #more-complex-report-intervals29897 +Node: Intervals with custom start date30532 +Ref: #intervals-with-custom-start-date30764 +Node: Periods or dates ?32338 +Ref: #periods-or-dates32540 +Node: Events on multiple weekdays32982 +Ref: #events-on-multiple-weekdays33161 +Node: DEPTH34024 +Ref: #depth34124 +Node: QUERIES34458 +Ref: #queries34567 +Node: Query types35508 +Ref: #query-types35627 +Node: Combining query terms38299 +Ref: #combining-query-terms38474 +Node: Queries and command options39277 +Ref: #queries-and-command-options39480 +Node: Queries and account aliases39729 +Ref: #queries-and-account-aliases39932 +Node: Queries and valuation40052 +Ref: #queries-and-valuation40245 +Node: Querying with account aliases40474 +Ref: #querying-with-account-aliases40683 +Node: Querying with cost or value40813 +Ref: #querying-with-cost-or-value40988 +Node: CONVERSION & COST41289 +Ref: #conversion-cost41422 +Node: Recording conversions42311 +Ref: #recording-conversions42483 +Node: Implicit conversion42935 +Ref: #implicit-conversion43092 +Node: Priced conversion43889 +Ref: #priced-conversion44068 +Node: Equity conversion44459 +Ref: #equity-conversion44643 +Node: Priced equity conversion45411 +Ref: #priced-equity-conversion45583 +Node: Inferring missing conversion rates45931 +Ref: #inferring-missing-conversion-rates46171 +Node: Inferring missing equity postings46287 +Ref: #inferring-missing-equity-postings46518 +Node: Cost reporting46666 +Ref: #cost-reporting46843 +Node: Conversion summary47363 +Ref: #conversion-summary47506 +Node: VALUATION48228 +Ref: #valuation48346 +Node: -V Value49113 +Ref: #v-value49237 +Node: -X Value in specified commodity49432 +Ref: #x-value-in-specified-commodity49625 +Node: Valuation date49774 +Ref: #valuation-date49936 +Node: Market prices50373 +Ref: #market-prices50555 +Node: --infer-market-prices market prices from transactions51738 +Ref: #infer-market-prices-market-prices-from-transactions52005 +Node: Valuation commodity53361 +Ref: #valuation-commodity53572 +Node: Simple valuation examples54798 +Ref: #simple-valuation-examples54994 +Node: --value Flexible valuation55653 +Ref: #value-flexible-valuation55855 +Node: More valuation examples57499 +Ref: #more-valuation-examples57706 +Node: Interaction of valuation and queries59705 +Ref: #interaction-of-valuation-and-queries59944 +Node: Effect of valuation on reports60416 +Ref: #effect-of-valuation-on-reports60611 +Node: PIVOTING68308 +Ref: #pivoting68413 +Node: OUTPUT70089 +Ref: #output70191 +Node: Output destination70282 +Ref: #output-destination70416 +Node: Output styling71073 +Ref: #output-styling71221 +Node: Output format71978 +Ref: #output-format72122 +Node: CSV output73486 +Ref: #csv-output73604 +Node: HTML output73707 +Ref: #html-output73847 +Node: JSON output73941 +Ref: #json-output74081 +Node: SQL output74998 +Ref: #sql-output75116 +Node: Commodity styles75617 +Ref: #commodity-styles75744 +Node: COMMANDS76520 +Ref: #commands76632 +Node: accounts79997 +Ref: #accounts80097 +Node: activity80793 +Ref: #activity80905 +Node: add81288 +Ref: #add81391 +Node: aregister84184 +Ref: #aregister84298 +Node: aregister and custom posting dates86663 +Ref: #aregister-and-custom-posting-dates86829 +Node: balance87381 +Ref: #balance87500 +Node: balance features88493 +Ref: #balance-features88633 +Node: Simple balance report90557 +Ref: #simple-balance-report90739 +Node: Filtered balance report92219 +Ref: #filtered-balance-report92406 +Node: List or tree mode92733 +Ref: #list-or-tree-mode92901 +Node: Depth limiting94246 +Ref: #depth-limiting94412 +Node: Dropping top-level accounts95013 +Ref: #dropping-top-level-accounts95215 +Node: Multi-period balance report95525 +Ref: #multi-period-balance-report95738 +Node: Showing declared accounts98013 +Ref: #showing-declared-accounts98206 +Node: Data layout98737 +Ref: #data-layout98892 +Node: Sorting by amount106832 +Ref: #sorting-by-amount106987 +Node: Percentages107657 +Ref: #percentages107815 +Node: Balance change end balance108776 +Ref: #balance-change-end-balance108969 +Node: Balance report types110397 +Ref: #balance-report-types110587 +Node: Useful balance reports114866 +Ref: #useful-balance-reports115047 +Node: Budget report116132 +Ref: #budget-report116316 +Node: Budget report start date121591 +Ref: #budget-report-start-date121769 +Node: Budgets and subaccounts123101 +Ref: #budgets-and-subaccounts123308 +Node: Selecting budget goals126748 +Ref: #selecting-budget-goals126920 +Node: Customising single-period balance reports127954 +Ref: #customising-single-period-balance-reports128163 +Node: balancesheet130338 +Ref: #balancesheet130476 +Node: balancesheetequity131775 +Ref: #balancesheetequity131926 +Node: cashflow133306 +Ref: #cashflow133430 +Node: check134576 +Ref: #check134681 +Node: Basic checks135315 +Ref: #basic-checks135433 +Node: Strict checks135984 +Ref: #strict-checks136125 +Node: Other checks136561 +Ref: #other-checks136701 +Node: Custom checks137058 +Ref: #custom-checks137178 +Node: close137595 +Ref: #close137699 +Node: close and prices139790 +Ref: #close-and-prices139919 +Node: close date140314 +Ref: #close-date140498 +Node: Example close asset/liability accounts for file transition141255 +Ref: #example-close-assetliability-accounts-for-file-transition141556 +Node: Hiding opening/closing transactions142415 +Ref: #hiding-openingclosing-transactions142686 +Node: close and balance assertions144063 +Ref: #close-and-balance-assertions144321 +Node: Example close revenue/expense accounts to retained earnings145675 +Ref: #example-close-revenueexpense-accounts-to-retained-earnings145953 +Node: codes146843 +Ref: #codes146953 +Node: commodities147665 +Ref: #commodities147794 +Node: descriptions147876 +Ref: #descriptions148006 +Node: diff148310 +Ref: #diff148418 +Node: files149465 +Ref: #files149567 +Node: help149714 +Ref: #help149816 +Node: import150634 +Ref: #import150750 +Node: Deduplication151615 +Ref: #deduplication151740 +Node: Import testing153634 +Ref: #import-testing153799 +Node: Importing balance assignments154287 +Ref: #importing-balance-assignments154493 +Node: Commodity display styles155142 +Ref: #commodity-display-styles155315 +Node: incomestatement155444 +Ref: #incomestatement155579 +Node: notes156884 +Ref: #notes156999 +Node: payees157367 +Ref: #payees157475 +Node: prices158001 +Ref: #prices158109 +Node: print158478 +Ref: #print158590 +Node: print-unique163905 +Ref: #print-unique164033 +Node: register164318 +Ref: #register164447 +Node: Custom register output168893 +Ref: #custom-register-output169024 +Node: register-match170361 +Ref: #register-match170497 +Node: rewrite170848 +Ref: #rewrite170965 +Node: Re-write rules in a file172871 +Ref: #re-write-rules-in-a-file173034 +Node: Diff output format174183 +Ref: #diff-output-format174366 +Node: rewrite vs print --auto175458 +Ref: #rewrite-vs.-print---auto175618 +Node: roi176174 +Ref: #roi176274 +Node: Spaces and special characters in --inv and --pnl177960 +Ref: #spaces-and-special-characters-in---inv-and---pnl178200 +Node: Semantics of --inv and --pnl178688 +Ref: #semantics-of---inv-and---pnl178927 +Node: IRR and TWR explained180777 +Ref: #irr-and-twr-explained180937 +Node: stats184005 +Ref: #stats184106 +Node: tags185486 +Ref: #tags185586 +Node: test186105 +Ref: #test186221 +Node: About add-on commands186968 +Ref: #about-add-on-commands187105 +Node: JOURNAL FORMAT188236 +Ref: #journal-format188364 +Node: Transactions190591 +Ref: #transactions190706 +Node: Dates191720 +Ref: #dates191836 +Node: Simple dates191901 +Ref: #simple-dates192021 +Node: Secondary dates192530 +Ref: #secondary-dates192678 +Node: Posting dates194014 +Ref: #posting-dates194137 +Node: Status195509 +Ref: #status195619 +Node: Code197327 +Ref: #code197439 +Node: Description197671 +Ref: #description197799 +Node: Payee and note198119 +Ref: #payee-and-note198227 +Node: Comments198562 +Ref: #comments198684 +Node: Tags199878 +Ref: #tags-1199989 +Node: Postings201382 +Ref: #postings201506 +Node: Virtual postings202532 +Ref: #virtual-postings202643 +Node: Account names203948 +Ref: #account-names204085 +Node: Amounts204573 +Ref: #amounts204710 +Node: Decimal marks digit group marks205695 +Ref: #decimal-marks-digit-group-marks205872 +Node: Commodity206893 +Ref: #commodity207082 +Node: Directives influencing number parsing and display208034 +Ref: #directives-influencing-number-parsing-and-display208295 +Node: Commodity display style208788 +Ref: #commodity-display-style208996 +Node: Rounding211191 +Ref: #rounding211311 +Node: Transaction prices211723 +Ref: #transaction-prices211889 +Node: Lot prices lot dates214320 +Ref: #lot-prices-lot-dates214503 +Node: Balance assertions214991 +Ref: #balance-assertions215169 +Node: Assertions and ordering216202 +Ref: #assertions-and-ordering216384 +Node: Assertions and included files217084 +Ref: #assertions-and-included-files217321 +Node: Assertions and multiple -f options217654 +Ref: #assertions-and-multiple--f-options217904 +Node: Assertions and commodities218036 +Ref: #assertions-and-commodities218262 +Node: Assertions and prices219419 +Ref: #assertions-and-prices219627 +Node: Assertions and subaccounts220067 +Ref: #assertions-and-subaccounts220290 +Node: Assertions and virtual postings220614 +Ref: #assertions-and-virtual-postings220850 +Node: Assertions and precision220992 +Ref: #assertions-and-precision221179 +Node: Balance assignments221446 +Ref: #balance-assignments221616 +Node: Balance assignments and prices222780 +Ref: #balance-assignments-and-prices222946 +Node: Directives223170 +Ref: #directives223333 +Node: Directives and multiple files227825 +Ref: #directives-and-multiple-files228021 +Node: Comment blocks228713 +Ref: #comment-blocks228890 +Node: Including other files229066 +Ref: #including-other-files229240 +Node: Default year230164 +Ref: #default-year230322 +Node: Declaring payees230729 +Ref: #declaring-payees230900 +Node: Declaring the decimal mark231146 +Ref: #declaring-the-decimal-mark231346 +Node: Declaring commodities231743 +Ref: #declaring-commodities231934 +Node: Commodity error checking234452 +Ref: #commodity-error-checking234602 +Node: Default commodity234859 +Ref: #default-commodity235039 +Node: Declaring market prices236155 +Ref: #declaring-market-prices236344 +Node: Declaring accounts237157 +Ref: #declaring-accounts237337 +Node: Account error checking238539 +Ref: #account-error-checking238705 +Node: Account comments239884 +Ref: #account-comments240068 +Node: Account subdirectives240492 +Ref: #account-subdirectives240677 +Node: Account types240990 +Ref: #account-types241164 +Node: Auto-detected account types242580 +Ref: #auto-detected-account-types242735 +Node: Account display order243970 +Ref: #account-display-order244130 +Node: Rewriting accounts245281 +Ref: #rewriting-accounts245460 +Node: Basic aliases246217 +Ref: #basic-aliases246353 +Node: Regex aliases247097 +Ref: #regex-aliases247259 +Node: Combining aliases247978 +Ref: #combining-aliases248161 +Node: Aliases and multiple files249437 +Ref: #aliases-and-multiple-files249636 +Node: end aliases250215 +Ref: #end-aliases250362 +Node: Default parent account250511 +Ref: #default-parent-account250701 +Node: Periodic transactions251585 +Ref: #periodic-transactions251768 +Node: Periodic rule syntax253685 +Ref: #periodic-rule-syntax253885 +Node: Two spaces between period expression and description!254589 +Ref: #two-spaces-between-period-expression-and-description254902 +Node: Forecasting with periodic transactions255586 +Ref: #forecasting-with-periodic-transactions255885 +Node: Budgeting with periodic transactions258656 +Ref: #budgeting-with-periodic-transactions258889 +Node: Auto postings259298 +Ref: #auto-postings259434 +Node: Auto postings and multiple files261613 +Ref: #auto-postings-and-multiple-files261811 +Node: Auto postings and dates262020 +Ref: #auto-postings-and-dates262288 +Node: Auto postings and transaction balancing / inferred amounts / balance assertions262463 +Ref: #auto-postings-and-transaction-balancing-inferred-amounts-balance-assertions262808 +Node: Auto posting tags263311 +Ref: #auto-posting-tags263520 +Node: CSV FORMAT264156 +Ref: #csv-format264284 +Node: Examples266913 +Ref: #examples267016 +Node: Basic267224 +Ref: #basic267326 +Node: Bank of Ireland267868 +Ref: #bank-of-ireland268005 +Node: Amazon269467 +Ref: #amazon269587 +Node: Paypal271306 +Ref: #paypal271402 +Node: CSV rules279046 +Ref: #csv-rules279164 +Node: skip279497 +Ref: #skip279597 +Node: fields list279972 +Ref: #fields-list280111 +Node: field assignment281677 +Ref: #field-assignment281829 +Node: Field names282864 +Ref: #field-names283004 +Node: date field283384 +Ref: #date-field283504 +Node: date2 field283552 +Ref: #date2-field283695 +Node: status field283751 +Ref: #status-field283896 +Node: code field283945 +Ref: #code-field284092 +Node: description field284137 +Ref: #description-field284299 +Node: comment field284358 +Ref: #comment-field284515 +Node: account field284826 +Ref: #account-field284978 +Node: amount field285553 +Ref: #amount-field285704 +Node: currency field286949 +Ref: #currency-field287104 +Node: balance field287361 +Ref: #balance-field287495 +Node: separator287867 +Ref: #separator287999 +Node: if block288539 +Ref: #if-block288666 +Node: Matching the whole record289067 +Ref: #matching-the-whole-record289244 +Node: Matching individual fields290047 +Ref: #matching-individual-fields290253 +Node: Combining matchers290477 +Ref: #combining-matchers290675 +Node: Rules applied on successful match290988 +Ref: #rules-applied-on-successful-match291181 +Node: if table291835 +Ref: #if-table291956 +Node: end293694 +Ref: #end293808 +Node: date-format294032 +Ref: #date-format294166 +Node: decimal-mark295162 +Ref: #decimal-mark295309 +Node: newest-first295648 +Ref: #newest-first295791 +Node: include296474 +Ref: #include296607 +Node: balance-type297051 +Ref: #balance-type297173 +Node: Tips297873 +Ref: #tips297964 +Node: Rapid feedback298263 +Ref: #rapid-feedback298382 +Node: Valid CSV298834 +Ref: #valid-csv298966 +Node: File Extension299158 +Ref: #file-extension299312 +Node: Reading multiple CSV files299741 +Ref: #reading-multiple-csv-files299928 +Node: Valid transactions300169 +Ref: #valid-transactions300349 +Node: Deduplicating importing300977 +Ref: #deduplicating-importing301158 +Node: Setting amounts302191 +Ref: #setting-amounts302348 +Node: Amount signs304789 +Ref: #amount-signs304943 +Node: Setting currency/commodity305630 +Ref: #setting-currencycommodity305818 +Node: Amount decimal places306992 +Ref: #amount-decimal-places307184 +Node: Referencing other fields307496 +Ref: #referencing-other-fields307695 +Node: How CSV rules are evaluated308592 +Ref: #how-csv-rules-are-evaluated308767 +Node: TIMECLOCK FORMAT310218 +Ref: #timeclock-format310358 +Node: TIMEDOT FORMAT312419 +Ref: #timedot-format312557 +Node: COMMON TASKS317119 +Ref: #common-tasks317248 +Node: Getting help317655 +Ref: #getting-help317789 +Node: Constructing command lines318342 +Ref: #constructing-command-lines318536 +Node: Starting a journal file319233 +Ref: #starting-a-journal-file319433 +Node: Setting opening balances320621 +Ref: #setting-opening-balances320819 +Node: Recording transactions323960 +Ref: #recording-transactions324142 +Node: Reconciling324698 +Ref: #reconciling324843 +Node: Reporting327100 +Ref: #reporting327242 +Node: Migrating to a new file331241 +Ref: #migrating-to-a-new-file331391 +Node: LIMITATIONS331690 +Ref: #limitations331818 +Node: TROUBLESHOOTING332561 +Ref: #troubleshooting332676  End Tag Table diff --git a/hledger/hledger.txt b/hledger/hledger.txt index b63e1a97b..5424ae5e2 100644 --- a/hledger/hledger.txt +++ b/hledger/hledger.txt @@ -1033,7 +1033,7 @@ QUERIES this changed in hledger 1.22, previously it was the reverse, see the discussion at #1625. - CONVERSION & COST +CONVERSION & COST This section is about converting between commodities. Some defini- tions: