At a glance
- Data quality is measured against its intended purpose: the same data may be sufficient for monthly reporting but too imprecise for a daily forecast.
- Six core dimensions are considered standard: accuracy, completeness, consistency, timeliness, validity, and uniqueness.
- Data quality can be measured using metrics such as error rate, duplicate rate, or the completion rate of mandatory fields.
- Data errors are least costly when detected during data capture or integration, rather than later in a management report.
- AI amplifies the effect: AI-powered analyses and forecasts only produce useful results when based on validated data.
What would you like to know about data quality?
Your input is sent to an AI service to answer it and is stored to improve the answers. Please do not enter any personal data. Privacy policy
Data quality definition
Data quality refers to the degree to which data is suitable, accurate, and reliable for a specific purpose. It is assessed based on various quality characteristics such as accuracy, completeness, timeliness, consistency, and uniqueness. High data quality ensures that data can be processed and analyzed reliably and used as a basis for well-founded decisions.
Data quality is not merely a technical detail; it is a key prerequisite for business success. Reliable, up-to-date, and complete data enables companies to generate sound insights and build reliable automated processes. In an era of business intelligence, artificial intelligence (AI), and data-driven decision-making, the quality of the underlying data is critical.
A high standard of data quality means that data must not only be technically correct but also understandable, relevant, and usable in the right context. Ideally, data should support processes rather than hinder them. Companies that recognize this invest systematically in capturing, validating, cleansing, and continuously monitoring their data.
„Since we have been working with DeltaMaster on a central data foundation, we no longer discuss whether the figures are correct, but rather the measures behind them. We track conspicuous values via drill-down down to the individual document.“Head of Controlling
Mechanical Engineering
What does data quality mean for a company?
Data quality in a company means that data is fit for its specific purpose: for month-end closing, sales planning, or an AI project. A dataset is never inherently good or bad; its quality always depends on the requirements of its users. In the literature, this principle is known as “fitness for use.”
Data quality goes beyond technical correctness. Data must also be consistently defined, understandable, and usable in the right context. A revenue figure is of little use if sales and controlling interpret it differently – for example, as gross revenue versus net revenue.
In business intelligence and controlling, data quality determines whether reports inspire confidence or trigger discussions about the numbers. Data quality is therefore not a one-time project but an ongoing responsibility shared by business functions and IT.
Trusted by market leaders and hidden champions





