Choose vendor master data support for supplier intake and controlled change packets. Choose data quality support for written field checks across records. Neither role approves suppliers, changes tax or bank details, merges records, runs bulk actions, or administers a live system.
The roles overlap on source checks and exceptions. The useful split is the record domain and the decision at stake, not a promise that either assistant can fix data without review.
Log intake, check required fields, list missing documents, show possible duplicates, and prepare change packets. Supplier approval, tax, bank, payment, identity, merge, and activation decisions stay with authorized owners.
Compare approved sources with field rules, flag missing or unsupported values, prepare correction packets, and maintain an exception queue. Owners retain controlled corrections, definitions, bulk actions, access, retention, and system administration.
Use the smaller lane that matches the next repeatable job. A title cannot make a vague source or a controlled action safe to delegate.
A supplier request, supplier document packet, possible vendor duplicate, or controlled supplier change is the immediate work.
A written field rule, source conflict, missing value, duplicate candidate, or exception queue spans controlled records.
Does the next review start with a supplier record or a field rule across records?
Required supplier fields, approved documents, an existing-record search, and a named supplier, procurement, tax, or finance owner.
A written field rule, approved source type, current value, proposed value, report view, and a named data owner.
Stop when the source is missing, conflicts, or does not support the proposed value.
A missing supplier document, conflicting intake detail, possible supplier duplicate, or controlled supplier-change request.
A malformed field, unsupported value, duplicate candidate, report exception, or correction packet that needs review.
Preserve the difference. Do not resolve it by guessing or changing a live record.
Supplier approval, activation, legal identity, tax treatment, bank or remittance change, merge, deactivation, and payment release.
Controlled corrections, merges, deletes, imports, exports, bulk edits, definitions, permissions, retention, reporting conclusions, and administration.
A clean packet does not transfer authority over a controlled record or business decision.
The supplier-data, procurement, tax, finance, or authorized data owner reviews the packet before a controlled supplier action.
The authorized data owner and relevant business or system owner review the source, proposed value, held action, and exception.
Name the reviewer before the first live queue is assigned.
Use a named account with MFA and only the supplier records and fields needed for one queue. Keep tax, bank, payments, merges, and administration locked.
Use a named account with MFA and only the view, records, and fields needed for one documented check. Keep exports, bulk actions, recovery, and administration locked.
An authorized owner approves permissions, review dates, and removal steps.
A source-linked intake register, missing-document note, duplicate comparison, change packet, or exception queue with an owner and next check.
A field-check sheet, current and proposed value, source link, duplicate comparison, exception queue, or approved report refresh.
Expand only when the reviewer can see the source, held action, and next decision without rebuilding the trail.
Choose vendor master data support when the first job is checking required fields, listing missing documents, searching existing supplier records, and preparing a controlled packet. The owner still decides whether evidence is acceptable, whether a supplier is approved, and whether a master record changes.
Choose data quality support when the job starts with a written field rule, approved sources, a current value, and a proposed correction for review. The assistant can preserve the conflict and prepare the evidence. The owner decides the rule, correction, merge, and any production action.
Split the request before assigning it. Supplier intake and change-packet preparation belong in the vendor-master lane; repeat source-rule checks across supplier and other records belong in the data-quality lane. Do not let the word cleanup hide tax, bank, merge, bulk-action, or permission decisions.
Both roles can organize approved evidence, flag conflicts, draft follow-up, and make review easier. Owners retain supplier approval, tax, bank, payment, merges, controlled corrections, data definitions, access, retention, reporting conclusions, and system administration.
"Use the approved source, prepare the named record or field check, and stop when the request changes supplier approval, tax, bank, payment, merge, controlled value, data definition, permission, retention, or system setting. Link the evidence and route the question to the named owner."
Start with one narrow queue and a small review sample. Add an adjacent lane only after the owner can inspect the first evidence trail without reconstructing it.
Use required fields, documents, a duplicate search, limited access, and owner review before supplier-record work expands.
Read the vendor master role guideData-control pathUse field rules, approved sources, correction packets, exception records, and owner review before the queue expands.
Read the data quality role guideSource preparationUse this function path when the first job is collecting approved information before a controlled record or field review.
Read the data-entry support guideReview evidenceCheck source accuracy, held actions, correction notes, and the owner handoff before adding records or access.
Open the work-sample sheetNo. Vendor master data support prepares supplier intake, document checks, duplicate candidates, and controlled supplier-change packets. Data quality support prepares source checks, field-rule comparisons, correction packets, duplicate candidates, exception queues, and approved report refreshes across controlled records.
Possibly, after each lane has its own approved source, limited access, held actions, and named review path. Start with the smaller documented lane instead of treating supplier approval, controlled corrections, and system access as one generic cleanup task.
No. The assistant can prepare a side-by-side comparison and preserve the evidence. An authorized owner decides whether records remain separate, merge, redirect, deactivate, or are deleted.
Give a named account with MFA and only the records, view, and fields needed for one documented queue. Keep bank, tax, payment, broad exports, bulk actions, recovery controls, administration, and permission changes with authorized owners.
These sources inform the task examples and access caution. They do not standardize job titles, authorize controlled changes, or prove a staffing outcome.
Use OutsourcedU to write the role, SOPs, onboarding steps, and weekly review before you hire more people.