ISC · Information Systems and Data Management · 9 practice questions
ERP Vendor Master Data Governance: One Controlled Source
An integrated ERP needs one authoritative, controlled vendor master, not competing departmental records. Below, sort vendor-master practices by whether they control the source, detect errors later, or leave the source problem unresolved.
Try one first
Hint
Ask whether each option prevents conflicting master-data updates at the source (a preventive governance solution) or only finds/fixes differences after replication (detective/corrective).
Answer D. A centralized MDM that creates a single authoritative ('golden') customer master, combined with a web-based change-request and approval workflow and role-based access controls, is a preventive governance solution that stops conflicting or duplicate updates at the source. Preventive controls reduce the chance inconsistent data is ever propagated to downstream systems. By contrast, more frequent transfers, manual reconciliations, or post-transfer merges are detective or corrective measures that only find or fix errors after they occur and therefore do not address the root governance problem.
Why not A: Why this tempts: Faster syncing and automated reconciliations reduce the time window for divergence and may appear to keep systems better synchronized. Why it fails: These are latency-reduction and detective measures, they do not establish a single authoritative source or prevent conflicting updates from being created in the CRM or ERP. Faster cycles can also increase exception volume and processing overhead without resolving governance.
Why not B: Why this tempts: Automated duplicate detection and merging can reduce visible duplicates and improve invoice accuracy over time. Why it fails: Fuzzy matching and automated merges risk false positives and negatives and can erroneously consolidate distinct customers. This is a corrective, symptom-focused fix that does not create a single source of truth, so inconsistencies and governance issues will likely recur.
Why not C: Why this tempts: Daily reconciliation and manual correction give direct oversight and can catch discrepancies before invoices go out. Why it fails: This is a detective/corrective, labor-intensive approach that is prone to human error, delays, and scalability issues. It fixes discrepancies after they occur rather than preventing inconsistent master-data entries at the source.
Sort it
Does Green establish authoritative vendor data or prevent conflicting records before use?
Does Green detect or correct vendor-master errors only after records have been created or changed?
Do competing, uncontrolled, or incorrect vendor records remain available for processing?
| Item | Goes to |
|---|---|
| Green uses one shared ERP vendor master. Only authorized maintainers can submit changes, which require independent approval. | Controls the sourceRelated modules use the same approved record rather than separately maintained departmental versions. |
| Green changes its procurement interface from nightly to hourly but retains independently maintained vendor tables. | Leaves the source problem unresolvedFaster transmission reduces delay, not conflicts between competing vendor records. |
| Green's controller reviews logged vendor bank-detail changes each week. | Finds or fixes errors laterReview can identify improper changes, but only after the master record has changed. |
| Green blocks new vendor setup until an automated duplicate check and approval are complete. | Controls the sourceThe control addresses duplicate creation before the new record can feed purchasing or payments. |
| Green treats a purchasing spreadsheet as the authoritative bank-detail list and manually overrides ERP payment batches from it. | Leaves the source problem unresolvedThe spreadsheet competes with the ERP master, leaving payment instructions dependent on repeated manual exceptions. |
| Green designates the ERP vendor master as authoritative and requires its procurement front end to synchronize and validate vendor codes before transmission. | Controls the sourceThe connected tool follows governed master data instead of independently defining vendor identity. An MDM hub is not required. |
| Green compares purchasing and accounts payable vendor files at month-end and manually corrects differences. | Finds or fixes errors laterThe comparison detects inconsistencies after separate records have already been available for processing. |
| Before conversion, Green cleans duplicate vendors and maps departmental vendor codes to one standardized set. | Controls the sourceStandardized identities prevent legacy coding conflicts from entering the integrated system. |
| Green stores an incorrect bank account in its shared vendor master, and the error remains undetected before payment. | Leaves the source problem unresolvedThe shared record can consistently supply wrong bank details to downstream payment processing. |
| Green uses an MDM hub with one golden vendor record, approved change requests, and restricted direct edits. | Controls the sourceThe hub governs changes before distributing authoritative vendor data to connected systems. |
| Green runs a nightly routine that identifies and merges suspected duplicate vendors, with later review of merge logs. | Finds or fixes errors laterThe routine cleans existing records rather than preventing duplicate setup before use. |
| Green limits edits to purchasing staff but keeps unsynchronized vendor files in purchasing and accounts payable. | Leaves the source problem unresolvedRestricting editors does not make approved changes reach both files or eliminate competing records. |
Key points
- Remember: A shared vendor master spreads the same data everywhere, including errors.
- Control vendor creation before purchases and payments use the record.
- An external procurement tool can remain if it uses or validates against authoritative vendor data.
- Standardize vendor codes before conversion; integration does not resolve conflicting definitions.
How the exam traps you
- Choose faster transfers between conflicting vendor files. Fix authoritative ownership and validation first. Faster transfers do not resolve conflicting records.
- Treat reconciliation or duplicate cleanup as the preventive solution. Check for duplicates and approve changes before records become available for use.
- Assume every connected system requires an MDM hub. A controlled ERP master with governed synchronization and validation can also establish authoritative data.
Question 2
Hint
Focus on what a shared enterprise database changes about data flow between related modules, not on whether basic accounting controls disappear.
Answer A. An integrated enterprise system with a common database allows transaction data entered by one function to be available to other modules without reentry, improving consistency. That makes processes like three-way matching (purchase order, receiving report, vendor invoice) easier and often more timely to perform. Integration helps efficiency and control but does not eliminate the need for proper matching and related controls.
Why not B: Tempting because automation reduces manual work, but matching is still needed to verify the purchase order, receipt, and invoice agree before payment. A shared database makes the control easier to perform, not unnecessary.
Why not C: This confuses access control with data design. Enterprise systems typically use a shared vendor master; preventing unauthorized changes is handled with access controls and approval workflows, not by creating duplicate vendor files that increase inconsistency.
Why not D: This reflects outdated batch-processing thinking. A key benefit of integration is more timely transaction visibility and processing across modules rather than delaying updates until period-end.
Question 3
Hint
Focus on the system feature that would eliminate repeated entry of the same transaction across departments.
Answer D. The facts indicate a data integration problem: the same order is entered multiple times into separate systems, producing inconsistent transaction records and delayed inventory updates. An integrated enterprise system with a shared database would ensure related functions read and update the same underlying data, reducing duplicate entry and reconciliation errors. Because each application is described as processing inputs correctly, the root cause is the lack of a unified data source rather than a single application failure.
Why not A: Encryption protects data confidentiality during transmission, but the stem provides no evidence of interception or confidentiality breaches. The errors arise from duplicate manual entries and lack of a shared database, so encryption would not address the inconsistency.
Why not B: This is tempting because multiple departments handle the order process, but the stem gives no indication of incompatible duties assigned to the same person, fraud, or unauthorized transactions. The issue described is inconsistent data across independent systems, not poor role assignment or control of duties.
Why not C: This distractor seems plausible since inventory isn't updated when orders are entered, suggesting a timing issue. However, even with real-time processing, manual re-entry into separate applications can still create mismatches; the fundamental problem is missing integrated data rather than processing latency alone.
Question 4
Hint
Focus on which external process becomes the authoritative record and forces recurring manual journal entries or reconciliations that the ERP cannot enforce.
Answer A. Option A is correct because when uncontrolled spreadsheets remain the authoritative source and are used to create recurring manual journal entries, the ERP cannot enforce access controls, validation, or consistent transaction lineage. That arrangement preserves manual reconciliation work, prevents reliable near‑real‑time consolidation, and weakens segregation of duties since critical accounting records are created and modified outside the centralized system.
Why not B: This is tempting because key payroll calculations remain off‑system and inaccessible, which reduces visibility and auditability. It fails as the best answer because the provider still delivers summarized journal entries and remittance files into the ERP that can be posted, reconciled, and controlled centrally, so the ERP remains the transactional posting point even though underlying workpapers are external.
Why not C: This distractor tempts by invoking parallel statutory books, which can suggest fragmentation of records. It fails because the ERP is configured to maintain local ledgers and produce statutory reports from ERP transaction data, meaning the ERP stays the authoritative transactional repository and supports centralized consolidation and controls.
Why not D: This is attractive because lack of a real‑time interface reduces immediacy of data. It fails as the best answer because overnight batch imports can be automated and reconciled, allowing daily consolidation and preserving much of the ERP's control and reconciliation benefits, they undermine timeliness more than they make an external system the authoritative accounting source.
Question 5
Hint
Focus on what an enterprise system needs in order to produce one consistent set of transactions and reports across departments.
Answer B. An ERP relies on shared master data across functions, so duplicate vendor IDs and mismatched item codes will produce conflicting transactions and inconsistent reports. These symptoms indicate weak master-data governance and inconsistent coding standards. Standardizing, cleansing, and mapping master data before go-live creates a single source of truth and prevents module-level discrepancies.
Why not A: Backups are important, but the stem explicitly notes backup procedures are already adequate. The observed problems are data-consistency issues (duplicate vendors, mismatched item codes), not recoverability concerns, so more frequent backups won't resolve them.
Why not C: Allowing separate departmental codes and relying on period-end reconciliations defeats the ERP's purpose of a common data set. It leaves inconsistent master data in place and perpetuates reporting and processing discrepancies rather than fixing the root cause.
Why not D: Custom reports may change presentation but still draw from the same inconsistent master records. Without standardizing vendor and item data, reporting changes alone won't make the underlying transactions or margins consistent across modules.
Question 6
Hint
Focus on whether the changed information is standing data about the vendor or data specific to one payable transaction.
Answer B. Banking instructions are standing vendor data and belong in the vendor master file, not on individual payable transactions or in the general ledger. An approved change to vendor payment information should be made via authorized master-data maintenance so all future payments consistently use the updated details.
Why not A: Tempting because open invoices will be paid, but manually editing each transaction creates inconsistency and control problems. The bank account is vendor master data and should be maintained centrally.
Why not C: Changing payment instructions does not create an accounting event that affects balances in the general ledger. It's a data maintenance action within the ERP, not a journal posting.
Why not D: A batch override may address one payment run but relies on repeated manual exceptions and weakens controls. When standing vendor data has changed and is approved, the master record should be updated so future processing is correct.
Question 7
Hint
Focus on the typical systemic benefit of integrating modules (data centralization and reduced redundancy) and beware of absolute statements that an ERP always removes interfaces, customization effort, or control responsibilities.
Answer B. A core advantage of an integrated ERP is a unified database that reduces duplication of master data, decreases reconciliation needs, and supports more consistent and timely financial reporting across modules. This improves data integrity and provides real-time visibility compared with separate systems that require frequent interfacing and reconciliation.
Why not A: This is tempting because ERPs provide standardized modules and configuration tools, but it is incorrect: true customization for industry-specific needs can be complex and costly in ERPs; upgrades and vendor constraints can make custom work more expensive than specialized point solutions.
Why not C: Candidates may overgeneralize that one system removes all interfaces, but this is incorrect: many organizations still require third-party or industry-specific tools and therefore must maintain interfaces; the absolute phrase 'eliminates the need for any' makes this choice incorrect.
Why not D: This distractor is appealing because ERPs support role-based access, but it is wrong: segregation of duties depends on how the system is configured and monitored, an ERP does not automatically enforce SOD or remove the need for access controls and periodic review.
Question 8
Hint
Focus on what a shared database improves versus what it does not automatically prevent.
Answer C. A shared database reduces duplicate data entry and helps keep modules aligned, but it does not guarantee the data entered is correct. If master data (for example, customer or inventory records) is entered incorrectly, every module that uses that data will reflect the error, producing consistent yet inaccurate records across the system.
Why not A: This plays on an association with older systems; modern ERP platforms commonly support real-time or near-real-time processing, and integration does not inherently force batch-only processing.
Why not B: This distractor confuses integration with restricted visibility. One core benefit of ERP is that authorized users across functions can access the same underlying transaction data, not that they lose access.
Why not D: This option mistakes reporting constraints for system capability. ERP systems generally improve the ability to generate interim and up-to-date financial reports throughout the year.
Question 9
Hint
Focus on the difference between fixing reporting symptoms and fixing the underlying source-data structure.
Answer A. The fundamental problem is fragmented master data across disconnected systems, causing duplicate entry, inconsistent records, and time-consuming reconciliations. Implementing an integrated enterprise system with shared master data creates a single source of truth for customer and product information across functions. That change addresses the root cause and reduces the need for manual reconciliations and conflicting departmental reports.
Why not B: This may help detect discrepancies, but it treats the symptom rather than the cause. Reconciliations are manual, time-consuming, and error-prone and do not eliminate duplicate entry or inconsistent master data across systems.
Why not C: A BI tool can present consolidated reports, but it does not correct inconsistent source data. If master records remain fragmented, reports may still conflict or reflect inaccurate underlying data, so reporting alone does not solve the integration problem.
Why not D: Stronger approvals address authorization controls but do not create a single, consistent master data source. Adding approvals may slow processing without resolving duplicate data entry or inter-system inconsistencies.
Common questions
Does ERP integration guarantee accurate vendor master data?
No. If Green stores an incorrect bank account in its shared vendor master, downstream payments may use it. Consistency does not guarantee accuracy.
Is an MDM hub required when ERP and procurement systems both store vendor records?
No. Green can make the ERP master authoritative and require the procurement system to synchronize with or validate against it. An MDM hub is another way to govern shared records.
What control best prevents duplicate vendors in an ERP?
Restrict vendor creation to authorized users and require duplicate checks and approval before setup. Later reconciliations and merges find or fix records that already exist.
Watch it solved
A full CPA ISC task-based simulation on Enterprise and accounting information systems, worked step by step.
ISC Simulation: Mapping Controls Through Order-to-Cash 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 Enterprise and accounting information systems
- ERP Cores, Hybrid Architectures, and Best-of-Breed
- AP-to-GL Batch Recovery: Fix, Reprocess, and Reconcile
- ERP Revenue Recognition: Shipment vs. Invoice Date
- Auditing ERP Automated Controls: ITGCs and Data Conversion
- ERP Data Residency: When Local Laws Govern Deployment
All Enterprise and accounting information systems 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.