idpaterson
commented
8 months ago This seems like it would be better handled inside Monarch. In a comment reply the OP recommended recording the source of each balance entry and, at least by default, preserving Monarch balances with the import just filling in blanks or overwriting a past import. If it were possible to pull historic balance history from the institution that may be even better since it would allow reverting after a bad import rather than making a decision up front. Either way, this is not the place to request features for the Monarch app.
In reddit post Monarch loses CURRENT balances after importing HISTORIC balances from Mint a Monarch user was disappointed that inaccurate balances exported from Mint due to connection issues override valid daily balances in Monarch. I understand why import works this way, but maybe we can do better with the extension to mitigate the problem.
There may be a way in the extension to identify accounts that have not synced recently and trim the export to the last balance change. That way if the last 3 weeks of the CSV is all $132.89 you get only up to the first $132.89 then the rest is left to Monarch to either retain existing balances or carry that $132.89 forward.
I feel like it may not even be necessary to detect whether the account has stopped syncing… maybe this is something we could do for any account. We probably only want to trim duplicate values if the account is still active (i.e. exported data has balances up to the present day). In the worst case scenario you could get a CSV with only 1 row if an account has never had a balance change, but that is already the case if that balance happens to be $0 and I think that would still be okay for importing into Monarch.
Any thoughts on this?