# ERP Data Quality Scorecard Worksheet

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

## Short answer

Enter record and pass counts per master data domain and the worksheet calculates quality percentages and an overall score.

## Category

erp-operations

## Audience

- MDM lead
- Data steward
- CIO

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### Domain

**Key:** domain

**Type:** text

#### Active records

**Key:** records

**Type:** number

#### Complete records

**Key:** complete

**Type:** number

#### Valid records

**Key:** valid

**Type:** number

#### Non-duplicate records

**Key:** unique

**Type:** number

#### Completeness

**Key:** comp_pct

**Type:** number

**Expr:** if(gt(records,0), complete / records * 100, 0)

**Format:** percent

#### Validity

**Key:** val_pct

**Type:** number

**Expr:** if(gt(records,0), valid / records * 100, 0)

**Format:** percent

#### Uniqueness

**Key:** uniq_pct

**Type:** number

**Expr:** if(gt(records,0), unique / records * 100, 0)

**Format:** percent

#### Domain score

**Key:** score

**Type:** number

**Expr:** (comp_pct + val_pct + uniq_pct) / 3

**Format:** percent

**Rows:**

**Domain:** Items

**Records:** 18400

**Complete:** 16900

**Valid:** 17700

**Unique:** 17600

**Domain:** Vendors

**Records:** 2150

**Complete:** 1990

**Valid:** 2080

**Unique:** 2030

**Domain:** Customers

**Records:** 3600

**Complete:** 3350

**Valid:** 3480

**Unique:** 3410

**Domain:** BOMs

**Records:** 5200

**Complete:** 4900

**Valid:** 4850

**Unique:** 5200

**Domain:** Routings

**Records:** 4800

**Complete:** 4300

**Valid:** 4500

**Unique:** 4800

**Totals:**

#### Total active records

**Key:** records

**Agg:** sum

**Format:** integer

**Summary:**

#### Average domain score

**Key:** avg_domain

**Expr:** avg_score

**Format:** percent

**Primary:** true

**Notes:** Counts come from your rule runs: complete means all mandatory fields filled, valid means formats and lists pass, non-duplicate means not flagged as a likely duplicate. The domain score is a simple equal-weighted average. Weight dimensions if your policy requires.

## Content

**Intro:** A scorecard gives managers one page that says how healthy each master data domain is. Enter record counts from your data quality checks and the worksheet calculates completeness, validity, uniqueness and a score per domain.

**Sections:**

#### How to fill it in

**Body:** Add one row per domain such as items, vendors, customers, BOMs and routings. Use active records only, because inactive history inflates counts and hides problems. Take the complete, valid and non-duplicate counts from your rule runs. Completeness is complete records divided by active records. Validity and uniqueness follow the same pattern. Each percentage is shown per row and averaged into a domain score.

**Bullets:**

- Count active records only
- Use the same rules each period
- Record the run date in the notes
- Keep the previous period's file for trends

#### Reading the score

**Body:** Do not treat the score as a grade. Use it to compare domains and track movement. A 94% completeness on 18,400 items still means over a thousand items with a missing mandatory field, which may include fast moving parts. Combine the scorecard with a defect log that lists the actual records and owners, and prioritize by business impact.

#### Choosing what to measure

**Body:** Measures should reflect decisions. For items, completeness of planning attributes such as lead time, UoM and planner code drives MRP. For vendors, tax ID and bank data drive payments and compliance. For BOMs, consistency such as no inactive components drives costing and shop floor releases. Define each measure once in your rule catalog so the numbers are comparable between periods.

#### Common mistakes

**Body:** Changing rules between periods, which makes trends meaningless, counting a record as complete when a field holds a placeholder such as TBD or 999, and reporting one big percentage that hides a bad domain. Check for placeholder values in your completeness rule.

**Cta:** If the counts are gathered by hand each month, we can run the checks against your ERP read-only and populate this scorecard automatically.

**Faq:**

#### What is a good data quality score?

**Answer:** There is no universal target. Many teams aim for the high 90s on critical fields and accept lower scores on optional attributes. Set targets by business impact and raise them over time.

#### Should the dimensions be weighted?

**Answer:** Equal weighting is a fair starting point. If duplicates are far more costly than blank optional fields in your business, weight uniqueness higher and document the choice.

#### How often should I update the scorecard?

**Answer:** Monthly is common for governance reviews, with weekly rule runs feeding it. Daily runs suit high volume creation and migration cutovers.

#### Can I add more dimensions?

**Answer:** Yes. Export to Excel and add columns for consistency or timeliness, then include them in the domain score formula.

## Search terms

data quality scorecard, erp data quality scorecard excel, master data quality kpi, data quality metrics template, data completeness percentage, mdm scorecard template, master data health check

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