Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Features - Fiscal years; export CSV with custom date range; merchant or vendor field #55

Open
seb26 opened this issue Feb 7, 2025 · 3 comments
Labels
enhancement New feature or request

Comments

@seb26
Copy link

seb26 commented Feb 7, 2025

Hello Mayswind, here are 3 features/enhancements:

  1. Fiscal years - Allow a user to specify a fiscal year start date (by default 1 January) in user preferences, and add "This fiscal year" and "Previous fiscal year" as date ranges for filtering.

This has limited value obviously for those in countries who use 1 Jan-31 Dec because it would deliver same results as This year and Last year. But at least for major English speaking countries we have USA on 1 Oct-30 Sep, Australia on 1 Jul-30 Jun, and the UK on 6 Apr-5 Apr.

I am working on a PR for this.

  1. Export CSV with criteria, using date ranges (the available date ranges, and custom) and other filters perhaps like category, tags, and so on. This Export could be initiated from the Transaction Details page in a way that exports the results of the user's custom filters.

  2. Merchant, vendor or shop field - to indicate which entity the transaction was "paid to". There is a possibility of a saved list of merchants which the user could recall and select. Currently a user could tag transactions with a tag of the merchant's name, but it is not explicit. Single transactions almost always only have one merchant.

Do you have any thoughts on these?

@mayswind
Copy link
Owner

mayswind commented Feb 7, 2025

  1. I agree with you, and I'm glat to see a PR for this.
  2. I think it can add a dropdown menu with exporting to csv and tsv when hovering over the import button in transaction list page for desktop version.
  3. ezBookkeeping is not designed for enterprise accounting, but for personal users to record daily data. Therefore, the items in transaction data are designed for storing different types of data. The other plain text items used for classification or filtering, such as payers and payees are not parts of the transaction data. It is recommended to use transaction tags to storing these data. Maybe, in the future, it can add category to the transaction tag.

@mayswind mayswind added the enhancement New feature or request label Feb 7, 2025
@DriftingWind
Copy link

同样希望增加商户(收款人)字段,或者开放多个标签类别以便自定义,这样利于用户统计在某个商户上的开支。
例如我想查看全年在X宝、X东、X多多各消费了多少钱,这个“商户”字段就很有意义。

@mayswind
Copy link
Owner

同样希望增加商户(收款人)字段,或者开放多个标签类别以便自定义,这样利于用户统计在某个商户上的开支。 例如我想查看全年在X宝、X东、X多多各消费了多少钱,这个“商户”字段就很有意义。

ezBookkeeping would not add payee or payer for transaction, and plans to add category to the transaction tag. You can add some transaction tags like "X宝", "X东", "X多多" to transaction.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants