Skip to content

ADR 0025: Contractor Classification and Information-Return Filing

Context

Purchasing and Payables Summary needs to distinguish a supplier/payee role, worker relationship, supplier category, and information-return treatment without treating them as one vendor type.

An independent contractor is a supplier/payee, but not every supplier/payee is an independent contractor. Employees belong to payroll and W-2 processing, which remain outside the initial release. Vendor status, receipt of a W-9, an invoice, or contract wording does not by itself decide worker classification or information-return treatment.

The prospective contractor supplies IRS Form W-9, Request for Taxpayer Identification Number and Certification. The form supplies the name, address, federal tax classification, taxpayer identification number, certifications, and signature used to establish the payee tax profile. BooksPlus retains or references the W-9 as sensitive evidence; it does not file Form W-9 with the IRS.

Federal reporting thresholds, form categories, exemptions, payment-method rules, and exceptions change by tax year. Current IRS guidance illustrates why BooksPlus must not hard-code a universal $600 threshold: many covered payments moved to a $2,000 threshold for payments made during 2026, later years may be inflation-adjusted, and some categories retain different rules.

Decision

BooksPlus must not use the term “1099 employee.”

The following meanings remain separate:

Meaning Values
party role supplier_payee, employee, customer, owner_member, government_agency, financial_institution
worker relationship employee, independent_contractor, classification_under_review, not_applicable
supplier category goods_supplier, independent_service_provider, professional_service_firm, landlord, medical_provider, government_agency, utility, financial_institution, other
information-return treatment nec_candidate, misc_candidate, exempt, undetermined, foreign_payee_review, backup_withholding_required

A party may have more than one role. Worker relationship and information-return treatment are effective-dated review decisions, not permanent labels inferred from the party role.

Initial-release payee boundary

The initial boundary is a company-scoped PayeeTaxProfile linked to stable source-system and external-payee identity. It is not a general BooksPlus party master, operational vendor master, customer master, employee record, or payable subledger.

This boundary preserves the accepted rule that operational vendor detail stays outside BooksPlus while retaining the reviewed tax and reporting facts needed for support output. A later general Party domain may adopt the profile without changing its source or tax-year identity.

Worker classification

An individual labor provider may have an effective-dated WorkerClassificationRecord containing:

  • worker relationship;
  • effective dates;
  • decision date;
  • approving actor;
  • review date;
  • reason or reviewed conclusion;
  • supporting questionnaire, contract, or other Source Document references; and
  • superseded classification reference when changed.

BooksPlus must not determine worker status from a W-9, invoice, supplier category, payment account, or written contract alone. Classification under review remains visible and cannot be silently treated as independent contractor status.

Unresolved classification does not block recognition of a valid payable or recording the accounting result of an externally issued payment. It blocks contractor classification and information-return readiness and remains a visible compliance exception. BooksPlus must not omit an actual liability or payment from ledger truth because its worker classification is unresolved.

Payee tax profile

The profile may contain:

  • legal name and DBA name;
  • 1099 reporting name and address;
  • federal tax classification;
  • W-9 received date, signed date, certification status, and validation status;
  • taxpayer-identifier type, masked display value, validation status, and protected full value;
  • worker classification references when applicable;
  • supplier categories;
  • information-return treatment and MISC reporting category when applicable;
  • foreign-payee review status;
  • backup-withholding review status;
  • effective dates, reviewer, review date, and Source Document references; and
  • source-system and external-payee identity.

A vendor-level 1099 vendor checkbox is not sufficient.

Because BooksPlus must prepare an IRS filing, secure full-TIN retention is part of the initial-release scope rather than a later optional enhancement.

BooksPlus also needs a company-scoped InformationReturnPayerProfile containing the payer's legal name, reporting address, protected full and masked TIN, filing-contact information, effective dates, reviewer, and evidence. Transport credentials and TCC secrets do not belong in this profile or ordinary company configuration.

Payment-level reporting facts

Information-return treatment is determined from both the payee profile and the nature and method of each payment. Each candidate payment preserves or references:

  • posted journal-entry and Purchasing fact identity;
  • payee identity;
  • payment date and tax year;
  • payment nature and proposed reporting category;
  • gross and reportable amount;
  • payment method and payment-network classification;
  • vendor-invoice allocation when applicable;
  • exclusion or exception reason;
  • backup-withholding amount when externally supplied and posted; and
  • rule-set version used for evaluation.

