Quality Cost Measurement Systems

Introduction

Quality costing converts the consequences of conformance and nonconformance into information that managers can use. A quality department may know that defects are increasing, while finance knows that warranty expense is rising and operations knows that rework hours are consuming capacity. A quality cost measurement system connects these views by establishing common definitions, reliable data flows, accountable ownership, validation controls, and reconciliations to the general ledger and operational systems.

The purpose is not merely to produce a monthly “cost of quality” report. A mature system explains where quality-related resources are consumed, why they are consumed, who controls the underlying process, and whether improvement investment is producing financial value. It must therefore combine management accounting, quality management, operational measurement, information governance, and internal control.

Quality costs are commonly classified into four categories:

These categories are managerial classifications rather than universally prescribed financial-statement categories. Some costs, such as depreciation of inspection equipment or customer-support salaries, require an explicit policy decision. The policy must be applied consistently and must not obscure statutory accounting requirements.

Learning Objectives

By the end of this chapter, the reader should be able to:

1. Design a quality-cost taxonomy and coding structure aligned with processes, products, responsibility centres, and accounting accounts.
2. Define data ownership, collection rules, evidence requirements, validation checks, and approval workflows.
3. Integrate quality records with operational systems, enterprise resource planning systems, and financial ledgers.
4. Calculate and interpret quality-cost measures, including cost of quality as a percentage of sales or conversion cost.
5. Reconcile operational quality records with financial accounting and investigate variances.
6. Evaluate governance, ethical, technological, and managerial risks in quality-cost reporting.

1. Foundations of Quality Cost Measurement

1.1 Measurement as a management-control system

A measurement system is a structured arrangement of definitions, data sources, procedures, controls, people, technology, and reports. It transforms events into information for decisions. In quality costing, an event may be a failed test, a corrective action, a rejected batch, a customer return, or an engineering review.

A useful system satisfies six tests:

• Relevance: the measure supports a decision.
• Reliability: the value is supported by evidence and repeatable rules.
• Comparability: results can be compared across periods, sites, products, or processes.
• Timeliness: information arrives while corrective action is still possible.
• Traceability: a reported amount can be traced to source records and accounting entries.
• Behavioural validity: the measure does not encourage concealment, reclassification, or unsafe decisions.

Measurement must distinguish between the cost of an event and the economic impact of an event. For example, a recorded rework labour charge may be $800, while the economic impact includes delayed delivery, lost capacity, overtime, and customer dissatisfaction. A primary quality-cost system should report the reliably measurable cost and may separately report quantified consequential effects.

1.2 The prevention–appraisal–failure model

The four-category model helps managers see quality expenditure as a portfolio. Prevention and appraisal are generally investments or control costs; internal and external failures are consequences of nonconformance. The classification is not a claim that every prevention dollar reduces failure costs in a simple linear way. A poorly designed inspection regime may increase appraisal cost without preventing defects, and excessive prevention may have diminishing returns.

A basic total quality cost identity is:

where:

• C_Q = total measured quality cost;
• C_P = prevention cost;
• C_A = appraisal cost;
• C_IF = internal-failure cost; and
• C_EF = external-failure cost.

The identity applies when the categories are mutually exclusive and collectively exhaustive for the selected measurement boundary. It is a management-reporting identity, not a rule that determines financial-statement recognition.

A normalized indicator is often more useful than an absolute amount:

where QCR is the quality-cost ratio in percent and B is the selected business base, such as net sales, conversion cost, manufacturing cost, or units produced. The base must be stated because interpretation changes with the denominator. Sales-based ratios may rise because sales fall even when quality costs are unchanged; unit-based ratios may be distorted by product mix.

For a specific category:

where C_i is the cost of category i. Percentages are meaningful only when the numerator and denominator cover the same period, organizational scope, currency, and product or service boundary.

1.3 Measurement boundaries

Before collecting data, an organization should define the boundary of the system. Important boundary choices include:

• legal entity, plant, business unit, or value stream;
• product family, customer segment, or service line;
• manufacturing quality only, or design-to-service quality;
• recorded accounting cost only, or recorded cost plus estimated opportunity effects;
• actual cost, standard cost, or a combination;
• local currency and reporting currency;
• accounting period and operational event date.

A narrow boundary can be appropriate for a pilot, but it must not be presented as the organization’s total quality cost. Boundary metadata should be stored with every report.

