In this week's post, I explain how I am happy still not having closed out my 2024 transactions. Read about it at https://hledgerfan.com/glad-not-to-have-closed-out-2024/.
I also glad not to have closed the year because although I do not use iadd, emacs/nvim also suggests the payee based on old transactions and facilitates to copy old transactions. However, I do 'pseudo-close' the year. I introduce an assertion for my assets and liabilities at the end of 2024 but I do not remove the transactions of 2024. So, it is kind of closing because I ensure assets/liabilities are not modified by mistake but I maintain 2024 transactions to ease my input of new transacitons for 2025.
1 Like
Nice approach. And eventually do you separate your 2024 and 2025 data into separate files?
I have my current journal which is always the same book/book.journal with the current year (2005) and one or two previous years (2024 and 2023). Every end of year I introduce a balance assertion. And when I want to reduce the number of transactions of the book/book.journal I separate the oldest year to another file book-2023/book.journal so I always have in my current journal my most recent transactions (2025 and 2024).
1 Like