BizTalk Server has had execellent support for SWIFT from its 2004 version. Most recent version of BizTalk’s Financial Accelerator for SWIFT (A4SWIFT 3.0) has additional support for SWIFT MX messages. Next version of BizTalk Server (2009) is coming up with enhanced support for SWIFT. Live date for MX and MT Standards Release 2008 is 15 Nov 2008. BizTalk Accelerator for SWIFT 2008 Message Pack: http://www.microsoft.com/do...

Financial Institutions and other business domains should leverage technology for their cost cutting. Most Financial Institutions have been very slow in upgrading themselves with new technologies. Obviously they cannot do frequent upgrades BUT all of them should regularly review their existing systems to identify areas where technology can help them in cost reduction. An example - One of big operation cost for any financial institution is in sending financial messages via proprietary networks like...

SWIFT decided to move to XML standards in year 1999. Since then, we have been hearing about MX standards (XML based). In all SWIFT presentations I have seen so far, I always hear about MX messages. SWIFT also maintains and releases MX standards every year. I always get a message that SWIFT will finally be moving everything to MX, but I never get a concrete end-date! Yes, we should not move to new technology/approach for the sake of changing! But here, I clearly see a case for moving towards XML based...

SWIFT (Society for Worldwide Interbank Financial Telecommunication) is one of widely accepted way to do financial transaction between financial institutions. It has over 8,300 banking organizations, securities institutions and corporate customers in more than 208 countries. If you look at the SWIFT evolution in the market they cover overall market in financial institutions; from securities to cash to treasury, etc. And all of these communities have one common problem – Integration Problem. They are...

One of common issues that I came across recently from some of BizTalk users are: Unable to see A4SWIFT properties in filter section. This is when you setup port properties from BizTalk explorer and BizTalk administration console. Unable to get to the configuration wizard after installation of A4SWIFT is over. After installation of A4SWIFT is over you get error messages like - "unable to deploy assemblies" or "some of the assemblies are already deployed and you need to redeploy A4SWIFT assemblies....

“BizTalk Accelerator for SWIFT” documentation has a detailed document which outlines the steps required to processes 1 SWIFT message per file. I am only adding few things we need to do to process multiple messages from a single file. The file may also contain messages of different types. SWIFT Disassembler Pipeline Component Properties : Set “Fragmentation” to TRUE Set “Inbound Debatching” to TRUE This set of property will create separate output files of one message per file i.e. input file with...

Looking for a tool for processing SWIFT messages for your existing solution? You must give a look at BizTalk and it's Financial Accelarator for SWIFT. You can work effortlessly with SWIFT messages by using BizTalk Server and BizTalk's Financial Accelerator for SWIFT. Best part is you don't need to know much about SWIFT messages. As expected from a Microsoft product it comes with great user friendly GUI. A4SWIFT provides you comprehensive Business Rules which helps you in validating SWIFT messages....

Microsoft have recently released the message pack for SWIFT 2006. You can get the SWIFT 2006 Message Pack for BizTalk Accelerator for SWIFT from - http://support.microsoft.co... Service Pack 1 is also released for A4SWIFT for both versions of 2.1 and 2.3. This service pack is a prerequisite for installing the 2006 Message Pack for BizTalk Server Accelerator for SWIFT. A4SWIFT 2.1 SP1 - http://support.microsoft.co... A4SWIFT 2.3 SP1 - http://support.microsoft.co...

I am using BizTalk Server 2006 and A4SWIFT 2.3 for processing SWIFT messages. My requirement is to process multiple SWIFT messages from 1 file. I know this can be done by enabling "Fragmentation" and "Inbound Debatching" properties of the "A4SWIFT DisAssembler" but I am not able to do this so far. I am missing something... I will post the details once I successfully complete it - it might be helpful for others. I was not able to find a single document/article which talks about it. Solution at - http://geekswithblogs.net/j...