Skip to content

Commit

Permalink
;doc:forecasting: drop unnecessary reference to budgeting
Browse files Browse the repository at this point in the history
  • Loading branch information
simonmichael committed Jan 9, 2024
1 parent 80e4428 commit 76209d5
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion hledger/hledger.m4.md
Original file line number Diff line number Diff line change
Expand Up @@ -5040,7 +5040,8 @@ Forecasting, or speculative future reporting, can be useful for estimating futur
The simplest and most flexible way to do it with hledger is to manually record a bunch of future-dated transactions. You could keep these in a separate `future.journal` and include that with `-f` only when you want to see them.
## --forecast
There is another way: with the `--forecast` option, hledger can generate temporary "forecast transactions" for reporting purposes, according to [periodic transaction rules](#periodic-transactions) defined in the journal. Each rule can generate multiple recurring transactions, so by changing one rule you can change many forecasted transactions. (These same rules can also generate budget goals, described in [Budgeting](#budgeting).)
There is another way: with the `--forecast` option, hledger can generate temporary "forecast transactions" for reporting purposes, according to [periodic transaction rules](#periodic-transactions) defined in the journal.
Each rule can generate multiple recurring transactions, so by changing one rule you can change many forecasted transactions.
Forecast transactions usually start after ordinary transactions end. By default, they begin after your latest-dated ordinary transaction, or today, whichever is later, and they end six months from today. (The exact rules are a little more complicated, and are given below.)
Expand Down

0 comments on commit 76209d5

Please sign in to comment.