Offshore BookkeepersPowered by StealthAgentsPlan my role

Payroll & Tax

Contractor classification evidence in bookkeeping: a review protocol

A source-backed protocol for assembling, testing, and escalating the worker-status evidence that sits behind contractor payments, without turning bookkeepers into legal decision-makers.

A source-backed protocol for assembling, testing, and escalating the worker-status evidence that sits behind contractor payments, without turning bookkeepers into legal decision-makers.
Table of contents

Key takeaways

  • Worker status depends on facts and control, not on the payment label or the contract title.
  • Build a reproducible population of non-payroll payees and test each file against the same evidence codes.
  • Route every conflicting or incomplete file to the owner and tax adviser with a dated record of the decision.

Research question and scope

This report asks how a bookkeeping team should maintain and review the evidence behind a decision to treat a worker as an independent contractor. The unit of review is one worker relationship for one payment year. The output is an evidence file, a list of unresolved status questions, and a record of who owns each decision. The protocol is a documentation control, not a legal opinion.

The scope covers the payment records, contract terms, invoices, and supporting correspondence that a bookkeeping team can observe. It does not cover the full legal analysis of worker status or the final tax treatment. Those decisions belong to the business owner and a qualified tax or legal adviser. The review is designed to make the available facts visible before a filing or an audit request arrives.

A bookkeeping team sees the payment side of a contractor relationship long before anyone asks whether the relationship was structured correctly. The team can see invoices, payment timing, tax forms, and the vendor master. It usually cannot see the degree of supervision, the right to assign work, or the reason a worker was engaged. That gap is the reason a documentation protocol is useful.

The protocol does not try to close the gap with assumptions. It defines what evidence the team can collect, how to test it, and when to stop and escalate. The result is not a status determination. It is a file that shows what the business knew, what it recorded, and what remains unresolved. That file is more useful to an owner than a bookkeeper's private opinion.

Why the ledger cannot decide worker status

A vendor ledger records a payment and a tax form, not the degree of control behind the relationship. Two workers with identical invoice amounts can have very different facts about supervision, schedule, tools, and exclusivity. The ledger cannot show whether the business had the right to direct how the work was done. A review that treats the payment type as proof of status will miss the risk.

The IRS explains that worker status depends on the facts of each case and on the right to control the result versus the details of the work. The DOL describes misclassification as treating an employee as an independent contractor under the FLSA. Those are related but separate tests, and a bookkeeping team should not collapse them into one label. The evidence file should preserve facts and route the question rather than assert a conclusion.

Define the worker and payment population

Start with a complete list of payees that received payments outside payroll, including contractors, consultants, and sole proprietors. Reconcile the list to the accounts payable ledger, the bank, and the tax-reporting file. Exclude reimbursements and true vendor purchases only when the evidence supports the exclusion. Record the period, the payment total, and the source of each list. Keep the extraction query and the date it ran so the next review can reproduce the same population.

Group payees by relationship rather than by name alone. A single person may have two payee records, one for consulting and one for expense reimbursement. A company may pay the same individual through two entities. Keep a stable worker identifier and a note on the legal name. The population should be reproducible from the source reports without relying on memory.

Collect the facts that are observable

For each worker, collect the contract, the statement of work, invoices, payment history, and evidence of who controlled the schedule and the method. Look for job descriptions, approval emails, tool access, and training records. Record whether the worker could refuse work, work for others, or send a substitute. These facts are more useful than a generic questionnaire because they come from the actual relationship.

Do not ask the bookkeeper to decide whether the facts add up to employee status. Ask the bookkeeper to record what the file shows and what it does not show. A missing contract is an evidence gap, not proof that no contract exists. A contract that calls the worker a contractor is also not proof of status. The review should distinguish a document title from the underlying facts.

Classify indicators with a shared code set

Use a small code set so two reviewers describe the same fact the same way. Useful codes include written agreement, invoice practice, schedule control, training or instruction, tool ownership, exclusivity, substitution, and reimbursement. Add a code for unable to determine. Define each code in the workpaper and give one example so the meaning does not drift. A short guide at the top of the workpaper is enough when every reviewer applies it consistently.

Apply the codes only to facts that are in the file. A reviewer should be able to open the linked document and see the basis for the code. If the basis is a conversation, record the date, the person, and the question asked. Codes that cannot be traced back to evidence should be marked as provisional rather than treated as findings.

