PracticeISCFree practice exam

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.

The ruleWhen AR reports aggregate balances by customer ID, duplicate customer records can fragment balances and undermine aging and allowance estimates. Duplicate master records alone do not establish duplicate sales postings.

Try one first

Company X migrated customer master data into a new ERP but failed to standardize customer IDs and address formats, producing many duplicate customer records and inconsistent IDs across order entry, billing, and collections. Month‑end accounts receivable (AR) balances, the AR aging report, and estimates of the allowance for doubtful accounts are generated by aggregating balances by customer ID, and no deduplication or reconciliation was performed before month‑end. Which of the following is the most likely direct consequence of these data‑management failures?
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.

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?

  1. 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.

  2. 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.

  3. Accept the aging because ETL completed and row counts reconcile.

    Wrong Successful transfer does not establish that separate IDs belong to separate customers.

  4. 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.

  5. 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.

5 more, each from a different angle

0 of 5 answered · 0 correct

Question 2

A company keeps customer information in separate sales, billing, and shipping systems. In 20X6, several customers were set up more than once under slightly different names, and invoices were mailed to outdated addresses even though another system had the correct address. Management has confirmed that the problem is not unauthorized access, system downtime, or data loss. Which is the primary issue?
Hint

Focus on what kind of problem is actually described: confidentiality, availability, record lifecycle, or consistency of core data across systems.

Question 3

Before implementing a new ERP system, Rowan Co. migrated its legacy inventory master data without removing duplicate item records or standardizing units of measure. Assume system access, backup, and disaster recovery controls did not change. Which effect is most likely after go-live?
Hint

Ask what happens when flawed master data is moved into a new system without cleansing or standardization.

Question 4

A manufacturer implemented a master data management hub for customer data. In the hub, customer legal name and tax ID become read-only after data steward approval. Address and NAICS industry code, however, are still maintained independently in the CRM, billing system, and service platform. Each night, the hub replaces its stored address and industry code with the value from whichever source system has the most recent update timestamp, with no survivorship rules or conflict review. Management uses tax ID and legal name from the hub to identify customers for credit review, and uses the hub's industry code for concentration-risk reporting. Assume all interfaces run successfully and no unauthorized access occurs. What is the most likely consequence of this design?
Hint

Separate the attributes that are actually governed from the attributes that are only centralized. Then ask which downstream use depends on which attribute.

Question 5

BlueLine Co. is preparing consolidated statutory financial statements for Year 1. Each of its three business units maintains separate customer and billing systems; there is no enterprise-wide unique customer identifier. Data is consolidated nightly into a centralized data warehouse via ETL. The ETL applies fuzzy matching to deduplicate customers and invoices, but matching rules vary by business unit, are not consistently documented or audited, and the accounting team identified duplicate invoices during preliminary reconciliations. Data quality metrics report 92% completeness for required customer attributes, but only a 60% match rate across business-unit customer records. Data lineage documentation exists for only one business unit; the others lack source-to-target mappings. A written data retention policy exists but is not consistently enforced. The Controller asks whether the centralized data warehouse is currently reliable enough to be used as the primary source for consolidated statutory financial reporting. What is the best conclusion?
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).

Question 6

A company allows its sales, shipping, and billing departments to each maintain separate customer master files. The company does not reconcile those files and does not use a single authoritative customer record. Which consequence is most likely?
Hint

Focus on what usually happens when important master data is stored in multiple places without reconciliation.

Drill all 170 Data management questionsMixed across every rule in the topic, so you have to spot which one applies. That is how the exam does it.

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

All Data management practice →

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.