Kemlat Header
Kemlat
  • Home
  • About
  • Services
    Business & TransformationA clear view of the problem and a plan you can deliver.8 Project & DeliveryGovernance that connects plans to results.3 ERP & CRMConnected processes and data in systems that fit your work.2 Digital ProductsWebsites, apps and platforms built around your needs.8 AI & AutomationPractical solutions for tasks that should take less time.8 Quality EngineeringMore confidence in every release.3 Cloud & SecurityA dependable foundation for your digital work.5 Managed ServicesStability, support and improvement after launch.3 Brand & CreativeAn identity and experience that tell your story clearly.4 Digital GrowthBetter visibility and decisions based on performance.5 Games & ImmersiveInteractive experiences for learning and for brands.4 Training & EnablementSkills your team can put to work.3
    All services56

    The KEMLAT Method

    KEMLAT
    Build your projectPick the services you need and get an approximate cost range in a minute.
  • Work
  • The Method
  • Insights
  • Contact
ARGet in touch
  • Home
  • About
  • Business & Transformation Project & Delivery ERP & CRM Digital Products AI & Automation Quality Engineering Cloud & Security Managed Services Brand & Creative Digital Growth Games & Immersive Training & EnablementAll services Build your project
  • Work
  • The Method
  • Insights
  • Contact
Get in touch
العربية [email protected] +962 79 122 3241
Check the Main Menu location in Apppearance->Menus->Display Location.
Master Data: Why Your Customer List Has Five Versions of One Client - Kemlat Insights
Kemlat2026-10-21T16:56:13+03:00
All insightsاقرأ بالعربية
Enterprise Systems

Master Data: Why Your Customer List Has Five Versions of One Client

When one client appears five times in your system, invoices, credit limits and reports all suffer. Why duplicate master data happens, and a practical way to clean it and keep it clean.

27 October 20265 min read
Share
Master Data: Why Your Customer List Has Five Versions of One Client - Kemlat Insights

Search your system for one of your biggest customers. There is a fair chance you will find it more than once: in English and in Arabic, with and without “Co.”, under the old trading name, and once more as a duplicate a new salesperson created last month.

This is the problem that master data management exists to solve. Each version looks harmless on its own. Together they split the customer’s history, confuse credit control and make every report on that customer slightly wrong.

What master data is, and why it matters

Master data is the core reference information that transactions depend on: customers, suppliers, products, employees, price lists, chart of accounts, locations. It changes slowly, but every order, invoice and payment points to it. When master data is wrong or duplicated, the error spreads into every transaction that uses it.

Consider a pharmaceutical distributor in Amman that merged the customer lists of two sales teams, one serving pharmacies and one serving hospitals. Some private hospitals bought through both channels, so they now appear twice, with different payment terms and credit limits. One record is over its credit limit and blocked. The other is not, so orders keep flowing. Finance sees overdue balances on both records but cannot see the total exposure without exporting and combining them by hand.

How duplicates creep in

Duplicates are rarely the result of carelessness alone. Most come from predictable situations:

Source of duplicatesWhat it looks like
Spelling and transliterationThe same family or company name written as Mohammad, Mohammed or Muhammad, or with and without the “Al” prefix
Two languagesOne record created in Arabic by a branch, another in English by head office
Legal and trading namesA company recorded under its registered name and again under the name on its shopfront
Branches and sitesEach branch of a customer created as a separate customer instead of a delivery address under one account
Weak search before creatingA salesperson searches, misses the existing record because of a spelling difference, and creates a new one
System migrations and mergersLists from two systems or two companies combined without matching

The same patterns affect products, where one item may exist under a supplier code, an internal code and a slightly different description, and suppliers, where the same vendor is set up separately by purchasing and by finance.

Practical tip: choose a reliable unique identifier for each type of master data and make it mandatory. For business customers and suppliers, the tax number is usually the strongest candidate, because it does not change with spelling.

Cleaning the data you already have

