Trade automation platform
Flemingo
One governed operational path from incoming instruction to booked, reconciled trade - across structured feeds, files, APIs and email.
Operator-controlled rulesReplayable lineageMurex delivery
Sample processingTrade flow
Demo1CapturePassed
2ValidatePassed
3EnrichPassed
4BookPassed
5ReconcileComplete
TradeSourceProductStatus
FX-1842StorkFX SpotBooked
FX-1841FileFX ForwardBooked
FX-1840FIXFX SwapReview
How it works
Six stages. One accountable outcome.
Each stage produces an observable event, so operators can see what changed, why it changed and where intervention is required.
Capture
Feeds, files, queues and APIs enter one governed envelope. Stork can add email intake as a complementary Mail Intelligence layer.
Sanitize
Required fields, formats and structural integrity are checked before processing.
Map
Source-specific fields are mapped into a stable, governed trade model.
Transform
Business transformations and enrichments are applied as explicit rules.
Normalize
The trade is prepared for its configured downstream delivery adapter.
Reconcile
Target acknowledgement closes the loop or raises an actionable exception.
Flemingo processing trace
Route FX_SPOT_STANDARD
Illustrative flowInbound pathsFIXReal-timeFILEScheduledAPIPolledQUEUEBuffered
01InboundCHECKPOINT02SanitiseCHECKPOINT03MapCHECKPOINT04TransformCHECKPOINT05NormaliseCHECKPOINT06ReconcileMATCH
AIMapping exception detectedCorrection suggested: CNY → CNH92% confidenceHuman approvalRe-run
Envelope retainedRules and mappings recordedSix lineage snapshots
Trade booking software
ADAPTER-BASEDMurex / CalypsoOr your existing platform
Booking response received10:42:18.104 · Captured10:42:19.026 · Normalised10:42:21.842 · Reconciled
Multiple sources in. One governed record out.
The visual mirrors the real Flemingo model: source-specific inputs converge into a governed envelope, move through six persisted stages, and retain lineage for investigation and reconciliation.
Operations experience
Automation that keeps operators in control.
Actionable exception review
When a control fails or a booking cannot complete, Flemingo surfaces the cause, the affected fields and the relevant lineage - without making operators hunt across systems.
REVIEW QUEUE · FX-1840Action required
Value-date rule failedHoliday calendar · INRReview
Counterparty mapping missingSource: Northbridge MarketsResolve
Configuration over custom projects
Rules, mappings and routes are separated from source code, helping operations adapt flows without rebuilding the processing core.
Source-to-booking lineage
Retain the original instruction and follow every version, decision, delivery attempt and acknowledgement through the lifecycle.
Designed for change
Murex today. Adapter-based delivery tomorrow.
Flemingo normalizes trade data before delivery, keeping downstream integration separate from the core workflow.
Multiple capture channels
Support market feeds, file drops, vendor APIs and internal queues, with Stork available as a complementary Mail Intelligence layer for email intake.
Explicit business policy
Keep validation, mapping, transformation and routing logic visible and governable.
Pluggable destinations
Use a delivery adapter for Murex today and onboard additional target systems as your landscape evolves.
Live product walkthrough
See Flemingo process one of your flows.
Walk through capture, validation, delivery, reconciliation and exception handling using a representative trade workflow.