# Master Data Quality Rules Catalog Worksheet

> Source: https://netray.co/tools/master-data-quality-rules-catalog-worksheet
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

An editable catalog of data quality rules with check type, threshold, owner and run frequency.

## Category

erp-operations

## Audience

- Data steward
- MDM lead
- ERP administrator

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### Rule ID

**Key:** rule_id

**Type:** text

#### Domain

**Key:** domain

**Type:** select

**Options:**

- Item
- Vendor
- Customer
- BOM
- Routing
- Finance

#### Field

**Key:** field

**Type:** text

#### Rule description

**Key:** rule

**Type:** text

#### Check type

**Key:** check

**Type:** select

**Options:**

- Completeness
- Validity
- Uniqueness
- Consistency
- Timeliness

#### Pass threshold

**Key:** threshold

**Type:** number

**Unit:** %

#### Owner

**Key:** owner

**Type:** text

#### Run frequency

**Key:** freq

**Type:** select

**Options:**

- Daily
- Weekly
- Monthly
- At creation

**Rows:**

**Rule id:** ITM-001

**Domain:** Item

**Field:** Description

**Rule:** Not blank and at least 10 characters

**Check:** Completeness

**Threshold:** 100

**Owner:** Materials steward

**Freq:** Weekly

**Rule id:** ITM-002

**Domain:** Item

**Field:** Unit of measure

**Rule:** Value exists in approved UoM list

**Check:** Validity

**Threshold:** 100

**Owner:** Materials steward

**Freq:** At creation

**Rule id:** ITM-003

**Domain:** Item

**Field:** Description + manufacturer part no.

**Rule:** No two active items share the same pair

**Check:** Uniqueness

**Threshold:** 99

**Owner:** Materials steward

**Freq:** Weekly

**Rule id:** VEN-001

**Domain:** Vendor

**Field:** Tax ID

**Rule:** Present for domestic active vendors

**Check:** Completeness

**Threshold:** 100

**Owner:** AP lead

**Freq:** Monthly

**Rule id:** VEN-002

**Domain:** Vendor

**Field:** Bank account

**Rule:** No two active vendors share an account

**Check:** Uniqueness

**Threshold:** 100

**Owner:** AP lead

**Freq:** Weekly

**Rule id:** BOM-001

**Domain:** BOM

**Field:** Component

**Rule:** Component record is active

**Check:** Consistency

**Threshold:** 100

**Owner:** Engineering data lead

**Freq:** Weekly

**Totals:**

#### Rules in catalog

**Key:** threshold

**Agg:** count

#### Average pass threshold

**Key:** threshold

**Agg:** avg

**Format:** number

**Notes:** Add one row per rule. Keep rules testable: each should be answerable with a query that returns the failing records. Start with 15 to 25 rules that matter to planning, purchasing, costing and payments.

## Content

**Intro:** A data quality program starts with a written list of rules. This worksheet records each rule once with its field, check type, threshold, owner and frequency, so the team knows what is checked, by whom and how often.

**Sections:**

#### How to use the worksheet

**Body:** Add a row per rule. Give it an ID with a domain prefix, name the field, and write the rule in plain words so a business user can read it. Pick the check type, set the pass threshold as a percent of records that must pass, and name an owner who will act on failures. Export to Excel and share with the governance group for review.

**Bullets:**

- One testable rule per row
- Name an owner who can fix failures
- Use 100% only where an exception is truly unacceptable
- Review the catalog quarterly

#### The five check types

**Body:** Completeness asks whether a required value is present. Validity asks whether it conforms to a format, list or range. Uniqueness asks whether a real world thing appears once. Consistency asks whether related fields or records agree, for example an active BOM line pointing to an inactive item. Timeliness asks whether data is current enough to use, such as a review date within policy. These categories are common in data quality frameworks and keep the catalog balanced.

#### Choosing thresholds

**Body:** Set thresholds from business impact, not habit. A missing tax ID on a payable vendor may justify 100%. A fuzzy duplicate rule will produce false positives, so a lower threshold with human review is more honest. Tighten thresholds gradually as the backlog of defects clears, and record changes in the catalog.

#### Common mistakes

**Body:** Writing rules nobody can test, creating hundreds of rules before fixing the first ten, and having no owner. Rules that fail every day with no action teach people to ignore the report. Start small, publish results, and make failures visible to the owner.

**Cta:** Once the rules are written, we can automate them as read-only queries against your ERP and send exception lists to owners.

**Faq:**

#### How many rules should I start with?

**Answer:** Fifteen to twenty-five that affect real decisions: planning, purchasing, costing, payments and compliance. A short catalog that is acted on beats a long one that is ignored.

#### Where do the rules run?

**Answer:** Rules can run as SQL or report queries in the ERP, as ETL checks in a data platform, or as validations at data entry. The catalog is the same regardless of where they run.

#### What is the difference between a rule and a KPI?

**Answer:** A rule tests individual records and produces a list of failures. A KPI summarizes pass rates across rules, for example percent complete. The scorecard worksheet turns rule results into KPIs.

#### Who approves new rules?

**Answer:** The data owner for the domain, with input from the steward. Changes should be dated and logged so trend reports stay comparable.

## Search terms

data quality rules catalog, master data quality rules excel, erp data validation rules list, data quality rule template, mdm rules register, data quality checks spreadsheet

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json