How does data quality differ from related terms?
Data quality is the measurable outcome that data integrity and data governance make possible.
| Term | Key question | Example |
|---|---|---|
| Data quality | Is the data fit for its purpose? | The customer master contains no duplicates and complete addresses. |
| Data integrity | Does data remain unchanged and structurally correct during storage and transmission? | An order always references an existing customer. |
| Data governance | Who is responsible for which data and according to which rules? | Sales maintains customer data; controlling defines metrics. |
| Data management | How is data captured, stored, integrated, and made available? | ETL processes load ERP data into the data warehouse every day. |
Why is data quality so important?
Companies with high data quality not only work more efficiently but can also respond more quickly to market changes because they have access to reliable data.
Poor data quality affects:
What are the criteria and dimensions of data quality?
Data quality is generally measured across six core dimensions: accuracy, completeness, consistency, timeliness, validity, and uniqueness. Each dimension can be assessed using its own verification question and set of rules.
| Dimension | Meaning | Typical verification question | Example from controlling |
|---|---|---|---|
| Accuracy | Data corresponds to reality. | Do the values reflect the actual circumstances? | The posted invoice amount matches the invoice. |
| Completeness | All required datasets and mandatory fields are present. | Are any fields or entire datasets missing? | Every item is assigned to a product group. |
| Consistency | Data does not contradict itself, including across systems. | Do the values match across all sources? | Revenue in the ERP system matches revenue in the BI report. |
| Timeliness | Data is sufficiently current for its intended purpose. | When was the data last updated? | Incoming orders in the daily report are no more than one day old. |
| Validity | Data conforms to defined formats and value ranges. | Are all fields populated using the correct format and value range? | A discount is between 0 and 100 percent. |
| Uniqueness | Each object exists only once in the dataset. | Are there duplicates? | A customer is not recorded under two customer numbers. |
What other criteria are relevant?
In addition to the core dimensions, other criteria are important, particularly for use by business functions. The ISO/IEC 25012 standard defines a total of 15 data quality characteristics.
- Relevance: The data answers the questions for which it was collected.
- Understandability: Metrics and fields are clearly defined and documented.
- Provenance transparency: Every figure can be traced back to its source (data lineage).
- Accessibility: Authorized users can access the data on time and without unnecessary effort.
What are the characteristics of good data quality in everyday use?
Good data quality is evident when people no longer debate the numbers themselves but focus on what they mean. Typical characteristics include:
- Reports from different departments show the same values for the same metric.
- Controllers no longer manually correct figures in Excel before publishing them.
- Anomalies in reports have business-related causes, not technical ones.
- Business functions know who is responsible for their data and report errors at the source.
How do you assess and measure data quality?
Data quality is assessed by companies defining validation rules for each dimension, measuring the actual state as a metric, and comparing it against a target value. Without measurement, data quality remains a guess: according to Gartner, 59 percent of organizations do not measure their data quality.
What steps does an assessment follow?
- Determine critical data: Which data feeds into management metrics, planning, or AI applications? That is where the review begins.
- Define validation rules: The business department and IT define, for each dimension, what "correct" means, such as mandatory fields, value ranges, or reconciliation rules between systems.
- Measure the actual state: Data profiling reveals fill rates, value distributions, duplicates, and format errors.
- Set thresholds: A target value is defined for each metric, for example at least 98 percent filled mandatory fields.
- Monitor continuously: The metrics are checked with every data load and made visible in a data quality report.
Which metrics are suitable for measurement?
| Metric | Calculation | Dimension |
|---|---|---|
| Completeness rate | filled mandatory fields divided by all mandatory fields, as a percentage | Completeness |
| Duplicate rate | number of duplicates divided by all records, as a percentage | Uniqueness |
| Error rate | records with a rule violation divided by all checked records | Validity, accuracy |
| Reconciliation difference | deviation of a total between source system and BI system | Consistency |
| Data age | time since the last successful update | Timeliness |
| Correction effort | hours of manual rework per month-end close | all dimensions (indirectly) |
The thresholds depend on the purpose. For consolidated financial statements, a reconciliation difference of zero is mandatory, while for a trend analysis in marketing lower accuracy is often sufficient.
What impact does data quality have on business results?
Poor data quality costs money, time, and trust. A Gartner study from 2020 puts the cost of poor data quality at an average of at least 12.9 million US dollars per organization per year (Gartner). The figure is based on estimates from large companies and should be understood as an order of magnitude.
The costs rise the later an error is detected. The so-called 1-10-100 rule describes this effect: an error that costs 1 euro at capture costs about 10 euros to clean up later and about 100 euros as a wrong decision. Checks at the source and during data integration are therefore the most economical.
| Area | Consequence of poor data quality | Example |
|---|---|---|
| Decisions | Management steers based on wrong figures. | A product appears profitable because returns are missing. |
| Planning and forecasting | Forecasts carry over errors from the actual data. | Duplicates in the customer master inflate sales planning. |
| Processes | Employees correct data manually instead of analyzing it. | Controllers reconcile Excel lists before every close. |
| Customers | Faulty master data leads to wrong deliveries or invoices. | An invoice goes to an outdated address. |
| Compliance | Audits and reports become vulnerable. | Diverging values between the report and accounting are noticed in the audit. |
| AI | Models learn errors along the way and pass them on as recommendations. | An AI forecast overestimates demand because cancellations are missing. |
How can data quality be improved?
Data quality improves permanently only when organization and technology work together: clear responsibilities, uniform definitions, and automatic checks in data integration. A one-time cleanup removes symptoms, but not the causes.
Organizational measures
- Name a data owner for each data area, for example sales for customer data and purchasing for supplier data.
- Define metrics in a shared glossary so that "revenue" means the same in all reports.
- Set rules for data capture and train employees in them.
- Have errors fixed at the source instead of overwriting them in the report.
Technical measures
- Validate entries in the source system, for example through mandatory fields and selection lists.
- Build validation rules into ETL processes so that faulty records are caught before loading.
- Consolidate data in a central data basis that serves as a single source of truth.
- Detect and merge duplicates using matching rules.
- Measure and report data quality metrics with every load.
How do you improve data quality with BI tools?
BI tools improve data quality because they make errors visible where business users notice them: in reports, variance analyses, and drill-downs. A controller spots an implausible monthly value faster than any generic validation rule.
| Function in the BI tool | Contribution to data quality |
|---|---|
| Central data model | All reports access the same data and definitions. |
| Validation rules in data integration | Format errors, duplicates, and missing values are caught before loading. |
| Anomaly detection | Implausible values and outliers are flagged automatically. |
| Variance analysis and drill-down | Users trace a conspicuous figure down to the individual document. |
| Reconciliation reports | Totals from the ERP system and the BI system are compared regularly. |
| Comment function | Business departments document known data problems directly on the report. |
Which errors occur frequently and how can they be avoided?
The most common error is treating data quality as a one-time IT project. Without ongoing checks and clear responsibilities, old errors quickly return.
| Error | Consequence | Avoidance |
|---|---|---|
| One-time cleanup instead of ongoing checks | Errors reappear after a short time. | Build validation rules permanently into data integration. |
| Checking only in the finished report | Corrections cost a lot of time just before the deadline. | Check data at the source and during loading. |
| No one responsible for data | Errors are reported but not fixed. | Name a data owner for each data area. |
| Inconsistent metric definitions | Departments argue over the "right" figures. | Use a shared metrics glossary and a central data model. |
| Manual corrections in Excel outside the system | Reports deviate from the data basis, corrections are lost. | Make corrections in the source system or in data integration. |
| Treating all data equally | Effort goes into unimportant fields. | Start with the data that feeds into management metrics and AI. |
| Cleaning errors silently | The cause in the source system remains. | Log cleanups and report them back to the source. |
What role does data quality play for artificial intelligence?
Data quality and artificial intelligence are connected in two directions: AI needs verified data, and AI helps find data errors. Both sides gain importance as AI is adopted in controlling.
Why does AI need high data quality?
AI models adopt the errors in their data and pass them on as seemingly well-founded results. The principle is called "garbage in, garbage out". An AI forecast based on incomplete actual data looks plausible and is nevertheless wrong.
With language models, another level is added: if a large language model accesses documents via retrieval-augmented generation (RAG), the timeliness and clarity of texts also matter. Outdated guidelines or duplicate versions lead to contradictory answers.
Lawmakers also impose requirements: Article 10 of the European AI Regulation (EU AI Act) requires that, for high-risk AI systems, the training, validation and testing data be relevant, sufficiently representative, and to the best extent possible free of errors and complete in view of the intended purpose (Art. 10 AI Act).
How does AI improve data quality?
AI recognizes patterns that fixed validation rules overlook. Typical fields of application are:
- Detecting anomalies and implausible values in large data volumes
- Tracking down duplicates with differing spelling
- Classifying unstructured information, for example from conversation records
- Suggesting mappings and cleansing steps when connecting new sources
The AI data integration from Bissantz automatically detects format breaks, typos and implausible values, suggests cleansing and reduces manual review loops. The functional assessment of the suggestions remains with humans, supported by Explainable AI.
Which trends shape the topic of data quality?
The most important trends move data quality forward into data integration and make it a prerequisite for AI. Instead of looking for errors in the finished report, companies increasingly check data automatically and continuously.
| Trend | What lies behind it | Significance for companies |
|---|---|---|
| AI-supported data quality | AI detects anomalies, duplicates and format errors and suggests cleansing. | Fewer manual review loops as data volumes grow |
| Data quality as an AI prerequisite | Companies check their data basis before introducing AI analyses, forecasts or agents. | Data quality becomes part of every AI strategy. |
| Unstructured data | Texts, records and documents flow into analyses via RAG and MCP servers. | Quality rules no longer apply only to numbers. |
| Data observability | Data pipelines are continuously monitored for timeliness, volume, schema changes and distributions. | Errors are noticed before users become aware of them. |
| Data contracts | Data suppliers and data consumers agree on schema and quality requirements in a binding way. | Clear responsibilities between business departments and IT |
| Validation at the source (shift-left) | Validation moves from the reporting level into upstream systems and integration. | Lower error costs according to the 1-10-100 rule |
| Regulation | The EU AI Act and audit requirements call for documented data quality and data lineage. | Data quality becomes subject to proof. |
Practical example: data quality in sales controlling
A mid-sized manufacturer reports its monthly revenue from the ERP system and from the BI system. The values regularly differ, and before every closing the controlling team spends days reconciling in Excel. Management doubts the figures of the sales planning.
The analysis reveals three causes: after connecting the CRM system, customers exist twice, new items are not assigned to any product group, and credit notes are posted in the systems at different points in time.
| Problem | Dimension | Solution with Bissantz |
|---|---|---|
| Duplicate customers after the CRM connection | Uniqueness | The AI data integration detects anomalies during loading and suggests cleansing. |
| Items without product group | Completeness | Validation rules in the ETL process report missing assignments to the data owner in sales. |
| Differing revenue between ERP and BI system | Consistency | A central DeltaMaster database serves as a single source of truth, a reconciliation report compares the totals. |
| Conspicuous values are only noticed in the management report | Accuracy | DeltaMaster highlights variances automatically, controllers trace them via drill-down down to the voucher. |
The result: causes are corrected in the upstream system instead of overwritten in the report. Controlling comments on remaining anomalies directly in DeltaMaster, and management again discusses measures instead of figures.
Application examples: where data quality is decisive
Data quality affects almost all data-driven processes in a company. The following examples show typical areas of use in which reliable data determines sound decisions.
Where would you like to improve data quality in your company?
Your input is sent to an AI service to answer it and is stored to improve the answers. Please do not enter any personal data. Privacy policy
How does Bissantz support data quality?
Bissantz relies on the highest possible data quality as the foundation for reliable analysis and effective business management. After all, intelligent BI is only as good as the data it is based on. For this reason, DeltaMaster consistently relies on structured, validated, and integrated data models, for example from data warehouses or ERP systems. This ensures that all analyses are consistent, traceable, and correct – regardless of how complex the underlying company data may be.
Bissantz BI solutions actively support data quality by:
- relying on centralized, redundancy-free data storage (the single source of truth),
- automatically identifying variances and highlighting them visually (for example, through the patented two-color logic),
- enabling commentable analyses that make faulty or unusual data situations visible directly in the planning context,
- creating transparency into data provenance, without a black box.
Data quality is a business-critical factor, particularly in integrated planning, forecasting, and AI-powered analysis. That is why Bissantz does not treat data validation as a preliminary step but as an integral part of the entire analysis and management process – from import and modeling through to decision-making.
DeltaMaster thinks along: Faulty, incomplete, or contradictory data is not processed silently but deliberately made visible – visually, linguistically, and through system support. This turns potentially misleading information into reliable knowledge – and transforms a high standard of data quality into a tangible competitive advantage.
| Function | Benefit |
|---|---|
| Central, redundancy-free data storage | all reports access the same data as a single source of truth |
| Patented two-color logic | variances are automatically identified and visually highlighted |
| Analyses that can be commented | conspicuous data situations become directly visible and documentable in the planning context |
| Transparency about data origin | figures remain traceable, with no black box |
| AI data integration | format breaks, typos and implausible values are automatically detected and corrections are suggested |
„The automatic check already during data integration uncovers duplicates and missing assignments before they make it into our reports. This saves us the manual correction loops before every monthly closing.“BI Manager
Retail Company
Frequently asked questions
What is data quality in simple terms?
Data quality describes how well data is suited to its intended purpose. Data may technically exist and still be outdated, inconsistent, or incomplete. Good data quality means having the right data, in the right format, at the right time, without errors. Like a compass, data is only useful if it actually points north.
What is the difference between data quality and data integrity?
Data integrity ensures that data remains unchanged and consistent – both technically and structurally. Data quality is broader: it also assesses whether data is factually correct, complete, up to date, and fit for its intended purpose. Data integrity is a prerequisite for data quality, but the two are not the same.
What are typical causes of poor data quality?
Common causes include manual data entry without validation, missing or inconsistent standards between systems, outdated datasets without regular updates, unclear responsibility for data maintenance, and inadequate ETL processes for data integration.
How is data quality measured?
Data quality is measured across six dimensions: timeliness, uniqueness, accuracy, validity, consistency, and completeness. Specifically, metrics such as error rates, duplicate rates, completeness rates, or deviations from defined reference values are captured and monitored.
What is a single source of truth, and why is it relevant to data quality?
A single source of truth is a single, centralized, reliable data source that all users access. It prevents different departments from working with different, contradictory datasets and is therefore a key element of consistent data quality across the organization.
How does Bissantz support data quality?
DeltaMaster integrates data quality checks directly into the analysis and reporting process: variances are automatically detected and highlighted, the data foundation is centralized and redundancy-free, and the origin of every metric can be traced transparently. Bissantz also supports the design of quality standards and ETL processes, ensuring that data quality is embedded systematically from the outset.
Summary
Data quality is the silent foundation of all data-driven activities: only when data is accurate, complete, consistent, and up to date can analyses, reports, and AI applications deliver reliable results. It is not a one-time project but an ongoing process, embedded in data models, ETL processes, and an established data culture. With DeltaMaster and its consulting expertise, Bissantz makes data quality an integral part of corporate management—visible, manageable, and sustainably secured.
Related topics
Data quality for BI and AI
Our BI and data engineering consultants work with you to develop processes and rules for integrating data into your BI system efficiently and smoothly while improving data quality and ensuring it over the long term.
Improve data quality