⚠ NSW Point V2 is decommissioned on 30 September 2026 (source: point.digital.nsw.gov.au). Every dependent system must move to NSW Point V3 or an alternative.
—
Read the migration guide →
AddressIQ is the address-intelligence layer inside mapERP and AssetIQ: one governed API and one drop-in widget that validates, geocodes and enriches every address across SAP, Salesforce, ServiceNow, Oracle, Maximo and TechnologyOne — silently routing each request to the best-fit provider, from authoritative G-NAF to global commercial sources.
Every enterprise capturing addresses across multiple systems integrates each one separately against one or more geocoding vendors. That means duplicated contracts, duplicated API keys, duplicated caching logic, duplicated field-mapping work — and inconsistent answers to "where is this asset?"
Each ERP, CRM and EAM system carries its own geocoding integration — built, tested and maintained separately. The same work is paid for once per system, every upgrade cycle.
Google forbids storing results. HERE requires a ~US$10k/yr licence to cache. Mapbox's cheap tier bans retention. When integrations are scattered, nobody is enforcing these terms — until an audit.
A single provider misses ~1 in 10 addresses. For asset registers, work orders and emergency dispatch, locality-level guesses and silent failures become field crews at the wrong site.
NSW Point V2 — the NSW Government address validation service many systems depend on — is decommissioned 30 September 2026 (V1 already went in June 2023, and API fees have applied since July 2024). NSW Point V3 is the successor, but it's a different API contract: every V2 integration must be rebuilt, per system — or re-pointed once through an aggregation layer.
Applications call one contract — resolve, autocomplete, enrich, classify. AddressIQ routes each request through a per-region fallback chain, normalises every provider's response into one canonical address object, enforces each provider's licence terms at the routing layer, and meters every call for billing evidence.
Australian addresses resolve against Geoscape G-NAF and NSW Point (which runs on Geoscape technology over GNAF/GNAF-Live/MailAddress) before any global commercial source — and the routing engine carries NSW Point V2's 30 Sep 2026 sunset date, switching off that endpoint automatically or over to V3 when your keys move. Per-country chains: PAF for UK, Smarty for US, open-data fallback everywhere.
Low confidence or provider outage cascades to the next source automatically — with every attempt logged. Built to survive a provider disappearing entirely (it happened twice in 2026).
Every geocoded point classifies into your zones — country, state, postcode range, suburb, or drawn boundaries — with deterministic overlap weighting, plus LGA, flood-risk and zoning enrichment in one governed pipeline.
One SDK core with native wrappers: SAP Fiori custom control, Salesforce Lightning component (Flow-embeddable), ServiceNow UI Builder component, and a dependency-free web component for everything else. Configuration only — no per-system build.
Bring your own Google/HERE accounts per provider, or use Hastha-managed pooled credentials with transparent metering and markup — set per provider, per system. Your procurement keeps control either way.
Describe a zone in plain English and review the proposed boundary. Get routing recommendations grounded in your real usage ledger. Map a new ERP's address fields from a sample record. Always human-confirmed, never auto-applied.
Who it's for
Address intelligence touches finance, architecture, operations, engineering and compliance differently. Here's what each of you gets — and where to look first.
Duplicated integrations, duplicated vendor contracts and manual data-fix labour collapse into one governed capability with an evidence-backed invoice.
Run the ROI model →A single internal API in front of every provider, deployable natively on SAP BTP or as a Docker/Kubernetes stack on your cloud — same code, same tests.
See the deployment matrix →Authoritative-first matching, zone classification and flood/LGA enrichment mean work orders carry trustworthy locations — not locality-level guesses.
How routing works →Native widgets for Fiori, Lightning, ServiceNow UI Builder and plain web. Configuration only: an API key, a field mapping, one save event.
The widget contract →Per-provider storage rights enforced at the routing layer, immutable change logs and a usage ledger your auditors can reconcile line-by-line.
The licence trap explained →One codebase, two deployment shells. SAP customers run AddressIQ natively on BTP with HANA and XSUAA. Everyone else runs the identical product as a Docker/Kubernetes stack on AWS, Azure, GCP or on-prem — with zero SAP BTP subscription cost.
| SAP BTP deployment | Standalone deployment (Docker/K8s) | |
|---|---|---|
| Business logic, routing, zones, billing | Identical — same codebase, same test suite | |
| Database | SAP HANA Cloud | PostgreSQL + PostGIS |
| Identity | XSUAA / SAP IAS (Azure AD federation) | Any OIDC IdP (Keycloak, Entra ID, Okta) |
| Admin UX | Fiori Elements on your launchpad | Generic web admin + the same JS widget |
| BTP subscription required | Yes (you already have it) | None — $0 BTP cost |
Move the sliders to your estate. Figures use conservative industry defaults for integration build/maintain effort and published provider pricing; the briefing replaces them with your real numbers.
We show benefit net of what you'd pay us — an ROI model that hides its own cost line doesn't survive CFO diligence, and shouldn't.
Model: build 25 engineer-days per additional system integration; maintenance 20% of build per year; provider saving = volume × (current blend − optimised $0.0009/call authoritative-first blend), floor 0; NSW Point migration 30 days once vs per affected system; failed-lookup remediation $4.20/record on 15% of the 9pp of volume improved; minus 3 × your AddressIQ annual cost estimate. Conservative by design — the briefing replaces every input with your real numbers.
AddressIQ ships inside mapERP and AssetIQ engagements, delivered by the SAP BTP/CAP team behind Hastha's transport and infrastructure work — including TfNSW-adjacent delivery and SCM0020 panel membership. This is not a self-serve API startup; it's a governed capability inside platforms you already procure.
Per-provider licence terms — caching rights, metered vs subscription cost models, even China's GCJ-02 coordinate-law constraint — are encoded in the routing engine and enforced on every call, with an immutable audit trail. Your compliance team gets evidence, not assurances.
Soft-delete only. Change-log on every configuration change. Scope-gated access where unauthorised functions are hidden, not disabled. Draft-based transactional editing. Full i18n. The same standards applied across the Hastha IQ family.
The executive briefing is 45 minutes: we run a sample of your asset or customer addresses through the aggregator, show the match-rate and provider-cost deltas against your current setup, and map the NSW Point exposure across your estate.
Book via addressiq@hastha.com.auExisting mapERP / AssetIQ customers: ask your engagement lead — AddressIQ may already be in your platform scope.