A basic business requirement exists to translate and match appropriate information between disparate protocols, information systems, payment mechanisms and trading partners.

Stark Consulting Group and our partners have developed a set of resources to promote electronic payment throughout large companies for cost savings and process efficiencies.  We have specialized in data analysis and mapping to collapse implementation timeframes and have obtained a patent on our SCG Analysis and Reporting Tool^©.  We, along with our clients, have utilized our  patented, proprietary file transformation tool many times to convert data from one input file type to another (output) file type. Here’s an example of work we’ve done.

A major bank wanted to provide services for an end client in northern Europe.  The client had its own proprietary file format, nonstandard, and wanted to make sure that all of the information in their file could be carried and reported in a major payment network’s standard file format.

Initially, the client sent a paper specification describing the structure of their file to the mapping support team.  This specification was only a few pages.  Typically, file format information is received by way of a paper specification ranging in size from a page or two to a stack of paper an inch thick.

The first thing the mapping team does is to create an electronic version of the proprietary file (the “input file”) into its electronic database.  In this instance, the electronic version of the target file, the network’s standard file, is also located in the electronic database.

Through use of a point-and-click graphic interface, a mapping report is created which shows the coding team exactly how to handle each element in the input file to convert it into the appropriate target file data element. 

Down the left hand side of the report page are the input file fields, along with their format.  To the right of the page are listed the target fields, along with any information about how to transform the input field into the output field.  Using this data map, the developers were able to accept the nonstandard file and to transform it into the standard file format so the customer could utilize the standard reporting tools.

Let us show you how we can make your mapping challenges go away!

BACK