Modules
Trade is organized around a credible compliance operating model, not a pile of feature claims.
The module structure is simple: Trade Core runs the screening and analyst workflow, Export License Lifecycle adds authorization control, Controlled Data Delivery is in beta with internal secure-portal pickup live, and Enterprise Connect handles rollout and integration complexity.
Trade Core flow
Export review built around the queue
Transaction queue
ERP/API intake staged for analyst review
Policy signal
Counterparty and routing context surfaced early
Evidence
Decision trail held with the case
Direct answer
What modules are in SecurePoint Trade?
SecurePoint Trade is marketed here as four clear layers: Trade Core for transaction review, Export License Lifecycle for authorization management, Controlled Data Delivery as planned direction, and Enterprise Connect for implementation and rollout. The copy stays aligned to repo evidence so buyers can tell what is live now versus what is still ahead.
- Clear status labeling by module
- Internal links between the core pages
- Built to support future solution and comparison content
Module overview
A single page buyers can scan fast.
This page is designed for quick comparison, direct-answer extraction, and future expansion into deeper solution or industry pages.
Transaction screening, analyst workflow, policy controls, evidence generation, and an audit-ready operating record.
Grounded in repo routes for transactions, approvals, evidence, policies, audit, import, analytics, jobs, and settings.
- API, CSV, and SFTP-oriented intake posture with analyst review queues (production ERP adapters are scoped per engagement)
- Restricted-party screening against OFAC SDN, BIS Entity, and UN consolidated today (DDTC Debarred, EU consolidated, and UK consolidated are roadmap)
- Evidence packs, approvals, and an append-only audit trail at the database level
- Connector and API-key control plane for managed rollout
License headers and lines, quantity and value drawdown, transaction linkage, alerts, and balance visibility.
Grounded in live license routes, drawdown services, transaction-link actions, alerting flows, and license UI components.
- Header and line-level authorizations with linked transactions
- Quantity and value drawdown tracking with remaining-balance visibility
- Threshold, expiration, and overdraw-blocked alerting inside the product
- Append-only drawdown ledger and audit support for defensible review
A workflow for controlled technical data requests, approval, packaging, and sealed-package delivery via internal secure-portal pickup, with an audit-ready proof trail. CDD is secure_portal only today; SharePoint, Cryptshare, FAA SharePoint, and SFTP are not shipped and are refused at dispatch.
Grounded in live delivery request/approval/package/dispatch/evidence routes, sealed-package state guards, and the secure-portal internal-pickup proof path. SharePoint, Cryptshare, FAA SharePoint, and SFTP connectors are proof-contract stubs that the server refuses outside an internal-development environment (no synthetic delivery proof is produced).
- Request, recipient, and legal-check capture before any release
- Classification and export-control gates before approval
- Sealed packages with artifact upload to a private storage bucket
- Secure-portal internal pickup is the only shipping delivery method today; external connectors (SharePoint, Cryptshare, FAA SharePoint, SFTP) are roadmap and server-gated off in customer tenants
Implementation and rollout support for upstream systems, sample CSV field mappings, and controlled enterprise deployment. Not an installed ERP adapter today.
Current repo evidence supports API keys, connector management, and a sample Oracle EBS CSV field mapping for demo data. Broader SAP, SharePoint, secure exchange, and custom ERP rollout are positioned carefully as rollout-engagement scope — no production ERP adapter ships in the current repo.
- Connector and API-key management for controlled integration access
- Sample CSV field mappings for Oracle EBS imports (demo data only — no production ERP adapter ships today)
- API intake and staged-deployment posture; production ERP adapters are scoped per engagement
- SAP, SharePoint, secure exchange, and custom rollout framed as scoped implementation work
Comparison
What each module does, how it is positioned, and why the status matters.
The goal is to remove guesswork for buyers evaluating rollout sequence, near-term fit, and roadmap alignment.
| Module | Status | What it does | How it is grounded |
|---|---|---|---|
| Trade Core | Available now | Transaction screening, analyst workflow, policy controls, evidence generation, and an audit-ready operating record. | Grounded in repo routes for transactions, approvals, evidence, policies, audit, import, analytics, jobs, and settings. |
| Export License Lifecycle | Available now | License headers and lines, quantity and value drawdown, transaction linkage, alerts, and balance visibility. | Grounded in live license routes, drawdown services, transaction-link actions, alerting flows, and license UI components. |
| Controlled Data Delivery | Beta | A workflow for controlled technical data requests, approval, packaging, and sealed-package delivery via internal secure-portal pickup, with an audit-ready proof trail. CDD is secure_portal only today; SharePoint, Cryptshare, FAA SharePoint, and SFTP are not shipped and are refused at dispatch. | Grounded in live delivery request/approval/package/dispatch/evidence routes, sealed-package state guards, and the secure-portal internal-pickup proof path. SharePoint, Cryptshare, FAA SharePoint, and SFTP connectors are proof-contract stubs that the server refuses outside an internal-development environment (no synthetic delivery proof is produced). |
| Enterprise Connect | Implementation layer | Implementation and rollout support for upstream systems, sample CSV field mappings, and controlled enterprise deployment. Not an installed ERP adapter today. | Current repo evidence supports API keys, connector management, and a sample Oracle EBS CSV field mapping for demo data. Broader SAP, SharePoint, secure exchange, and custom ERP rollout are positioned carefully as rollout-engagement scope — no production ERP adapter ships in the current repo. |
Next step
Start with the module that matches your current pain.
If the pain is review backlog, start with Trade Core. If it is authorization drift, go deeper on License Lifecycle. If it is controlled technical data release, evaluate the beta delivery workflow with the caveat that internal secure-portal pickup is live and external connectors are roadmap.