Payment-card and qualifying third-party-network payments must be distinguishable from checks, ACH, and other ordinary AP payments. BooksPlus applies the tax-year rule set; it does not assume all electronic payments are reportable by a settlement entity.

Versioned tax rules

Thresholds and reporting decisions are data selected by jurisdiction, tax year, form, reporting category, payment nature, payment method, payee tax classification, and applicable exception.

Every rule set preserves:

  • stable rule-set key and version;
  • jurisdiction and tax year;
  • effective dates;
  • form and reporting category;
  • threshold and aggregation basis;
  • payee exemptions and special categories;
  • payment-method inclusion or exclusion rules;
  • backup-withholding rules used for support evaluation;
  • authoritative source reference and review date; and
  • superseded rule-set reference when replaced.

Historical support runs retain the exact rule-set version used. A later rule change must not rewrite a prior run.

Reporting and filing basis

Information-return support derives from posted ledger truth, linked Purchasing facts, payment allocations, and reviewed payee/payment classifications. Import candidates, Summary batches, W-9 status, and unposted payments are not report amount truth.

After the tax year ends, BooksPlus:

  1. aggregates posted payments by payee, nature, method, and reporting category;
  2. applies the reviewed tax-year rule set and threshold operator;
  3. identifies included, excluded, exempt, and unresolved amounts;
  4. prepares a draft Form 1099-NEC return for each eligible payee;
  5. requires review and protected approval;
  6. prepares the untruncated IRS filing data and the permitted masked recipient statement;
  7. creates its reviewed IRIS Taxpayer Portal handoff; and
  8. preserves the submission receipt, acceptance, rejection, recipient-delivery status, and any later correction relationship.

Payments generally carry no federal withholding. A backup-withholding amount is reported only when it was actually required, supplied by the source, and posted; filing rules may require a return regardless of the ordinary threshold when backup withholding occurred.

The first filing scope is Form 1099-NEC for nonemployee compensation. The data model may retain MISC candidate categories, but Form 1099-MISC preparation and filing remain outside the first contractor filing slice unless explicitly accepted.

The initial release does not:

  • make a legal worker-classification determination;
  • generate W-2 payroll reporting;
  • calculate or execute backup withholding;
  • file state or local information returns except through a separately accepted combined federal/state path;
  • resolve foreign-payee reporting; or
  • replace professional tax review.

Support totals and draft-return review use posted ledger truth. Filing submissions are durable external-submission records, not journal entries or ordinary reports.

For a payee_tax_year rule, aggregation follows the stable source-system and external-payee identity across effective profile versions. Draft preparation selects the effective reviewed payee profile for the filing date, preserves all contributing support-line references, and persists only masked taxpayer identifiers plus protected-payload references. Untruncated identifiers are assembled only by the later protected filing handoff.

IRS filing transport

The filing transport must remain replaceable. Current IRS IRIS options include the Taxpayer Portal, which accepts keyed or IRS-template CSV data, and Application to Application (A2A), which uses approved software, IRIS credentials, schema packages, assurance testing, and a Transmitter Control Code.

BooksPlus owns provider-agnostic return preparation, approval, submission identity, status, acknowledgments, corrections, recipient-statement status, and audit behavior. An IRIS Portal export or IRIS A2A implementation is an external adapter and must not redefine the canonical return.

The initial release uses a reviewed IRIS Taxpayer Portal handoff. BooksPlus prepares the approved portal payload and preserves its identity and evidence; an authorized user uploads and confirms it through the company's IRIS account.

The initial transport profile is irs_iris_taxpayer_portal_keyed version 1. It produces a versioned protected BooksPlus keyed-entry package for authorized human entry. Core BooksPlus does not hard-code IRS CSV columns because portal templates are owned and versioned by the IRS for a particular tax year and form. Approval, protected handoff export, user confirmation of portal submission, and protected result recording are distinct actions. Exporting the package is not proof of submission or acceptance.

Direct A2A transmission is deferred. It may later replace the portal adapter without changing provider-agnostic return preparation, approval, filing identity, correction, acknowledgment, or recipient-statement meaning.

Sensitive-data controls

A full taxpayer identification number must never appear in ordinary screens, search indexes, logs, audit reason text, exception text, telemetry, or routine exports.

