The Relationship Management Application component of BOX for SWIFTNet (BOX RMA) has been certified by SWIFT for SWIFTNet 6.0 to 6.3. SWIFT have now successfully tested  BOX RMA for compliance with SWIFTNet 7.0 (See:  SWIFTNet 7.0 backward compatibility tests results).

With the advent of SWIFTNet Phase 2, Intercope incorporated the RMA component as part of the BOX product, and was the first vendor to receive SWIFT certification for this application. Since that time the application has been continuously enhanced and future versions will include RMA functionality for FileAct and InterAct for SWIFTNet 7.

Today BOX RMA is used by 23 customers in several countries including service provides who use the application on behalf of many financial institutions.

BOX RMA provides rich application functionality extending the scope of SWIFT mandatory features including functions such as an easy handling of multiple authorizations in one step, an RMA permission check by a SOA service and a MERVA interface and real-time updates for external CBT datastores. With the BOX CBT version available in Q4 2010, RMA handling is further streamlined as the CBT BOX component can directly access the BOX RMA datastore avoiding delays and the complexity of synchronization mechanisms.

Box for SWIFTNet (BOX) was been designed right from the very beginning as a high volume system. Throughout its life development have continuously enhanced BOX to enable it to handle higher and higher message volumes. As a result of these efforts latest benchmark tests in the Intercope lab showed a transaction rate of 58.5 transactions per second (or over 210,000 transactions per hour).

This latest performance measurement has been achieved using a QuadCore 32 bit Linux System. 10,000 messages were downloaded from the SWIFT TANK file and fed into the system via MQ. These messages were processed using the standard BOX FIN workflow and transmitted via FMT (Financial Message Transfer). The generated ACK/NAK confirmations where routed to a backend application via MQ, to a printer or a BOX queue for manual intervention as determined by the workflow.

In parallel, for each SWIFT input message, a SWIFT output message was generated, received and routed to a backend application via MQ. In 342 seconds 10.000 SWIFT input messages and ACK/NAK confirmations and 10.000 SWIFT output messages were processed which corresponds to a throughput of some 200,000 message per hour.