Skip to main content

Agentic AI Design Patterns for Enterprise Compliance

A Practitioner's Guide to Building Autonomous Compliance Agents with Confidence Scoring, Source Traceability, and Human-in-the-Loop Controls

Full Article with Interactive Diagrams

For the complete article with rich SVG architecture diagrams and enhanced formatting, view the full interactive version.

"The most effective compliance agents aren't black boxesβ€”they're transparent systems that explain why they made each decision, cite their sources, and know when to defer to human judgment."


Overview​

Enterprise compliance is evolving. Organizations are moving from manual, reactive processes to intelligent, autonomous systems that can screen vendors in milliseconds, identify regulatory requirements instantly, and make decisions with confidenceβ€”all while maintaining complete audit trails.

This guide explores how to build agentic AI systems for compliance that leverage two critical capabilities:

  1. Confidence Scoring - Quantified match quality enabling graduated responses
  2. Source Traceability - Citations linking to authoritative documents

These features form the foundation of what we call the Evidence Frameworkβ€”the mechanism that enables AI agents to work autonomously while maintaining the transparency and accountability that regulated industries require.


Architecture: Orchestrator-SubAgent Pattern​

The core architecture pattern uses an Orchestrator Agent that coordinates specialized sub-agents executing in parallel:

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Business Event Trigger β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
β”‚
β–Ό
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Orchestrator Agent β”‚
β”‚ Coordinates sub-agents β€’ Applies decision logic β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
β”‚
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β–Ό β–Ό
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ WHO Sub-Agent β”‚ β”‚ WHAT Sub-Agent β”‚
β”‚ Entity Screening β”‚ β”‚ Regulatory Query β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
β”‚ β”‚
β–Ό β–Ό
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Sanctions API β”‚ β”‚ Regulatory API β”‚
β”‚ OFAC β€’ BIS β€’ UN β”‚ β”‚ FDA β€’ ICH β€’ EMA β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
β”‚ β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
β–Ό
Returns: Confidence Scores + Source Citations
β”‚
β–Ό
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Threshold Evaluation β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
β”‚
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β–Ό β–Ό β–Ό
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ < 0.5 β”‚ β”‚ 0.5 - 0.85 β”‚ β”‚ > 0.85 β”‚
β”‚ Auto-Approve β”‚ β”‚ Analyst Reviewβ”‚ β”‚ Auto-Reject β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Key Architecture Principles​

  • Orchestrator-SubAgent Pattern: The main agent coordinates specialized sub-agents (WHO checks, WHAT checks) that execute in parallel
  • API-First Intelligence: Sub-agents call purpose-built compliance APIs rather than relying on general LLM knowledgeβ€”ensuring accuracy and auditability
  • Evidence-Based Decisions: APIs return confidence scores and source citations that the orchestrator uses for threshold-based routing
  • Graduated Autonomy: Low-confidence cases auto-approve; high-confidence matches auto-reject; the "gray zone" routes to humans
  • Feedback Loop: Human decisions feed back into the system, enabling threshold tuning and progressive autonomy over time

Use Case 1: Pharmaceutical Supply Chain Vendor Qualification​

Consider a pharmaceutical company qualifying a new Contract Manufacturing Organization (CMO). This scenario requires answering two fundamental compliance questions:

  • WHO can we work with? β€” Are the company and its key personnel on any sanctions lists?
  • WHAT regulations apply? β€” What cGMP, ICH, and country-specific requirements must the vendor meet?

The Problem: Manual Vendor Qualification​

Pain PointImpact
Total Time per Vendor8-18 hours over 3-5 days
Name Variation Coverage~60% (exact match only)
Regulatory CurrencyUnknownβ€”depends on analyst's last search
Audit Trail QualityInconsistentβ€”screenshots in email folders
ScalabilityLinearβ€”each vendor requires full analyst time

The Agentic AI Solution​

