Input processing scripts - The following scripts are supplied in the standard package:
Note: Every version adds scripts for additional banks. Check out what is in the next version!
Also included is an experimental script to parse a report from MS Money which has been "sent" to the desktop in XML format. I am not sure of the immediate added value of such a script but it proved the principle that XML formats can also be handled if required.
I may do others. This is depending on demand, completeness of the specifications and availability of some test data!
MT940 support - Scripts are provided for MT940 files from the following banks:
The User Interface
When MT2OFX is started without parameters (for example from the Start menu icon) the graphical user interface is displayed:
Click on "Browse" to select the input file. Click on "Convert!" to perform the conversion. Initially, the program will derive the name of the output file by removing any extension from the input file and adding the configured default extension.
The program settings are accessed by clicking on the "Options..." button.
The "Help" button displays the program help file; the "About" button gives information about the program.
By clicking on "Close" the program is terminated.
From the command line
If MT2OFX is run with a parameter on the command line, it assumes this is the name of an MT940 file. This file is silently converted to OFX/OFC/QIF in the same directory as the source file.
By associating the ".STA" file extension (and/or other extensions such as ".SWI" or ".940") with the MT2OFX program, it is possible to convert a file with a double-click from Windows Explorer. This association is set up during installation.
This allows pattern-based replacement of the payee, so payees including a date, sequence number or whatever can be translated to a standard value. This is often seen as a great weakness of personal finance software, which often provides a facility to map multiple FIXED payee names to a single value, but this cannot handle payee names which are different every time. MT2OFX can now sort this out for you!
The Payee which is found by the script is compared to each pattern in turn until there is a match. If a match is found, the payee is replaced with the replacement value and (optionally) the Transaction Category (for QIF output) is set. If no match as found, the Payee found by the script is left alone.
The pattern syntax is as supported by the RegExp object. By using parentheses, parts of the string can be saved. These "saved strings" can be inserted into the replacement by using "%1" etc. For example, Albert Heijn (Dutch Supermarket) always appends the branch code, as in "ALBERT HEIJN 1176". If you use a pattern of "ALBERT HEIJN (\d\d\d\d)", the branch number is saved as %1. If the replacement is "AH Branch %1", the result in this case will be "AH Branch 1176".
Set up Payee Mapping from the options dialog - there is a new button near the bottom. The mapping information is held in a file "PayeeMap.dat" which is neither delivered nor overwritten by installing MT2OFX.
To select a different file in the script, set Session.PayeeMapFile to the file name. Set it to "" to disable payee mapping for this run. To exempt an individual transaction from payee mapping, set SkipPayeeMapping=True in the Txn object.
The format of the files which various banks offer, varies considerably from bank to bank. Even though the program can handle input files which comply with the MT940 standard, some information is contained in these files in such a way that it is impossible for MT2OFX to find it without some help. The most important examples are the name of the payee and the actual transaction date, both of which are normally found somewhere in the transaction description.
To assist the program with its processing, the facility is offered to use small programs (written in VBScript).
Scripts for the supported banks are included.
For further information see the help file, which is available from the download page.
A Few Screenshots: