Customer Master Data
Customer master data is the central collection of a company's permanent customer information – such as addresses, contact persons and payment and delivery terms. In the ERP system it forms the master data foundation that sales, accounting and shipping access for every customer transaction.
Customer master data is the central, permanently maintained collection of all basic information about a company's customers. Each customer is kept as its own master record – with master data such as company name, addresses, contact persons, tax numbers and individual payment and delivery terms. As part of the partner master data, customer master data forms the reference in the ERP system that every customer-related document draws on: from the quotation and the order through to the invoice and the dunning notice.
Unlike a single order or invoice, which documents one specific business transaction, a customer master record describes the ongoing business relationship with a customer. It is created once and maintained throughout the entire customer relationship, while the associated transaction data is continuously generated anew. Customer master data thus provides the stable frame of reference for sales, accounts receivable and shipping – and its quality directly determines how reliably documents can be generated, terms applied and customer revenues evaluated.
At a glance
- Central collection of permanent customer data: addresses, contacts, terms, tax attributes
- Part of the master data or partner master data – counterpart: supplier master data
- Each customer = one master record with a unique customer number
- Basis for quotations, orders, invoices, dunning and revenue analysis
- Data quality and freedom from duplicates determine process reliability and GDPR compliance
What belongs to customer master data
A customer master record bundles all the information a company permanently needs about a customer. At its core are the identification and address data: a unique customer number, the company name or the name, billing, delivery and differing addresses as well as communication data such as phone, email and website. For business customers, contact persons with roles (purchasing, accounting, management) are added.
In addition, customer master data contains commercial and tax attributes that are pulled automatically into the document: payment terms and payment method, cash discount and credit limits, individual price lists or discount groups, the preferred shipping method as well as tax-relevant details such as the VAT identification number and the tax status. Complementing this, the accounts receivable number for the accounting department, a customer group or industry classification, the language and further classifications for analysis and marketing are often stored.
Debtor vs. customer – a subtle difference
In the ERP a distinction is often made between the customer in the sales sense and the debtor in the accounting sense. The customer master record describes the sales relationship with terms and contact persons, while the assigned accounts receivable account controls receivables accounting. The two are closely linked but not always identical: a corporate group can maintain several customer sites as sales partners that settle against a shared accounts receivable account – or vice versa. Cleanly maintained customer master data keeps this assignment unambiguous.
Why customer master data is so important in the ERP
In the ERP system, customer master data is the single authoritative source for customer information that all modules access jointly. When an order is entered, the system automatically pulls addresses, prices, payment terms and tax attributes from the master record – without clerks having to re-enter them. This maintain-once principle ensures that sales, accounting and shipping work with the same, consistent data, and is one of the core advantages of an integrated ERP over separate isolated solutions.
The leverage of data quality is correspondingly large. An outdated delivery address leads to wrong deliveries, an incorrect payment term delays incoming payment, a faulty tax status distorts invoicing. Duplicates are particularly costly: if the same customer is created multiple times with slightly differing spellings, revenues and open-item lists fragment across several master records, and credit-standing and credit-limit checks no longer work reliably. Clean, unambiguous customer master data is therefore the prerequisite for automated processes, dependable per-customer reporting and a smooth connection of shops and marketplaces.
Customer master data, CRM and interfaces
Customer master data in the ERP overlaps with the contact base of a CRM system, but pursues a different focus. The ERP holds the transaction-relevant master data for order, invoice and shipping, while the CRM adds relationship and sales data such as leads, opportunities, activities and communication history. Many systems cover both; where ERP and CRM are separate, an interface must clarify which system is authoritative for the customer master data, in order to avoid duplicate maintenance and contradictions.
In e-commerce, part of the customer master data is created automatically: when a customer registers in the online shop or orders through a marketplace, the interface creates a master record or assigns the order to an existing customer. To prevent duplicates in the process, clear matching criteria are needed – such as email address or customer number – and a defined authoritative data source.
Customer master data vs. supplier master data
Customer master data and supplier master data are the two halves of the partner master data. Customer master data describes the sales side (accounts receivable, sales terms), supplier master data the procurement side (accounts payable, purchasing terms). The structure is very similar, but the stored terms and posting logic are mirror-inverted. A business partner who is both customer and supplier is kept in both masters in many ERP systems and linked via netting.
DACH specifics: GoBD and GDPR
In German-speaking countries, customer master data is regulatorily relevant in two respects. From an accounting standpoint, the assigned accounts receivable accounts and tax attributes must fit the requirements of the GoBD and – in the practice of many tax firms – the DATEV structure, so that invoices are processed audit-proof and with the correct VAT. For intra-community supplies, the VAT identification number stored in the customer master data is decisive; it should be verified and documented via the confirmation procedure.
At the same time, customer master data is almost always personal data and falls under the GDPR. This affects purpose limitation, rights of access and above all deletion concepts: an ERP must not only store customer data but also be able to block and delete it in a controlled manner as soon as no commercial or tax retention obligation applies any longer. In practice this means an interplay of retention periods for posting-relevant data and deletion routines for contact and marketing attributes that are no longer needed – cleanly structured master fields make this separation considerably easier.
Maintaining and migrating customer master data
For customer master data to remain reliable over the long term, structured maintenance processes are needed: mandatory fields, naming conventions, a duplicate check when creating new records as well as clear responsibilities for who may change addresses, terms and credit limits. Without such rules, customer master data drifts apart over time, especially when sales, accounting and the online shop maintain the same customers.
During an ERP implementation or a system changeover, customer master data is regularly among the most demanding parts of the migration. Existing customer data must be extracted from legacy systems, cleansed, de-duplicated and mapped to the field structure of the new system. The principle applies of not carrying out any migration without prior data cleansing – historically grown customer lists almost always contain dead records, typos and inconsistent formats. A proven approach is to run test imports, review the results from a business perspective and take customer master data live only after sign-off.
Example
Example: customer master data cleanup at a B2B wholesaler
A wholesaler for catering supplies kept its customers in parallel for years in the shop system, in an Excel address list and in the accounting program. Larger customers with several branches were therefore created multiple times – partly with differing spellings, partly with different payment terms. The consequence: per-customer revenue analyses were unusable, credit limits ran into the void, and the same billing address appeared in three variants.
With the ERP implementation, the customer master data was first consolidated: each customer received a unique customer number, duplicates were merged, branches were kept as differing delivery addresses under the main customer, and payment terms were standardized. Since then, sales, warehouse and accounting access exactly one master record per customer. The result: correct documents, reliable revenues per customer and working credit-limit checks – the real effort lay not in the software, but in tidying up the customer data beforehand.
Frequently asked questions
Matching ERP systems
Related services
Sources
Questions about Customer Master Data in your ERP project?
We advise vendor-neutrally – and implement it ourselves on request.