Export compliance software
Export compliance software built for real transaction review, license control, and audit-ready workflows.
SecurePoint Trade gives export compliance teams a purpose-built operating workspace for transaction screening, analyst decisions, evidence packaging, export license lifecycle control, and integration-ready rollout.
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 does SecurePoint Trade do?
SecurePoint Trade helps aerospace, defense, and manufacturing exporters run export transaction screening, analyst review, evidence-oriented decisions, and export license drawdown control in one product. The current repo supports live transaction, evidence, audit, settings, and license workflows; controlled data delivery is in beta with internal secure-portal pickup, and external connectors are clearly labeled as roadmap rather than shipped capability.
- Replaces spreadsheet-plus-email review motion with a dedicated queue
- Tracks license usage against transactions and balances
- Keeps evidence and audit posture close to the decision record
The problem
Most export compliance teams are still stitching together decisions after the fact.
The friction is not just screening. It is the gap between intake, analyst review, license usage, approval pressure, and proof when someone asks what happened.
Disconnected workflows between ERP intake, analyst review, and final release decisions.
Spreadsheet-based license tracking that drifts away from shipment reality.
Weak shipment-to-license visibility when authorizations are managed outside the transaction workflow.
Audit stress caused by scattered rationale, evidence, and hand-built review packets.
SharePoint and email chaos for controlled technical data requests and delivery proof.
Core capabilities
A clear product structure for teams that need both workflow control and honest scope.
Trade is packaged around an operational core, a license add-on, a planned controlled-data workflow, and an implementation layer for enterprise rollout.
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
How it works
A buyer-friendly workflow that mirrors what compliance teams actually do.
Trade is designed around the movement from intake to screening to decision to proof, not around disconnected admin screens.
Ingest the transaction record
Bring export orders in through API intake, CSV mapping, or connector-driven feeds so the queue starts from real operational data.
Screen counterparties and route context
Trade screens counterparties, applies policy logic, and assembles a reviewable case instead of handing analysts a raw row dump.
Review, adjudicate, and escalate
Analysts work the queue, approvals move to the right people, and the product keeps the decision trail attached to the transaction.
Link evidence and release with proof
Evidence packs, audit records, and release rationale stay aligned so the team can explain what happened after the shipment moves.
Trade shows why a hit fired, so analysts spend time on the names that matter.
Every screening hit carries a transparent match breakdown instead of a single opaque flag. Analysts see a composite score alongside its phonetic, Jaro-Winkler, Levenshtein, and trigram components, so a near-exact sanctioned-party match and a loose fuzzy collision do not look identical in the queue.
- Composite match score with its phonetic, Jaro-Winkler, Levenshtein, and trigram components shown per hit
- Queue triage that surfaces stronger matches first instead of a flat, unranked alert list
- A per-transaction disposition rationale so a cleared or escalated decision carries its reasoning
- An append-only decision history so every adjudication stays defensible under audit
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
License Lifecycle turns authorizations into an operational control, not a side ledger.
The current repo includes a live license workspace with headers, lines, drawdowns, alerts, and transaction linkage. That lets teams see authorized quantity and value, remaining balance, threshold posture, and blocked overdraw attempts in context.
- Capture license headers and lines with operational context
- Record quantity and value drawdown against real transactions or shipment events
- Surface remaining balance, threshold posture, and expiration pressure
- Keep the trail reviewable for audit and internal compliance defense
Drawdown view
License balance without spreadsheet drift
DSP-5 line 01
Authorized qty 500
Used qty 420
Remaining 80
DSP-5 line 01
Authorized value $950k
Used value $742k
Remaining $208k
Alert posture
80% threshold crossed
Expiration watch active
Overdraw blocked
Linked transaction
Shipment-to-license traceability
Thresholds
80/90/95/100 posture visibility
Audit support
Context preserved on each drawdown
Create the authorization structure
Capture license headers, lines, values, quantities, and supporting context instead of keeping the authorization in a spreadsheet.
Link transactions and shipments
Associate the right transaction to the right line so usage is tied to the operational event that consumed the authorization.
Record drawdown with controls
Track quantity and value drawdown, preserve event context, and block overdraw attempts before the ledger drifts away from reality.
Monitor balances and alerts
Expose remaining authorization, threshold posture, and expiration pressure so the team can act before a shipment creates a problem.
Controlled Data Delivery governs technical-data release with internal secure-portal pickup today.
The current repo runs the request, approval, sealed-package, and audit-ready proof workflow as a beta module we enable per tenant. Internal secure-portal pickup is live; external connectors (SharePoint, SFTP, Cryptshare, FAA SharePoint) are proof-contract stubs in the repo and labeled as roadmap rather than live byte transport.
- Request and recipient capture before a file leaves the team
- Classification and export-check gates before approval
- Sealed packages with artifact upload to a private storage bucket
- Internal secure-portal pickup proof live today; external connectors on the roadmap
V1 workflow
Replace file-share guesswork with a governed release chain
Request
What data, for whom, and why
Check
Classification and recipient review
Approve
Compliance and legal release path
Deliver
Package, handoff, and proof
Request
Capture what data is being requested, by whom, and for which program or transaction context.
Classify and check
Evaluate export-control posture, recipient eligibility, and data readiness before a file ever leaves the team.
Approve
Route the release through the right legal, compliance, or program approvers with a documented rationale.
Package, deliver, prove
Assemble the delivery package, log the handoff, and retain proof that the controlled release followed the approved path.
Who it is for
Trade is aimed at serious export programs, not generic SaaS ops.
The strongest fit is where export review, authorization control, and evidence pressure meet daily operational volume.
Why Trade
Workflow clarity, auditability, and practical operating discipline.
The product story is strongest when it stays grounded: a queue-first screening workflow, evidence-ready decision support, a live license module, and careful rollout language for what is next.
Built around actual export transaction review rather than a generic CRM-style lead funnel.
Keeps screening, analyst decisions, evidence, and audit posture in the same operating record.
Introduces license lifecycle control without pretending to be a full global trade suite overnight.
Labels Controlled Data Delivery honestly: internal secure-portal pickup live as beta, external connectors on the roadmap.
FAQ
Direct answers for buyers, SEO, and answer engines.
These are the questions serious compliance teams ask before they trust a new workflow with their transaction and authorization record.
SecurePoint Trade is a trade compliance workspace for export transaction screening, analyst review, export license control, evidence packaging, and audit-ready operational records.
Trade is built for teams that currently stitch together spreadsheets, email, ERP exports, and manual approval trails. It centralizes the transaction queue, evidence trail, and license control workflow in one workspace.
Yes. This repo includes a live license workspace with license headers and lines, quantity and value drawdown, transaction linkage, balance visibility, alerts, and overdraw-blocking controls.
Trade records drawdown events against license lines, updates remaining balances, preserves context for the event, and surfaces threshold or overdraw risk inside the workflow.
It is available as a beta module that we enable per tenant rather than turning on by default. CDD is secure-portal only today — internal secure-portal pickup, sealed packaging, and the audit-ready proof trail are live. SharePoint, Cryptshare, FAA SharePoint, and SFTP are not shipped and are refused at dispatch in customer tenants (the server raises a not-shipped error rather than producing a synthetic delivery proof).
Trade screens against OFAC SDN, BIS Entity, and UN consolidated lists today. DDTC Debarred, EU consolidated, and UK consolidated lists are roadmap and should not be assumed in current customer screening coverage.
No. DDTC publishes no DECCS submission API and BIS publishes no SNAP-R submission API. Trade prepares a structured JSON packet (not a PDF) that an Empowered Official uploads manually at the regulator portal. Trade logs the manual submission reference and any regulator-issued case ID; it does not file on the operator's behalf.
No. The repo positions Trade as a focused compliance operating workspace for transaction review, evidence, and license control, not as a claim to replace every export-management suite capability.
Next step
See the module structure and start the Trade evaluation path.
Use the public pages to understand the workflow, then move into SecurePoint sign-in for scoped evaluation and live workspace access.