An agentic AI approach transforms this fragmented process into a unified, automated pipeline:

  1. Automated Entity Extraction (Instant) - Agent triggers on vendor creation, extracts all entity data programmatically
  2. Parallel Compliance Screening (under 100ms) - Single API call screens company + all personnel against all sanctions lists
  3. Semantic Regulatory Query (under 500ms) - Natural language query retrieves applicable regulations with source citations
  4. Automated Checklist Generation (Instant) - Agent compiles qualification checklist from regulatory results
  5. ERP Update with Full Audit Trail (Instant) - Agent writes qualification record with complete audit trail

Productivity Impact​

MetricManual ProcessAgentic AIImprovement
Time per Vendor8-18 hoursUnder 2 minutes99% reduction
Name Variation Coverage~60%95%++35 percentage points
Regulatory Data CurrencyUnknownDaily syncAlways current
Audit Trail Completeness~40%100%Full traceability
Analyst Capacity2-3 vendors/dayUnlimited (API-bound)10x+ throughput

Potential ROI Example​

A pharmaceutical company qualifying 50 new vendors per month could potentially achieve:

  • Potential Time Savings: 50 vendors Γ— 10 hours = up to 500 analyst hours/month
  • Potential Cost Impact: Based on 500 hours at ~$75/hour = up to $37,500/month
  • Risk Reduction: Improved sanctions coverage through fuzzy matching
  • Compliance Confidence: Comprehensive audit trail = examination-ready

Note: Actual results depend on current process efficiency, vendor volume, complexity of screenings, and organizational implementation.


Use Case 2: Financial Services Customer Onboarding​

A fintech payment processor needs real-time sanctions screening during merchant onboarding to meet BSA/AML requirements.

The Problem: Manual KYC Onboarding​

Pain PointImpact
Time to Onboard (Clear Cases)24-48 hours even when no issues
Analyst Utilization80% of time on clear cases that could be automated
False Positive HandlingNo scoringβ€”common names always flagged
Workflow Adaptability2-4 weeks to implement rule changes

The Agentic AI Solution​

Confidence ScoreStatusAgent ActionHuman Involvement
0.00 - 0.50CLEARAuto-approve, proceed to next stepNone required
0.50 - 0.70REVIEWQueue for analyst with pre-populated caseAnalyst review within 24h
0.70 - 0.85POTENTIAL MATCHHold application, create high-priority caseSenior analyst required
0.85 - 1.00MATCHAuto-reject, notify BSA OfficerBSA Officer notification

Productivity Impact​

MetricManual ProcessAgentic AIImprovement
Time to Approve (Clear)24-48 hoursUnder 5 seconds99.9% reduction
Analyst Time per App15-30 minutes (all)0 minutes (auto-approved)100% for 70-80% of volume
False Positive Rate15-25%Under 5%70-80% reduction
Rule Change Deployment2-4 weeksMinutes to hours100x faster

The Evidence Framework​

What makes compliance agents trustworthy is that every recommendation comes with evidence.

1. Confidence Scores​

When the SanctionsWise API returns a potential match, it includes a confidence score between 0 and 1:

{
"entity": "Viktor A. Petrov",
"status": "potential_match",
"matches": [
{
"matched_name": "PETROV, Viktor Anatolyevich",
"list": "OFAC SDN",
"confidence": 0.89,
"programs": ["RUSSIA-EO14024", "UKRAINE-EO13661"]
}
],
"screening_id": "scr_7f8a9b2c3d4e5f6g"
}

This confidence score enables graduated responses:

  • Not a binary match/no-match
  • Agent can auto-approve low-risk, escalate uncertain cases
  • Human reviewers see exactly why something was flagged

2. Source Citations​

Every regulatory recommendation links to authoritative documents:

