Address Validation for SAP S/4HANA
Clean addresses.
Ready for S/4HANA.
Turn messy legacy customer and supplier addresses into postal-validated records load-ready for SAP S/4HANA Business Partners — rules first, AI where rules can't help, and a person approving every change.
The SimpleMigrate suite
One platform for SAP S/4HANA data migration.
Cloud-native and AI-assisted, with people approving every change. Start with the application you need; the rest share the same sign-in, roles and audit trail.
Address Validation
Legacy customer and supplier addresses, checked, enriched and postal-validated — load-ready for S/4HANA Business Partners.
See how it works → Early accessData Migration
Extraction from your source systems, profiling, data-quality rules, mapping and value maps, and loading into S/4HANA.
Ask about early access → Coming soonDescription Builder
Consistent, S/4-ready material and product descriptions built from your legacy text and attributes.
Tell us your use case →Built for data migration leads, master data owners, program directors and the system integrators who run migrations for many clients.
The problem
Business-partner addresses are where go-lives slip.
Legacy ERPs hold addresses as free text. Teams fix them in spreadsheets for months — and the load still fails.
They don't fit S/4
Names over 40 characters, PO boxes over 10, free-text lines. Load errors and repeated mock loads.
Codes don't map
Legacy region codes, spelled-out states, and one country code that means two countries.
Dead partners migrate
Nobody decides who is still active, so you clean and load data you should leave behind.
No audit trail
One-by-one spreadsheet fixes and no record of who changed what, or why.
How it works
One guided workflow, from legacy to S/4.
Every step shows how many records wait for it. One role — the Address Owner — runs them all.
Ingest
From any ETL tool's input tables, or Excel, CSV and TSV files up to 500 MB. Transactions and S/4 code lists too.
Check
Every record graded A–D and measured against your activity cut-off. Entry checks and source markings surfaced.
Map
Confirm each source country/region pair once — every record that uses it follows.
Prepare
Automatic rules and an address parser split the fields and pull tax numbers out of street lines. No per-record cost.
Enrich with AI
AI proposes fixes for what rules could not. A person accepts, edits or keeps each one.
Validate
Licensed postal data from Loqate or Smarty, with match scores and candidates to choose from.
Approve
Approve in bulk, review the flagged, or exclude — with a reason recorded.
Map to S/4
Region names become your S/4 keys; fields and lengths are the ones S/4 Business Partners take.
Side paths: Out of Scope for partners before your cut-off (include any one with a click) and Excluded for records that won't migrate.
One record, start to finish
From a legacy row to S/4 fields.
An illustrative supplier, as it leaves a legacy ERP and as it goes to the S/4 load.
Before · the legacy record
- Name
- MUELLER PRAEZISIONSTEILE GMBH & CO. KG ABT. EINKAUF ZENTRALLAGER 61 characters — S/4 takes 40
- Street
- HAUPTSTR. 12A, USt-IdNr. DE123456789 tax number in the street
- City
- D-80331 MUENCHEN post code in the city
- Country
- GER not an ISO code
- Region
- BAVARIA S/4 expects a key
After · ready for S/4HANA
- Name 1
- MUELLER PRAEZISIONSTEILE GMBH & CO. KG
- Name 2
- ABT. EINKAUF ZENTRALLAGER
- Street · No.
- HAUPTSTRASSE · 12A
- Post code · City
- 80331 · MÜNCHEN postal-validated
- Country · Region
- DE · 09 your S/4 region key
- Tax number
- DE123456789 kept for the tax-numbers sheet
Rules and the parser did the split, the country/region mapping was confirmed once for every GER/BAVARIA record, the name split was a proposal the Address Owner accepted, and Loqate confirmed the address. Every step is in the record's change log.
Spend only where it counts
Rules first. Paid last. People in between.
Validation APIs alone check everything, junk included. SimpleMigrate scopes and prepares first, so you only pay to validate records you will actually migrate.
Runs by itself every minute. House number, street, city and post code split; VAT, GST, ABN, EIN, CNPJ, RFC and CUIT numbers found and kept.
Anthropic Claude or OpenAI fills what rules could not — shown beside the original, accepted or rejected by a person before anything is paid for.
Loqate or Smarty checks the address against licensed postal data. Full matches go to approval; the rest to review.
Features
Everything the Address Owner needs.
Works with your tools
Any ETL tool — Informatica, Talend, SSIS and others — writes the input tables and reads the results. No plug-in.
Scope you control
Your cut-off date and your source's markings decide what moves. Nothing is excluded on activity alone.
Source markings honored
"Do not use" and "use alternate" records surfaced; alternate keys checked for existence, loops and chains.
Country suggestions
When a city or company name points to another country, the record says so — accept, change or keep.
Tax numbers rescued
Registration and tax numbers hidden in address lines are captured and removed from the address.
Candidates, not guesses
Ambiguous validation results keep every candidate with its SAP fields; the Address Owner picks one.
Change log per record
Who changed what and when — people and automatic steps alike — with reasons required on overrides.
Related records
Every address of the same partner side by side, so locations are decided together.
Runs in the background
Ingest, preparation, AI and validation run as jobs; screens refresh and notify you when they finish.
Built for S/4HANA
Load-ready for S/4HANA, not just validated.
Every address comes out in the shape SAP S/4HANA Business Partners take — customers and suppliers, the same fields, the same lengths, your own region keys — ready for whichever load tool you use: the SAP Migration Cockpit (Customer S_CUST_GEN and Supplier S_SUPPL_GEN sheets), your ETL tool, or another.
- Field lengths enforced before the load, not discovered during it
- Region names mapped to the keys in your S/4 region table
- PO box overflows and over-long names flagged for a decision
- Output tables any load tool can read — no SimpleMigrate plug-in needed
| Group | Fields delivered |
|---|---|
| Names | Name 1–4, c/o |
| Street | Street, supplements 1–3, location, house numbers |
| Building | Building, floor, room |
| City | City, district, post code |
| Region / country | S/4 region key, country |
| PO box | PO box, PO box city |
Security and deployment
Secure by design. Deployed your way.
Isolated per client
Row-level security in the database keeps every client's data apart — not just the screens.
Invite-only access
No public sign-up. Roles per client and per environment, with expiry dates.
Audit everywhere
Created and updated by and when on every table; a change log on every record.
Your AI, your validation
Choose Claude or OpenAI, Loqate or Smarty — with your own keys or ours.
Backed up
Continuous backups with point-in-time recovery, plus a nightly off-site copy.
Deployment options
SimpleMigrate cloud
We host it; you sign in. The fastest start, with your data isolated from every other client's.
Bring your own database
SimpleMigrate runs against a database in your own account, so your migration data stays in your database.
Your own cloud
The whole application installed in your AWS, Azure or Google Cloud account, managed by your IT.
Your ETL tool always runs inside your network. Ask us which option fits your policies.
Questions customers ask
Before you book a demo.
Where is our data stored?
In the SimpleMigrate cloud on AWS in the United States, with every client's data kept apart by row-level security in the database, and continuous backups with point-in-time recovery. If your policy keeps data in-house, SimpleMigrate can run against your own database or inside your own cloud account.
What does the AI see, and can it change our data?
Only the address fields of the records sent to AI enrichment, through Anthropic Claude or OpenAI — with your key or ours. The AI never changes a record by itself: each fix is a proposal a person accepts, edits or rejects.
What is under the hood?
PostgreSQL for your data, with row-level security; the open-source libpostal parser and our own rules for the free preparation step; Anthropic Claude or OpenAI for AI proposals; Loqate or Smarty for postal validation. No proprietary plug-in is installed in your systems.
Do we need our own Loqate or Smarty licence?
No. Use ours, or bring your own key — whichever your procurement prefers.
Which source systems and ETL tools does it work with?
Any. Your ETL tool (Informatica, Talend, SSIS and others) writes the input tables and reads the results, or you upload Excel, CSV or TSV files. SAP ECC, Oracle-based and home-grown ERPs all arrive the same way.
Does it load into S/4HANA?
It hands you load-ready Business Partner addresses — S/4 fields, lengths and region keys — and the load tool you already use performs the load: the Migration Cockpit, your ETL tool, or another.
Who does the work on our side?
One role: the Address Owner, usually someone from master data. They confirm mappings, check AI proposals and approve. Everything else runs by itself.
What happens after the demo?
We look at a sample of your own addresses together, so you see your data come out clean before you decide anything.
Talk to us
See it on 100,000 addresses.
Tell us about your migration and we'll set up a 30-minute demo on our public-data demonstration client.
Or write to us directly:
[email protected]