Bank Feeds in Canada (BMO)

Hello ​@jeff00,

In 2024 R2 there is a new function to use Bank Feed from File using Secure SFTP. Have you explored this option with BMO Bank?

https://acumatica-builds.s3.amazonaws.com/builds/24.2/ReleaseNotes/AcumaticaERP_2024R2_ReleaseNotes.pdf

Regards,

Amaan Fazeer

Thank you Amaan.  I did see that earlier when R2 was announced but we still have another month before its rolled out for us.  But good suggestion. Will contact the bank and see if they will support it.

Thanks!

Jeff.

​@jeff00 we try to connect with BNC, we can connect to BNC with Plaid but we dont see all the credit card without any known reasons.

We arent able with MX at this time and we don’t know why!

Interresting!

I attached the list of institution of Plaid for Canada, if needed(we got it via Plaid API )

​@AmaanFazeer11 : do you know what is the file type supported by the STFP? There isnt a lot of information on the help about that? And the mapping?

Thanks!

This client has opted to use the new SFTP functionality in 2024R2 and is working with the bank to get things set up before their Always Current Upgrade date in February.

So this should resolve the reliability issue but I agree with you that the update documentation leaves some gaps in the steps. It indicates that we will have to define the mapping manually.

So that will be fun!

Hello ​@raphrf 

Currently in 24 R2 csv file type is supported. There are plans to incorporate other file types such as BAI2 and VCF in future versions.

Regards,

Amaan

Hi

The bank ask me if they support theses kind of files

Do you know which are supported? maybe I misunderstand

Thanks

Did this end up getting resolved in 25R1 or the upcoming 25R2 release?

I do not believe it is really Acumatica that should be resolving the coding part of the issue although Acumatica must have taken the lead on this to coordinate between the MX/PLAID and financial institutes. After all Acumatica is selling the Bank Feed and MX/PLAID are Acumatica integrated services. In our case we are bounced between Acumatica, MX and BMO OLBB and BMO SD for months now. each one blames another without any resolution yet.

Hello ​@raphrf 

Currently in 24 R2 csv file type is supported. There are plans to incorporate other file types such as BAI2 and VCF in future versions.

Regards,

Amaan

Hi

The bank ask me if they support theses kind of files

Do you know which are supported? maybe I misunderstand

Thanks

 

Hi, may I know if you were able to proceed with this or thought of any work around?

We finished to do a parser which parse the bank file into a csv so we can use bank feed from file, it work perfectly

Did you continue to ask BMO’s side to help on this or you didn’t need to? Can you provide additional guidance how to implement this? 

Hi ​@pauledpalina66 
We didn't need BMO to do anything custom on their side beyond enabling the SFTP delivery. Here's what we did:

1. Asked the bank to push us a daily transaction file via SFTP (direct feed, one file per day) in their standard format (in this case CDF3 )— no custom development on their end.
2. Wrote a custom parser that converts the bank's native file format (CDF3 XML for MasterCard) into a flat CSV.
3. Configured Acumatica's "Bank Feed from File" to pull that CSV via SFTP, with a CSV data provider that maps each column (BankAccountName, Transaction date, Amount, Description, Card number, MCC, etc.) to the corresponding Acumatica fields.
4. Amount Format is set to Debit/Credit in Same Column (positive = purchase, negative = payment/credit).
5. The parser runs in a Docker container that polls the SFTP IN/ folder every couple of minutes, drops the CSV in OUT/, archives the original, and emails on errors.

So the integration is entirely on our side — the bank just delivers their standard daily file to SFTP, and our parser + Bank Feed from File handles the rest. Works perfectly.

Hi , a couple of important things I forgot to mention:

    •    Files must be dropped on SFTP one at a time, with a small delay between them (a couple of seconds is enough). If multiple files land at the same time, Acumatica’s retrieve can behave unpredictably. Our pipeline writes them sequentially with a short pause, which avoids the issue entirely.
    •    We also had to customize Acumatica itself with a small graph extension to fix two issues with the stock Bank Feed behavior:
    •    Late-arriving transactions were silently dropped. Acumatica’s internal ImportStartDate climbs to the most recent transaction date already imported, and anything older that arrives in a later file gets skipped with no log or error. Our override bypasses the dynamic filter while keeping the static start date as a safety floor.
    •    No global deduplication across statements. Stock dedupe is scoped to the current statement only, so the same ExtTranID could be inserted into two different statements. We added a global check on CashAccountID + ExtTranID to prevent that.

Both done via a PXGraphExtension with [PXOverride]