GeoPostCodes vs ioNova ARS
— one is already inside the other
GeoPostCodes is a high-quality global postal reference data product — the very dataset ioNova ARS embeds as its 246-country verification layer. It is not a parser: comparing them is a category question, not a product race. A bank that licenses ARS already receives the benefit of GeoPostCodes data without separate procurement.
The data layer — and the engine built around it
The honest read from our analysis: GeoPostCodes is the reference-data supplier inside ioNova ARS. One is a dataset; the other is the compliance engine and application that already contains it.
GeoPostCodes
A specialist data product: self-hosted postal reference tables covering 246 countries, delivered as files and a download API — no parsing service, no inference component.
- 9.3M postal codes, 4M cities, 24M streets across 84 countries, 116K UNLOCODEs.
- Weekly updates compiled from 1,500+ authoritative sources.
- Air-gapped by design — downloaded data, zero internet dependency, cannot hallucinate.
- Small private SME (~30–50 employees); no formal security certifications documented.
ioNova ARS
A purpose-built compliance engine — and a full application — that parses SWIFT MT free text and ISO 20022 XML, preserves financial identifiers, and emits regulator-citable corrected XML for the November 2026 mandate.
- Embeds the GeoPostCodes 246-country dataset as its verification layer — plus the parsing, correction, audit and integration engine around it.
- Extracts and preserves 50+ financial identifiers (BIC, IBAN, LEI, ABA…); 30 reason codes citing EPC153-22, PMPG, EU Reg 2023/1113, CBPR+.
- Full application: Exceptions Workbench, live dashboards and Developer Portal — not just an engine.
- Six integration mechanisms; start in days, live in 2–4 weeks; Cloud / VPC / on-prem / air-gapped.
Dimension by dimension
One supplies reference tables; the other supplies everything a compliance operation runs on — with those same tables already inside.
| Dimension | GeoPostCodes | ioNova ARS |
|---|---|---|
| Category | Reference data product — tables + download API | End-to-end compliance engine + full application |
| What you get | CSV/SQL/GeoJSON data files; customer builds everything else | Parse, correct, verify and emit ISO 20022 XML in one call |
| Parsing capability | None — “it cannot explain a parse because it does not perform a parse” | Deterministic 7-step pipeline with 30 reason codes |
| Financial identifiers | None | 50+ types extracted and preserved pre-parse |
| Determinism | Weekly data drift, no documented version pinning | Bit-identical output on versioned rules and data |
| Operational tooling New | N/A — customer’s own platform | Exceptions Workbench + live dashboards, built in |
| Onboarding New | License data, then build or buy a parsing engine on top | Developer Portal sandbox in days; live in 2–4 weeks |
| Composite score | 1.07 / 5.00 | 4.90 / 5.00 |
| Risk-adjusted score | 0.00 / 5.00 (floored) | 4.90 / 5.00 — no penalties |
| Verdict | Category error as a standalone parser; conditionally recommended as a data layer for non-payment uses | Recommended — the engine that already includes this data |
Closest on enterprise operations — near zero wherever a parse is required
Average score per category (out of 5). GeoPostCodes holds its own on the enterprise fundamentals its data-only design supports — and barely registers on the signature and payments criteria that define a financial-messaging compliance engine.
GeoPostCodes is the ingredient.
ioNova is the finished application.
Licensing reference data leaves the entire engine — parsing, correction, audit, review workflow, monitoring, integration — to be built. ARS ships all of it, with the same data already inside.
Exceptions Workbench
Low-confidence resolutions route to maker-checker review queues with per-field confidence, the proposed repair and the rule citation behind it — every action audit-logged.
Live Dashboards
Real-time STP rate, exception ageing, latency percentiles, reason-code distribution and per-country compliance posture — examiner-ready evidence, always current.
Developer Portal
Self-service onboarding, API keys, sandbox with SWIFT MT / ISO 20022 test corpora, OpenAPI specs and integration guides. First message parsed the day access is granted.
Six ways to integrate — versus a file download
ioNova ARS — start in days, live in 2–4 weeks
- D1Developer Portal sign-up: sandbox keys, test corpora, OpenAPI specs — first message parsed same day.
- W1Integrate via the mechanism that fits your stack (REST API, SFTP, IBM MQ, Database, Kafka or MCP).
- W2–4Parallel-run against production traffic in the Workbench; tune thresholds; go live.
GeoPostCodes as a “parser” — the build is the project
- 1License the data — the easy part, and the only part that exists.
- 2Build or buy the parsing engine, identifier extraction, audit trail and rule maintenance on top.
- ∞Own certification, monitoring and every regulatory change — a standing engineering commitment.
† GeoPostCodes has no service component; statements reflect the May 2026 analysis. File uploads are also supported directly in the application UI.
Where GeoPostCodes is genuinely strong
Best-in-category reference data — the reason ARS embeds it. These strengths are real; an ARS licence already includes their benefit.
Best-in-category data
246 countries, 9.3M postal codes, 4M cities — “a high-quality offering” in the words of our own analysis. The reference dataset a global address stack wants underneath it.
Fresh and authoritative
Weekly updates compiled from 1,500+ authoritative sources — postal operators, national statistics agencies and mapping authorities — keep the tables current.
Sovereign by design
Self-hosted, air-gapped, zero internet dependency — the data lives entirely inside your perimeter. A 5/5 tie with ioNova on data sovereignty (ENT-7).
Cannot hallucinate
There is no inference component at all — static reference tables cannot invent an address. A 5/5 tie with ioNova on hallucination resistance (ENT-3).
International coverage parity
A 5/5 tie on international coverage (PQ-1) — unsurprising, because it is the same data ARS uses as its verification layer.
ISO 20022-aligned templates
Publishes per-country address format templates aligned to ISO 20022 structures — useful groundwork that earns it a PAY-4 score of 2/5 despite having no parser.
A category mismatch — not a vendor failing
GeoPostCodes’ zero and low scores are architectural: it ships data, not a service, and performs no parse at all. Scores out of 5, from the May 2026 analysis.
SIG-1–6 · 0–1/5 Not a parser
All six signature capabilities — financial-ID preservation, disambiguation, historical names, de-duplication, explainability, confidence routing — are effectively absent. Architectural, not remediable.
ENT-1 · 0/5 No explainability
It cannot explain a parse it never performs. There are no reason codes, no rule citations and no per-field confidence — the regulator-facing evidence trail is entirely the customer’s build.
ENT-2 · 1/5 Determinism drift
Weekly refresh with no documented version pinning — the same query can answer differently week to week, breaking reproducibility for any system built on top.
ENT-5 · 2/5 Certification gap
No SOC 2 or ISO 27001 certification documented — a profile that may fail a Tier-1 bank’s vendor security assessment before evaluation even starts.
VENDOR · Medium Small-SME risk
A private company of roughly 30–50 employees. The data is excellent, but acquisition or discontinuation risk sits with a small vendor at the base of a compliance stack.
BUILD · High Seven engines to build
Reusing the data across domains means building a parsing engine for each — payments, logistics, CRM and beyond each need their own parse, correction and audit layer on top of the same tables.
All 25 criteria, scored side by side
GeoPostCodes ties ioNova wherever data quality alone decides the criterion — and scores near zero wherever a parse is required.
| Criterion | GeoPostCodes | ioNova ARS | Δ |
|---|---|---|---|
| Signature capabilities · 48% | |||
| Financial-ID preservationSIG-1 · BIC / IBAN / LEI / ABA | 0 / 5 | 5 / 5 | +5 |
| Geographic disambiguationSIG-2 | 1 / 5 | 5 / 5 | +4 |
| Historical name resolutionSIG-3 | 0 / 5 | 5 / 5 | +5 |
| Data de-duplicationSIG-4 · cross-field, multilingual | 0 / 5 | 5 / 5 | +5 |
| Full explainabilitySIG-5 · rule citations, audit trail | 0 / 5 | 5 / 5 | +5 |
| Confidence scoring & routingSIG-6 | 0 / 5 | 5 / 5 | +5 |
| Parsing quality · 12% | |||
| International coveragePQ-1 · countries, scripts | 5 / 5 | 5 / 5 | Tie |
| Component taxonomyPQ-2 | 2 / 5 | 5 / 5 | +3 |
| Normalisation & abbreviationPQ-3 | 0 / 5 | 5 / 5 | +5 |
| Robustness to messy inputPQ-4 | 0 / 5 | 4 / 5 | +4 |
| Enterprise operations · 25% | |||
| Regulatory explainabilityENT-1 · FCA / OCC / BaFin / MAS | 0 / 5 | 5 / 5 | +5 |
| Determinism & consistencyENT-2 | 1 / 5 | 5 / 5 | +4 |
| Hallucination / correction resistanceENT-3 | 5 / 5 | 5 / 5 | Tie |
| Human overrideENT-4 · Exceptions Workbench | 4 / 5 | 4 / 5 | Tie |
| Bank-grade securityENT-5 · SOC 2, ISO 27001, RBAC | 2 / 5 | 5 / 5 | +3 |
| Governance & change managementENT-6 | 2 / 5 | 4 / 5 | +2 |
| Data sovereigntyENT-7 · no external API | 5 / 5 | 5 / 5 | Tie |
| Deployment flexibilityENT-8 · SaaS / VPC / on-prem / air-gapped | 3 / 5 | 5 / 5 | +2 |
| Performance & scalabilityENT-9 | 3 / 5 | 4 / 5 | +1 |
| Payments domain · 15% | |||
| SWIFT MT field handlingPAY-1 · fields 50 / 52 / 56 / 57 / 59 | 0 / 5 | 5 / 5 | +5 |
| Sanctions & compliance integrationPAY-2 | 0 / 5 | 5 / 5 | +5 |
| Correspondent bankingPAY-3 · multi-party chain | 0 / 5 | 5 / 5 | +5 |
| ISO 20022 migration readinessPAY-4 | 2 / 5 | 5 / 5 | +3 |
| Payment routing & country derivationPAY-5 | 1 / 5 | 5 / 5 | +4 |
| Batch & real-time processingPAY-6 | 2 / 5 | 5 / 5 | +3 |
Source: ioNova 25-criterion competitive analysis, May 2026 (v2.0, 70-question research protocol). ioNova meets all 25 criteria; its four 4/5 ratings were documentation gaps at analysis time — the Exceptions Workbench and live dashboards in the current application release address the ENT-4 and monitoring notes. GeoPostCodes’ −3.00 risk penalty derives from its signature-capability zeros (−1.00), two ENT scores below 2 (−1.00) and four PAY scores below 2 (−1.00); the risk-adjusted score is floored at 0.00. The scores are a category mismatch, not a vendor failing.
What teams ask about GeoPostCodes vs ioNova ARS
No — it is ioNova’s embedded data supplier. ARS ships with the GeoPostCodes 246-country dataset inside as its verification layer, so the two sit in the same stack, not on the same shortlist. The real procurement question is “which problem are we solving”: parsing-and-correction (an engine) versus reference-data enrichment (a dataset).
For non-payment uses: logistics, e-commerce, ERP, GIS and market-research teams that need self-hosted global postal reference data and are prepared to build their own logic on top. For payments address compliance, the same data is already inside ARS — a direct licence adds procurement effort without adding capability.
Because it was scored against a parser’s job description. Twelve of the 25 “Not Met” results are architectural: a reference-data product cannot extract financial identifiers or produce confidence scores, because it performs no parse at all. Within its own category, the analysis calls it a high-quality offering — the low composite is a category mismatch, not a quality verdict.
Yes — that is the in-house path, and the data licence is the smallest line item in it. The parsing engine, financial-identifier extraction, regulator-grade audit trail and ongoing rule maintenance are an 18–36 month build with a standing engineering team behind it. ARS delivers the same outcome, on the same data, in 2–4 weeks.
For a data product, no — freshness is a feature. For a compliance system built directly on it, unpinned weekly drift breaks replayability: the same input can resolve differently after a refresh, and a regulator cannot re-run last quarter’s decision. ARS versions both its rules and its embedded data, so identical input replays identically.
ioNova ARS is a full application. Operations teams work exceptions in a maker-checker Workbench with per-field confidence and rule citations; managers watch live dashboards for STP, exception ageing and compliance posture; developers self-serve on the Portal with sandbox keys and test corpora. With a postal API, each of those is a system you build and maintain yourself.
Don’t buy the ingredient.
Deploy the finished engine.
The same 246-country reference data — wrapped in a deterministic compliance engine, an Exceptions Workbench, live dashboards and a Developer Portal. Start in days, live in 2–4 weeks.
See structured resolution in action