Your tax software shouldn’t have to become tax infrastructure.

Don’t build the IRS integration yourself.

Your platform already owns the customer, vendor, payment, and tax data. The painful part is everything between that data and a successful filing.

1. Your data
2. Tax mapping
3. Validation
4. IRS schemas
5. Submission
6. Acknowledgements
7. Corrections
8. Audit trail

IrisTaxFiling handles the infrastructure layer.

Product

Everything between your tax data and the IRS.

Forms

37 IRIS forms. One API.

The full IRIS catalogue is in the API, with IRS template columns, rules and CSV templates for every form. Four forms are fileable end to end in the demo; the rest have the bulk readiness check today.

Use cases

Built for software that generates tax data.

Pick your platform. Each scenario shows what you send, what comes back and what works in the demo today.

POST /v1/filings?mode=validate

{ "form": "1099-NEC", "tax_year": 2026,
  "payer": { "name": "Acme Platforms Inc", "tin": "12-3456789", ... },
  "recipients": [{
    "name": "Jane Contractor",
    "tin": "123-45-6781",
    "nonemployee_compensation": 12500.50
  }] }

→ { "status": "valid", "summary": { "blockers": 0 } }

curl -X POST https://api.iristaxfiling.com/v1/forms/1099-K/validate \
  -H "Authorization: Bearer $IRISTAXFILING_KEY" \
  -H "Content-Type: text/csv" \
  --data-binary @sellers.csv

→ { "object": "readiness", "status": "blocked",
     "summary": { "records": 25000, "blocked_records": 312 } }

POST https://your-app.example/hooks/irisfile
IrisFile-Signature: t=1791640000,v1=9f2c...

{ "type": "filing.accepted",
  "livemode": false,
  "data": { "filing": { "id": "fil_...", "status": "accepted" } } }

{ "form": "1099-INT", "tax_year": 2026,
  "recipients": [{
    "name": "Alex Saver", "tin": "123-45-6781",
    "amounts": { "interest_income": 842.17,
                 "federal_tax_withheld": 0,
                 "foreign_tax_paid": 3.50 },
    "details": { "foreign_country": "CA" }
  }] }

{ "form": "1099-MISC", "tax_year": 2026,
  "recipients": [{
    "name": "Pine Street Holdings", "tin": "98-7654321",
    "tin_type": "ein",
    "amounts": { "rents": 18000, "other_income": 250.75 }
  }] }

curl -X POST "https://api.iristaxfiling.com/v1/imports/fire?create=true" \
  -H "Authorization: Bearer $IRISTAXFILING_KEY" \
  --data-binary @fire.txt

→ { "object": "fire_import", "created": true,
     "summary": { "issuers": 3, "payees": 3, "imported": 2, "skipped": 1 } }

GET /v1/forms/3922/template      → text/csv
POST /v1/forms/3922/validate     → readiness report

curl https://api.iristaxfiling.com/v1/forms/3922 \
  -H "Authorization: Bearer $IRISTAXFILING_KEY"

Developer-first by design

Bring your data. IrisTaxFiling handles the filing infrastructure.

Your engineers shouldn’t have to become experts in IRS transmission formats, filing workflows, and correction mechanics.

curl -X POST "https://api.iristaxfiling.com/v1/filings?mode=validate" \
  -H "Authorization: Bearer $IRISTAXFILING_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "form": "1099-NEC",
  "tax_year": 2026,
  "payer": { ... },
  "recipients": [{
    "name": "Jane Contractor",
    "tin": "000-00-0000",
    "address": { ..., "state": "ZZ" },
    "nonemployee_compensation": 12500.50
  }]
}'

{
  "object": "validation",
  "status": "blocked",
  "summary": { "blockers": 2, "warnings": 0 },
  "issues": [
    { "code": "tin_invalid",
      "path": "recipients[0].tin",
      "fix": "Verify the TIN with the recipient and correct it." },
    { "code": "state_invalid",
      "path": "recipients[0].address.state",
      "fix": "Use a 2-letter US state ... e.g. TX." }
  ]
}

FIRE to IRIS

FIRE is changing. Your infrastructure has to change with it.

The IRS is transitioning information-return filing from the legacy FIRE system to IRIS. For software companies that have built or depend on filing infrastructure, this creates a significant migration and integration requirement.

Move from legacy filing workflows without rebuilding everything.

Keep your existing data model. Let IrisTaxFiling handle the translation, validation, and filing workflow.

1. Legacy data: CSV / FIRE / internal system
2. IrisTaxFiling
3. Normalize
4. Validate
5. IRIS-ready
6. Submit

Reliability

Built for filing deadlines.

Pricing

API pricing that scales with filing volume.

Usage-based filing volume is a secondary pricing dimension. Prices are illustrative and not final.

Built for the infrastructure problem behind information returns.