Open Kaligule opened 7 years ago
Same here.
Does this test_icsv2ledger.sh help?
Does this test_icsv2ledger.sh help?
It does if this is the expected CSV Fromat: 2050/01/02,Spotify,-5\n
Here is what my bank gives me:
xxxxxxxxxxxxx-xxx-xxxxxx-0 ,31-Dec-2019,System Generated Entry ,,21.05,,490.56
xxxxxxxxxxxxx-xxx-xxxxxx-0 ,30-Dec-2019,Pre-Authorized Credit - Incoming STRIPE ,,,485.2,511.61
icsv2ledger goes belly up because it has no idea what to do with this information, and neither did I. I respect that it's very difficult for a program to be universally compatible with diverging standards for formatting, but it would be nice to know with crystal clarity what icsv2ledger wants.
OK I think the issue here is that we always have to be explicit with the data. And even then, the formatting might be unexpected. Documented examples should include real data examples and real working command-line attempts. Or perhaps, stress the importance of the config file.
All the information you need is in the README but clarity on how to get things set-up is important.
Nothing fancy, just 3 lines of csv converted to 3 entries of ledger.
I tried for 20 Minutes now and couldn't get anything working, so it would be nice to see how it is intended to work.