BooksPlus stores the full value only when it can:

  • encrypt it using an accepted sensitive-field design in addition to ordinary database access controls;
  • show only a masked value by default;
  • require distinct protected actions for maintenance, full-value viewing, and sensitive export;
  • record access and change audit events without recording the value; and
  • preserve it in encrypted backups without exposing it in support bundles.

W-9 and classification evidence remains under Source Document identity and must be treated as sensitive evidence.

Protected actions:

  • payee_tax_profile.maintain
  • payee_tax_profile.view_tin
  • information_return_payer_profile.maintain
  • information_return_payer_profile.view_tin
  • information_return_support.generate
  • information_return_draft.prepare
  • information_return_filing.approve
  • information_return_filing.export_handoff
  • information_return_filing.submit
  • information_return_filing.record_result
  • information_return_filing.correct
  • information_return_recipient_statement.prepare
  • information_return_recipient_statement.export
  • information_return_recipient_statement.record_delivery
  • information_return_support.export_sensitive

Validation and exception rules

  • Employee, contractor, supplier category, and information-return treatment fields do not substitute for one another.
  • An employee relationship cannot be reported as nonemployee compensation.
  • A W-9 does not establish independent-contractor status.
  • classification_under_review, undetermined, and foreign_payee_review remain visible exceptions.
  • Unresolved worker classification does not block valid payable recognition or recording an externally issued payment.
  • Unresolved worker classification blocks contractor and information-return readiness until reviewed.
  • A payment is aggregated once under one reviewed reporting category and rule set.
  • Card or third-party-network exclusions require explicit payment-method evidence and an applicable rule; ACH alone is not such evidence.
  • Reversed or corrected payments follow posted correction truth and must not be double counted.
  • Support totals reconcile to posted payment activity and explain exclusions, exceptions, and differences.
  • Missing secure TIN readiness prevents filing approval and submission without blocking masked support totals.
  • Filing approval requires payer identity, payee W-9/profile readiness, untruncated IRS TIN data, rule-set version, reconciled totals, filing year, form version, and recipient-statement readiness.
  • A logical return has one filing identity. Retry, acknowledgment polling, and corrections must not create duplicate original returns.
  • A correction is an append-only linked submission against the latest eligible accepted or correction-required member of the same company, tax year, jurisdiction, form, and stable-payee return chain. It requires reviewed Source Document evidence and cannot replace or fork prior filing history.
  • IRS acceptance, rejection, and correction results remain linked to the exact submitted payload and do not rewrite the posted ledger basis.
  • Each approved original or correction filing has one reconciled masked recipient-statement identity. Delivery outcome is separately evidenced and a delivered correction statement supersedes, but never deletes, the earlier statement.

Acceptance record

Accepted with these confirmations:

  • Step 8 uses the source-referenced PayeeTaxProfile boundary and does not introduce a general BooksPlus Party master.
  • Unresolved worker classification does not block valid payable recognition or recording an externally issued payment; it blocks contractor and information-return readiness.
  • The initial release uses a reviewed IRIS Taxpayer Portal handoff.
  • Direct IRIS A2A transmission remains a replaceable later adapter.

Consequences

  • Contractor classification remains distinct from vendor and tax-reporting treatment.
  • Tax-year changes do not require code changes or rewrite historical support runs.
  • Posted payment facts, rather than vendor checkboxes or staging records, support information-return totals and prepared returns.
  • Sensitive taxpayer data requires a narrower authorization and audit surface than ordinary Purchasing evidence.
  • Information-return filing becomes an external submission workflow with durable approval, idempotency, acknowledgment, correction, and recipient-statement records.
  • Core invoice-led Purchasing implementation may proceed independently of the later contractor-support and filing slices.

Authoritative tax references

  • 0012-policy-based-authorization.md
  • 0013-encrypted-company-data.md
  • 0014-append-only-security-audit-events.md
  • 0020-initial-release-scope-and-financial-workflow-taxonomy.md
  • 0024-operational-summary-workflow-boundaries-and-purchasing-facts.md
  • ../../contracts/purchasing-and-payables-summary-fact.contract.md
  • ../../contracts/contractor-and-information-return-filing.contract.md
  • ../../contracts/source-document.contract.md
  • ../../contracts/security/role-permission-contract.md