iCreateOFX Basic
1. The License Screen.
2. Loading file into the program.
3. The Statement Information Dialog.
4. The Loaded Grid.
5. Adding Scripts to the program and submitting files for support.
On initial start up, you will be prompted with the usage licence.
Please take a while to read through the terms specified there-in. After reading through, confirm that you have read the license by selecting the check-box to the bottom left of the license screen.
If you are satisfied with the terms accept them to proceed, otherwise decline the terms and un-install the software.
The remainder of this guide will only be relevant to you if you have accepted the terms.
To load a file into the program grid, from the Bank Script Stack (left of program and screen), select the appropriate bank name (script). You will be presented with an Open File Dialog from which you should browse to the location of the file you wish to load. Select it and press Open from the dialog.
The same routine is implemented for loading *.CSV, *.QIF and *.OFX files into the grid. For the latter two, select Load QIF or Load OFX from the stack and proceed with browsing for and selecting your file.
Extended Functionality: The program ships with four Generic scripts which can be accessed from the Generic Scripts button (as illustrated right) on the stack. The layout of the scripts are as follows:
1. Generic 3 Column: Date,Description,Amount
2. Generic 4 Column: Date,Description,Debit Amount,Credit Amount
3. Generic 5 Column: Date,Description,Details,Debit Amount,Credit Amount
4. iCreateOFX CSV: Date,MEMO,Details,Transaction ID,Amount
On having selected the file, you will then be presented with the Statement Information dialog.
The Statement Information dialog will be presented to you whenever a new file is loaded into the grid. You will not be able to proceed unless you fill out all the details since these are REQUIRED to write a valid OFX file. These details relate to the bank account for which you are writing the file.
Some banks include this information in the CSV downloads, and in some instances, the software utilises this information to populate these fields. You will, however, still need to confirm these.
By default, the dates in this dialog are set to the earliest and latest dates contained in the loaded transactions date range. This may not necessarily represent your statement anniversary dates, and you should change these to reflect that if necessary.
You can change statement information before finally committing to writing the OFX file, however, to proceed from this stage, you will have to complete the details. Select OK to proceed from this screen.
The layout of the grid, (as per illustration), is straight forward and includes only the required fields needed to write a valid OFX file. A commonly omitted field by retail banks is the Transaction ID, which is a unique identifier for any transaction on an account. The software recognises instances where this is not provided and generates this for you.
Another point of interest is the error notification. Valid OFX files require that the Details field is no more than 32 characters long. Whenever an item in this field exceeds this length, an error is shown next to the offending row. The item itself is also highlighted in RED to draw your attention to it, in addition to the Write OFX button being disabled. Editing the item and ensuring that the number of characters is 32 or less will remove the error.
It may be worth a mention here that any UNIQUE Transaction IDs that the software generates will persist no matter how many times you (load to) convert your CSV statement to OFX. PFMs utilise this ID to determine whether the transaction has previously been uploaded and therefore a duplicate.
By selecting Download Other Banks button, you can check our servers for support for your bank should it not be included on the Bank Script Stack.
You will be presented with the Currently available Bank List (illustrated left) dialog listing the scripts on our server and NOT already installed on your system. Select your required script if it is listed and select OK. Once this is done, the downloaded scripts will be listed under the Other Banks button on the Bank Script Stack. If however your bank is not listed, to add support for your bank, select Submit file header to have it included. Bear in mind that support for unlisted banks is dependent on users submitting their respective banks' file header layout.
NOTE: The scripts downloaded via this method will be listed under the Other Banks button located on the Bank Scripts Stack.
If your bank is not listed and would like for support to be added, choose the option to Submit file header from the Currently available Bank List dialog above. Before proceeding, open your bank file in a plain text reader e.g Notepad and copy the header plus at least two transactions, and paste into the resultant dialog (as illustrated right). You will also need to enter a name for the bank, and finally if you'd like to be immediately notified when the script has been uploaded, check the Notify Me box and enter your email. This last step is optional, but recommended.
NOTE: 1. Anonymize any personal information that may be included in the data by replacing numbers with XXX.2. Please do NOT edit your file in Excel before sending us the headers.