How to File Corrections via IRIS

What an IRIS Correction Actually Is — and When You Need One

A correction is not an edit. Once the IRS Information Returns Intake System has accepted a return, that filing is permanent in the agency’s records, and the only way to change what the IRS believes is to submit a second, separate filing that explicitly references and replaces the first. Understanding that the original never disappears — it gets superseded — is the foundation for everything else in this guide.

The trigger for a correction is narrow but important: it applies only to returns that IRIS has already accepted. If you discover a wrong dollar amount, a transposed digit in a Taxpayer Identification Number, or a misspelled payee name after the acknowledgement comes back clean, you are in correction territory. The correction is a new record that the system links to the original by its identifier, updates with the right data, and uses to override the earlier filing. When the correction is accepted, the original return’s status flips to superseded and the corrected values become the version of record.

It helps to separate three situations that filers routinely confuse, because IRIS treats each one differently and only one of them is a correction. A return that was accepted and contains a mistake is fixed with a correction, which is the subject of this article. A return that was rejected — turned away before it ever entered the IRS records — is not corrected at all; you repair the data and re-send it as a fresh original, because there is nothing on file to supersede. And an entire transmission that failed at the manifest level is handled with a replacement, a manifest-level resend that is governed by its own rules and is covered separately below. Filing the wrong one of these three is the single most common way a fix turns into a rejection.

Original vs Correction: The Two Flags IRIS Reads First

IRIS decides whether a filing is an original or a correction from two pieces of data, and getting them consistent is the whole game. The first is TransmissionTypeCd on the transmission manifest, which tells the system the nature of the whole batch — O for original, C for corrected, or R for a replacement. The second is CorrectedInd on each individual record, which marks that specific form as either an original (0) or a correction (1). The two must agree, and IRIS enforces that agreement before it will read your data.

The mismatch rules are unforgiving, which is why they belong at the front of your mental checklist rather than the back. If your manifest says the batch is original or a replacement, every record inside it must carry CorrectedInd equal to 0; the rule FTMFST001_001 rejects the transmission if even one record is flagged as a correction. The inverse rule, FTMFST003_001, rejects a batch declared as corrected (TransmissionTypeCd = C) if any record inside it still carries CorrectedInd = 0. In practice that means you keep originals and corrections in separate transmissions rather than mixing them, and you make the manifest agree with what the records actually are.

When a record is flagged as a correction, it cannot float free — it has to name the original it is replacing. The element that does the naming is UniqueRecordId, which is built from three parts joined by pipes: the ReceiptId of the accepted transmission, the submission number within it, and the record number within that submission, written as 2025-63385508791-4a6c57eda|1|1. Rule SHAREDIRFORM010_001 checks that the submission portion of that identifier matches a submission the IRS has previously accepted, and SHAREDIRFORM014 checks that the tax year of your correction matches the tax year of the original. You cannot correct a record that the IRS never accepted, and you cannot correct it into a different tax year.

One-Step vs Two-Step: It Depends on What You’re Fixing

Not every correction is the same shape. The IRS draws a line between errors you can fix in a single corrected record and errors that require two records to fix — and the line falls exactly where the wrong data is the payee’s identity rather than the payee’s money.

The one-step correction (most fixes)

When the original return reached the right person but reported the wrong figures — an overstated amount, a box left blank, a withholding number that was off — the fix is a single corrected record. You submit one form with CorrectedInd set to 1, the PrevSubmittedRecRecipientGrp carrying the original’s UniqueRecordId, and the corrected values in place of the wrong ones. IRIS supersedes the original with this one record, and you are done. This is the path for the large majority of corrections, because most mistakes are arithmetic, not identity.

The two-step correction (name or TIN errors)

When the original return reported the wrong payee — a wrong Taxpayer Identification Number, or a name that does not belong to that TIN — a single corrected record is not enough, because the IRS first has to undo the filing that was attached to the wrong identity before it can accept the right one. This is the two-step, or two-transaction, correction. The first record voids the original by re-stating the wrong name and TIN exactly as they were filed but zeroing every dollar amount, which tells the IRS to disregard that filing. The second record then reports the corrected name and TIN with the full, correct amounts as a clean entry. Both records travel together in the same correction transmission so the IRS processes the undo and the re-report as one logical change.

How to File a Correction, Step by Step

The mechanics below assume you are filing directly against IRIS and already hold an accepted original. The order matters, because each step produces the identifier the next step depends on — you cannot build a correction until you can name the original it replaces.

Corrections vs Replacements: Two Words That Are Not Synonyms

IRIS uses “correction” and “replacement” to mean two genuinely different operations, and treating them as interchangeable is a fast route to a reject. A correction changes data on a return the IRS accepted. A replacement re-sends a transmission or submission the IRS rejected — it never entered the records, so there is nothing to supersede, only to resend correctly.

A replacement is declared at the manifest with TransmissionTypeCd set to R, and it has to point back at what it is replacing using one of two identifiers — never both. If the whole transmission was rejected, you reference the original’s OriginalReceiptId on the manifest. If only some submissions in a partially accepted transmission were rejected, you reference each rejected submission’s OriginalUniqueSubmissionId instead. Rule FTMFST004_001 makes these two mutually exclusive, rejecting a replacement that supplies both at once as well as one that supplies neither. Because a replacement carries originals rather than corrections, every record inside it must keep CorrectedInd at 0.

What Can and Cannot Be Fixed With a Correction

Corrections are powerful but bounded, and knowing the boundaries up front saves you from building a fix that IRIS will simply refuse. Within the form data itself, a correction can change almost anything — amounts, boxes, withholding, account numbers, addresses, and even the payee’s identity through the two-step path. What it cannot do is reach across the structural lines IRIS draws around a filing.

• You cannot correct a rejected return. Rejected returns never entered the IRS records, so there is no accepted filing to supersede — fix the data and re-file it as a new original.
• You cannot correct an extension request. Rule SMF030 blocks a corrected transmission from carrying a Form 8809 extension submission, so an extension cannot be amended through the correction channel.
• You cannot change the form type. A corrected record supersedes one specific accepted record and carries that original’s FormTypeCd, so a wrong-form-type mistake is handled by voiding and re-filing, not by correcting across types.
• You cannot move a correction to a different tax year. Rule SHAREDIRFORM014 requires the correction’s tax year to equal the original’s.
• You cannot correct against a submission that was never accepted. Rule SHAREDIRFORM010_001 requires the UniqueRecordId to point at a previously accepted submission.

Common Rejection Reasons (and How to Avoid Them)

Corrections fail for a small, predictable set of reasons — almost always a mismatch between what the manifest claims and what the records actually carry, or a broken link back to the original. Each of these is a hard reject, which means the correction never lands and the wrong data stays on file until you fix and resend. They are ordered by how often filers hit them.

Skip the Identifier Bookkeeping: The e1099f Advantage

A superseded original and an accepted correction — not a duplicate-filing reject.

Frequently Asked Questions

Not tax advice. This is general information about IRS IRIS procedures and may change as the IRS updates the system and its business rules; the published IRS materials are authoritative. Consult a tax professional for your situation.