hledger-forecast 0.4.0 → 1.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 85bd96722d50a8d5b2c8e8cbb9f973d88832827f74226d3b78d5f511b96265bf
-  data.tar.gz: b69f6698e5c7294cd2b62c8672887044a416d0ed6624803293acd9246a84fa14
+  metadata.gz: 37dbc9f011b6a43fa1d186e92dfb77c3c184cdb4a7cc5ef690a77d53c57f4722
+  data.tar.gz: e71185f0ad678b45f1ffa155c89c491bd37d36307d845dd023b823db6ced42d4
 SHA512:
-  metadata.gz: 2e3c4e2a1ef57546778525c37fa4b53854a10244f3e509c3bd48d8c3fcb49c2edc892c84f221f7980c56687ec4766f5379939ea82a06a06b238a8aa3f1a1ed8b
-  data.tar.gz: 4fd49fc32b5fd5aa17e24ac166f384352a5cb85a72f57cb3aa774b8837c62c94439412252ba7164641b59c4cec7fc60a218eab1419dad913ea008c30058722d5
+  metadata.gz: d25713fb91fde68daaa07f6809a3c567afc18864a759e47fd032c31cd78cbe195eba2919deff4547d2fe6888e032f7394af4012aea839d1fc6b3d4ee7b1e94bf
+  data.tar.gz: 363185c38d788ae91528dc1fde6e21201fc19bec673848202a43589c36c8be3f6fe8e54cb367bfb8652ea286eda6513ab38e86e20aef99f8b7011cb1351fed3b

data/.github/workflows/ci.yml

@@ -12,7 +12,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        ruby-version: ['2.6', '2.7', '3.0', '3.1', '3.2']
+        ruby-version: ['3.0', '3.1', '3.2']
 
     steps:
       - uses: actions/checkout@v3

data/.gitignore