Measure agreement and unresolved cases

Count how many workers have a complete file, a partial file, or no file. Count how many have at least one fact that points in a different direction from the payment label. Report the counts with the population size and the review period. Do not turn the counts into a legal conclusion, because they measure documentation coverage and review attention rather than tax status.

Have a second reviewer re-code a sample of files without seeing the first reviewer's codes. Compare the results and discuss every disagreement. A disagreement often means the code definition is unclear or the evidence is ambiguous. Record the resolution and update the code set when the same ambiguity repeats. This is how the review improves instead of becoming a one-time exercise.

Test the payment and reporting trail

Tie each worker's payments to the ledger, the bank, and the tax form. Check that the tax form matches the legal name and tax identifier used in the payment file. Check that the payment total on the form agrees to the ledger for the reporting year. A mismatch may be a data-entry problem, a duplicate payee, or a payment made through another entity. Route it to the owner rather than correcting the form informally.

Check whether the worker was also paid through payroll in the same period. A person can be an employee for one role and a contractor for a separate business, but the file needs to explain the separation. Look for reimbursements that were run through accounts payable when the worker is otherwise on payroll. The payment trail should show the relationship, not just the amount.

Set escalation and correction boundaries

Escalate any file with a status question, a conflicting fact, or a missing contract to the business owner and the tax adviser. The bookkeeper can prepare a summary, but the owner decides whether to change the treatment, file a corrected form, or seek a determination. Record the date of the referral and the response. Do not let an open question sit in a review queue without an owner.

If a correction is approved, document the original entry, the new entry, the reason, and the approval. Keep the old record rather than overwriting it. Update the vendor master and the tax-reporting file only after the approval. The vendor master change verification discipline applies here because a status change affects payment, reporting, and future onboarding. The file should also state whether a tax form needs an amendment or only a note for the next filing cycle.

Review the protocol's own evidence

The protocol needs its own quality check. Count how many files have a linked contract, a payment tie-out, and a completed code sheet. Check whether the reviewer comments explain the basis for each uncertain code. A file that cannot be reconstructed by a second reviewer is not finished, even if the payment label looks correct. Record the check as part of the workpaper rather than as an informal conversation.

Review the code set after the first full cycle. Remove codes that no reviewer used, split codes that caused repeated disagreement, and add a code when a new fact pattern appears. Keep a version date so later files can be read in the context of the definitions used at the time. This small maintenance step keeps the protocol useful after the first busy season.

Document limitations and repeat the review

State clearly that the review covers documentation and payment evidence for a defined period. It does not cover every worker, every state test, or every fact that a regulator might examine. It does not provide legal advice or a determination. The owner should know which files were reviewed and which were outside the sample. A limitation written down is safer than an implied assurance.

Repeat the review when a worker's contract, payment pattern, or role changes. Also repeat it before a large filing season or after a new entity starts paying the same worker. GAO's internal-control standards support documented review and assigned responsibility, and the protocol uses that discipline without claiming to settle the legal question. The payroll journal preparation controls and vendor records and 1099 support workflows both benefit from the same evidence discipline.

Evidence map

These notes connect bounded statements on this page to the listed public sources. They do not turn operational interpretations into empirical findings.

  1. The IRS states that worker status depends on the facts of each case and on the right to control the result rather than the details of the work, so the protocol records facts instead of relying on a payment label.
  2. The IRS provides Form SS-8 for firms or workers to request a worker-status determination, which the protocol treats as a formal escalation route rather than a bookkeeping decision.
  3. The DOL explains that misclassification occurs when an employer treats an employee as an independent contractor under the FLSA, so the review separates federal labor questions from payment processing.
  4. The SBA notes that a contractor found to meet the legal definition of an employee can create back taxes and penalties, which is why unresolved files are escalated to the owner and tax adviser.
  5. GAO internal-control standards support documented review and assigned responsibility, which the protocol applies to evidence handling rather than to legal classification.

Listed sources

  1. IRS, Independent Contractor Defined
  2. IRS, About Form SS-8
  3. U.S. Department of Labor, Misclassification of Employees as Independent Contractors Under the FLSA
  4. U.S. Small Business Administration, Manage your business
  5. U.S. GAO, Standards for Internal Control in the Federal Government

Related research