Business glossary: what it is and how it differs from a data dictionary

A business glossary is the dictionary a company writes about itself.

It sounds like an IT thing, but it is not. It is the list of terms the company uses every day, each with a single meaning, approved by the very areas that use the word.

I have seen large companies, with expensive ERPs and well structured master data, get stuck in a meeting because purchasing called one thing a "customer" and finance called a different thing a "customer". Both were right within their own area. The problem is that nobody had written down, anywhere, what the official meaning of that word was for the whole company.

What a business glossary is

A business glossary is the set of official definitions for the terms a company uses to talk about its own business, such as customer, approved supplier, active material, open order or recurring revenue. Each term has an owner, an approved definition and, ideally, a practical example of use.

It is not a reference document stored in a folder nobody opens. It is the agreement that lets purchasing, sales, finance and IT use the same word to mean the same thing, even while working in different systems.

This idea comes from the discipline of data governance, described in the DAMA-DMBOK, the field's reference guide. But it is born from a much simpler problem: every company has words everyone uses and almost nobody defines.

The difference between a business glossary and a data dictionary

This is the most common confusion when a company starts organizing data governance.

A data dictionary describes system fields: column name, type, length, whether it accepts null values, which table it lives in. It speaks the language of whoever develops and administers databases.

A business glossary describes business concepts: what the company understands by an active customer, an approved supplier, a critical material. It speaks the language of whoever buys, sells, bills and decides.

A system field may be named "customer_status", but that does not explain to a sales manager what an active customer actually is for the company. The glossary is what builds that bridge. The data dictionary documents the technical structure. The business glossary documents the meaning the business gives to that structure.

The two connect: the glossary term points to the corresponding field in the database, and the dictionary field points back to the business definition. When that link exists, anyone can leave a report screen and understand exactly what that number represents.

How the glossary works day to day

A well built business glossary is not long. It covers the terms that cause disagreement, rework or wrong decisions, not every word the company uses.

The process usually follows a simple sequence. First, list the terms that have already caused discussion or misunderstanding between areas, the way purchasing and finance disagreed about what a customer is. Then, take each term to the business owner in the area involved, so they write the definition in their own words, without technical jargon. Next, submit the definition to a data committee or a governance forum for formal approval. And then publish the term in an accessible catalog, linked to the corresponding system field, reviewing the definition every six months or a year.

That process avoids a classic mistake: IT writing the definition of a business term on its own. When that happens, the glossary is born technically correct and useless day to day, because nobody in the business area recognizes themselves in that definition.

Who is responsible for the business glossary

Responsibility is shared, and that tends to raise doubts for whoever is setting up the governance program.

The data steward usually runs the process: organizing meetings, recording definitions, keeping the catalog up to date and asking for review when the business changes. But the owner of the definition is always the business area. The one who defines what an approved supplier is, is purchasing, not IT. The one who defines what recurring revenue is, is finance, not the data team.

The governance committee steps in to resolve cases where two areas disagree, and to formally approve the most critical terms, the ones that show up in contracts, board reports or financial indicators.

This division of roles is usually where a data governance program shows whether it is really working. When only IT participates, the glossary becomes technical documentation. When only the business participates without governance support, it becomes a loose list, disconnected from the technical data.

Which tools support a business glossary

A glossary can start in a spreadsheet, and many companies start exactly that way. The problem shows up when the number of terms grows and nobody knows anymore which version is current.

Data catalog tools such as Collibra, Alation and Microsoft Purview offer a business glossary module integrated with the technical catalog. That lets a business term stay automatically linked to the tables, columns and reports where that concept appears, so any user can see the official definition of that data right on the report screen.

Master Data Management platforms, the kind that support customer, supplier and material records, typically rely on the glossary to make sure the business concept used in a quality rule is the same one approved by the area. Without that link, it is common for a data quality rule to check a technically correct condition that does not actually represent what the business means by that term.

The right tool depends on the company's size and the maturity of the governance program. The most common mistake is usually a different one: buying an expensive catalog platform before the definition and approval process is actually running with the business areas.

How to learn to structure a business glossary

Anyone who wants to go deeper into business glossaries usually gets there through one of two paths: data governance or master data management.

The DAMA-DMBOK is the most solid reference, and the CDMP certification, from DAMA, validates knowledge of the whole discipline, including glossary, catalog and data quality. There is a myth, common in some markets, that certification is useless for a data career. Not true. Certification validates the theoretical base, and that base is what keeps you from building a glossary with no process, no owner and no review.

Beyond the theory, the fastest learning comes from actually taking part in building a glossary inside a company, discussing definitions with purchasing, finance and sales, and feeling firsthand how each area pulls the concept toward its own side.

Career opportunities tied to the business glossary

The business glossary is a recurring task for anyone working as a data steward, data governance analyst or master data analyst. It is also one of the first deliverables an MDM consultant asks for before designing quality rules and record approval workflows.

The data governance market is hot, driven by data protection laws, SAP S/4HANA migration projects and the arrival of generative AI in companies, which needs data with a clear meaning to work properly. Professionals who know how to run that conversation between business and technology, without relying only on a tool, are in demand at companies of every size.

Anyone already working with master data records, supplier support or ERP system support has a real advantage in this transition: they already live every day with the terms the glossary formalizes. All that is missing is organizing that knowledge.

Frequently asked questions about the business glossary

Is a business glossary the same thing as a data dictionary?

No. A data dictionary describes system fields and tables. A business glossary describes the meaning the company gives to its own business concepts, such as active customer or approved supplier.

Who should write the definition of a glossary term?

The business area that owns the concept, with support from the data steward and approval from the governance committee when the term is critical.

Do I need a catalog tool to have a business glossary?

Not at the start. A well organized spreadsheet already handles the first few dozen terms. A catalog tool becomes worthwhile when the number of terms and users grows and the link to the technical data becomes indispensable.

How many terms should a business glossary have?

Enough to cover the terms that have already caused disagreement or a wrong decision. Most companies that do this well work with a few dozen core terms, not hundreds.

Does a business glossary make sense for small companies too?

Yes, and it is usually easier to implement, because there are fewer areas and systems involved. The common mistake is assuming only large companies need data governance.

MDM Academy

MDM Academy is 4MDG's school for data governance and master data. It was created to practically train the professional who today learns MDM and governance alone, reading scattered articles and watching disconnected videos with no structured path.

The courses cover everything from master data fundamentals to topics such as material master records, SAP, data quality and governance applied to a company's daily operations, always with real examples from purchasing, supply chain and master data, not just slide theory.

MDM Academy lessons and materials are in Portuguese. You can take the program from any country, and an English version is on our roadmap, with no committed date. The certificate is issued in Brazil, in Portuguese, and is valid in Brazil.

Anyone who wants to better understand how to structure a business glossary, set up their first data committee or get ready to work as a data steward can check out MDM Academy and also join the Data Club, our WhatsApp group for people who work or want to work with data: https://chat.whatsapp.com/H4RudT3peYA1PDBAgOFqXG

Conclusion

A business glossary looks like bureaucracy until the day two areas disagree on the meaning of a word on top of a contract or a board report. That day, the company discovers the cost of never having written down, anywhere, what it actually means by its own terms.

It is not about the tool. It is about the company understanding itself.

In your company, does active customer mean the same thing to purchasing, sales and finance?