IRC 6721 Information Return Penalty: Tier Structure, Reasonable Cause, and OBBBA 2026

1. The IRC 6721-6724 Penalty Cluster: An Overview

Information returns are the backbone of third-party reporting in the federal tax system. When a business pays an independent contractor, a broker pays dividends, or a bank reports interest income, the information return filed with the IRS serves as an independent record that the IRS can compare to the recipient's filed return. The accuracy and completeness of that system depends entirely on filers meeting their obligations. Congress created the IRC 6721-6724 cluster to impose meaningful financial consequences for failures and to provide a structured path to relief for good-faith errors.

The four provisions operate as a coordinated framework:

• IRC 6721 covers the IRS-copy filing obligation: filing the return with the IRS by the required deadline and with correct information. The required returns include Forms 1099-NEC, 1099-MISC, 1099-INT, 1099-DIV, 1099-B, 1099-R, 1099-S, 1098, W-2G, 1042-S, and the full list in IRC 6724(d)(1).
• IRC 6722 covers the recipient-copy furnishing obligation: delivering the payee statement (W-2, 1099, or equivalent) to the person who received the payment, by the required date and with correct information.
• IRC 6723 covers other information reporting requirements, most importantly TIN solicitation obligations under IRC 3406 and magnetic media or electronic filing requirements for high-volume filers. The per-occurrence penalty under IRC 6723 is a separate charge from the per-return penalty under 6721.
• IRC 6724 provides the waiver. If the filer can establish that the failure was due to reasonable cause and not willful neglect, no penalty is imposed. The section also codifies the inconsequential failure exception and the de minimis error safe harbor under IRC 6721(c).

A single payment transaction can generate exposure under multiple provisions simultaneously. A business that fails to file a Form 1099-NEC with the IRS and fails to send the payee copy to the contractor faces both a 6721 penalty and a 6722 penalty for the same underlying failure.

2. IRC 6721 Penalty Tier Structure

IRC 6721 imposes penalties on a graduated scale based on how late the return is filed. The statute divides failures into three tiers by lateness and adds a separate regime for intentional disregard. All per-return amounts and annual caps are adjusted annually for inflation under IRC 6721(f); the amounts in the table below represent the tier structure with illustrative reference points. Verify the current indexed amounts in the applicable Revenue Procedure or at IRS.gov before relying on specific dollar figures.

Important note on indexed amounts. All per-return penalty amounts and annual aggregate caps under IRC 6721, 6722, and 6723 are adjusted annually for inflation under IRC 6721(f). The approximate figures shown in this table are illustrative of the tier structure only. Rely on the current-year Revenue Procedure (typically issued in the fall of the preceding year) or IRS.gov for the actual indexed amounts in effect for the filing period at issue.

Small Filer Status

A filer qualifies for the lower annual aggregate caps if its average annual gross receipts for the three most recent tax years are $5 million or less. This threshold is not indexed for inflation. For entities that cross the $5 million threshold mid-stream, the caps applicable to their filing period govern. Controlled groups may need to aggregate gross receipts for this test; verify the current aggregation rules under IRC 6721(d)(2) at IRS.gov.

The Three-Year Limitations Period

The IRS generally has three years from the due date of the information return to assess IRC 6721 penalties. For returns that were filed but contain incorrect information, the period runs from the due date or actual filing date, whichever is later. For returns not filed at all, the limitations period may not run at all until the IRS receives actual notice. Practitioners advising clients on historical exposure should calendar the limitations periods for each filing year carefully and evaluate whether the three-year window has closed before agreeing to pay or contest a penalty assessment. See the related guide on IRC 6651 failure-to-file penalty for parallel FTA procedures applicable to the same compliance history test.

3. IRC 6722: Failure to Furnish Correct Payee Statements

IRC 6722 targets a distinct but related obligation: furnishing a correct payee statement to the recipient of the payment. The payee statement is the copy of the information return that goes to the person who received the payment (the W-2 to the employee, the 1099-NEC to the independent contractor, the 1099-DIV to the investor). The IRS-copy obligation and the payee-copy obligation are separate legal duties, and failure to satisfy either one triggers its own penalty.

