The 2026 1099 reset gives AP teams a filing-ready vendor data model.

The operating model: from vendor evidence to accepted return.

IRIS readiness is a data-contract exercise.

IRIS gives filers two practical paths: the Taxpayer Portal for smaller or manual workflows, and application-to-application for transmitters that want an XML-based integration. The right choice depends on filing volume, partner strategy, internal engineering capacity, and the cost of corrections. The design principle is the same in either case: generate the filing package from approved ERP records instead of a one-off spreadsheet.

That requires more than totals. The data contract should carry payer, payee, form, box, amount, withholding, address fields, tax year, source payments, replacement or correction status, and an acknowledgment loop. When a record is rejected or corrected, the workflow should update the vendor tax profile and payment facts to reduce repeat exceptions next year.

{
  "iris_submission_package_id": "iris_2026_nec_us_0042",
  "tax_year": 2026,
  "payer": {
    "legal_name": "Rivane Example Co.",
    "tin_token": "tin_tok_payer_71b8",
    "transmitter_control_code": "iris_tcc_active"
  },
  "payee": {
    "vendor_id": "ven_10428",
    "legal_name": "North Ledger Advisory LLC",
    "tin_match": {
      "status": "matched",
      "checked_at": "2026-08-17T15:42:00Z",
      "source": "irs_tin_matching"
    },
    "w9_evidence_id": "doc_w9_ven_10428_v2"
  },
  "return": {
    "form": "1099-NEC",
    "box": "nonemployee_compensation",
    "amount": 18420.00,
    "backup_withholding": 0.00,
    "source_payment_ids": ["ap_pay_811", "ap_pay_944", "ap_pay_1208"]
  },
  "review": {
    "prepared_by": "ap_tax_ops_01",
    "reviewed_by": "controller_02",
    "approved_at": "2027-01-19T18:12:00Z"
  },
  "irs_acknowledgment": {
    "status": "accepted",
    "received_at": "2027-01-20T09:31:00Z"
  }
}

The durable data objects are small, but they need clear ownership.

A strong 1099 workflow can start with a compact model. The key is to keep vendor tax facts, payment facts, filing packages, notices, and corrections connected. If tax operations has to join three exports to answer why a vendor was included, excluded, withheld, corrected, or rejected, the ERP design is leaving operating leverage on the table.

The ownership model should be explicit. AP owns payment facts and vendor operational status. Tax owns reportability rules, form mapping, thresholds, and corrections. The controller owns close review, evidence completeness, and financial-statement implications of withholding liabilities or accruals. IT or ERP operations owns access, integration reliability, and change control.

Audit evidence should answer the questions reviewers actually ask.

The IRS B notice process exists because filed information returns can contain missing, incorrect, or not-issued TINs. That is a concrete evidence problem for finance operators. When a notice arrives, the team should be able to see the vendor master version, certification evidence, TIN match history, payment set, withholding decision, recipient communication, and correction status without rebuilding history.

Form 1099-K adds another recurring reconciliation challenge. IRS FAQs explain that payment settlement entities report certain payment card and third-party network transactions. AP and tax teams therefore need payment-method evidence so they can avoid duplicative reporting and explain exclusions. This is where ERP design pays off: payment rail, processor, merchant category, settlement path, and source invoice can be ordinary facts in the payment record.

Questions for ERP and AP automation vendors.

A useful vendor demo should cover invoice capture, payment approval, and the tax evidence behind the payment. Ask whether the product can produce a filing-ready record without finance exporting the problem into a spreadsheet.