PracticeISCFree practice exam

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.

The ruleUse one authoritative vendor master with restricted maintenance, approvals, and duplicate checks. Govern ownership, changes, synchronization, and validation across connected systems; an MDM hub is one option, not a requirement.

Try one first

A mid-size company uses a separate CRM for sales (customer profiles and credit terms) and an ERP for finance (accounts receivable and billing). CRM updates are transferred to the ERP via a nightly batch interface. Finance has begun finding duplicate customer records and mismatched billing addresses in the ERP, causing incorrect invoices and collection delays. Current controls are: (1) nightly control-total comparisons for the batch transfers, (2) weekly exception-report reviews, and (3) ERP audit logs. Management asks IT which combination of changes would most effectively reduce the risk of inconsistent customer master data across systems. Which response is most appropriate?
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).

Sort it

Controls the source

Does Green establish authoritative vendor data or prevent conflicting records before use?

Finds or fixes errors later

Does Green detect or correct vendor-master errors only after records have been created or changed?

Leaves the source problem unresolved

Do competing, uncontrolled, or incorrect vendor records remain available for processing?

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

8 more, each from a different angle

0 of 8 answered · 0 correct

Question 2

Marlow Co. replaces separate purchasing, receiving, and accounts payable applications with an enterprise system that uses one shared database. Purchasing enters approved purchase orders, receiving records goods receipts in the same system, and accounts payable can view both records before processing vendor invoices. Assuming the system is properly configured, which conclusion is best?
Hint

Focus on what a shared enterprise database changes about data flow between related modules, not on whether basic accounting controls disappear.

Question 3

A distributor uses separate applications for order entry, inventory, shipping, and billing. Employees in each department manually re-enter the same customer order data into their own application. Management has found that quantities billed sometimes differ from quantities shipped, and available inventory is not updated when a sales order is entered. Assume each application processes its own inputs correctly. What is the primary issue with the current information system?
Hint

Focus on the system feature that would eliminate repeated entry of the same transaction across departments.

Question 4

A multinational manufacturing company is implementing a single ERP across five subsidiaries to centralize accounting, produce near‑real‑time consolidated financials, reduce manual reconciliations, and strengthen segregation of duties. After go‑live, some local processes will remain outside the ERP. Which out‑of‑system scenario most clearly prevents the company from achieving those objectives?
Hint

Focus on which external process becomes the authoritative record and forces recurring manual journal entries or reconciliations that the ERP cannot enforce.

Question 5

Lakeview Manufacturing is replacing separate sales, purchasing, inventory, and general ledger applications with an enterprise resource planning (ERP) system. During testing, the same vendor appears under multiple IDs, item codes differ between purchasing and inventory, and managers receive different margin reports depending on which module they use. Assume access security, backup procedures, and user training plans are otherwise adequate. What is the primary issue Lakeview should address before go-live?
Hint

Focus on what an enterprise system needs in order to produce one consistent set of transactions and reports across departments.

Question 6

Green Co. uses an integrated ERP system with a vendor master file and separate accounts payable transaction records. On June 20, Green receives a properly verified and approved request to change Vendor T's ACH banking information for all future payments. No invoice amounts, terms, or due dates change. Under sound enterprise and accounting information system design, what is the correct treatment?
Hint

Focus on whether the changed information is standing data about the vendor or data specific to one payable transaction.

Question 7

Company L, a mid-sized manufacturer, currently runs several best-of-breed systems (accounts payable, accounts receivable, inventory management, production scheduling, and payroll), each with its own database and interfaces. Management is evaluating replacing these with an integrated enterprise resource planning (ERP) system that centralizes finance and operational data. Which of the following best describes a typical advantage of adopting an integrated ERP versus maintaining multiple best-of-breed point solutions?
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.

Question 8

A company is implementing an enterprise resource planning (ERP) system that integrates sales, inventory, purchasing, and the general ledger into one shared database. The controller says this integration should eliminate most data problems because every module will use the same information. Which condition is the best exception or limitation to the controller's statement?
Hint

Focus on what a shared database improves versus what it does not automatically prevent.

Question 9

A growing company uses separate applications for sales, inventory, purchasing, and the general ledger. Management reports that customer and product data are entered in multiple systems, departments often produce conflicting reports, and accounting staff spend significant time reconciling differences at month-end. Which action is the best way to address the underlying problem?
Hint

Focus on the difference between fixing reporting symptoms and fixing the underlying source-data structure.

Drill all 170 Enterprise and accounting information systems questionsMixed across every rule in the topic, so you have to spot which one applies. That is how the exam does it.

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

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.