The penalty tier structure under IRC 6722 mirrors the IRC 6721 structure exactly: three tiers by lateness, with the same per-statement amounts (indexed) and the same annual aggregate caps. As with IRC 6721, the intentional disregard tier under IRC 6722(e) eliminates the annual cap entirely. The per-statement penalties under 6722 and the per-return penalties under 6721 are assessed simultaneously for a single transaction failure, producing combined exposure that can be material for even modest-sized filers.

Who Bears the IRC 6722 Penalty

The IRC 6722 penalty falls on the person required to furnish the payee statement: the employer who issues W-2s, the broker or financial institution that issues 1099-B or 1099-DIV statements, the payor of royalties or rents that issues 1099-MISC. For transactions where the payor is a business entity, the entity (not individual officers) is the responsible party for 6722 purposes, though in some circumstances responsible-party rules could apply. This is distinct from the trust fund recovery penalty analysis applicable to payroll tax failures under IRC 6672.

Overlap Between IRC 6721 and IRC 6722

A single failure to correctly report a transaction generates both IRC 6721 and IRC 6722 exposure. For example: if a business pays an independent contractor $5,000 and fails to file a Form 1099-NEC with the IRS and fails to send the contractor a copy, the business faces a Tier 3 IRC 6721 penalty (for the missing IRS-copy return) and a Tier 3 IRC 6722 penalty (for the missing payee statement). These penalties are separate and cumulative. Filing a corrected return with the IRS without also sending the corrected statement to the payee cures the 6721 violation but leaves the 6722 violation unresolved, and vice versa.

4. IRC 6723: Other Information Reporting Requirements

IRC 6723 covers failures to comply with information reporting requirements that are not the filing of the information return itself or the furnishing of the payee statement. The primary targets of IRC 6723 are:

• TIN solicitation failures. Under IRC 3406 and associated regulations, payors are required to solicit TINs from payees before making reportable payments. Failure to solicit a TIN before initiating backup withholding, or failure to follow the required B-notice solicitation procedures after receiving a CP2100, is a separate violation subject to the IRC 6723 per-occurrence penalty.
• Electronic filing failures. Filers with 250 or more information returns of a given type (the threshold will drop to 10 or more under rules phased in after the Taxpayer First Act) are required to file electronically. Filing on paper when electronic filing is required is a failure subject to IRC 6723.
• Other technical compliance failures. Failures to comply with other requirements specified in the information return regulations, including record retention requirements for backup withholding, are addressed under IRC 6723.

The per-occurrence penalty under IRC 6723 is a separate charge from the per-return penalties under IRC 6721 and 6722. Verify the current-year indexed IRC 6723 per-occurrence amount at IRS.gov.

5. OBBBA 2026: How the $2,000 Threshold Change Affects IRC 6721 Scope

Because IRC 6721 penalizes the failure to file a correct information return that was required to be filed, the scope of IRC 6721 exposure is directly tied to the scope of the underlying filing obligation. The OBBBA raised the threshold under IRC 6041 from $600 to $2,000 for payments required to be reported on Forms 1099-NEC and 1099-MISC (and related forms governed by IRC 6041). Payments below $2,000 that were formerly reportable are now outside the IRC 6041 obligation entirely, which means they are also outside the IRC 6721 penalty exposure for the filing periods to which the new threshold applies.

The practical implications for practitioners:

• Review client accounts payable systems to identify payments previously tracked for 1099 purposes that fall between $600 and $1,999. Those payments no longer require a Form 1099-NEC or 1099-MISC under the new threshold.
• Payments at or above $2,000 remain fully reportable, and IRC 6721 applies in full to failures regarding those payments.
• The OBBBA threshold change does not affect other information return types that have their own statutory thresholds (e.g., Forms 1099-INT with a $10 threshold, or Forms 1099-B which generally have no de minimis threshold). Verify the applicable threshold for each return type separately.
• The OBBBA threshold change does not reduce or eliminate the IRC 6721 penalty for returns that were required to be filed under the law in effect at the time of the original filing obligation. If a payment was reportable under the old $600 threshold and no return was filed, the penalty analysis uses the law in effect for that filing period.

6. TIN Solicitation, CP2100 B-Notice, and Backup Withholding

