-
-
Notifications
You must be signed in to change notification settings - Fork 49
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
Multiple statements in a single MT940 #52
Comments
To be honest, I wasn't aware that the empty line with the Modifying the parser to yield multiple transaction collections isn't all that trivial but it shouldn't be too hard to wrap it so the lines are parsed separately. I currently don't have the time to implement it so I'll leave it open until I have time to dig into it :) |
As far as I can tell from the files I have here; the '-; separates statements. Each statement has an opening/closing (or intermediate opening/closing) balance and could technically have a different account. I will verify whether the latter happens in practice. I know that CAMT.053 files with ING Bank can contain multiple account statements in a single file, and that RABO MT940 used to contain multiple accounts. I think the solution would be to:
If I have some spare time I'll pick up on this; I can share some example files once I have fully anonymised them. |
I also have this problem. Hows the fix coming on? For now I have inserted the following at line 449 in models.py as a fixup:
Statements all begin with:
and end with:
the - doesnt mean a new account. The bank just splits the statement into multiple parts for some reason. Completely unnecessary in my opinion and think it would be fine to just join them in your code somehow while preserving the first opening balance. Maybe even a preliminary parse to strip out the unnecessary separations. |
I also speak a bit of german so if you need help with the specifications at https://hbci-zka.de/spec/3_0.htm , let me know. |
is this still being worked on? I have to parse some statements with this format |
I guess Alexandre is not working on it anymore. If anyone has an example file for me with a bit of explanation what kind of results they're expecting, I can see if I can fix it. It will take a few weeks for me to get started though, I've been really busy lately. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
In a single MT940 file there are multiple statements. {1:F0XXXXXXXXXXXXXXXX}{2:OXXXXXXXXXXXXXXX}{3:{108:00000000002170}}{4: |
Potentially not an issue: when exporting mt940 from several business accounts it will deliver blocks separated by an empty line with just '-'. Using mt940.parse(file) on these exported files will correctly yield a list of all transactions, but only the opening and closing balance of the last statement.
I am not sure if this was intentional, but ideally a list of MT940 statements, each containing opening/closing balance and transactions is produced (e.g. similar to in the CAMT.053 format).
Is this desirable?
The text was updated successfully, but these errors were encountered: