1. Trade Compliance
  2. Who it's for
  3. Global service groups
Who it's for

Global service groups

A group with several business units can score trade risks by unit and assign controls to named team members. Assessments have their own period and counterparty. The same reviewer can compare findings and action evidence across those records without flattening separate entity responsibilities.

How Trade Compliance is set up for you

Scope each case

Record the organization, counterparty and period on the assessment before testing.

Keep control context

Link scored risks to controls, then tests to the control actually examined.

Preserve the decision

Keep reviewer reason, revision and supporting evidence connected.

A group with several business units can score trade risks by unit and assign controls to named team members. Assessments have their own period and counterparty. The same reviewer can compare findings and action evidence across those records without flattening separate entity responsibilities.

Choose one business unit and one period first. Import organizations and team members, map risks and controls, and run a bounded assessment. Review a failed test, corrective action and retest before opening more entities. Define who can see shared evidence and who remains responsible for each action.

The pilot should include an ordinary case and an exception. For the exception, ask the Control Owner to show the failed result and its evidence reference. Give the action owner a due date, then have a separate reviewer inspect the retest. For the export case, use a destination and a license reference that the reviewer can reconcile with the organization's designated source. A status alone is not enough to explain either decision.

Agree the handoff before adding more teams: who maintains counterparty data, who owns controls, who supplies official determination evidence and who records the final decision. Reconcile the authorized attachment visibility with those assignments. When a reviewer returns a record, its owner needs to see the reason and the exact revision that was examined.

[Plan the first cycle](/trade-compliance/implementation) and [inspect the records](/trade-compliance/data-model).

Features to start with

Roles on the team

Independent Assurance Reviewer
Review eligible revisions independently and reconcile operational evidence.
Auditor
Read authorized evidence and reports.
Control Owner
Prepare assigned operational records and execute eligible reviewed actions.
App Administrator
Maintain organization configuration and membership.

Set up Trade Compliance your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started