These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Trade Compliance
- Implementation and migration
How a Trade Compliance rollout works
Start with one entity, period and export case that reviewers can reconcile.
Agree the boundary
Name the organization, business unit, counterparty and official screening and license sources for the pilot.
Map the records
Import people, risks and controls before assessments, tests and export reviews. Preserve source identifiers and revisions.
Configure a bounded pilot
Use one assessment period, a representative control test and an export review with its destination and license reference.
Rehearse exceptions
Record a failed test, action, independent retest, returned review and receipt needing review.
Reconcile and release
Compare the linked records and source evidence with the team's original case, then obtain the authorized review decision.
What the customer provides
- Organization and business unit identifiers, team members and access scope.
- Assessment periods, control codes, risk scoring scale and known open findings.
- Approved evidence sources for counterparty screening and license decisions.
- One ordinary export case and one exception with supporting documents.
Changing it afterwards
Review a changed control, member assignment or source mapping with its owner. Replay the exception cases against the changed configuration. Keep earlier decisions tied to their original revision and reason; use a new review when the underlying evidence changes.
Set up Trade Compliance your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.