2. Designing the Measurement Architecture

2.1 From quality event to financial report

A robust architecture follows the chain:

event → record → classification → valuation → approval → posting or accrual → reconciliation → report → decision.

The event is the real-world occurrence. The record documents it. Classification assigns quality category, process, product, cause, and responsibility. Valuation converts quantities and rates into monetary terms. Approval confirms validity. Posting or accrual connects the amount to accounting. Reconciliation checks completeness and agreement. Reporting presents trends and decisions.

The architecture should preserve both operational detail and financial aggregation. A general ledger may contain one account for warranty expense, while the quality system needs defect code, product, failure mode, customer, lot, and corrective-action identifiers. The systems should therefore be linked rather than forced to contain identical levels of detail.

2.2 Data model and coding dimensions

A coding scheme should be stable enough for trend analysis and flexible enough for new products and processes. A typical quality-cost record may contain the following dimensions:

A code should represent one concept. Combining multiple meanings in a single code, such as “P2-B-07,” may save space but becomes difficult to govern. A relational design with separate fields is generally more transparent. Code tables require version control, effective dates, permitted values, and an owner.

2.3 Cost valuation methods

Quality events can be valued using actual cost, standard cost, or estimated cost. The choice should reflect the decision purpose.

• Actual cost is appropriate where supplier invoices, labour transactions, or disposal records are available.
• Standard cost supports timely reporting and comparison, but variances must be analysed separately.
• Estimated cost is necessary for provisions or incomplete events, but estimates require assumptions, confidence levels, and later true-up.

For a simple rework event valued using labour and material, the measured cost may be expressed as:

where C_R is rework cost; h_L is rework labour hours; r_L is the applicable labour rate per hour; q_M is material quantity consumed; r_M is material rate per unit; and C_O is other directly attributable cost. The formula assumes that labour, material, and other components are non-overlapping and measured in compatible currencies. If overhead is included in r_L or C_O, the policy must prevent double counting.

For scrap, the organization must define whether cost means the full manufacturing cost, recoverable material loss, disposal cost, or a combination. A practical policy might record the standard production cost of scrapped units and separately credit recoverable scrap value. The selected treatment should be consistent with management-accounting policy and financial-reporting requirements.

2.4 Ownership and the three-lines perspective

Ownership should be assigned at several levels:

1. Event owner: records or confirms what happened.
2. Process owner: validates the operational cause and corrective action.
3. Finance owner: validates valuation, account mapping, period, and ledger treatment.
4. Data steward: maintains definitions, codes, and data quality rules.
5. Report owner: interprets trends and communicates decisions.
6. Internal assurance: independently reviews controls and reliability.

Separation of duties is essential. The person benefiting from a favourable performance result should not be the sole person who classifies or approves the underlying cost. Quality personnel should not be pressured to reclassify failures as appraisal merely to improve a departmental metric.

3. Data Collection and Validation

3.1 Sources of quality-cost data

Common sources include:

• nonconformance and deviation records;
• inspection and laboratory systems;
• manufacturing execution systems;
• maintenance and downtime systems;
• time sheets and labour systems;
• inventory, scrap, and material-issue records;
• purchasing and supplier-performance records;
• customer relationship and complaint systems;
• warranty and returns systems;
• corrective-action databases;
• enterprise resource planning and general-ledger systems.

No single source is complete. For example, a nonconformance record may identify 100 rejected units but not the final disposal value; the inventory system may show the value but not the failure mode. Integration should use stable identifiers such as work-order number, lot number, serial number, purchase order, complaint number, and general-ledger document number.

3.2 Data-capture design

Capture should occur as close as possible to the event. Required fields should be limited to information genuinely needed for classification, valuation, control, or analysis. A well-designed form uses controlled lists for category, cause, process, and disposition, while allowing explanatory notes where context matters.

A minimum evidence package may include:

• event description and date;
• quantity affected;
• disposition decision;
• labour, material, service, or disposal evidence;
• responsible cost centre;
• authorization record;
• link to the originating operational transaction;
• treatment of recoveries, insurance, or supplier chargebacks.

The system should distinguish missing, not applicable, not yet known, and zero. Treating these as the same value produces misleading totals.

3.3 Validation controls

Validation operates at three levels.

Field-level validation checks format, permitted codes, dates, currency, and numerical ranges. A quantity should not be negative unless a reversal transaction is explicitly supported.

