DotOne teamWhat is master data management?
Master data is the core reference data a business runs on, the records that change rarely but are used in almost every transaction. Master data management (MDM) is the set of rules, owners and processes that keep that data accurate, consistent and free of duplicates across every system and team.
Large enterprises buy dedicated MDM software. For most growing manufacturers, MDM is a discipline applied inside the ERP: clear naming rules, named owners and an approval step before a new master goes live.
Master data vs transactional data
| Master data | Transactional data | |
|---|---|---|
| What it is | Who and what the business deals with | What happened, and when |
| Examples | Item, customer, vendor, BOM, ledger | Invoice, PO, GRN, job card, payment |
| How often it changes | Rarely | Every day |
| Impact of an error | Repeats in every transaction that uses it | Usually limited to one document |
The master data a manufacturer runs on
- Item master: raw materials, components, consumables, semi-finished and finished goods, with codes, units, HSN, tax rate and reorder levels.
- Units of measure: base units and conversions, such as a roll to metres or a box to pieces.
- Bill of materials (BOM): what goes into each product, in what quantity, with expected scrap.
- Customer master: legal name, GSTIN, billing and shipping addresses, credit terms, price list.
- Vendor master: legal name, GSTIN, PAN, bank details, payment terms, approved items.
- Chart of accounts and ledgers: the ledgers your vouchers post to, which must match your books in Tally.
- Locations: plants, warehouses, bins and work centres.
- Employees: codes, departments, salary structure and statutory details.
Why master data goes wrong
- Duplicates. The same item created as "MS Sheet 2mm", "M.S. sheet 2 mm" and "Mild steel sheet 2.0". Stock splits across three records and none of them is right.
- No owner. Anyone can create a master, so everyone does, in their own style.
- Wrong units. Bought in kg, issued in pieces, with no conversion set up, so stock and costing drift apart.
- Missing tax details. Wrong HSN or GST rate on an item, or a wrong GSTIN on a customer, puts errors into every invoice and return.
- Old records left active. Discontinued items and inactive vendors still show up in dropdowns and get used by mistake.
Rules that keep master data clean
- Name an owner for each master. For example: stores owns items, purchase owns vendors, accounts owns ledgers and customer tax details.
- Agree a naming convention. For example: type, material, size, grade, in that order, with fixed abbreviations: "SHEET-MS-2.0MM-IS2062".
- Use structured fields, not names, for attributes. Size, grade and colour belong in fields or variants, so reports can filter on them.
- Search before you create. Make checking for an existing record a required step.
- Approve new masters. A short approval step for new items and vendors stops most duplicates.
- Validate tax data. Check GSTIN format and HSN codes when the record is created, not when the return is filed.
- Deactivate, don't delete. Mark old records inactive so history stays intact but nobody can pick them by mistake.
- Review quarterly. Run a duplicate and missing-field report and clean up.
Master data checklist before ERP go-live
- Item list de-duplicated, with codes, units, HSN and GST rates filled for every active item
- Unit conversions set up and tested on real purchase and issue examples
- BOMs entered and checked against one real production batch (see our BOM setup guide)
- Customer and vendor GSTINs, addresses and payment terms verified
- Ledgers mapped to your Tally company, if your books stay in Tally
- Opening stock counted and loaded by location
- Owners and the approval rule for new masters agreed and written down
DotOne syncs masters both ways with Tally through the Tally connector, so customers, vendors, items and ledgers stay the same in both systems.