The deterministic AI engine behind every correction
A seven-step pipeline across 24 endpoints at sub-50ms P95 — every correction reproducible and traceable to a cited regulatory clause, a guarantee LLM-based parsers cannot make.
The seven-step AutoCorrect pipeline
Behind every AutoCorrect call, the engine runs the same pipeline end to end, inside one API call.
Classify
Detect whether the input is unstructured, hybrid or structured.
Validate
Check field presence, character limits and occurrence rules per output mode.
Postal-verify
Match against real postal databases across 246 countries with a 0.0–1.0 confidence score.
Extract entities
Pull BIC, LEI and IBAN out of misplaced address lines into their correct structured fields.
Convert format
Promote town and country into structured fields; remove duplications; convert unstructured → hybrid or fully structured.
Apply scheme rules
The regulation-aware step: eight layers of rules applied automatically from three parameters (scheme, party role, execution datetime).
Render
Write corrected addresses back into the correct XPaths, preserve all namespaces, and return a complete, XSD-valid ISO 20022 message.
AutoCorrect vs PreCheck
Every decision traceable
The same input always produces the same output, every time. Every decision is traceable through a rule_source field on each of 30 structured reason codes.
Four output modes, bidirectional
A single engine renders to four configurable modes and converts in both directions — OUTBOUND to upgrade for the network, INBOUND to down-render for legacy sanctions or RTGS gateways, even mixed within a single call.
Specifications
| Metric | Specification |
|---|---|
| Latency | < 50ms P95 for the full seven-step pipeline |
| Throughput | 1,000+ TPS sustained |
| Capacity | 10B+ transactions per year |
| Batch | Up to 1,000 transaction sets, or 100 messages, per call |
246 countries (including 41 SEPA: 30 EEA + 11 non-EEA), 11+ payment schemes (SCT, SCT Inst, SDD Core, SDD B2B, OCT Inst, CBPR+, CHAPS, T2, EURO1, Fedwire and more), and 25+ ISO 20022 message types across pain, pacs and camt.
Frequently asked questions
Yes. A single REST endpoint accepts free-text, hybrid or structured input and returns corrected ISO 20022 output. MCP, IBM MQ, Kafka, SFTP and JDBC channels are also supported.
Sub-50ms P95 for the full seven-step pipeline; the structural PreCheck path is sub-100ms.
Deterministic. Identical input always produces identical output, with every correction tied to a cited regulatory rule_source — a requirement LLM parsers cannot meet.
Yes. The engine writes corrections back into the correct XPaths, preserves all namespaces, leaves untouched elements intact, and returns a complete, XSD-valid ISO 20022 message — no XPath logic on your side.