Record-level validation checks logical relationships. For example, an external-failure cost should normally have a customer, shipment, claim, or warranty reference. A rework charge should normally link to a work order or labour record.

Cross-system validation compares independent records. Examples include comparing rejected quantities with inventory movements, warranty claims with customer-return records, and quality-cost postings with general-ledger balances.

Useful control tests include:

• completeness: all qualifying events are recorded;
• validity: recorded events actually occurred;
• accuracy: amounts and classifications are correct;
• cut-off: events belong to the correct period;
• uniqueness: an event is not counted twice;
• consistency: the same rule is used across sites and periods;
• authorization: adjustments and write-offs are approved.

Exception reports should show the exception, responsible owner, due date, materiality, and resolution status. A control that produces exceptions but does not assign resolution responsibility is incomplete.

4. Integration with Operational and Financial Accounting Systems

4.1 Operational integration

Operational integration provides explanatory power. Quality records should connect to production orders, inspection lots, equipment, suppliers, customers, and corrective actions. This permits questions such as: Which process generates the highest internal-failure cost per unit? Which supplier contributes the largest external-failure exposure? Which corrective actions reduced recurrence?

Integration may be batch-based, near-real-time, or manual. The choice depends on materiality, system capability, event frequency, and decision speed. Real-time integration is not automatically superior: poorly governed real-time data can spread errors faster.

4.2 Financial integration

Financial integration normally includes:

• mapping quality-event types to general-ledger accounts;
• assigning cost centres, profit centres, projects, or work orders;
• applying approved standard or actual rates;
• recording accruals for incurred but uninvoiced costs;
• posting reversals and true-ups;
• accounting for recoveries and supplier chargebacks;
• reconciling subsidiary records to the ledger.

A quality-cost report should not simply add every amount found in a quality database to the general ledger. Some records are operational quantities, some are estimates, and some are already represented in financial postings. The system must specify whether a field is informational, accrual-generating, or ledger-derived.

4.3 Reconciliation framework

Reconciliation compares two records that should agree after defined timing and scope differences are considered. A basic reconciliation can be expressed as:

where D is the unexplained difference; Q_R is the quality-record amount; G_L is the general-ledger amount; and T is the documented timing, scope, currency, or classification adjustment. A satisfactory reconciliation requires D to be zero or within a formally approved tolerance.

A monthly reconciliation process should:

1. freeze the reporting period;
2. extract quality records and ledger balances using the same scope;
3. compare totals by site, category, account, and period;
4. identify timing differences, reversals, omissions, duplicates, and mapping errors;
5. document adjustments and approvals;
6. close unresolved items or carry them forward with an owner and due date;
7. retain evidence of the review.

Reconciliation is not merely an accounting exercise. A large unexplained difference may indicate that shop-floor failures are not being recorded, that finance is posting costs without quality classification, or that definitions have changed.

Worked example: monthly reconciliation

A plant’s quality system reports $126,400 of internal-failure cost for March. The ledger contains $119,000. Investigation identifies $4,800 of March rework labour posted in April and $2,100 of supplier recovery credited in the ledger but not yet reflected in the quality system. The remaining difference is unexplained.

The documented adjustment is:

T = 4,800 − 2,100 = 2,700

Thus:

D = 126,400 − 119,000 − 2,700 = 4,700

The $4,700 difference is not a rounding issue and should remain an open exception. Possible causes include duplicate quality records, missing ledger postings, incorrect account mapping, or an invalid event classification. It should not be forced to zero by an unsupported journal entry.

5. Reporting and Decision Use

5.1 Report design

A useful report combines financial, operational, and causal views. A recommended hierarchy is:

• executive summary of total quality cost and major movements;
• category trend for prevention, appraisal, internal failure, and external failure;
• normalized measures by sales, units, or conversion cost;
• Pareto analysis by process, defect, product, supplier, or customer;
• actual-versus-budget and current-versus-prior-period analysis;
• reconciliation status and unresolved data-quality exceptions;
• corrective-action portfolio and expected benefits.

Reports should distinguish descriptive, diagnostic, and decision information. “Warranty cost increased 12%” is descriptive. “The increase is concentrated in one product family and one failure mode” is diagnostic. “Approve the design change because expected avoided warranty cost exceeds implementation cost” is decision-oriented.

