Old entry trimmer hook. #127
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This hook excludes entries in the import that occurred prior to the last existing balance entry (that is already in the beancount ledger). Since these imported transactions should already be accounted for, the output of bean-extract becomes a lot smaller and easier to read. This is especially useful for financial institutions that do not allow customizing the date range of exported transactions. By default, we only trim entries already marked duplicate (e.g., by `DuplicateDetector`). If you do not use `DuplicateDetector` or want to trim old entries regardless of the "duplicate" metadata, set `only_trim_duplicates` to `False`.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This hook excludes entries in the import that occurred prior to the last existing balance entry (that is already in the beancount ledger). Since these imported transactions should already be accounted for, the output of bean-extract becomes a lot smaller and easier to read. This is especially useful for financial institutions that do not allow customizing the date range of exported transactions.
By default, we only trim entries already marked duplicate (e.g., by
DuplicateDetector). If you do not useDuplicateDetectoror want to trim old entries regardless of the "duplicate" metadata, setonly_trim_duplicatestoFalse.