@@ -10,6 +10,7 @@ pkg/*
 .rvmrc
 .ruby-version
 .ruby-gemset
+.tool-versions
 
 # Spec artifacts
 /coverage

data/.rubocop.yml

@@ -1,3 +1,6 @@
+AllCops:
+  TargetRubyVersion: 3.0
+
 Layout/LineLength:
   Max: 120
 

data/README.md

@@ -1,20 +1,28 @@
-# Hledger-Forecast
+<p align="center">
+<img src="https://github.com/olimorris/hledger-forecast/assets/9512444/5edb77e3-0ec6-4158-9b16-3978c1259879" alt="hledger-forecast" />
+</p>
 
-[![Tests](https://github.com/olimorris/hledger-forecast/actions/workflows/ci.yml/badge.svg)](https://github.com/olimorris/hledger-forecast/actions/workflows/ci.yml)
+<h1 align="center">hledger-forecast</h1>
 
-A wrapper which builds on [hledger's](https://github.com/simonmichael/hledger) [forecasting](https://hledger.org/dev/hledger.html#forecasting) capability. Uses a `yaml` config file to generate forecasts whilst adding functionality for future cost rises (e.g. inflation) and the automatic tracking of planned transactions.
+<p align="center">
+<a href="https://github.com/olimorris/hledger-forecast/stargazers"><img src="https://img.shields.io/github/stars/olimorris/hledger-forecast?color=c678dd&logoColor=e06c75&style=for-the-badge"></a>
+<a href="https://github.com/olimorris/hledger-forecast/issues"><img src="https://img.shields.io/github/issues/olimorris/hledger-forecast?color=%23d19a66&style=for-the-badge"></a>
+<a href="https://github.com/olimorris/hledger-forecast/blob/main/LICENSE"><img src="https://img.shields.io/github/license/olimorris/hledger-forecast?color=%2361afef&style=for-the-badge"></a>
+<a href="https://github.com/olimorris/hledger-forecast/actions/workflows/ci.yml"><img src="https://img.shields.io/github/actions/workflow/status/olimorris/hledger-forecast/ci.yml?branch=main&label=tests&style=for-the-badge"></a>
+</p>
 
-See the [rationale](#brain-rationale) section for why this gem may be useful to you.
+**"Improved", you say?** Using a _yaml_ file, forecasts can be quickly generated into a _journal_ file ready to be fed into [hledger](https://github.com/simonmichael/hledger). Forecasts can be easily constrained between dates, inflated by modifiers, tracked until they appear in your bank statements and summarized into your own daily/weekly/monthly/yearly personal forecast income and expenditure statement.
+
+I **strongly** recommend you read the [rationale](#paintbrush-rationale) section to see if this app might be useful to you.
 
 ## :sparkles: Features
 
 - :book: Uses a simple yaml file to generate forecasts which can be used with hledger
-- :date: Can smartly track forecasted transactions against actuals
+- :date: Can smartly track forecasts against your bank statement
 - :moneybag: Can automatically apply modifiers such as inflation/deflation to forecasts
-- :abacus: Supports calculated amounts in forecasts (uses the [Dentaku](https://github.com/rubysolo/dentaku) gem)
-- :heavy_dollar_sign: Full currency support (uses the [RubyMoney](https://github.com/RubyMoney/money) gem)
+- :abacus: Enables the use of maths in your forecasts (for amounts and dates)
+- :chart_with_upwards_trend: Display your forecasts as income and expenditure reports (e.g. daily, weekly, monthly)
 - :computer: Simple and easy to use CLI
-- :chart_with_upwards_trend: Summarize your forecasts by period and category and output to the CLI
 
 ## :package: Installation
 
@@ -42,7 +50,7 @@ The available options are:
 
 ### Generate command
 
-The `hledger-forecast generate` command will generate a forecast  _from_ a `yaml` file _to_ a journal file. You can see the output of this command in the [example.journal](https://github.com/olimorris/hledger-forecast/blob/main/example.journal) file.
+The `hledger-forecast generate` command will generate a forecast _from_ a `yaml` file _to_ a journal file. You can see the output of this command in the [example.journal](https://github.com/olimorris/hledger-forecast/blob/main/example.journal) file.
 
 The available options are:
 
@@ -59,7 +67,7 @@ The available options are:
 
 Running the command with no options will assume a `forecast.yml` file exists.
 
-### Using with Hledger
+### Using with hledger
 
 To work with hledger, include the forecast file and use the `--forecast` flag:
 
@@ -67,11 +75,13 @@ To work with hledger, include the forecast file and use the `--forecast` flag:
 
 The command will generate a forecast up to the end of Feb 2024, showing the balance for any asset accounts, overlaying some bank transactions with the forecast journal file. Of course, refer to the [hledger](https://hledger.org/dev/hledger.html) documentation for more information on how to query your finances.
 
-To apply any modifiers, use the `--auto` flag at the end of your command.
+> **Note**: To apply any modifiers, use the `--auto` flag at the end of your command.
 
 ### Summarize command
 
-As your `yaml` configuration file grows, it can be helpful to sum up the total amounts and output them to the CLI. This can be achieved by:
+As your `yaml` configuration file grows, it can be helpful to sum up the total amounts and output them to the CLI.
+Furthermore, being able to see your monthly profit and loss statement _if_ you were to purchase that new item may
+influence your buying decision. In hledger-forecast, this can be achieved by:
 
     hledger-forecast summarize -f my_forecast.yml
 
@@ -79,14 +89,16 @@ The available options are:
 
     Usage: hledger-forecast summarize [options]
 
-        -f, --forecast FILE              The path to the FORECAST yaml file to summarize
-        -h, --help                       Show this help message
+    -f, --forecast FILE              The path to the FORECAST yaml file to summarize
+    -r, --roll-up PERIOD             The period to roll-up your forecasts into. One of:
+                                     [yearly], [half-yearly], [quarterly], [monthly], [weekly], [daily]
+    -h, --help                       Show this help message
 
 ## :gear: Configuration
 
-### The YAML file
+### The yaml file
 
-> **Note**: See the [example.yml](https://github.com/olimorris/hledger-forecast/blob/main/example.yml) file for an example of a complex config file and its [output](https://github.com/olimorris/hledger-forecast/blob/main/example.journal)
+> **Note**: See the [example.yml](https://github.com/olimorris/hledger-forecast/blob/main/example.yml) file for an example config and its corresponding [output](https://github.com/olimorris/hledger-forecast/blob/main/example.journal)
 
 Firstly, create a `yaml` file which will contain the transactions you'd like to forecast:
 
@@ -175,6 +187,17 @@ monthly:
         to: "2025-01-01"
 ```
 
+It can also be useful to compute a `to` date by adding on a number of months to the `from` date. Extending the example above:
+
+```yaml
+- amount: 125
+  category: "Expenses:Holiday"
+  description: Holiday
+  to: "=12"
+```
+
+This will take the `to` date to _2024-02-29_. This can be useful if you know a payment is due to end in _n_ months time and don't wish to use one of the many date calculators on the internet.
+
 ### Calculated amounts
 
 > **Note**: Calculations will be determined up to two decimal places
@@ -191,7 +214,7 @@ monthly:
         description: New Kitchen
 ```
 
-Simply ensure that the amount starts with an `=` sign, is enclosed in quotation marks and uses standard mathematical notations.
+Simply ensure that the amount starts with an `=` sign, is enclosed in quotation marks and uses standard mathematical notations. Of course, it may make sense to restrict this transaction with a `to` date in months, as per the [transaction level dates](#transaction-level) section.
 
 ### Tracking transactions
 
@@ -203,10 +226,10 @@ To mark transactions as available for tracking you may use the `track` option in
 
 ```yaml
 once:
-    account: "Assets:Bank"
+  - account: "Assets:Bank"
     from: "2023-03-05"
     transactions:
-      - amount: 3000
+      - amount: -3000
         category: "Expenses:Shopping"
         description: Refund for that damn laptop
         track: true
@@ -220,7 +243,7 @@ To use this feature, ensure you pass a filepath to the `-t` flag, such as:
 
 The app will use a hledger query to determine if the combination of category and amount is present in the periods between the `from` key and the current date in the journal file you've specified. If not, then the app will include it as a forecast transaction in the output file.
 
-### Applying modifiers
+### Modifiers
 
 > **Note**: For modifiers to be included in your hledger reporting, use the `--auto` flag
 
@@ -228,17 +251,17 @@ Within your forecasts, it can be useful to reflect future increases/decreases in
 
 ```yaml
 monthly:
-    account: "Assets:Bank"
-    from: "2023-03-05"
-    transactions:
-      - amount: 450
-        category: "Expenses:Groceries"
-        description: Food shopping
-        modifiers:
-          - amount: 0.02
-            description: "Inflation"
-            from: "2024-01-01"
-            to: "2024-12-31"
+  account: "Assets:Bank"
+  from: "2023-03-05"
+  transactions:
+    - amount: 450
+      category: "Expenses:Groceries"
+      description: Food shopping
+      modifiers:
+        - amount: 0.02
+          description: "Inflation"
+          from: "2024-01-01"
+          to: "2024-12-31"
 ```
 
 This will generate an [auto-posting](https://hledger.org/dev/hledger.html#auto-postings) in your forecast which will
@@ -259,15 +282,64 @@ modifiers:
     to: "2025-12-31"
 ```
 
-### Additional settings
+### Roll-ups
+
+As part of the summarize command, it can be useful to sum-up all of the transactions in your `yaml` file and see what your income and expenditure is over a given period (e.g. "how much profit do I _actually_ make every year when all of my costs are taken into account?").
+
+In order to do this, custom forecasts need to have the `roll-up` key defined. That is, given the custom period you've specified, what number do you need to multiply the amount by in order to "roll it up" into an annualised figure. Let's look at the example below:
+
+```yaml
+custom:
+  - frequency: "every 2 weeks"
+    account: "Assets:Bank"
+    from: "2023-03-01"
+    roll-up: 26
+    transactions:
+      - amount: 80
+        category: "Expenses:Personal Care"
+        description: Hair and beauty
+```
+
+Every 2 weeks a planned expense of £80 is made. So over the course of a year, we'd need to multiply that amount by 26 to get to an annualised figure. Of course for periods like `monthly` and `quarterly` it's easy for hledger-forecast to annualise those amounts so no `roll-up` is required.
+
+To see the monthly summary of your `yaml` file, the following command can be used:
+
+    hledger-forecast summarize -f my_forecast.yml -r monthly
+
+You can also roll-up with the following periods:
+
+- daily
+- weekly
+- monthly
+- quarterly
+- half-yearly
+- yearly
+
+### Summary exclusions
+
+It can be useful to exclude certain items from your summary, like one-off items. This can be achieved by specifying `summary_exclude: true` next to a transaction:
+
+```yaml
+once:
+  - account: "Assets:Bank"
+    from: "2023-03-05"
+    transactions:
+      - amount: -3000
+        category: "Expenses:Shopping"
+        description: Refund for that damn laptop
+        summary_exclude: true
+        track: true
+```
+
+### Additional config settings
 
 Additional settings in the config file to consider:
 
 ```yaml
 settings:
-  currency: GBP                 # Specify the currency to use
-  show_symbol: true             # Show the currency symbol?
-  thousands_separator: true     # Separate thousands with a comma?
+  currency: GBP # Specify the currency to use
+  show_symbol: true # Show the currency symbol?
+  thousands_separator: true # Separate thousands with a comma?
 ```
 
 ## :camera_flash: Screenshots
@@ -282,12 +354,10 @@ settings:
 
 ## :paintbrush: Rationale
 
-Firstly, I've come to realise from reading countless blog and Reddit posts on [plain text accounting](https://plaintextaccounting.org), that everyone does it __completely__ differently! There is _great_ support in hledger for [forecasting](https://hledger.org/1.29/hledger.html#forecasting) using periodic transactions. Infact, it's nearly perfect for my needs. My only wishes were to be able to sum up monthly transactions much faster (so I can see my forecasted monthly I&E), apply future cost pressures more easily (such as inflation) and to be able to track and monitor specific transactions.
-
-Regarding the latter; I may be expecting a material amount of money to leave my account in May (perhaps for a holiday booking). But maybe, that booking ends up leaving in July instead. Whilst I would have accounted for that expense in my forecast, it will be tied to some date in May. So if that transaction doesn't appear in the "actuals" of my May bank statement (which I import into hledger), it won't be included in my forecast at all (as the latest transaction period will be greater than the forecast period). The impact is that my forecasted balance in any future month could be $X better off than reality. Being able to automatically look out for these transactions, and include them if they're not present, is a nice time saver.
+I moved to hledger from my trusty Excel macro workbook. This thing had been with me for 5+ years. I used it to workout whether I could afford that new gadget and when I'd be in a position to buy a house. I used it to see if I was on track to have £X in my savings accounts by a given date as well as see how much money I could save on a monthly basis. That time I accidentally double counted my bonus or thought I'd accounted for my credit card bill? Painful! Set me back a few months in terms of my savings plans. In summary, I relied _heavily_ on having a detailed and accurate forecast.
 
-Also, I like to look ahead up to 3 years at a time and understand what my bank balances might look like. For this to be really accurate, factors such as inflation and salary expectations should be included. This is where the idea for modifiers came in. Being able to apply a percentage to a given category between two dates and automatically have the impact included any extended forecasts.
+I love hledger. Switching from Excel has been a breath of fresh air. There's only so many bank transactions a workbook can take before it starts groaning (yes, even on an M1 Mac). However there were a few forecasting features that I missed. The sort of features that in Excel terms mean I'd just copy a bunch of cells and paste them into columns which represented future dates or apply a neat little formula to divide a big number by 12 to get to a monthly repayment. Because I like to plan 3-5 years out at a time, I wanted to crudely account for future price and salary increases. Sure, I can add some auto-postings to the end of my journal file but I bet a lot of users didn't know about this or even know how to constrain them between two dates.
 
-Now I'll freely admit these are two minor issues. So minor infact that they can probably be addressed by a dedicated 5 minutes every month as part of your hledger workflow. However I liked the idea of automating as much of my month end process as possible and saw this as an interesting challenge to try and solve.
+I also made an assumption that a lot of users probably think of their finances in terms of their monthly costs (e.g. car payments, mortgage, food), half-yearly costs (e.g. service charge if you have an apartment in the UK) and yearly costs (e.g. holidays, gifts) etc. But likely never do the math to add them all together and workout how much money they have left over by the end of it all. Well I built that into this app and my daily profit figure hit me hard :rofl:. Give it a try!
 
-Whilst I tried to work within the constraints of a `journal` file, moving to a `yaml` format made the implementation of these features much easier and allowed me to stay true to how you'd accomplish forecasting in hledger, manually. Whilst the config file can end up being many lines long, the output journal should be relatively streamlined and easy to follow.
+So I thought I'd share this little Ruby gem in the hope that people find it useful. Perhaps for those who are moving from an Excel based approach to [plain text accounting](https://plaintextaccounting.org), or for those who want a little bit of improvement to the existing capabilities within hledger.

data/example.journal

@@ -1,40 +1,51 @@
-~ monthly from 2023-03-01  * Bonus, Salary, Food, New cell phone, Holiday savings
-    Income:Bonus         £-100.00  ;  Bonus
-    Income:Salary        £-2,000.00;  Salary
-    Expenses:Food        £500.00   ;  Food
-    Expenses:Phone       £75.00    ;  New cell phone
-    Expenses:Holiday     £208.33   ;  Holiday savings
+~ monthly from 2023-03-01  * Salary, Bills, Food, New Kitchen
+    Income:Salary             $-3,500.00;  Salary
+    Expenses:Bills            $175.00   ;  Bills
+    Expenses:Food             $500.00   ;  Food
+    Expenses:House            $208.33   ;  New Kitchen
     Assets:Bank
 
-~ monthly from 2023-03-01 to 2024-01-01  * Mortgage
-    Expenses:Mortgage    £1,000.00 ;  Mortgage
+~ monthly from 2023-03-01 to 2025-01-01  * Mortgage
+    Expenses:Mortgage         $2,000.00 ;  Mortgage
     Assets:Bank
 
-~ monthly from 2023-03-01  * Pension draw down
-    Income:Pension       £-500.00  ;  Pension draw down
-    Assets:Savings
+~ monthly from 2023-03-01 to 2024-02-29  * Holiday
+    Expenses:Holiday          $125.00   ;  Holiday
+    Assets:Bank
 
-~ every 3 months from 2023-04-01  * Bonus
-    Income:Bonus         £-1,000.00;  Bonus
+~ monthly from 2023-03-01 to 2025-01-01  * Rainy day fund
+    Assets:Savings            $300.00   ;  Rainy day fund
     Assets:Bank
 
-~ every 6 months from 2023-04-01  * Holiday
-    Expenses:Holiday     £500.00   ;  Holiday
+~ monthly from 2024-01-01  * Pension draw down
+    Income:Pension            $-500.00  ;  Pension draw down
+    Assets:Pension
+
+~ every 3 months from 2023-04-01  * Quarterly bonus
+    Income:Bonus              $-1,000.00;  Quarterly bonus
+    Assets:Bank
+
+~ every 6 months from 2023-04-01  * Top up holiday funds
+    Expenses:Holiday          $500.00   ;  Top up holiday funds
     Assets:Bank
 
 ~ yearly from 2023-04-01  * Annual Bonus
-    Income:Bonus         £-2,000.00;  Annual Bonus
+    Income:Bonus              $-2,000.00;  Annual Bonus
     Assets:Bank
 
-~ every 5 days from 2023-03-01  * Car fuel
-    Expenses:Car:Fuel    £150.00   ;  Car fuel
+~ every 2 weeks from 2023-03-01  * Hair and beauty
+    Expenses:Personal Care    $80.00    ;  Hair and beauty
     Assets:Bank
 
-~ 2023-06-01  * [TRACKED] Forecast new car cost
-    Expenses:Car         £5,000.00 ;  Forecast new car cost
+~ 2023-06-01  * [TRACKED] Refund for that damn laptop
+    Expenses:Shopping         $-3,000.00;  Refund for that damn laptop
     Assets:Bank
 
 = Expenses:Food date:2024-01-01..2024-12-31
-    Expenses:Food        *0.1      ;  Food - Inflation
-    Assets:Bank          *-0.1
+    Expenses:Food             *0.02     ;  Food - Inflation
+    Assets:Bank               *-0.02
+
+= Expenses:Food date:2025-01-01..2025-12-31
+    Expenses:Food             *0.05     ;  Food - Inflation
+    Assets:Bank               *-0.05
 

data/example.yml

@@ -2,32 +2,44 @@ monthly:
   - account: "Assets:Bank"
     from: "2023-03-01"
     transactions:
-      - amount: -100
-        category: "Income:Bonus"
-        description: Bonus
-      - amount: -2000
+      - amount: -3500
         category: "Income:Salary"
         description: Salary
+      - amount: 2000
+        category: "Expenses:Mortgage"
+        description: Mortgage
+        to: "2025-01-01"
+      - amount: 175
+        category: "Expenses:Bills"
+        description: Bills
       - amount: 500
         category: "Expenses:Food"
         description: Food
         modifiers:
-          - amount: 0.1
+          - amount: 0.02
             description: "Inflation"
             from: "2024-01-01"
             to: "2024-12-31"
-      - amount: 75
-        category: "Expenses:Phone"
-        description: New cell phone
-      - amount: "=2500/12"
+          - amount: 0.05
+            description: "Inflation"
+            from: "2025-01-01"
+            to: "2025-12-31"
+      - amount: "=5000/24"
+        category: "Expenses:House"
+        description: New Kitchen
+      - amount: 125
         category: "Expenses:Holiday"
-        description: Holiday savings
-      - amount: 1000
-        category: "Expenses:Mortgage"
-        description: Mortgage
-        to: "2024-01-01"
-  - account: "Assets:Savings"
+        description: Holiday
+        to: "=12"
+  - account: "Assets:Bank"
     from: "2023-03-01"
+    to: "2025-01-01"
+    transactions:
+      - amount: 300
+        category: "Assets:Savings"
+        description: "Rainy day fund"
+  - account: "Assets:Pension"
+    from: "2024-01-01"
     transactions:
       - amount: -500
         category: "Income:Pension"
@@ -39,7 +51,7 @@ quarterly:
     transactions:
       - amount: -1000.00
         category: "Income:Bonus"
-        description: Bonus
+        description: Quarterly bonus
 
 half-yearly:
   - account: "Assets:Bank"
@@ -47,7 +59,7 @@ half-yearly:
     transactions:
       - amount: 500
         category: "Expenses:Holiday"
-        description: Holiday
+        description: Top up holiday funds
 
 yearly:
   - account: "Assets:Bank"
@@ -59,21 +71,23 @@ yearly:
 
 once:
   - account: "Assets:Bank"
-    from: "2023-03-01"
+    from: "2023-03-05"
     transactions:
-      - amount: 5000.00
-        category: "Expenses:Car"
-        description: Forecast new car cost
+      - amount: -3000
+        category: "Expenses:Shopping"
+        description: Refund for that damn laptop
+        summary_exclude: true
         track: true
 
 custom:
-  - frequency: "every 5 days"
+  - frequency: "every 2 weeks"
     account: "Assets:Bank"
     from: "2023-03-01"
+    roll-up: 26
     transactions:
-      - amount: 150
-        category: "Expenses:Car:Fuel"
-        description: Car fuel
+      - amount: 80
+        category: "Expenses:Personal Care"
+        description: Hair and beauty
 
 settings:
-  currency: GBP
+  currency: USD

data/hledger-forecast.gemspec

@@ -4,6 +4,7 @@ $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
 require 'hledger_forecast/version'
 
 Gem::Specification.new do |s|
+  s.required_ruby_version = '~> 3.0'
   s.name        = 'hledger-forecast'
   s.version     = HledgerForecast::VERSION
   s.authors     = ['Oli Morris']

data/lib/hledger_forecast/calculator.rb

@@ -0,0 +1,21 @@
+module HledgerForecast
+  # Calculate various
+  class Calculator
+    def initialize
+      @calculator = Dentaku::Calculator.new
+    end
+
+    def evaluate(amount)
+      return amount unless amount.is_a?(String)
+
+      @calculator.evaluate(amount.slice(1..-1))
+    end
+
+    def evaluate_date(from, to)
+      return to unless to[0] == "="
+
+      # Subtract a day from the final date
+      (from >> @calculator.evaluate(to.slice(1..-1))) - 1
+    end
+  end
+end

data/lib/hledger_forecast/cli.rb

@@ -118,6 +118,29 @@ module HledgerForecast
           options[:forecast_file] = file
         end
 
+        opts.on("-r", "--roll-up PERIOD",
+                "The period to roll-up your forecasts into. One of:",
+                "[yearly], [half-yearly], [quarterly], [monthly], [weekly], [daily]") do |rollup|
+          options[:roll_up] = rollup
+        end
+
+        opts.on("--from DATE",
+                "Include transactions that start FROM a given DATE [yyyy-mm-dd]") do |from|
+          options[:from] = from
+        end
+
+        opts.on("--to DATE",
+                "Include transactions that run TO a given DATE [yyyy-mm-dd]") do |to|
+          options[:to] = to
+        end
+
+        opts.on("-s", "--scenario \"NAMES\"",
+                "Include transactions from given scenarios, e.g.:",
+                "\"base, rennovation, car purchase\"") do |_scenario|
+          # Loop through scenarios, seperated by a comma
+          options[:scenario] = {}
+        end
+
         opts.on_tail("-h", "--help", "Show this help message") do
           puts opts
           exit
@@ -155,8 +178,10 @@ module HledgerForecast
     end
 
     def self.summarize(options)
-      forecast = File.read(options[:forecast_file])
-      puts Summarize.generate(forecast)
+      config = File.read(options[:forecast_file])
+      summarizer = Summarizer.summarize(config, options)
+
+      puts SummarizerFormatter.format(summarizer[:output], summarizer[:settings])
     end
   end
 end

data/lib/hledger_forecast/formatter.rb

@@ -0,0 +1,24 @@
+module HledgerForecast
+  # Formats various items used throughout the application
+  class Formatter
+    def self.format_money(amount, settings)
+      Money.from_cents(amount.to_f * 100, (settings[:currency]) || 'USD').format(
+        symbol: settings[:show_symbol] || true,
+        sign_before_symbol: settings[:sign_before_symbol] || false,
+        thousands_separator: settings[:thousands_separator] ? ',' : nil
+      )
+    end
+
+    def self.output_to_ledger(*compiled_data)
+      output = compiled_data.compact.map do |data|
+        data.map do |item|
+          next unless item[:transactions].any?
+
+          item[:header] + item[:transactions].join + item[:footer]
+        end.join
+      end.join("\n")
+
+      output.gsub(/\n{2,}/, "\n\n")
+    end
+  end
+end