ISC · Information Systems and Data Management · 6 practice questions
How Poor Master Data Management Distorts AR Reports
Duplicate customer IDs can split one customer's receivables across records, making AR aging and allowance estimates unreliable. Below, compare responses to a customer master data problem and identify the fix that addresses its cause.
Try one first
Hint
Think about what happens when month‑end balances and allowance estimates are produced by aggregating by customer ID but the master records are duplicated and inconsistent.
Answer C. Because month‑end AR and allowance estimates are produced by aggregating balances by customer ID and no deduplication occurred, a single customer's balances can be split across multiple IDs. That fragmentation undermines accurate AR aging and allowance‑for‑doubtful‑accounts calculations, increasing the risk of misstated receivables and allowance estimates. The stem does not describe duplicate transaction postings, so revenue double‑counting is not the most direct outcome.
Why not A: This distractor is plausible, duplicate records do increase storage and maintenance effort, but it describes a secondary operational cost. The question asks for the most likely direct consequence affecting month‑end financial reporting, where AR fragmentation is more immediate.
Why not B: This option tempts because duplicates of master records might be (mistakenly) assumed to create duplicate reported amounts. It fails because double‑counting revenue requires duplicate transaction entries or flawed transaction‑level consolidation; the stem describes duplicate customer masters, not duplicate sales postings.
Why not D: This choice is tempting because fragmented records can degrade analytics that rely on a complete customer history. However, it describes an operational/credit‑risk impact rather than the most direct month‑end reporting consequence; the stem points specifically to AR aggregation and allowance calculations, making fragmentation of AR balances the primary issue.
What should you do?
The situation
Harbor Co. migrated customer records into an ERP without standardizing IDs. One customer's $10,000 receivable is split between IDs carrying $6,000 and $4,000. Month-end AR aging and allowance estimates aggregate balances by customer ID. ETL completed, and row counts reconcile, but no customer deduplication occurred. Access controls are effective, and no duplicate sales postings were found. How should the controller respond?
Validate a common customer identity, consolidate the records, regenerate aging, and reassess the allowance estimate.
Best This addresses fragmented identity at its source and checks the affected reporting outputs.
Flag the aging as unreliable and require verified customer-level reconciliation before using it for the allowance estimate.
Acceptable This limits immediate reporting risk but does not permanently correct the customer master records.
Accept the aging because ETL completed and row counts reconcile.
Wrong Successful transfer does not establish that separate IDs belong to separate customers.
Reverse $4,000 of revenue because the second customer record duplicates the sale.
Wrong The $4,000 is part of the customer's actual receivable. No duplicate sales posting was found.
Tighten access controls and leave the customer records unchanged.
Wrong Access controls are effective. Restricting access does not resolve the existing identity mismatch.
Key points
- Remember: Two IDs for one customer can split a balance without creating an extra sale.
- Successful ETL and matching row counts do not prove that customer identities are consistent.
- Access controls govern who can change records, not whether authorized records represent the same customer.
How the exam traps you
- Assuming duplicate customer records automatically double reported revenue. Distinguish duplicate master records from duplicate transaction postings.
- Treating successful ETL and reconciled row counts as proof of reliable AR reports. Verify customer identity across records before relying on customer-level aggregation.
- Tightening access controls instead of correcting customer IDs. Address master data consistency when authorized records contain conflicting identifiers.
Question 2
Hint
Focus on what kind of problem is actually described: confidentiality, availability, record lifecycle, or consistency of core data across systems.
Answer C. The scenario describes duplicate and inconsistent customer information across multiple active systems and conflicting address data, a classic master data management (MDM) problem. MDM and master-data governance establish a single source of truth and controls for creating and maintaining core entities like customer records, which would prevent duplicates and conflicting values.
Why not A: Encryption protects confidentiality of data in transit or at rest and mitigates unauthorized disclosure. It does not address duplicate records, conflicting addresses, or synchronization and governance of core data across systems.
Why not B: This may tempt candidates who associate data problems with IT reliability, but disaster recovery concerns restoring systems or data after downtime or loss. The stem rules out downtime and data loss, and the issue here is active inconsistency and duplication, not recovery capability.
Why not D: Poor retention could leave outdated records, but retention/disposal policies address lifecycle and deletion, not the creation and governance of a single, accurate customer master. The core problem is inconsistent master data across systems rather than end-of-life record handling.
Question 3
Hint
Ask what happens when flawed master data is moved into a new system without cleansing or standardization.
Answer D. Migrating poor-quality master data into a new system usually preserves those data problems. Duplicate item records and inconsistent units of measure can distort quantities, valuation, and reorder calculations, producing unreliable reports and poor ordering decisions; an ERP does not automatically fix bad underlying data.
Why not A: More historical records do not equal better quality when those records are duplicate or unstandardized. Keeping duplicate or conflicting item records typically reduces data quality and increases confusion unless the data are cleansed and governed.
Why not B: This is tempting if a candidate equates more records with better visibility. In reality, duplicate master data is a quality issue and does not reduce unauthorized-change risk, access controls and monitoring (which did not change) determine that risk.
Why not C: This reflects the common shortcut that a new system will fix dirty data. Centralizing data helps prospectively, but loaded duplicates and inconsistencies usually persist until cleaned, so reconciliations may still be required or even increase after conversion.
Question 4
Hint
Separate the attributes that are actually governed from the attributes that are only centralized. Then ask which downstream use depends on which attribute.
Answer C. The governed attributes in the hub are legal name and tax ID, and those are the fields used for credit-review entity matching. By contrast, industry code is still subject to last-update-wins overwrites from multiple source systems with no conflict resolution, so reporting based on that field can vary with source timing rather than authoritative classification. The design therefore creates stronger reliability for identity matching than for analytical classification.
Why not A: This distractor appeals to the common shortcut of equating timeliness with accuracy. Recency alone does not establish that a value is correct, especially when multiple systems can overwrite one another without survivorship rules, validation, or steward review. In this design, the overwrite process can actually reduce consistency and stability of the mastered attribute.
Why not B: This is tempting because candidates may focus on unstable address data and assume all downstream uses of customer records are equally affected. But the stem says credit review relies on tax ID and legal name, the steward-controlled attributes, while concentration-risk reporting relies on industry code, which is not truly governed. The uncontrolled field directly tied to the reporting use case makes reporting less reliable than credit review.
Why not D: This is tempting if a candidate overgeneralizes that stricter governance always slows data capture. However, the facts do not say new customer creation is blocked; they say certain attributes become read-only after approval. The clearer consequence is not missing records, but unstable non-governed attributes being treated as if they were authoritative master data.
Question 5
Hint
Look beyond a single metric like completeness, assess whether records can be consistently identified and traced across systems (unique IDs, standardized matching, and documented lineage).
Answer C. Consolidated statutory reporting depends on consistent master-data identity, standardized matching, and traceable data lineage. The absence of an enterprise-wide unique identifier, inconsistent/undocumented fuzzy-matching that produced duplicate invoices, and incomplete source-to-target mappings create material risk of misstatement. These foundational issues must be remediated (for example, enterprise MDM, standardized matching rules, documented lineage, and tested reconciliations) before the warehouse can be the primary source for statutory consolidation.
Why not A: This is tempting because centralization and a high completeness metric suggest good coverage, but completeness alone does not ensure correct linking or de-duplication across systems. Without a consistent enterprise identifier and standardized, audited matching logic (and with evidence of duplicate invoices), the risk of consolidation error remains despite 92% completeness.
Why not B: Manual reconciliation may detect some errors and can be a temporary detective control, but it is not a sustainable or sufficient substitute for fixing underlying master-data mismatches and undocumented matching logic. Statutory reporting needs reliable, repeatable, and auditable processes rather than ad hoc manual fixes.
Why not D: An unenforced retention policy is a genuine control weakness that affects audit evidence, but it is not the root cause of duplicate invoices and mismatched customer records. Enforcing retention alone would not resolve the lack of a unique identifier, inconsistent deduplication, or incomplete lineage that threaten consolidation accuracy.
Question 6
Hint
Focus on what usually happens when important master data is stored in multiple places without reconciliation.
Answer B. When the same master data is maintained in multiple places without reconciliation, duplicate records and conflicting values commonly occur. That weakens data integrity and can cause reports to show different customer information depending on the source used. A single authoritative record is a basic data management approach to reduce that risk.
Why not A: This is tempting if a candidate assumes decentralizing data means each system stores less. In practice, separate master files usually increase duplication because the same customer data is stored multiple times. The more direct consequence is inconsistent data, not lower storage use.
Why not C: This can seem reasonable because more users can update records quickly. However, independent updating without governance often leads to missing fields, conflicting changes, and duplicate records rather than better completeness. Independence without control usually hurts data quality.
Why not D: This distractor is appealing because referential integrity is a database concept tied to data management. But referential integrity does not arise automatically just because multiple departments keep data. Separate files without a unified structure or controls make consistent relationships harder, not easier, to enforce.
Common questions
How do duplicate customer IDs affect AR aging?
They split one customer's balances across separate records. Customer-level aging and the allowance estimate can become unreliable when reports aggregate by those IDs.
Do duplicate customer records mean revenue is double-counted?
No. Duplicate master records do not establish duplicate sales postings. In this scenario, the direct problem is fragmented receivable balances.
Can successful ETL fix inconsistent customer IDs?
Not by itself. ETL can transfer every source row successfully while preserving duplicate identities; validated customer matching and consistent identifiers are still needed.
Watch it solved
A full CPA ISC task-based simulation on Data management, worked step by step.
Data Quality Defects & ETL Reconciliation | CPA ISC Simulation (TBS) on YouTube
Practice ISC like the real exam
The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.
Open the free simulator →More on Data management
Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.