Why Truugo?

Electronic data interchange (EDI) helps to speed up business processes, but data quality issues and inefficient deployment processes cause surprisingly high costs. Truugo helps organizations to minimize these issues by providing a platform for detailed message validation.

If electronic data contains an error, it will usually have more severe consequences than having an error in traditional paper / fax based data interchange. Thus electronic data must be error-free to gain real benefits from automated processes. High quality data is reached only via detailed and systematic testing.

Constant need for message validation

Detailed validation is needed everywhere and all the time.

  • Validation is required to ensure that messages conform to receiver's requirements in deployments (supplier/customer onboarding).
  • When system updates are being made, one must check that messages are still valid.
  • Fast and accurate error detection and reporting is vital for production environment to minimize risks.
  • Help desk must react on a number of data quality issues on a daily basis.

Problems in traditional test process

Old test process

Traditionally validation process requires resources from both parties when validation and reporting are performed bilaterally based on a common schedule. A delay between a test and a feedback might stretch into days when a total time might sum up to weeks in challenging deployments requiring many iterations. Iterative and manual tasks consume a lot of resources. Thereby quite a high volume is required to justify a new EDI connection. Bilateral and partly manual testing process is also a significant challenge for a test reporting especially when there are more than one person responsible for the reporting. Same error might be reported in various ways depending on a day and a person in duty.

General XML editors (XML Spy, Stylus Studio, oXygen) help to identify structural errors by providing schema validation based on W3C XML schema. Using XML validator is a good start, but schema validation doesn't cover content validation. In addition, schema validation generates very technical (even cryptic) error descriptions, requiring special knowledge for interpretation.

Even though an XML document is well-formed and valid against a message schema (DTD or W3C XML Schema) it doesn't imply, that its content is valid. The wider the message scope the less significant is the schema validation. In other words, a message which passes schema validation might lack all data required by a message receiver. This is usually the case when a message is based on a international message format which covers a wide variety of use cases.

General test tool are poor at locating errors concerning message content and data relationships. These errors are challenging to locate manually, even for a professional. It's also a waste of resources and a significant risk to overload the most valuable resources with an uninspiring task.


New test process

Truugo is 24/7 message validation platform for detailed message validation. Tests can be performed at own pace and system provides instant feedback on errors. A formalized procedure harmonizes test reporting and makes it possible to automate the task.


Tests can be performed as a self-service which adds flexibility and diminishes unnecessary bilateral interaction. A calendar time spend on testing will decrease drastically especially in challenging iterative cases where an instant feedback mechanism enables validation and error correction at once. Data quality will increase when also infrequent errors are located by running more tests, without additional costs.

See overview of Truugo benefits.

Next article: Subset Editor - create validator and documentation at once