MercuryGate adds Integration Point denied party tool

The global trade management software provider’s denied-party screening tool will complement MercuryGate’s import and export generation and Automated Export System and Importer Security Filing capabilities, the company said in a statement Tuesday.    The on-demand transportation management software provider MercuryGate has established an agreement with cloud-based global trade management software provider Integration Point that will allow MercuryGate users to access Integration Point’s denied party screening tool, MercuryGate said in a statement Tuesday.
   “There are many benefits to integrating GTM capabilities with TMS systems,” Tom Barnes, CEO of Integration Point, said in a statement. “GTM and TMS enables organizations to optimize, automate, and monitor cross-border transactions in ways that were not available traditionally from TMS providers.”
   MercuryGate’s system allows shippers and 3PLs to manage transportation and documentation related to international shipments, including the capability to directly file electronic export information (EEI) via the Automated Export System (AES) and submit Importer Security Filings (ISF) to comply with U.S. Customs and Border Protection’s 10+2 regulations. The system’s template management tool allows customers to generate all necessary import and export documents.
   Integration Point has had a longstanding partnership with GT Nexus, another provider of global transportation management tools, that integrates GTM tools directly into its platform.
   Other software providers in the space, like Amber Road, BluJay Solutions, Descartes, Oracle, and SAP, provide integrated transportation and trade management tools.
   “We work with numerous global customers to manage the complexity of their supply chains and as a result recognize the increasing challenges often encountered with compliance, especially in today’s ever-changing global trade environment,” said Monica Wooden, CEO and Co-founder, MercuryGate.

Correction: A previous version of the headline for this article mistakenly referred to MercuryGate as “Mercury.”