We are having difficulties to import BMO statements.
The .CSV file has a variable number of non-transactional rows at the begining, it has a Total Row at the End and transaction amount has a $ symbol, so the Import template doesn't work. To use this .CSV file, it needs to be manipulated before importing.

The bank has a .QFX file format that doesn't import to Adagio BankRec either.

If there is anybody out there that is importing BMO statements in BankRec we would like to know what type of file is used, if there is any special filter used. Or otherwise, if the import is smooth or has to be manipulated as described above.

Any information will be greatly appreciated.

Hi Patricia,

If you change the extension of the .QFX to .OFX does it work when you choose "OFX" as the import file type?

Hi Andrew:

I changed the extension from .QFX to .OFX and I got the same errors: "No CRLF at buffer offset 0" "Missing OFX tag 'OFX'. Import will be aborted." "Import cancelled because of errors on validateion. -1 records read. 0 errors were found. No records were imported."

Please e-mail me both the CSV and QFX files you have downloaded.

Thanks

Hi,

Both of these issues and the BMO import files have already been reported to R&D. For the .CSV file, we implemented in the latest Hotfix a fix for the $ signs in the file but had to leave the T record at the end of the file for later release.

OK - thanks. I missed that. Sorry.

Patricia, seems there's a fix. Don't bother sending me the files. we already have a set.

The .CSV file will not be useful since BMO's interface exports a variable number of rows before the transactional record.

I am having trouble as well, importing BMO CSV statements. Trouble started after my update in November. The system is adding a second negative sign in front of the imported negative sign on the CSV statement. Help please!

Hi, Lynn,

Please contact your Adagio consultant. They will be able to provide you with a hotfix that resolves this issue.

In regards to import issues with bank rec,rather than having a 'fix' that my consultant charges to have installed can softrak correct this problem with an update? Soon?