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

Tag 86 at the end does not get parsed #27

Open
sprileyMSTS opened this issue Jan 30, 2019 · 2 comments
Open

Tag 86 at the end does not get parsed #27

sprileyMSTS opened this issue Jan 30, 2019 · 2 comments

Comments

@sprileyMSTS
Copy link

I have :86: at the end of a statement. Per https://www.sepaforcorporates.com/swift-for-corporates/account-statement-mt940-file-format-overview/ this tag is to be treated as meta data at the statement level:
Tag 86 – Information to Account Owner
Optional – 6x65x
Additional information about the statement as a whole

In debugging it in the parser, this tag is getting associated as meta data for tag 64 (Available Balance) which immediately precedes it AND does not have an add_meta_data method. I believe this information should be added at the statement level as meta data. In my case the value is ":86:/OSDR/HSBCPLPW" which is the SWIFT code or BIC.

@Uepsilon
Copy link
Contributor

Uepsilon commented Jun 3, 2019

@sprileyMSTS sorry for the delay

i saw this myself a few times. but most banks add information related to transactions. the additional information at the end of a statement is omitted most of the times.

which swift code or bic do you get from you statement? is it the one of your account? it should not be related to any transaction as there might be multiple per statement.

is this something we should work on together? :)

@sprileyMSTS
Copy link
Author

In our case, HSBC is providing it as the SWIFT code for our bank account. We receive multiple files from multiple sources that we are processing, so this piece of information is useful for knowing which account at which bank we are dealing with (banks seem to be less than reliable about whether they use the IBAN in Tag 25. Ultimately we ended up not relying on this information, but expanding how we parse the account number and looking up the SWIFT code for our purposes.

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

No branches or pull requests

2 participants