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

[Feature Request] Support description_patterns for ECImporter #108

Closed
putzwasser opened this issue Nov 6, 2022 · 4 comments
Closed

[Feature Request] Support description_patterns for ECImporter #108

putzwasser opened this issue Nov 6, 2022 · 4 comments

Comments

@putzwasser
Copy link

putzwasser commented Nov 6, 2022

Thanks for the great work.

It would be very useful, if you'd add support for the description_patterns to the ECImporter as well. If you send money for different purposes to the same receiver (e.g. rent and costs for utilities in separate transactions), then you can't distinguish the transactions. Same holds true if send money to yourself (transfering money to different saving accounts, etc).

Using the more unique transaction description could help here.

As this might add ambiguity for the importer how to categorize I'd suggest that the order is: if description_pattern and payee_pattern matches, then payee_pattern gets disregarded as it is more general.

@siddhantgoel
Copy link
Owner

Great suggestion! I'll try to have a look in the next days!

@momu
Copy link

momu commented Dec 21, 2022

Thanks a lot for the importer.

From me +1 for the feature request.
Another nice to have option would be a third optional argument for the payee_pattern: the amount.
I've multiple transactions from the same person, but they differ in description and amount.

As mentioned above evaluating the description_pattern would also work in this case. But it would be easier in some cases with repeating transactions to differentiate the transactions by the transaction amount.

@siddhantgoel
Copy link
Owner

Just published v0.15.0 which allows for pattern-matching transactions in ECImporter against description strings.

Regarding the case when both payee and description strings match, I decided to go with payee pattern as I've noticed that it's usually more specific than the description. The importer should also log a warning to the console for such cases so the user knows about it when running bean-extract.

@momu could you please open a new issue with the suggestion for amount? I can see the use case for that suggestion but as the matching logic might become slightly more complex with it, maybe we could have that discussion on the newer issue. Thanks!

@momu
Copy link

momu commented Jan 15, 2023

@siddhantgoel Done. Sorry for the delay, but I bought a book about plaintext accounting with python and had to immediately read it ;)

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

No branches or pull requests

3 participants