Build an IRIS Transmitter Control Code (TCC) Application Worksheet

Skill: Convert a firm's onboarding details into a complete IRIS IR-Application-for-TCC worksheet

Region: United States Category: Information Returns (IRIS enrollment) Does: Takes a firm's organizational, official, and filing details and assembles them into a structured, validated worksheet that mirrors every section of the IRS IR Application for TCC for IRIS — so the online application can be completed in one pass and the firm can e-file before FIRE shuts down. System: IRIS (Information Returns Intake System)

A TCC is required before any IRIS filing, and a FIRE TCC does not carry over to IRIS — filers must apply for a new IRIS TCC through the IR Application for TCC. The application itself is an online, ID.me-authenticated form (there is no file to upload), so this skill produces a preparation worksheet, not a transmittable artifact: it organizes and checks the data so each Responsible Official can enter and e-sign it without missing a section. Verify required fields, role minimums, and the application flow against current IRS IRIS guidance before submitting — the portal's requirements change between cycles.

What the IR Application for TCC asks for

Each RO must complete ID.me identity verification and e-sign the application with their PIN before the TCC is issued.

Build procedure

1. Read the source. Accept the firm's details as pasted text, a form/key-value list, or a JSON/CSV of people and roles.
2. Extract the firm block — legal name, DBA, EIN, structure, address, phone.
3. Determine roles — Issuer and/or Transmitter and/or Software Developer, based on whether the firm files only its own returns, files for others, and/or develops software.
4. Choose transmission method — Portal or A2A (flag that A2A requires ATS testing before production).
5. Collect the people — every Responsible Official and Contact with the required identifying and contact fields; enforce the role minimums (≥ 2 ROs unless sole proprietor; ≥ 2 Contacts).
6. List the forms the firm will file.
7. Emit the worksheet as the JSON structure below, plus a readiness checklist of the steps that happen outside the data (ID.me, e-signature).
8. Validate against the checklist; if any required field or the minimum number of ROs/Contacts is missing, ask rather than guess.

Source → worksheet field map

Worked example (end-to-end)

Input — firm details (pasted)

Firm: Acme Compliance LLC (DBA: AcmeFile), EIN 12-3456789, single-member LLC.
Address: 100 Congress Ave, Suite 400, Austin, TX 78701. Phone 512-555-0100.
We file 1099-NEC and 1099-MISC for our own clients (so we transmit for others).
We will upload CSVs through the Taxpayer Portal.
Responsible Officials: Maria Lopez (Owner) and Sam Chen (Operations Director).
Contacts: Maria Lopez (Owner, 512-555-0100, maria@acmefile.example) and
          Priya Patel (Filing Lead, 512-555-0188, priya@acmefile.example).
Will file: 1099-NEC, 1099-MISC.

Output — IRIS TCC application worksheet (JSON)

{
  "application": "IRIS IR Application for TCC",
  "firm": {
    "legalName": "Acme Compliance LLC",
    "dba": "AcmeFile",
    "ein": "12-3456789",
    "businessStructure": "Single-member LLC",
    "address": {
      "line1": "100 Congress Ave",
      "line2": "Suite 400",
      "city": "Austin",
      "state": "TX",
      "zip": "78701"
    },
    "phone": "512-555-0100"
  },
  "roles": ["Issuer", "Transmitter"],
  "transmissionMethod": "Taxpayer Portal (CSV)",
  "responsibleOfficials": [
    {
      "name": "Maria Lopez",
      "title": "Owner",
      "ssn": "REQUIRED - collect securely",
      "dateOfBirth": "REQUIRED - collect securely",
      "usCitizen": true,
      "phone": "512-555-0100",
      "email": "maria@acmefile.example",
      "idMeVerified": false,
      "willESign": true
    },
    {
      "name": "Sam Chen",
      "title": "Operations Director",
      "ssn": "REQUIRED - collect securely",
      "dateOfBirth": "REQUIRED - collect securely",
      "usCitizen": true,
      "phone": "512-555-0142",
      "email": "sam@acmefile.example",
      "idMeVerified": false,
      "willESign": true
    }
  ],
  "contacts": [
    {
      "name": "Maria Lopez",
      "title": "Owner",
      "phone": "512-555-0100",
      "email": "maria@acmefile.example"
    },
    {
      "name": "Priya Patel",
      "title": "Filing Lead",
      "phone": "512-555-0188",
      "email": "priya@acmefile.example"
    }
  ],
  "forms": ["1099-NEC", "1099-MISC"],
  "softwareDeveloper": null,
  "outOfBandSteps": [
    "Each Responsible Official completes ID.me identity verification",
    "Each Responsible Official e-signs with their 5-digit PIN",
    "If A2A were chosen: complete ATS testing before production"
  ]
}

Note: SSN and date of birth for each RO are required by the application for identity verification but are sensitive — the worksheet flags them for secure collection rather than guessing. Because Acme transmits returns for its own clients it needs both Issuer and Transmitter roles; a firm filing only its own corporate returns would list only Issuer.

Worksheet structure

worksheet
├── firm                  (legalName, dba, ein, businessStructure, address, phone)
├── roles[]               (Issuer | Transmitter | Software Developer)
├── transmissionMethod    (Taxpayer Portal | A2A)
├── responsibleOfficials[]  ≥ 2 unless sole proprietor; each ID-verified + e-signs
├── contacts[]            ≥ 2; day-to-day
├── forms[]               (information returns to be filed)
├── softwareDeveloper     (only if that role selected; else null)
└── outOfBandSteps[]      (ID.me, e-signature, ATS testing)

Mandatory: firm, roles, transmissionMethod, responsibleOfficials, contacts, forms. Optional/conditional: softwareDeveloper (Software Developer role only).

Code tables

IRIS roles

Transmission method

Data rules

• Role minimums: require at least two Responsible Officials unless the firm is a sole proprietorship; require at least two Contacts. If fewer are supplied, ask.
• No invented identity data: never fabricate an SSN, date of birth, or PIN — flag them for secure collection.
• EIN format: 9 digits (NN-NNNNNNN); the firm must use an EIN, not an SSN, for the organization.
• A2A implies testing: if transmissionMethod is A2A, include the ATS testing step in outOfBandSteps.
• One application per firm/EIN: consolidate all roles and forms into a single worksheet rather than producing duplicates.

Validation checklist

• Firm block complete: legal name, EIN (9 digits), business structure, full address, phone
• At least one role selected; Software Developer details present only if that role is chosen
• Transmission method chosen; ATS testing step included when A2A
• At least two Responsible Officials (unless sole proprietor), each with name, title, contact, and identity fields flagged for secure collection
• At least two Contacts with phone and email
• Forms to be filed listed
• Out-of-band steps captured: ID.me verification and e-signature for each RO
• Nothing invented — any missing required field surfaced as a question

Last updated: 2026-06-12 — a new IRIS TCC is required before filing and a FIRE TCC does not transfer. The IR Application for TCC is an online ID.me-authenticated form; confirm the current required sections, role minimums, identity-verification flow, and signature requirements against IRS IRIS guidance before submitting.