TIN mismatches are one of the most common sources of IRC 6721 and 6722 exposure for businesses with large numbers of independent contractors or vendors. When the IRS processes filed information returns and finds that a payee's TIN does not match IRS records, it sends the payor a CP2100 or CP2100A notice. The payor's response to the CP2100 directly affects its ongoing compliance status and its exposure on future returns.

First B-Notice and Second B-Notice

The First B-notice is sent when a TIN mismatch appears for the first time for a given payee. It requests a correct TIN on a new Form W-9. If the payee responds with a TIN that still does not match IRS records, or fails to respond, the payor must begin backup withholding at the applicable rate (currently 24%) on future payments.

A Second B-notice is triggered when the same payee's TIN produces a mismatch in a subsequent year. The Second B-notice instructs the payee to obtain a TIN verification letter directly from the IRS (or to contact the Social Security Administration for SSN issues). Backup withholding must continue until the payor receives IRS certification that the TIN is correct.

How Backup Withholding Interacts with IRC 6721

Backup withholding is a prospective compliance mechanism. It does not cure past IRC 6721 penalties for returns already filed with incorrect TINs. However, once the payor properly initiates backup withholding and begins filing returns that correctly report the withheld amounts, those subsequent returns are correct and do not generate new IRC 6721 exposure. Good-faith B-notice compliance also supports a reasonable cause argument under IRC 6724 for the periods before the CP2100 was received, because the payor can demonstrate it was relying on payee-provided TIN data and had no way to detect the mismatch before the IRS notification.

7. IRC 6724 Reasonable Cause Waiver

IRC 6724 is the statutory waiver provision for the information return penalty cluster. It provides that no penalty shall be imposed under IRC 6721, 6722, or 6723 if the failure is due to reasonable cause and not due to willful neglect. The waiver is self-executing in that no separate form or proceeding is required by statute, but in practice the IRS requires a written request explaining the reasonable cause basis before it will grant relief.

The Five-Factor Analysis Under Treasury Regulation 301.6724-1

Treasury Regulation 301.6724-1 provides the analytical framework for reasonable cause determinations. The five factors are:

1. The nature of the failure. Was the failure a single error or a systemic failure? Did it affect a small number of returns or a large volume? A one-time system failure affecting a small number of returns is more sympathetically analyzed than a pattern of repeated, widespread noncompliance.
2. The efforts made to comply. Did the filer take affirmative steps to meet its obligations before the failure occurred? Did it use commercially reasonable software, hire qualified compliance staff, or contract with a reputable service bureau? Evidence of compliance infrastructure supports reasonable cause.
3. The overall compliance history of the filer. A filer with a clean prior history (no penalties for the three preceding years) has a stronger reasonable cause argument than one with a pattern of failures. This factor also feeds into the FTA analysis discussed below.
4. The extent to which the failure was beyond the filer's control. System outages, natural disasters, vendor failures, and third-party data errors can support a finding that the failure was beyond the filer's reasonable control, particularly when the filer took prompt corrective action.
5. The significance of the failure in relation to the filer's overall reporting obligations. A failure affecting 5 out of 50,000 returns is analytically different from a failure affecting 45,000 of 50,000 returns, even if the total penalty amount is the same. The IRS considers proportionality in its reasonable cause analysis.

Inconsequential Failure Exception

IRC 6724(a) separately provides that no penalty is imposed if the failure is inconsequential. A failure is inconsequential if it does not prevent the IRS from processing the return or hinder the payee from using the statement for tax compliance purposes. In practice, errors in TINs, dollar amounts, or payor identity are rarely inconsequential under the regulatory standard. The exception is most relevant for minor formatting errors or technical non-compliance that has no effect on the IRS's ability to match the return to the payee's filed return.

8. First-Time Abatement for IRC 6721 and 6722 Penalties

FTA Eligibility Criteria

To qualify for FTA under the IRM policy for information return penalties, the filer must:

1. Have no prior penalties (or have had all prior penalties waived or abated) for the three tax years preceding the filing period for which abatement is requested. This means no unresolved IRC 6721, 6722, 6723, or related failures in the prior three years.
2. Have filed all required information returns for the years at issue, or have obtained a valid extension. If required returns are still outstanding, FTA will not be granted until the filing delinquency is resolved.
3. Have paid, or made arrangements to pay, all penalties owed or under dispute. The IRS does not require full payment before granting FTA, but it typically requires that the taxpayer be in compliance or have an installment agreement in place.

