SWIFT Printing

SWIFT printing – an obsolete technique?

When, as a system architect, you design a SWIFT solution you will think about many aspects of the solution like application integration, XML capabilities, routing facilities, performance and availability, but SWIFT printing functions will probably not even enter your mind. Financial messaging is a typical example of highly automated computer based handling of business information but it is also an area where human intervention is still required and specialized graphical user interfaces are provided as an integral component of these digital information systems. Given all of the above SWIFT printing might look like an obsolete technique from former ages without any relevance for state of the art processing of highly structured data.

Users see SWIFT printing different

Take care! Users of your system will often see things very differently. Obviously people tend to have a persistent affinity towards paper based information processing, and you may feel deeply disappointed if your highly sophisticated solution design is not accepted simply because you forgot to provide SWIFT printing functions. Nicely formatted printouts of SWIFT messages with the header in the right place, neatly formatted columns and detailed explanations of fieldnames.

Routing criteria for SWIFT printing

Of course the users also want to be able to use such SWIFT printing functions whenever they think they are required. But that’s not all of it by far. You also should provide facilities for automatic SWIFT printing options depending on routing criteria and on devices in configurable locations. And don’t forget about the two departments sharing the same printer but hating to mix up their printouts. So if you don’t want to start an argument with them, provide options to start automatic SWIFT printing for department A at 10.00 am and for department B after their lunchtime.

Meeting all requirements for SWIFT printing

Intercope has outstanding long-term experience in understanding and implementing both technical and user requirements of SWIFT solutions starting with telex and testkey systems some 25 years ago, followed by MERVA deployment and consultancy over many years and more recently the development of the latest generation of SWIFTNet interfaces. For more details check out how your requirements for a SWIFT solution are met with Box for SWIFTNet including sophisticated SWIFT printing functions.