5.2 Trend and mix interpretation

Absolute quality cost can rise while performance improves if production volume expands or prevention investment increases. Conversely, quality cost can fall because inspections were reduced or failures were not recorded. Therefore, interpretation should consider volume, mix, exposure, and data completeness.

For example, cost per unit is:

where CPU_Q is quality cost per unit and N is the number of units in the defined population. The measure assumes that units are comparable. For a mixed portfolio, product-weighted or process-specific measures may be more informative.

A quality-cost dashboard should include leading and lagging indicators. Prevention training completion and process-capability improvement are leading indicators; scrap, complaints, and warranty claims are lagging indicators. Neither type is sufficient alone.

5.3 Linking quality cost to financial return

Quality-cost information supports investment appraisal when expected savings and implementation costs are defined clearly. A simple annual net benefit is:

where NB is annual net benefit, AS is annual avoidable cost saving, and CI is annualized implementation cost. If a project requires an initial investment and produces cash benefits over time, discounted cash-flow analysis is more appropriate. A net present value is:

where I₀ is initial investment, CF_t is incremental cash flow in period t, r is the discount rate, and n is the number of periods. The formula assumes cash flows are estimated consistently, the timing convention is known, and the discount rate reflects the relevant risk and currency. Avoided costs should not be treated as cash savings unless they actually reduce cash expenditure or release capacity that has economic value.

6. Illustrative Case: Northstar Medical Components

Background

Northstar Medical Components, a fictional manufacturer, produces sterile fluid connectors. Its finance team reported rising warranty expense, while operations reported stable first-pass yield. Senior management suspected that quality costs were being understated because operational and financial records used different definitions.

Problem

The plant used four disconnected sources: inspection records, a spreadsheet for rework, the ERP system for scrap, and a customer-service database for complaints. Rework entries were often posted to production overhead, and warranty costs were posted by customer account without product-failure codes. No monthly reconciliation existed.

Analysis

A cross-functional team mapped the event-to-report process. It found three problems:

1. Rework labour was recorded operationally but not consistently charged to quality cost.
2. Customer returns were recorded by shipment date, whereas the ledger used invoice date.
3. Supplier recoveries were netted against expense in finance but reported as gross cost in the quality dashboard.

The team defined a measurement boundary covering the plant, the connector product family, and costs incurred during the financial month. It adopted four categories, introduced a shared event ID, and specified gross cost and recovery as separate fields.

Approach and solution

The redesigned system used the following controls:

• inspection and nonconformance records required a production-order reference;
• rework hours flowed from the time system using approved labour rates;
• scrap quantities were matched to inventory transactions;
• warranty claims required product and failure-mode codes;
• finance reviewed account mapping before period close;
• quality and finance jointly signed a reconciliation report;
• late postings were identified through a cut-off exception report.

The dashboard showed costs for the first quarter after implementation:

The plant’s net sales were $24,000,000, so:

QCR = (1,200,000 ÷ 24,000,000) × 100 = 5%

A Pareto analysis identified one sealing operation as the largest contributor to internal and external failure. A process-improvement project required an initial investment of $300,000 and was expected to avoid $520,000 of annual failure cost, with $80,000 annual maintenance cost. The annual net benefit estimate was:

NB = 520,000 − 80,000 = 440,000

The project was approved subject to verification of actual savings and confirmation that the avoided cost represented real capacity or cash benefit.

Outcome

After two quarters, recorded external failures declined, but the team did not claim that all improvement was caused by the project. It compared product mix, shipment volume, reporting completeness, and complaint lag. The reconciliation process also revealed that the earlier “stable” first-pass yield had excluded a category of inspection rejections. The revised measure was less favourable but more credible.

Learning points

The case demonstrates that measurement-system maturity can initially increase reported cost. This is not necessarily deterioration; it may be improved visibility. Reliable data requires common definitions, event-level traceability, independent validation, and financial reconciliation. Improvement claims should be based on controlled comparisons rather than a single favourable trend.

7. Governance, Ethics, and Limitations

Quality-cost measurement affects budgets, performance evaluations, supplier decisions, and investment approvals. It therefore creates incentives that may distort behaviour. Common risks include suppressing nonconformance reports, delaying recognition until the next period, classifying failures as prevention, allocating costs to another department, and excluding customer dissatisfaction because it is difficult to monetize.

Governance should require:

