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

Add support for SWIFT headers #9

Closed
bumi opened this issue Jun 7, 2016 · 9 comments
Closed

Add support for SWIFT headers #9

bumi opened this issue Jun 7, 2016 · 9 comments

Comments

@bumi
Copy link
Contributor

bumi commented Jun 7, 2016

SWIFT headers like {1:F01AXISINBBAXXXXXXXXXXXXX}{2:I940XXXXXXXXAXXXN}{4: should be supported.
see also issue #8

@FooBarWidget
Copy link

I want to report that ING in the Netherlands also has MT940 files with such SWIFT headers.

@bumi
Copy link
Contributor Author

bumi commented Dec 14, 2016

Hi @FooBarWidget thanks for the report. good to know.
Do the headers contain information that you need?
Sadly I am currently lacking time to add this functionality.

@FooBarWidget
Copy link

MT940 looks like arcane magic to me so I don't know how to answer that question. :) I haven't been able to parse my files using any Ruby parser library so I've switched to using CAMT053 XML files.

@bumi
Copy link
Contributor Author

bumi commented Dec 15, 2016

sorry to hear that. maybe we should just strip it by default as the headers are mostly not needed and just cause problems. parsing should work fine if you remove the header.

But if you can use CAMT53 it is the better format to use anyway.
Thanks for reporting and let me know if there is anything that I can help with.

@bumi
Copy link
Contributor Author

bumi commented Dec 15, 2016

could you provide a sample file of your format?

@FooBarWidget
Copy link

I can't provide a full sample, but maybe it's helpful if I provide the beginning (with some info stripped out):

{1:F01INGBNL2ABXXX0000000000}
{2:I940INGBNL2AXXXN}
{4:
:20:P161007000000001
:25:<some IBAN here>EUR
:28C:00000
:60F:C160831EUR1234,56
:61:1609130913D1700,05NTRFEREF//16257002497622
/TRCD/00100/
:86:/EREF/<some description>//CNTP/<some IBAN here>/<some BIC here>
/<vendor name here>///REMI/USTD//<another description>/

It seems the parser bailed out at the first line.

@bumi
Copy link
Contributor Author

bumi commented Dec 17, 2016

great thanks!

yes, the first 3 lines ({1: ...) are some header data the actual MT940 starts at :20: / after {:4

if you strip that header it should work. but as some banks have this header data the parser should support it.

@Uepsilon
Copy link
Contributor

Uepsilon commented Oct 8, 2018

fixed by #13

@Uepsilon Uepsilon closed this as completed Oct 8, 2018
@Uepsilon
Copy link
Contributor

Uepsilon commented Oct 8, 2018

included in new release 1.2.0

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

3 participants