Operations
Master Data Management for Multi-Entity Business Groups: A Practical Guide
By ATTPL HOLDCO / ATTPL GROUP Editorial Team · · 2 min read
Clean vendor, customer, item and account master data across group companies: common codes, GSTIN and PAN checks, ownership, controls and a 90-day plan.
What master data is and why it matters
Master data is the shared reference information that every transaction uses: vendors, customers, items or services, employees, cost centres and the chart of accounts. In a group with several companies, the same vendor or customer often appears under different names and codes in each entity. That leads to duplicate payments, wrong GST credits, weak spend analysis and slow consolidation.
Good master data is the foundation for group MIS reporting and for consolidated financial statements.
The main master data domains
- Vendor master: legal name, PAN, GSTIN, bank details, MSME (Udyam) status and payment terms
- Customer master: legal name, billing and shipping addresses, GSTIN, credit limit and group relationship
- Item or service master: description, unit, HSN or SAC code and tax rate
- Chart of accounts: one group structure with mapping for each company
- Employee and cost centre master: department, location and reporting line
- Intercompany master: a fixed code for every group company so balances match at month end
Validation checks that prevent errors
Build simple rules into the system or the onboarding form. A GSTIN has 15 characters, starts with the two-digit state code (08 for Rajasthan) and contains the party's PAN in characters 3 to 12, so mismatches are easy to catch. Verify GSTINs on the GST portal and bank accounts through a penny-drop or cancelled cheque. Flag duplicates by PAN, GSTIN and bank account, not only by name.
Record MSME status carefully: the MSMED Act requires payment to micro and small suppliers within the agreed period (not more than 45 days), and Section 43B(h) of the Income-tax Act links the tax deduction for such dues to timely payment.
Ownership and controls
Assign a data owner for each domain, usually procurement for vendors, sales for customers and finance for accounts. Separate the person who requests a new record from the person who approves it, and log every change to bank details. These controls support the internal audit of the group and reduce fraud risk.
A 90-day cleanup plan
- Days 1 to 30: export masters from every company, agree naming standards and group codes
- Days 31 to 60: remove duplicates, validate GSTIN, PAN and bank data, block inactive records
- Days 61 to 90: set approval workflows, publish the data standard and start monthly quality reports
Track a few measures each month, such as duplicate rate, incomplete records and time to create a new vendor.
How ATTPL can help
ATTPL IT supports ERP and software setup, and ATTPL Consultancy can help design processes and controls. To plan a group-wide data project, contact ATTPL HOLDCO.
Frequently asked questions
Who should own vendor master data?
Usually procurement owns the content and finance approves bank and tax details, with clear segregation between requesting and approving.
Do all group companies need the same chart of accounts?
Not identical, but each company's accounts should map to one group structure so consolidation and MIS are consistent.
How do we find duplicate vendors?
Match on PAN, GSTIN and bank account number rather than name alone, then merge or block duplicates.
Sources and further reading
This article is general information, not tax or legal advice. Rules on GST and MSME payments change; confirm current requirements with qualified professionals.