• documented definitions and classification rules;
• version-controlled data dictionaries;
• approval of material policy changes;
• audit trails for edits and overrides;
• access controls based on role;
• retention of source evidence;
• periodic independent review;
• protection of customer and employee information;
• escalation of safety, regulatory, and product-liability events.

Quality-cost systems must never encourage release of unsafe or nonconforming products to protect a cost ratio. Legal and regulatory obligations take precedence over managerial targets. Personal data in complaint or warranty records should be minimized, protected, and processed according to applicable privacy requirements.

The model also has limitations. Some costs are difficult to classify, prevention benefits may occur after a long delay, external failure effects may be uncertain, and accounting treatments differ across jurisdictions. Cost data can therefore support judgement but cannot replace engineering analysis, customer research, risk assessment, or compliance review.

8. Technology and Contemporary Practice

Modern systems increasingly use APIs, data warehouses, process mining, mobile data capture, and machine-learning tools. These technologies can improve timeliness and identify unusual patterns, but they do not solve weak definitions or poor ownership.

Artificial intelligence may assist with duplicate detection, defect-text classification, anomaly detection, and prediction of warranty exposure. Its use requires explainability, validation against known cases, monitoring for data drift, and human review of consequential decisions. An algorithm should not silently reclassify a failure or create a financial accrual without controlled approval.

Process mining can compare the designed quality workflow with actual event paths, revealing skipped approvals, repeated rework loops, or late closure. Digital thread architectures can connect design requirements, supplier data, production history, inspection evidence, and field performance. These developments increase traceability but also increase cybersecurity, access-control, interoperability, and data-retention obligations.

Best-Practice Design Checklist

A high-quality measurement system should:

1. define the purpose, scope, boundary, and reporting base;
2. establish mutually exclusive and collectively exhaustive categories;
3. maintain a controlled data dictionary and coding hierarchy;
4. capture events at source with unique identifiers;
5. separate operational facts, valuation rules, and accounting treatment;
6. assign ownership and segregate incompatible duties;
7. validate data at field, record, and cross-system levels;
8. reconcile quality records to the ledger every reporting period;
9. report both absolute and normalized measures;
10. distinguish actual savings from avoided or estimated costs;
11. preserve audit trails and protect sensitive information;
12. review whether measures create harmful incentives;
13. test reports through internal audit and management review; and
14. revise the system when products, processes, regulations, or accounting policies change.

Chapter Summary

Quality cost measurement is an integrated management-control discipline linking quality events, operational records, valuation rules, financial accounting, and improvement decisions. The prevention–appraisal–internal-failure–external-failure model provides a useful classification, but its value depends on clear boundaries and consistent application. A robust system uses controlled codes, event-level evidence, accountable ownership, field and cross-system validation, and periodic reconciliation to the general ledger.

Quality-cost reports should combine absolute amounts, normalized ratios, trends, causal analysis, and reconciliation status. Financial evaluation must distinguish recorded cost from economic impact and avoidable cost from merely estimated cost. Governance is essential because quality measures can influence behaviour, safety, compliance, and resource allocation. Technology can improve integration and analytics, but it cannot substitute for sound definitions, controls, professional judgement, and ethical leadership.

Key Terms

Quality cost: Cost associated with preventing, detecting, or experiencing nonconformance.

Prevention cost: Cost incurred to avoid defects or nonconformance.

Appraisal cost: Cost incurred to assess whether requirements are being met.

Internal-failure cost: Cost of nonconformance detected before delivery.

External-failure cost: Cost of nonconformance detected after delivery.

Measurement boundary: Defined organizational, product, process, and time scope of a measure.

Data dictionary: Controlled description of fields, codes, meanings, and permitted values.

Event ID: Unique identifier that links an operational event to evidence and accounting records.

Cost centre: Organizational or process unit to which costs are assigned.

Valuation rule: Approved method for converting an operational event into monetary value.

Standard cost: Pre-established cost used for consistent and timely measurement.

Accrual: Recognition of an incurred cost before the related invoice or final amount is recorded.

Reconciliation: Structured comparison of records to identify and explain differences.

Cut-off: Assignment of an event or cost to the correct reporting period.

Traceability: Ability to follow a reported amount back to its source evidence.

Normalization: Expression of cost relative to a base such as sales, units, or conversion cost.

Avoidable cost: Cost that can reasonably be eliminated by a decision or improvement.