A one-off clean-up is the starting point. Work through it in a controlled way, rather than letting everyone merge records as they find them.

  1. Extract and profile. Export all records of one type, such as customers, and count blanks in key fields like tax number, phone, email and address. This shows how much matching information you have to work with.
  2. Find likely duplicates. Match on unique identifiers first, then on phone numbers and email addresses, then on normalised names. Normalising means removing common words such as “company”, “trading” and “est.”, standardising “Al” prefixes and converting to a consistent spelling. Power Query in Excel has a fuzzy merge option that suggests pairs whose names are similar but not identical, which is a useful starting list for review.
  3. Review suggested matches with the business. Sales and finance should confirm which records are truly the same customer, and which are separate legal entities that happen to look alike. Automated matching proposes; people decide.
  4. Choose the surviving record. For each group, keep the record with the most complete and correct information, and copy across anything useful from the others, such as a missing tax number or an additional delivery address.
  5. Merge or block, depending on your system. Some systems allow true merges that move transaction history to the surviving record. Others only let you archive or block the duplicate. Either way, make sure no new transactions can be posted to the retired records.
  6. Check open balances and credit limits. After merging, review balances, credit limits and payment terms for each surviving customer, since these may have been set differently on each duplicate.

Do the clean-up in batches, starting with the customers who generate most of your revenue or most of your credit risk. Cleaning the top few hundred records properly delivers most of the benefit quickly, and the method can then be applied to the remaining records with less supervision.

Keeping master data clean afterwards

Without prevention, duplicates return within months. A few controls make the difference:

  • Restrict who can create master records. A small team, or a request form that a data owner approves, rather than every user.
  • Make key fields mandatory. Tax number, a primary phone or email, and the customer’s preferred language should be required before a record can be saved.
  • Check for duplicates at the point of entry. Many ERP (enterprise resource planning) and CRM (customer relationship management) systems can warn when a new record matches an existing one on tax number or phone. Where they cannot, a simple automated check can flag likely duplicates daily for review.
  • Use parent and child structures. Record customer branches as delivery addresses or child accounts under one parent, so credit and reporting work at the right level.
  • Assign a data owner. One person per data type, accountable for its quality, with a monthly review of new records and flagged duplicates.

Where customer records include individuals, remember that this is personal data. Jordan’s Personal Data Protection Law of 2023 is one reason to collect only what you need and to control who can see and change it.

One record for each customer, and rules that keep it that way

A quick way to size the problem is to export your customer list and count how many tax numbers appear on more than one record. That number, and the balances attached to those records, usually makes the case for a clean-up better than any argument.

Data quality and data architecture are a core part of our Enterprise Systems service. We help you clean existing master data, design the structures and controls that keep it clean, and automate the checks so problems are caught at the point of entry.

Found this useful?Share it with your team or someone who needs it.
  • WhatsApp
  • LinkedIn
  • X
  • Facebook
  • Telegram
  • Email
Related service

Enterprise Systems

We design and build systems, and migrate data into them, based on real operational needs, not generic templates.

Also related: Intelligent Automation

Explore our services

Related insights

Cleaning Historical Data Before a System Migration - Kemlat Insights
Enterprise Systems

Cleaning Historical Data Before a System Migration

Moving fifteen years of records into a new system just in case is a frequent reason migrations run late. Decide what to bring, clean it properly…

16 Nov 2026 · 5 min read
Mobile Apps for Field Teams: When They Are Worth Building - Kemlat Insights
Enterprise Systems

Mobile Apps for Field Teams: When They Are Worth Building

Paper job sheets sent by WhatsApp make the case for an app feel obvious. Sometimes a custom app is right. Often a simpler option fits the…

15 Nov 2026 · 5 min read
Budgeting for an ERP Project: The Costs People Forget - Kemlat Insights
Enterprise Systems

Budgeting for an ERP Project: The Costs People Forget

ERP budgets often overrun because of costs that were real from the start but never made it into the budget. These are the lines to add…

14 Nov 2026 · 5 min read

Kemlat Footer
Kemlat
Kemlat

We help organisations transform complex operations into clearer ways of working, practical solutions, and measurable outcomes.

Quick Links

  • Home
  • About Kemlat
  • Our Services
  • Selected Work
  • The Method
  • Contact Us

Services

  • Business & Transformation
  • ERP & CRM
  • Digital Products
  • AI & Automation
  • Cloud & Security
  • Digital Growth
  • All services
  • Build your project

Get in Touch

Email [email protected]
Location Almadina Almunawwara St., Amman, Jordan
WhatsApp & Phone +962 79 122 3241

© 2026 Kemlat. All rights reserved.

Privacy Policy Terms of Use
Kemlat Method

Request a Service

Tell us what you need and we will get back to you within one business day.

By sending this form you agree to our privacy policy.

Request received

Thank you. Our team will review your request and contact you within one business day.