At Railslove we build a lot of financial applications and work on integrating applications with banks and banking functionality. Our goal is to make simple solutions for what often looks complicated.
Cmxl is a friendly and extensible MT940 bank statement file parser that helps you extract data from bank statement files.
MT940 (MT = Message Type) is the SWIFT-Standard for the electronic transfer of bank statement files. When integrating with banks you often get MT940 or MT942 files as interface. For more information have a look at the different SWIFT message types
At some point in the future MT940 file should be exchanged with newer XML documents - but banking institutions are slow, so MT940 will stick around for a while.
Cmxl is a pure ruby parser and has no dependency on native extensions.
Add this line to your application's Gemfile:
gem 'cmxl'
And then execute:
$ bundle
Or install it yourself as:
$ gem install cmxl
Simple usage:
# Configuration:
# statement divider regex to split the individual statements in one file - the default is standard and should be good for most files
Cmxl.config[:statement_separator] = /\n-.\n/m
# do you want an error to be raised when a line can not be parsed? default is true
Cmxl.config[:raise_line_format_errors] = true
# try to stip the SWIFT header data. This strips everything until the actual first MT940 field. (if parsing fails, try this!)
Cmxl.config[:strip_headers] = true
# Statment parsing:
statements = Cmxl.parse(File.read('mt940.txt'), :encoding => 'ISO-8859-1') # parses the file and returns an array of statement objects. Please note: if no encoding is given Cmxl tries to guess the encoding from the content and converts it to UTF-8.
statements.each do |s|
puts s.reference
puts s.generation_date
puts s.opening_balance.amount
puts s.closing_balance.amount
puts s.sha # SHA of the statement source - could be used as an identifier (see: https://github.com/railslove/cmxl/blob/master/lib/cmxl/statement.rb#L49-L55)
s.transactions.each do |t|
puts t.information
puts t.description
puts t.entry_date
puts t.funds_code
puts t.credit?
puts t.debit?
puts t.sign # -1 if it's a debit; 1 if it's a credit
puts t.name
puts t.iban
puts t.sepa
puts t.sub_fields
puts t.reference
puts t.bank_reference
# ...
end
end
Every object responds to to_h
and let's you easily convert the data to a hash. Also every object responds to to_json
which lets you easily represent the statements as JSON with your favorite JSON library.
You probably will encounter encoding issues (hey, you are building banking applications!).
We try to handle encoding and format weirdnesses as much as possible. If no encoding is passed we try to guess the encoding of the data and convert it to UTF8.
In the likely case that you encounter encoding issues you can pass encoding options to Cmxl.parse(<string>, <options hash>)
. It accepts the same options as String#encode
If that fails, try to modify the file before you pass it to the parser - and please create an issue.
Cmxl currently does not support parsing of the SWIFT headers (like {1:F01AXISINBBA ....)
If your file comes with these headers try the strip_headers
configuration option to strip data execpt the actual MT940 fields.
Cmxl.config[:strip_headers] = true
Cmxl.parse(...)
CMXL is now also capable of parsing MT942 data. Just pass the data and the parser will identify the type automatically.
first_statement = Cmxl.parse(File.read('mt940.txt'), :encoding => 'ISO-8859-1').first
puts first_statement.mt942?
#=> false
first_statement = Cmxl.parse(File.read('mt942.txt'), :encoding => 'ISO-8859-1').first
puts first_statement.mt942?
#=> true
p first_statement.vmk_credit_summary.to_h
#=> { type: 'credit', entries: 1, amount: 9792.0, currency: 'EUR' }
p first_statement.vmk_dedit_summary.to_h
#=> { type: 'debit', entries: 0, amount: 0.0, currency: 'EUR' }
first_statement.transactions # same as for MT940
Because a lot of banks implement the MT940 format slightly different one of the design goals of this library is to be able to customize the individual field parsers. Every line get parsed with a special parser. Here is how to write your own parser:
# simply create a new parser class inheriting from Cmxl::Field
class MyFieldParser < Cmxl::Field
self.tag = 42 # define which MT940 tag your parser can handle. This will automatically register your parser and overwriting existing parsers
self.parser = /(?<world>.*)/ # the regex to parse the line. Use named regexp to access your match.
def upcased
self.data['world'].upcase
end
end
my_field_parser = MyFieldParser.parse(":42:hello from mt940")
my_field_parser.world #=> hello from MT940
my_field_parser.upcased #=> HELLO FROM MT940
my_field_parser.data #=> {'world' => 'hello from mt940'} - data is the accessor to the regexp matches
The Mt940 format often looks different for the different banks and the different countries. Especially the not strict defined fields are often used for custom bank data. If you have a file that can not be parsed please open an issue. We hope to build a parser that handles most of the files.
Maybe these are also interesting for you.
Automated tests: We use rspec to test Cmxl. Simply run rake
to execute the whole test suite.
git checkout -b my-new-feature
)git commit -am 'Add some feature'
)git push origin my-new-feature
)Cmxl is inspired and borrows ideas from the mt940_parser
by the great people at betterplace.
other parsers:
built with love by Railslove and some amazing people.
Released under the MIT-Licence.
Railslove builds FinTech products, if you need support for your project we are happy to help. Please contact us at team@railslove.com.