Net present value: Discounted value of future incremental cash flows less initial investment.

Data steward: Person responsible for data definitions, quality, and controlled use.

Process mining: Analysis of event logs to understand and compare actual process flows.

Review Questions

Short Answer Questions

1. What are the four conventional categories of quality cost?
2. Why must the measurement boundary be stated in a quality-cost report?
3. Distinguish actual cost, standard cost, and estimated cost.
4. What is the purpose of reconciling a quality database with the general ledger?
5. Give two examples of cross-system validation checks.

Long Answer Questions

1. Explain how a quality-cost event should progress from occurrence to management report, identifying the controls required at each stage.
2. Discuss the design of a coding structure that supports both operational analysis and financial accounting.
3. Evaluate the advantages and limitations of using quality cost as a percentage of sales.
4. Explain the roles of event owners, process owners, finance owners, data stewards, and internal assurance.
5. Discuss the ethical and governance risks created when quality-cost measures are linked to performance targets.

Analytical / Application Questions

1. A plant reports $90,000 of prevention cost, $150,000 of appraisal cost, $260,000 of internal-failure cost, and $200,000 of external-failure cost on sales of $14,000,000. Calculate total quality cost and the quality-cost ratio. Interpret the result and identify two additional measures needed before making a decision.
2. A quality system reports $75,000 of failure cost while the ledger reports $68,000. Finance identifies $3,000 of timing differences and $1,500 of supplier recoveries recorded only in the ledger. Calculate the unexplained difference using the reconciliation convention in this chapter and propose three investigation steps.
3. Design a monthly reconciliation and reporting process for a multi-site organization in which rework is recorded in a manufacturing execution system, warranty in a customer system, and costs in separate ledgers. Specify data owners, validation rules, escalation thresholds, and report outputs.

Multiple Choice Questions with Answers

Question 1

Which category includes the cost of customer warranty claims?

A. Prevention cost

B. Appraisal cost

C. Internal-failure cost

D. External-failure cost

Correct Answer: D. External-failure cost

Question 2

A plant records prevention cost of $80,000, appraisal cost of $120,000, internal-failure cost of $200,000, and external-failure cost of $100,000. What is total quality cost?

A. $300,000

B. $400,000

C. $500,000

D. $600,000

Correct Answer: C. $500,000

Question 3

If total quality cost is $500,000 and sales are $10,000,000, what is the quality-cost ratio?

A. 2%

B. 5%

C. 10%

D. 20%

Correct Answer: B. 5%

Question 4

Which control most directly detects whether the same quality event has been counted twice?

A. Uniqueness check

B. Currency conversion check

C. Access review

D. Budget variance review

Correct Answer: A. Uniqueness check

Question 5

Who is primarily responsible for validating account mapping and ledger treatment?

A. Customer-service representative

B. Finance owner

C. Equipment operator

D. External customer

Correct Answer: B. Finance owner

Question 6

A rework event uses 10 labour hours at $30 per hour and $200 of material. What is the measured rework cost, excluding other costs?

A. $230

B. $300

C. $500

D. $600

Correct Answer: C. $500

Question 7

Which statement best describes a reconciliation?

A. It replaces source evidence with management judgement.

B. It compares records and explains timing, scope, classification, or other differences.

C. It guarantees that all quality costs are avoidable.

D. It converts every operational record into a journal entry.

Correct Answer: B. It compares records and explains timing, scope, classification, or other differences.

Question 8

Why should supplier recoveries generally be shown separately from gross failure cost?

A. To prevent the gross exposure and recovery from being obscured by netting.

B. To eliminate the need for supplier records.

C. To ensure every recovery is classified as prevention.

D. To avoid reconciling the quality system with finance.

Correct Answer: A. To prevent the gross exposure and recovery from being obscured by netting.

Question 9

Which measure is most likely to be a lagging quality indicator?

A. Training completion rate

B. Corrective-action approval time

C. Warranty claims

D. Process-design review completion

Correct Answer: C. Warranty claims

Question 10

What is a principal governance risk when departments are rewarded for low reported failure cost?

A. Improved traceability is guaranteed.

B. Departments may suppress or misclassify nonconformances.

C. Ledger reconciliation becomes unnecessary.

D. Prevention costs automatically become zero.

Correct Answer: B. Departments may suppress or misclassify nonconformances.