Modern enterprises must connect business strategy with technical execution in a traceable and scalable manner. But how exactly does a high-level capability like “FX Risk Management” translate into APIs, services, and platforms?
The answer lies in clearly distinguishing — and connecting — four architectural layers:
Business Capability → Business Service → Application Service → Solution
What Are These Layers?
Business Capability (What an Enterprise Does)
“What the business must be able to do”
A business capability describes a stable, long-term ability of the enterprise — independent of process, organization, or technology.
Examples in FX Trading:
-
SLA Violation Management
-
Trade Dispute Resolution
-
Volume Forecasting
-
Regulatory Risk Oversight
Business Service (How It Does)
“How the business delivers value through operations”
A business service is realized through people, process, and systems. It defines a concrete deliverable or action.
Examples:
-
Notify FX Desk of SLA Breach
-
Execute Spot FX Trade
-
Generate Client-Specific Risk Report
Application Service
“What APIs or system interfaces are exposed to support the business”
An application service is a technical construct — usually an API or a messaging interface — that delivers a reusable capability.
Examples:
-
POST /sla-alert
-
fx-trade-lifecycle-events (Kafka topic)
-
GET /risk-score/{portfolioId}
Solution
“How the platform or application ecosystem implements everything above”
A solution is the end-to-end delivery of architecture: applications, infrastructure, models, workflows, and integrations.
Examples:
-
SLA Violation Detection Pipeline
-
FX Risk Insight Dashboard
-
LLM-Powered Dispute Assistant
How They’re Connected
Each layer depends on and supports the one above it:
Business Capability
→ realized by → Business Service
→ enabled by → Application Service
→ implemented via → Solution
This traceability enables:
-
Strategic clarity for the CIO
-
Executional alignment for the CTO
-
Governance and modeling for the Chief Architect
Why This Matters
Benefit: Traceability
Outcome: Understand what technical services support which business outcomes
Benefit: Modularity
Outcome: Update parts of the system without breaking overall capabilities
Benefit: Governance
Outcome: Standardize design and approval workflows across teams
Benefit: Transformation Readiness
Outcome: Migrate to cloud, AI, or modern stacks without losing strategic alignment
Closing Thoughts
Whether you’re building a next-gen FX platform or modernizing a retail core, enterprise architecture demands structure, consistency, and clarity. Understanding and applying the hierarchy of Business Capability → Business Service → Application Service → Solution is a powerful step toward that future.
Ready to model your platform the right way?
Start by defining your core business capabilities — and ensure every API and cloud workload can trace back to them.