{
"query": "CMO qualification requirements for API manufacturing",
"results": [
{
"title": "ICH Q7: Good Manufacturing Practice Guide for APIs",
"similarity": 0.84,
"section": "Section 2 - Quality Management",
"source_url": "https://www.ich.org/page/quality-guidelines"
}
]
}

This enables:

  • Verification - Reviewers can check recommendations against primary sources
  • Audit trails - Satisfy regulatory examination requirements
  • Training - New team members learn from cited documents

Progressive Autonomy: Tuning Thresholds​

Organizations can start with conservative thresholds, then gradually increase agent autonomy:

Phase 1: Conservative (Months 1-3)​

{
"auto_approve_threshold": 0.40,
"review_threshold": 0.40,
"escalate_threshold": 0.70,
"auto_reject_threshold": 0.95
}

Phase 2: Balanced (Months 4-6)​

{
"auto_approve_threshold": 0.50,
"review_threshold": 0.50,
"escalate_threshold": 0.75,
"auto_reject_threshold": 0.90
}

Phase 3: Optimized (Months 7+)​

{
"auto_approve_threshold": 0.55,
"review_threshold": 0.55,
"escalate_threshold": 0.70,
"auto_reject_threshold": 0.85
}

Key Metrics to Track​

MetricDefinitionTarget
Straight-Through Processing% auto-approved without review70-85%
False Positive Rate% flagged then clearedUnder 5%
False Negative Rate% actual matches missedUnder 0.1%
Average Review TimeTime from flag to resolutionUnder 4 hours
Audit Trail Completeness% with full documentation100%

Human-in-the-Loop: When Agents Should Defer​

Even with high-confidence matches, certain decisions should always involve human judgment:

  • SAR Filing Decisions - While agents can flag potential SAR-worthy activity, the decision to file should be human-reviewed
  • False Positive Resolution - Common names may require additional verification
  • Threshold Adjustments - Changes to decision thresholds should be approved by compliance leadership
  • New Sanctions Programs - When new sanctions are announced, human review ensures proper interpretation

ERP Rigidity vs. Agentic Flexibility​

Traditional ERP workflows are hardcodedβ€”changing the vendor qualification or onboarding process requires IT involvement, configuration changes, and often custom development.

Change NeededERP ApproachAgentic AI Approach
New sanctions listWeeks to addInstant (API provider adds upstream)
Threshold adjustmentDeveloper ticketConfiguration change
Country risk update6-week development cycleParameter change
Audit finding responseDelayed by system constraintsProcess update in minutes

Agentic AI provides configuration-driven flexibility. The agent's behavior is controlled by API parameters and threshold configurationsβ€”not hardcoded logic.


Getting Started​

Using SanctionsWise API for Entity Screening​

import requests

response = requests.post(
"https://api.sanctionswise.orchestraprime.ai/v1/screen/entity",
headers={"x-api-key": "your_api_key"},
json={
"name": "Viktor A. Petrov",
"entity_type": "individual",
"threshold": 0.7
}
)

result = response.json()
# Returns: status, matches with confidence scores, screening_id for audit

Next Steps​

  1. Get API Key - Sign up and get your API credentials
  2. API Reference - Explore the full API capabilities
  3. SDK Examples - Integration code samples
  4. Best Practices - Production deployment recommendations

Key Takeaways​

  1. Confidence Scores enable graduated responses, allowing agents to auto-approve low-risk cases while escalating uncertain ones
  2. Source Citations ground every recommendation in authoritative documents, enabling verification and building trust
  3. Threshold Tuning allows progressive autonomyβ€”start conservative, then increase automation as confidence grows
  4. Audit Trails satisfy regulatory requirements and provide examination-ready evidence
  5. Human-in-the-Loop remains essential for edge cases, threshold changes, and high-stakes decisions

The goal isn't to remove humans from complianceβ€”it's to augment human expertise with intelligent systems that handle routine decisions autonomously while preserving human judgment for the cases that truly need it.


February 2026 | OrchestraPrime Thought Leadership Series