Eligibility & Governance

Partner participation is controlled by documented threshold criteria, compliance controls, and formal governance approval cycles.

Minimum annual submission volume

Partner must evidence projected and historical throughput at or above 1,000 submissions per year across supported routes.

Control reference: EG-001

Multi-country footprint / corporate presence

Partner must maintain documented operating presence across multiple jurisdictions with centralized governance ownership.

Control reference: EG-002

Compliance capability

Partner must demonstrate operational compliance controls, escalation pathways, and named compliance accountability.

Control reference: EG-003

Dedicated account governance

Named account owner, backup owner, and governance liaison are required for all active partner records.

Control reference: EG-004

Audit requirements

Partner must maintain auditable document trails, change records, and retention controls aligned to program requirements.

Control reference: EG-005

References required

Program references and corporate verification records are required prior to any operational access consideration.

Control reference: EG-006

Partner Tier Matrix

Tier Annual Throughput Baseline Governance Requirement Operational Notes
Tier 1 5000+ submissions/year Enhanced governance review with quarterly audit touchpoints Eligible for high-throughput coordination windows
Tier 2 1000-4999 submissions/year Standard governance review with semi-annual controls Eligible for standard program window allocation
Tier 3 Below threshold Not eligible for current onboarding consideration May re-apply with updated evidence set

Policy references

  • Internal program governance standard
  • Compliance capability and controls checklist
  • Audit trail retention protocol
  • Account ownership and escalation rulebook

Scope & limitations

  • Threshold criteria are mandatory for consideration
  • Eligibility does not guarantee onboarding approval
  • Program participation is reviewed periodically
  • Control exceptions require governance sign-off