-
Notifications
You must be signed in to change notification settings - Fork 16
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
Parse Errors #33
Comments
Using #34 (comment)
|
Can you provide the full json config that you used? In the issue that you link, I only see the layout section |
|
Oh I see did you just use the default config?
You should create a new json config file, updated with the correct values, store it in
|
lol now I finally get it, we have a cross-communication issue.
You are suggesting a new config file is required but I was trying to create a sample pdf to use with default setting. Testing pdf(s) are also needed. Maybe |
Read |
What do you think about changing JSON cleaning as follows?
|
To be honest I'd prefer to be explicit on the column names, also because of my previously mentioned aversion to regex. I might be persuaded to go for some additional keys like
|
Are you reading the csv file into Excel? (hence the format change). The desired behaviour is actually to always output the date in iso-format |
I'll try to create a config for your mock pdf later this week. It'll actually be a a really good base to use for testing of all the other functionality |
Country code is irrelevant as bank format normally consistent across countries
json file already uses field coding names, more portable as not specific to actual statements
No, output format specified by software consuming file
Only difference from default is |
CbaBankStatement.pdf fully supported on https://github.com/flywire/pdf_statement_reader/commits/cba with extended functionality. CbaBankStatement.csv
Note: Original pdf file has 2 invalid balances because |
Issue remains for misidentified data after end of transaction data as previously described. Suggest support dropping all records after user described string. |
Done at #33 (comment) (pdf at #30).
Amount starting/ending/contains CR/DBNo year in dateSkip lines starting/ending/contains Balance/ForwardConcatenate wrapped Transaction descriptionAllow currency signAllow thousands separatorThe text was updated successfully, but these errors were encountered: