Screening, ISF, and VGM run against the NetSuite record itself
Denied party screening, ISF filings, SOLAS VGM, and customs compliance applied to the order and its parties, so a compliance hold stops the fulfillment instead of surfacing after it ships.
Compliance usually sits beside the ERP rather than inside it. Screening runs as a batch somewhere, filings happen in a broker's portal, and the ERP finds out when something is already on a vessel. Freightgate's NetSuite TMS integration runs these checks against the sales order, purchase order, and item fulfillment records directly, which means a failed check is an exception in the workflow rather than a discovery.
A compliance check that runs after the order ships is an audit finding.
Screening against restricted party lists happens on a schedule rather than on the transaction. An ISF filing is somebody's calendar reminder. VGM gets submitted by whoever remembered. None of these are in the fulfillment path, so none of them can actually stop anything.
When one of them fails, the cost is not the filing. It is the container, the penalty, and the explanation.
Compliance in the workflow, not beside it.
Denied party screening on the order
Order parties are screened against restricted party lists at the point the transaction is created and when it changes, not on a nightly batch.
ISF filings from order data
Importer Security Filing is produced from the data already on the NetSuite record rather than rekeyed into a separate portal.
SOLAS VGM on the fulfillment
Verified gross mass is captured and submitted against the shipment record, as part of the fulfillment rather than after it.
Customs compliance against the item
Classification and customs requirements are applied against the item record, so the obligation travels with the product rather than living in somebody's knowledge.
A hold that actually holds
A failed check creates an exception against the NetSuite record and stops the fulfillment. This is the difference between a compliance report and compliance control.
Checked before it moves.
Order created or changed
Parties and item data read from the NetSuite record.
Checks run against the record
Screening, classification, and filing requirements evaluated.
Clear or hold
A pass continues the workflow, a failure raises an exception on the order.
Filings produced
ISF, VGM, and customs documentation generated from the same data. On an ocean move, the VGM cut-off is tracked against the sailing the order was booked on.
“The seamless integration into NetSuite makes compliance a no-brainer.” Ascensia
What NetSuite teams ask first.
Does Freightgate do denied party screening inside NetSuite?
Yes. Order parties are screened against restricted party lists at the transaction level, against the NetSuite record rather than in a separate system.
Which compliance functions are covered?
Denied party screening, ISF filings, SOLAS VGM, and customs compliance.
When does screening run?
When the order is created and when it changes, rather than on a scheduled batch.
What happens when a check fails?
An exception is raised against the NetSuite record and the fulfillment is held, so the shipment does not proceed on a failed check.
Do we still need a customs broker?
Typically yes. Freightgate produces the filings and governs the checks from your order data. It does not replace your broker relationship.
Is compliance a separate module or part of the integration?
It runs against the same records as the rest of the SuiteApp. Compliance being embedded in the workflow rather than bolted alongside it is the point. The same record also carries the landed cost applied at PO creation.
Is this a validated SuiteApp?
Yes. Freightgate is a Built for NetSuite validated hybrid SuiteApp.
Pairs well with
See a hold fire on your own order.
Bring one order and one party list. We will show you the check running against the NetSuite record and the exception stopping the fulfillment.