Choose accounts payable support for vendor invoices, match notes, approval packets, due-date queues, coding questions, and invoice exceptions. Choose data quality support for written field checks, source conflicts, proposed corrections, duplicate candidates, report exceptions, and import-preparation records. Both roles prepare the evidence; authorized owners decide what is approved, changed, paid, imported, or released.
Choose a small lane a reviewer can inspect before assigning a broad support title.
Start with the vendor invoice, approved purchase or receiving records, match notes, due dates, approval packets, coding questions, and held exceptions. The output is a factual review packet, not an approved invoice or payment.
Start with a written field rule, source conflict, missing value, duplicate candidate, or import exception. The output is a source-backed correction packet, not a live record change or approved import.
Keep preparation work traceable from source record to named reviewer.
The table scrolls sideways on small screens.
| Factor | Accounts payable support | Data quality support | Owner check |
|---|---|---|---|
| Work starts with | A vendor invoice, match record, due date, coding question, or invoice mismatch. | A written field rule, source conflict, missing value, duplicate candidate, report exception, or import exception. | Is the next review about a bill or a controlled-record check? |
| Prepared output | An invoice packet, match note, due-date queue, coding-question record, or invoice-exception record. | A field-check sheet, correction packet, duplicate comparison, exception queue, approved report refresh, or import-exception record. | Can the reviewer see the source, held action, owner, and next check? |
| Where the work meets | Can flag a supplier or invoice record issue and preserve the evidence for finance review. | Can prepare a repeatable field-rule check or correction packet linked to an invoice workflow. | Link the records where needed, but keep invoice decisions and controlled-record decisions with their named owners. |
| Hold when | Approval, payment, coding, tax, accounting treatment, supplier action, or exception outcome is unclear. | A source, field rule, mapping, duplicate outcome, permission, or downstream effect is unclear. | Hold the item rather than infer a decision. |
| Not this role | Invoice approval, payment scheduling or release, supplier terms, bank details, tax treatment, coding overrides, credits, disputes, or accounting decisions. | Controlled corrections, merges, deletions, mappings, imports, exports, bulk edits, permissions, retention, reporting conclusions, or production changes. | Hold any task that changes money, a supplier record, a controlled value, access, or a final decision. |
Use accounts payable support when the reviewer needs the invoice, approved purchase or receiving sources, a match note, due date, named approver, and held question in one packet. The finance owner decides approval, coding exceptions, and payment.
Use data quality support when the reviewer needs the written field rule, approved source, current value, proposed value, and held question together. The authorized data owner decides the correction, merge, mapping, or production action.
Split the request at the decision point. Keep the invoice, match, coding, approval, and payment question in the accounts-payable lane. Put a field-rule check, duplicate comparison, correction packet, or import mapping question in the data-quality lane.
Stop and route anything that could approve or release an invoice, move money, alter supplier terms or bank details, change coding or tax treatment, change a controlled value, merge records, run an import, change access, or bypass a control.
"Use the approved source and prepare the named invoice packet or data-check record. Keep unknowns, conflicts, and held actions visible. Stop when the request affects invoice approval, payment, coding, tax, accounting treatment, supplier action, a controlled value, merge, mapping, import, overwrite, deletion, permission, retention, report conclusion, or production change. Link safe evidence and route the question to the named authorized owner."
The first samples should make it easy to inspect the source trail, exceptions, and review process.
Sort bookkeeping, invoice support, payroll administration, and accountant review before you write a role brief.
Review finance supportInvoice evidenceKeep the invoice, approved source, coding question, held action, reviewer, and recheck together before the finance owner decides.
Open the coding logData exceptionRecord the field rule, source, current and proposed value, held action, owner, and recheck without running the import.
Prepare an import exceptionReview evidenceCheck source accuracy, held actions, correction notes, and the owner handoff before adding records or access.
Open the work-sample sheetNo. Accounts payable support prepares vendor-invoice, match, approval, coding-question, and exception evidence. Data quality support prepares written field checks, source comparisons, correction packets, duplicate comparisons, exception queues, and import-preparation records. Both roles prepare work for review.
No. The role can organize approved source references and hold exceptions. The authorized finance owner decides invoice approval, coding exceptions, payment scheduling, and release.
No. The role can prepare a source-backed correction or duplicate comparison. An authorized owner decides whether a controlled value changes, records merge or remain separate, a mapping changes, or an import runs.
Prepare two linked records. Accounts payable support can organize invoice evidence and held finance questions; data quality support can prepare the field-rule check or correction packet. Each owner keeps their own decision point.
Accounts payable support can record the source, mismatch, current state, and next reviewer. The named finance owner decides whether to approve, override, dispute, or hold the invoice.
No. Those actions move money, change a sensitive or controlled record, or create a downstream outcome. The assistant documents and routes the request; the authorized owner decides through the business's controlled process.
These sources help frame record work and account access. They do not define the job titles, authorize financial actions, or prove a staffing outcome.
Use OutsourcedU to write the role, SOPs, onboarding steps, and weekly review before you hire more people.