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

Improve "known balances" UX for synchronized bank accounts #216

Open
Bone008 opened this issue Feb 1, 2021 · 1 comment
Open

Improve "known balances" UX for synchronized bank accounts #216

Bone008 opened this issue Feb 1, 2021 · 1 comment

Comments

@Bone008
Copy link
Owner

Bone008 commented Feb 1, 2021

Most likely due to the discrepancy between "Buchung", "Wertstellung" and the internally assigned date, putting in known balances for bank accounts is a very painful experience, requiring manual checking of imported transaction dates and comparing them to what is shown in online banking.

Situations like this often happen:

image

Need to investigate deeper to find simple but more reliable solutions. One important component is most likely to take a different date column from the imported CSV row when calculating account balances.

@Bone008
Copy link
Owner Author

Bone008 commented Feb 1, 2021

Another (UX only) problem is that transaction groups can make a bank transaction appear out-of-order with its physical date (e.g. if it was grouped with something far later).

While the code takes the correct date, the user cannot see this and currently has no way of listing "raw" transactions without grouping.

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

No branches or pull requests

1 participant