On 08.12.17,11:54, Colin Dean wrote:
> I'm trying to capture budgets that change over time. It may start with 
> simply a ~ Monthly transaction but, over time, I want to "retire" old 
> budget amounts as well as document future budget changes, e.g. stepped 
> payment plans on rent, student loans, etc.
> 
> I had something like this in test.ledger, but ended up reducing it down to 
> just this when I found that my future budgets were simply ignored:
> 
> ~ Monthly
>   Expenses:Rent:Office        700.00 USD
>   Assets
> 
> ~ Monthly from 2018-01-01
>   Expenses:Rent:Expansion         2100.00 USD
>   Assets
> 
> ~ Monthly from 2019-07-01
>   Expenses:Rent:Expansion         500.00 USD
>   Assets
> 
> ~ Monthly from 2020-02-01
>   Expenses:Rent:Expansion         500.00 USD
>   Assets
> 
> When I run 
> 
> ledger -f test.ledger --forecast "d<[2021-02-01]" register 
> 
> I expect to see a 700.00 USD transaction for December 2017, a 2800.00 USD 
> transaction (or total) for January 2018, 3300.00 USD total starting July 
> 2019, and so on. Instead, I only see the result of the first budget 
> transaction, the 700.00 USD monthly.
> 
>  https://groups.google.com/forum/#!topic/ledger-cli/nu5t9dFOOH4 led me to 
> believe that I need to actually include some transactions with the account 
> in order to make it appear. I ditched the second account and made some 
> other changes, such as setting explicit dates on the budget items:
> 
> ~ Monthly until 2021-02-28
>   Expenses:Rent:Office        700.00 USD
>   Assets
> 
> ~ Monthly from 2018-01-01 until 2021-02-28
>   Expenses:Rent:Office         2100.00 USD
>   Assets
> 
> ~ Monthly from 2019-07-01 until 2021-02-28
>   Expenses:Rent:Office         500.00 USD
>   Assets
> 
> ~ Monthly from 2020-02-01 until 2021-02-28
>   Expenses:Rent:Office         500.00 USD
>   Assets
> 
> 2017-12-01 Rent
>   Expenses:Rent:Office    700.00 USD
>   Expenses:Rent:Expansion   0.00 USD
>   Assets
> 
> but ledger still disregards the other monthly budget transactions when 
> executing the same command,
> 
> ledger -f test.ledger --forecast "d<[2021-02-01]" register 
> 
> What am I doing wrong? This is a powerful feature that I know I've probably 
> got something slightly off.
> 
> Here's an example output appending --yearly --columns 80 to the above in 
> order to keep this message a little shorter.
> 
> 17-Jan-01 - 17-Dec-31           Assets                  -700.00 USD  
> -700.00 USD
>                                 Expenses:Rent:Office     700.00 USD        
>     0
> 18-Jan-01 - 18-Dec-31           Assets                 -8400.00 USD 
> -8400.00 USD
>                                 Expenses:Rent:Office    8400.00 USD        
>     0
> 19-Jan-01 - 19-Dec-31           Assets                 -8400.00 USD 
> -8400.00 USD
>                                 Expenses:Rent:Office    8400.00 USD        
>     0
> 20-Jan-01 - 20-Dec-31           Assets                 -8400.00 USD 
> -8400.00 USD
>                                 Expenses:Rent:Office    8400.00 USD        
>     0
> 21-Jan-01 - 21-Dec-31           Assets                 -1400.00 USD 
> -1400.00 USD
>                                 Expenses:Rent:Office    1400.00 USD        
>     0
> 
> 2017 is correct but 2018 should be 33600.00 USD, 2019 should be 36600.00 
> USD, 2020 should be 37200.00 USD, and 2021 should be 6200.00 USD.
> 
> If I add something like this *after* the first budget transaction:
> 
> ~ Monthly
>   Expenses:Accountant        999.00 USD
>   Assets
> 
> It will show up in the forecast. If I put a *from* or *since *date spec on 
> the budget transaction, it won't. If I put an *until *or* to *on it, it 
> does get included.
> 
> What's up here? Did I find a bug or am I doing something wrong?
> 

Did you find out more on this one? Would be interesting to know the 
solution here.

Jostein

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to