How to Request FTA

FTA for IRC 6721/6722 penalties may be requested by telephone through the IRS Penalty Abatement Line (the number on the penalty notice) or by submitting Form 843 (Claim for Refund and Request for Abatement). Telephone requests for FTA are often processed more quickly than paper Form 843 submissions. When calling, identify the penalty notice number, the tax period(s), the penalty code, and state that you are requesting FTA under IRM 20.1.1.3.6.2. Document the call with the IRS representative's name, badge number, and the outcome. For paper submissions, include Form 843 with a cover letter stating the FTA basis and attaching the penalty notice.

Practitioners advising clients on IRC 6694 exposure in connection with information return failures should also review the IRC 6694-6695 tax preparer penalties guide for the interaction between preparer penalties and information reporting advice.

9. Filing Corrected Returns: Type 1 and Type 2 Corrections

Filing a corrected information return is the most direct way to reduce penalty exposure under the IRC 6721 tier structure. A return corrected within 30 days of the original due date is assessed at the Tier 1 rate; a return corrected between 31 days and August 1 is assessed at the Tier 2 rate; a return corrected after August 1 is assessed at the Tier 3 rate. The incentive to file corrected returns promptly is therefore substantial.

Type 1 Corrections

A Type 1 correction addresses errors in dollar amounts, codes, or other fields that do not affect the payee's TIN, payee name, or the type of return. For example, correcting an incorrect amount in Box 1 of a Form 1099-NEC is a Type 1 correction. Type 1 corrections are submitted by filing a corrected return (paper or electronic) with the "CORRECTED" box checked, showing the correct information. No void return is required. For electronic filers, Type 1 corrections are submitted through the IRS FIRE system using the applicable file specifications in IRS Publication 1220.

Type 2 Corrections

A Type 2 correction addresses errors in the payee's TIN, payee name, or the type of information return filed. Because the IRS uses TIN and name to match returns to payees, a TIN or name error cannot be fixed by simply filing a corrected return: the IRS's system would treat the corrected return as a new return associated with the wrong TIN. Type 2 corrections require a two-transaction process: first, file a return that voids the original (using zeros or the appropriate void code for the original TIN/name combination); second, file a new original return with the correct TIN, payee name, and information. The information return penalties practical guide covers the step-by-step Type 2 correction procedure in detail.

Effect of Corrected Returns on Penalty Tier

A corrected return moves the original failure from the Tier 3 category to the tier corresponding to when the correction is filed, as long as the correction is filed before the Tier 2 or Tier 1 cutoff date. If the original return was due March 31 and the correction is filed April 25 (within 30 days), the penalty applies at the Tier 1 rate rather than the Tier 3 rate. For high-volume filers, this timing distinction can reduce penalties by hundreds of thousands of dollars. Practitioners discovering errors after August 1 should still file corrections immediately: while the Tier 3 rate will apply, the correction demonstrates good faith and supports the reasonable cause or FTA argument for penalty relief.

10. Interaction with IRC 6694 Preparer Penalties and Payor Classification

Tax practitioners advising clients on information reporting obligations face a dual risk: the client may incur IRC 6721 penalties for filing failures, and the practitioner may incur IRC 6694 or 6695 penalties if the advice underlying those failures was based on an unreasonable position. The two penalty regimes are independent but can arise from the same factual pattern.

The most common scenario: a practitioner advises a client that certain payments to workers are not reportable because the workers are classified as employees rather than independent contractors (or vice versa). If that classification is incorrect, the client may owe IRC 6721 penalties for unfiled or incorrect 1099s, and the practitioner may face exposure under IRC 6694 for the unreasonable position on worker classification. Practitioners should document their classification analysis, flag uncertain payor-classification situations for disclosure, and advise clients to file on the conservative side when the reporting obligation is arguable. Review the IRC 6694-6695 tax preparer penalties guide for the preparer standard applicable to information reporting advice.

Frequently Asked Questions: Statutory Framework

Frequently Asked Questions: Penalty Relief and Procedures