License applications

Admin sessionDEMO

Demo workspaceData, downloads, and workflow events are simulated for evaluation.

Compliance

New license application

Capture a new application header and the applicant party. Items, additional parties, and supporting documents can be added on the detail page before EO approval.

Header

Application type*

Regulator*

Applicant display name*

Destination country (2-letter)

Summary value (USD)

Validity window (months)

Regulator account label

Optional — operator note pairing this application with a portal account.

Notes

Submission context

How this packet will be submitted to the regulator. Typed regulator IDs (DECCS case, BIS ACN, portal work item) and portal-status fields are populated by the EO after submission, on the detail page.

Submission party type

First-party: the registered exporter submits. Third-party: a Trusted Third Party files on the exporter's behalf under a written Power of Attorney via the regulator's web UI. We never store POA artefacts as credentials — attach them as documents on the application.

Submitter contact name

Submitter email

Submitter phone

Your Empowered Official will need their ECA digital certificate on their filing machine to submit through DECCS. We never store the certificate. The EO attests its presence at approval time.

Applicant party

The applicant party is required at create time. Additional parties (consignees, end users) can be added on the application detail page.

Legal name*

Country (2-letter)*

Address (single block)