Every TN document type is associated with a verification service. The wm.tn.doc:getEvents service looks up the appropriate verification service and executes it against the supplied document. The service attaches all resulting verification errors to the document and logs them to the activity log in the Trading Networks database (if the document is saved to the database). To retrieve the verification errors from the activity log, use wm.tn.doc:getEvents.

The XML verification service uses the Signature and SignedBody queries to extract those portions of the document. The signature is extracted and base-64 decoded. The signed body is extracted and converted to bytes in the UTF8 encoding. The resulting byte data must have been signed with the extracted signature. Additionally, the digital certificate used to sign the byte data must be the same as the one in the profile for the document's sender. If all of these conditions are met, verification succeeds.

If flags is non-null, the service uses the verify? flag to determine whether to verify the digital signature of the document. For the format of flags, see wm.tn.rec:PreProcessingFlags.