FYI the format quite simple
# this matches a financial year like FY2018 for the financial year ending
2018
FY_RE = re.compile(r"^fy(\d{4})$")
# this matches a quarter in a financial year like FY2018-Q2
FY_QUARTER_RE = re.compile(r"^fy(\d{4})-q(\d)$")
On Tuesday, 17 March 2020 13:47:36 UTC,
+1 for this as a feature request built into beancount.
I would be willing to help in the development of this feature too.
One of the ways I thought this could be done is in fava and actually it
looks like it has already have been done to a basic level.
There is a fava option fiscal-year-end
Hello Martin,
I've combined both the beancount command line client and fava extension
into https://github.com/redstreet/fava_tax_loss_harvester. It'd be great if
you could point to that repo in the contributions doc. Thanks!
On Tuesday, March 10, 2020 at 11:35:44 PM UTC-7, Red S wrote:
>
>
Updates to the TLH extension in these interesting times we live in:
- the command line client has now been folded in to the fava client and
uses the same code (refactored out to support both fava and bean-query)
- a --brief option to the command line client displays the summary only
- unit tests
I wasn't sure how to interpret Martin's reply. At first, I thought he
was saying that he's not aware of circumstances where the FY !=
calendar year. But then I realized that he he was just stating that
beancount doesn't have a concept of FY.
As you say (and I'm sure as Martin is full aware),
Fairly common for some organizations to have financial years starting on
(say) 1st August or something similar. Sometimes to sync up with regulatory
requirements, sometimes so that bonuses/promotions hit a particular period
of the year, sometimes due to expected peak dates for a particular
