IRC 6061 through IRC 6065 requires any return made under the provisions of the internal revenue laws must be signed by the taxpayer (or other such authorized individual) under penalties of perjury. A return not signed by the taxpayer (or an authorized individual) fails to meet the filing requirement , and may subject the taxpayer to penalties for failure to file. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

If it is determined the failure to sign a return was an intentional attempt to avoid civil or criminal penalties associated with signing a false return (see IRC 7206), then the penalty for failure to file should be duly explored to the fullest extent of the law. See IRM 20.1.2.3.7.5, Fraudulent Failure to File.

Also see IRM 20.1.2.2.9, Frivolous Returns.

26 CFR 301.7502(d) provides IRC 7502 also applies to timely electronic postmarks for e-filed returns. All timely conditions are considered met if the return:

An authorized Electronic Return Transmitter (ERT) transmits return information from the return originator to the IRS as defined in Rev. Proc. 2000-31. Generally, an electronic return is prepared with preparation software and then converted to processable format by another entity that originates the return and transmits to the IRS. The following entities may transmit returns to the IRS:

Electronic postmark is a record of the date and time an authorized ERT receives the transmission of a taxpayer’s electronically filed return on its host system in the ERT’s time zone.

For purposes of IRC 7502, the postmark of an electronic return is only valid if the postmark represents when the return is sent to an ERT, (or ERO/ISP when they are acting as an ERT). Because an electronic postmark is only created when an ERT receives an electronic return; any postmark relating to the time an ERO/ISP receives tax information, or originates a return, alone will not meet the electronic postmark requirements under IRC 7502.

IRC 7508 provides a certain period relating to duty in a combat zone as designated by the President by executive order (or in a contingency operation designated by the Secretary of Defense) is to be disregarded in determining whether a taxpayer has complied with statutory requirements to perform certain acts by a given date.

With respect to the time available (after the end of a tax year) to prepare and file a return, and to pay the tax, the period to be disregarded in determining any penalty for filing late or paying late is as follows:

The period to be disregarded applies to individuals serving in the Armed Forces of the United States and to those serving in support of those Armed Forces.

The period to be disregarded also applies to the spouses of those serving in the combat zone. However, the period to be disregarded does not apply to the spouses for any taxable year beginning more than two years after the date of termination of combat activities in the combat zone.

IRC 7508A provides the Secretary of the Treasury may specify a period of up to one year to be disregarded with respect to acts required to be performed by taxpayers determined by the Secretary to have been affected by a federally declared disaster, a terroristic action, or military action.

In order for the period to be disregarded to impact either the penalty for filing late or the penalty for paying late, the due date for filing or paying must fall within the disaster period as determined by the Secretary. If the normal due date for filing or paying falls within the disaster period, the taxpayer's return or payment will be considered on time if it is mailed by the date published by IRS for timely filing or paying for the covered disaster area.

IRS identifies taxpayers qualifying for disaster relief based on their zip code. Qualifying taxpayers receive a Transaction Code (TC) 971 with Action Code 086, 087, or 688 posted in the entity module of their account. Disaster TC 971 transactions contain a transaction date and a secondary date. The transaction date is the beginning date of the disaster period, and the secondary date is the ending date. The ending date corresponds with the date published by IRS for timely filing or paying.

Unlike periods disregarded due to time spent in a combat zone, disaster periods beginning after the end of the taxable year, and ending on or before the return due date, do not extend the time for filing and paying.

Any penalties for filing or paying late of affected taxpayers are computed using the disaster end date as the new "disaster due date" for determining the correct penalty.

Before 2015, IRS did not charge a penalty for paying late during disaster periods even in cases where the payment due date was prior to the start of the disaster period, as long as the extended return due date fell within the disaster period.

For disaster periods beginning after 12/31/2014, IRS will no longer suspend accrual of the penalty for paying late for any tax due prior to the start of the disaster period. See 26 CFR 301.7508A-1(f), Example 6. The penalty will continue to accrue during the disaster period, and will only be removed if the taxpayer is able to show reasonable cause for failure to pay at the time payment was due, or if the taxpayer qualifies for the first time abatement (FTA) administrative waiver. See IRM 20.1.1.3.3.2.1, First Time Abate (FTA).

The following taxpayers also qualify for relief under IRC 7508A; however, they generally must call the IRS disaster hotline at 866–562–5227 to request relief.

Taxpayers (or their authorized representatives) may call or write to self-identify if they qualify for disaster relief even though their address is outside the covered disaster area. Employees should research their functional IRM for instructions with respect to the input of TC 971 with Action Code 688 when taxpayers self-identify themselves as affected by the disaster. TC 971 with Action Code 688 should only be input after the specific disaster provisions for which the taxpayer qualifies have been verified.

Employees who do not have the ability to manually input the TC 971 for disaster relief should refer callers to the Disaster Special Services toll-free line at 1-866-562-5227.

IRS employees should not abate or adjust any penalties because of a federally declared disaster unless the appropriate TC 971 with AC 086, 087 or 688 is already posted in the entity, and the penalty is restricted from automatic computation by a restricting penalty transaction code or by other systemic limitations.

Some taxpayers may have been affected by multiple disaster declarations with respect to a single tax period.

When two or more disaster declaration periods overlap, they are treated as a single period beginning on the earliest disaster start date of the overlapping disaster periods and ends on the latest end date of the overlapping disaster periods.

When the original return due date falls within one disaster period, and the extended return due date falls within another non-overlapping disaster period, the earlier disaster period is ignored in computer programming in effect prior to 01/01/2022. The programming updates should compute the penalty correctly. If programming ignores an earlier disaster period, manual intervention is necessary to ensure the taxpayer receives the disaster relief provided by law. The following table provides instructions for resolving penalty issues in tax modules impacted by non-overlapping disasters.

IRS employees can research disaster areas by going to http://www.icce.irs.gov/fema/, or to SERP - Disaster Assistance Information (irs.gov). Information on tax relief in disaster situations is available to the general public at www.irs.gov .

In order to qualify for an extension of time to file, all taxpayers must estimate the amount of their tax for the year. When a specific form is designated for requesting an extension of time to file, the request for the extension should be filed on that form. However, if a specific form has not been designated, an extension may be requested by mailing a letter to the IRS office where the return is required to be filed. Such letter must include the following information:

Qualified taxpayers may request an automatic extension of time to file by filing the appropriate form, depending on the type of tax return. For a list of forms provided to request an extension of time to file, see Document 6209. Section 2, Part 4, Extension Forms.

In order to obtain an automatic extension of time to file, corporations are required to pay the amount properly estimated as the tax for the year covered by the extension request.

For taxable years ending 12/31/1993 and later, individuals are no longer required to pay the amount they estimate they will owe when they file Form 4868 in order to obtain the automatic extension of time to file; however, they are still required to enter their estimate of their tax liability on the applicable line of the form.

An extension of time to file does not extend the time to pay. However, 26 CFR 301.6651-1(c)(3) and 26 CFR 301.6651-1(c)(4)provides reasonable cause will be presumed for the period of the extension in the case of failure to pay income tax if the following criteria are met:

IRS computers are programmed to automatically apply this waiver of the late payment penalty for reasonable cause if the taxpayer qualifies.

Joint extension requests apply equally to each spouse, even if they subsequently file separate returns.

There are no regulations covering an extension of time to file employment tax returns. Therefore, these returns do not qualify for an extension of time to file. However, no penalty for filing late is asserted if the taxpayer paid (For example, via Federal tax deposits, and so on) 100 percent of the tax required to be paid on or before the due date for payment.

Partnerships and S corporations electing to have a taxable year other than a required taxable year (in other words, their taxable year does not end on December 31st), are required under IRC 7519 to file Form 8752, Required Payment of Refund Under Section 7519, and pay the amount shown on the return. The due date for the return is May 15th of the calendar year following the calendar year in which the fiscal year begins. For example, if the fiscal year began on November 1, 2015, then the return and payment are due May 15, 2016. Taxpayers may request an extension of time to file Form 8752 by writing a letter to the service center or director where they are required to file, on or before the May 15 due date. The director may approve an extension of time to file for up to 90 days (up to 6 months, if the taxpayer is abroad), or the request may be denied. The extension will be denied if the request was late, or if payment of the estimate has not been made. The extension request letter must include the following:

Extensions of time to file are recorded in the applicable tax module with Transaction Code (TC) 460 carrying the extended due date.

The computer generally will not allow the input of an extension beyond 6 months after the normal return due date. However, for IMF returns, when a longer extension is allowed by law, the extension may be input by using a "foreign" universal location code (ULC) on the TC 460 input screen. The foreign location codes available are:

Service centers not listed in (11) are not able to process an extension in excess of 6 months. The ULC used with this extension request does NOT extend the time to pay. If the taxpayer qualifies for an automatic extension of time to pay under 26 CFR 1.6081-5, the taxpayer's return will need to be processed with the proper file location code or computer condition code as applicable. See IRM 20.1.2.2.3.3, Taxpayers Abroad.

Taxpayers may use Form 1127, Application for Extension of Time for Payment of Tax Due to Undue Hardship, to apply for an extension of time to pay tax shown on their return. The IRS will grant the extension provided the taxpayer is able to show undue hardship will be suffered if payment is made on the payment due date. See IRC 6161(a) and regulations relating thereto. If granted, the extension generally may not exceed 6 months (12 months in the case of estate tax).

Taxpayers may also use Form 1127 to request an extension of time to pay certain taxes determined as a deficiency, providing the deficiency is not the result of negligence, intentional disregard of rules and regulations, or fraud with the intent to evade tax. The Secretary must be satisfied that payment of the deficiency upon the date fixed for the payment thereof would result in undue hardship to the taxpayer. If granted, the extension may not exceed 18 months; and in exceptional cases, an additional 12 months.

If an extension of time to pay is granted, the failure to pay (FTP) penalty for the underlying tax will not begin to accrue until after the expiration of the extension period.

For extensions of time to pay estate and gift taxes, see IRM 4.25.2.8.2.4, Extension of Time to File and IRC 6161 Extension of Time to Pay through IRM 4.25.2.8.2.6 , Estate Tax Extension of Time to Pay Under IRC 6163 and IRM 1.2.2.5.3, Delegation Order 4−3 (formerly DO−20, Rev. 3).

Except in the case of an extension to pay gift tax, IRS currently is not able to compute the FTP penalty systemically if an extension of time to pay was granted under IRC 6161 and the tax is not paid in full by the extended due date. In all such cases the FTP penalty must be manually computed and assessed. For specific processing instructions, see IRM 5.1.12.1, Overview—Cases Requiring Special Handling.

Extensions of time to pay are disregarded in determining the date prescribed for payment for the purpose of computing interest or the penalty for filing late. See IRC 6601(b)(1).

26 CFR 1.6081-5 provides for an automatic extension of time to file and pay for certain partnerships, corporations, and U.S. citizens and residents. The extended due date is the 15th day of the 6th month following the close of the taxable year. The extension applies to the following:

With respect to item e) above, an individual’s tax home and abode must both be outside the United States and Puerto Rico.

A taxpayer’s tax home is outside the United States and Puerto Rico if either of the following two conditions apply:

A taxpayer’s abode is outside the United States and Puerto Rico, in a real and substantial sense, if the taxpayer’s principle residence is (or was on the return due date) outside the United States and Puerto Rico.

A tax payer may have multiple residences; however, the taxpayer’s principle residence is where the taxpayer spends the majority of time. If the taxpayer does not spend more than half of their time at one residence, then the taxpayer’s principle residence is determined based on all pertinent evidence. Pertinent evidence includes, but is not limited to, where the taxpayer lists their address for legal documents, where the taxpayer’s family resides (for instance children attend school), where mail is received, and so on.

In order to qualify for this automatic extension of time to file and pay, the taxpayer must attach a statement to their return stating the taxpayer qualifies for this extension of time to file. Please note the attachment of the required statement does not guarantee the taxpayer will be identified as qualifying for this extension.

≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ If a taxpayer contacts the IRS because the extension was not given, even though the required statement was attached to the return, review the taxpayer’s address history.

Forms 1040 identified during pipeline processing as qualifying for this automatic extension of time to file are coded with a special file location code in the DLN, or with a special computer condition code:

Partnerships and corporations identified during pipeline processing as qualifying for this automatic extension are identified by computer condition codes "D" and "R" . These codes prevent Master File from ever automatically assessing either the penalty for filing or for paying late for that year's return; therefore, if either penalty ever applies, it must be manually computed and assessed.

If one of the entities in paragraph (1) qualifies for this automatic extension but needs additional time to file, the taxpayer must file the appropriate application for an extension on or before the due date as extended under 26 CFR 1.6081-5. A statement must be attached to the extension request stating the taxpayer qualifies for the extension in 26 CFR 1.6081-5.

IRM 20.1.1.3, Criteria for Relief From Penalties, provides guidance for determining if the taxpayer meets the criteria for penalty relief. See IRM 20.1.1-2, Penalty Reason Code Chart, in IRM 20.1.1, Introduction and Penalty Relief, for a complete list of penalty reason codes.

The IRS will abate the penalty for failure to file or pay when the taxpayer shows that the failure to comply was due to reasonable cause and not due to willful neglect.

Reasonable cause determinations for failure to pay must be made separately for each assessment (i.e., tax shown on the return, math error assessment, amended return, or deficiency). For example, a taxpayer may not have had reasonable cause for his failure to pay the tax shown on his return, while he may have had reasonable cause for his failure to pay additional tax assessed as a result of a math error correction.

When the failure to pay (FTP) penalty is abated for reasonable cause (Reason Code 062), the abatement should include the entire related penalty computed on the underlying tax liability, even if the penalty has not yet been assessed.

Examiners should address the reason for any failure to file or failure to pay when securing or examining returns where the penalty appears to apply. Making this initial determination will prevent the need for subsequent abatements.

Reasonable cause abatement requests must be documented via an adjustment with a source document.

When penalties for failure to pay are abated for reasonable cause using TC 271 with RC 062, Master File will not restrict future computer computations of the penalty (provided it was not previously restricted). The computer continues to compute the penalty for failure to pay, but will waive the amount associated with RC 062. Use TC 271 with RC 062 only if the underlying tax has been paid in full, and always abate the entire penalty related to the tax in question, including accruals.

A TC 271 input without RC 062 restricts subsequent computation of the penalty. Input TC 272 with a zero amount to remove the manual restriction on the FTP penalty when a module has been restricted in error.

A TC 271 without RC 062 (or a TC 270 for zero amount) should only be used to abate the FTP penalty for reasonable cause (and/or to prevent additional accrual of the penalty when the failure to pay is due to reasonable cause) under the following circumstances:

An abatement of the penalty for failure to pay (or TC 270 for zero amount) without the use of RC 062 should be very rare. A restricting penalty transaction precludes any future penalty assessments or accruals for failure to pay, and presupposes the taxpayer's continued reasonable cause beyond the present. A penalty abatement, pre-determined with respect to future conditions, can seldom be objectively valid. An exception to this general rule involves the first-time-abate provision in IRM 20.1.1.3.3.2.1, First Time Abate (FTA).

Field personnel in contact with taxpayers, being provided more detailed information regarding the conditions relating to the original penalty assessment, may abate the assessment in whole or in part; or, they may re-assess a prior penalty abatement provided supporting facts warrant it and the statute of limitations on assessment is still open. Field personnel should follow established local procedure to adjust penalties in accordance with the policies laid out in this IRM.

≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡See IRM 20.1.1.3.2, Reasonable Cause, and IRM 20.1.1.3.3.2.1, First Time Abate (FTA).

Also see IRM 20.1.1.3.3.2.1, First Time Abate (FTA), for first-time-abate/clean-compliance-history provisions.

A taxpayer may write in to request a waiver of FTP penalties based on relief granted under Notice 2013-24. The relief applies only to returns for tax periods ended 12/31/2012 or later, with a return due date before June 2013, without regard to extensions. This relief should be applied before applying "first time abate" (FTA) provisions.

Before granting the relief, verify the taxpayer has met all of the requirements for relief:

If the taxpayer qualifies for relief under this provision, abate the FTP penalty with TC 271, Reason Code 062, Penalty Reason Code 030. Include unassessed FTP penalty accruals in the abatement.

Notice 2015-09 provides penalty relief for qualifying taxpayers with respect to the penalty for failure to pay tax shown on their 2014 return. It also provides for relief with respect to the penalty for underpayment of estimated tax for 2014. (See IRM 20.1.3, Estimated Tax Penalties, for estimated tax waiver information.) Qualifying taxpayers requesting relief under Notice 2015-09 should be provided this relief before applying relief provided for in IRM 20.1.1.3.3.2.1, First Time Abate (FTA).

To qualify for the relief from the penalty for failure to pay, all of the following criteria must be met:

If any portion of the unpaid balance qualifies for relief under Notice 2015-09, the entire failure-to-pay penalty should be abated, even the portion that is unrelated to the repayment of the excess advance payment of the Premium Tax Credit.

If the taxpayer qualifies for the penalty relief and the tax has already been paid in full, abate the penalty as described in IRM 20.1.2.2.4.1 (4) with reason code 062 and penalty reason code 022.

If the taxpayer qualifies for the penalty relief and the tax has not yet been paid, abate the assessed penalty with TC 271, reason code 065, and penalty reason code 029.

Notice 2015-30 provides penalty relief for qualifying taxpayers with respect to the penalty for failure to pay tax under IRC 6651(a)(2) and IRC 6651(a)(3) on their 2014 return. It also provides for relief with respect to the penalty for underpayment of estimated tax under IRC 6654, and the accuracy-related penalty under IRC 6662 for 2014. (See IRM 20.1.3, Estimated Tax Penalties, for estimated tax waiver information, and IRM 20.1.5.7, Penalty Relief, for information on accuracy-related penalty relief.) Qualifying taxpayers requesting relief under Notice 2015-30 should be provided this relief before applying relief provided in IRM 20.1.1.3.3.2.1, First Time Abate (FTA).

To qualify for the relief from the penalty for failure to pay, all of the following criteria must be met:

If any portion of the unpaid balance qualifies for relief under Notice 2015-30, the entire failure-to-pay penalty should be abated, even the portion that is unrelated to the late receipt or incorrect Form 1095-A.

If the taxpayer qualifies for the penalty relief, abate the penalty as described in IRM 20.1.2.2.4.1 (4) with reason code 062 and penalty reason code 022.

IRS employees are not required to "second-guess" every penalty assessment encountered. However, in order to preserve the trust of taxpayers, it is expected IRS employees will review penalty computations when penalties are questioned by taxpayers, and errors will be corrected when they are identified.

Below are some examples of errors identified and corrected by diligent employees. It is expected IRS employees identify these errors. Please note this list is not all-inclusive:

Beginning in July 2014, IDRS command code INTST began using the same programming as master file for nearly all failure to pay penalty and interest computations. The total penalty and interest reflected on corporate files on-line (CFOL) (IDRS command code IMFOLT or BMFOLT) for a specific tax module should therefore match the total penalty and interest computed by INTST when computed to the interest date shown on CFOL. If there is a discrepancy in the interest and/or penalty between INTST and CFOL, and the discrepancy cannot be traced to a pending transaction, then the discrepancy must be reported to the responsible analyst in the Office of Servicewide Penalties or in the Office of Servicewide Interest. Penalties analyst assignments can be found on the irweb on the Knowledge Management Penalties’ News and Contacts page at Penalties Knowledge Base - PenaltyNewsAndAlertsAndContacts - GrpByChap (sharepoint.com).

The penalty for failure to pay is asserted beginning with the return due date with respect to "tax shown" on the taxpayer’s return. This amount is not synonymous with "total tax per taxpayer." "Tax shown" on a taxpayer’s return must take into account certain refundable credits claimed by the taxpayer, even if those credits are not allowed during return processing. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡" ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

When tax or certain refundable credits reported or claimed by the taxpayer are either not recorded or recorded incorrectly, the result is an incorrect penalty calculation for failure to pay tax shown on the return, because "tax shown" will not have been computed correctly during return processing.

"Tax shown on the return" is defined as total tax per taxpayer minus certain credits claimed by the taxpayer on his return. IRM 20.1.2.3.8.4.1 lists the credits taken into consideration in the computation of "tax shown on the return."

We can record the correct "tax shown on the return" amount via IDRS command code ADJ54 using item reference number 871 whenever necessary. The following are some circumstances where the recorded "tax shown" may require correction:

"Amount" in the bullets above refers to the amount of "tax shown" recorded for the return. (See IMFOLR and BMFOLR.) "Tax shown" is corrected or recorded in the account via ADJ54 by including item reference number 871 with the correct "tax shown" amount in the adjustment. Use appropriate Hold Code and Priority Code. See IRM 20.1.2.2.6.3 for additional information." Tax shown" is corrected or recorded in the account via AMCLS by including IRN 871 with the correct "tax shown" as an item 15 in the closing transaction. Use appropriate Hold and Priority Codes.

IMF returns pose a special challenge when computing "tax shown on the return" because not all of the tax shown on Form 1040 is necessarily assessed on MFT 30. Therefore, amounts assessed on MFT 29 (excise taxes from Form 5329) and on MFT 35 (shared responsibility payments) must be excluded when computing "tax shown on the return" for MFT 30 and MFT 31. The following table was designed to assist in the computation. Not all rows in this table will apply to all years. An IAT tool (or something similar) will be provided to aid in this computation.

Computing "tax shown on the return" is simpler for forms other than Form 1040.

Prior to 2016, the computer was not able to accurately compute the FTP penalty on tax shown on a taxpayer’s return if FTP penalty was due in any of the following conditions:

Since the computer was unable to compute the FTP penalty for these cases prior to 2016, FTP penalty had to be manually computed and assessed when applicable. See IRM 20.1.2.2.5, Manual Penalty Adjustment, paragraph 2(a).

Programming implemented in January 2016 allows for systemic computation of the FTP penalty for superseding returns and in cases where the wrong return posted first and created the posted TC 150 transaction. The following steps must be followed if the correction will result in a balance due, or if any of the tax due on the correct return was paid after the original return due date without regard to extensions:

Following the above procedures will ensure the FTP penalty will be computed correctly and systemically as applicable for the taxpayer’s correct return, and for any future adjustments. While the above procedures are only required for certain situations, they are encouraged to be used in any situation where the wrong return posted first.

The IRS provides explanations of all penalty and interest charges to the taxpayer when a Master File assessment notice is issued. Penalties and interest may also be explained to taxpayers "on request" using the Penalty and Interest Notice Explanation (PINEX) system.

Upon request, command code PINEX generates a notice of explanation to the taxpayer. The specific tax module requested must be on the Taxpayer Information File (TIF) data base and at least one unreversed penalty or interest transaction must be posted.

The PINEX notice includes a computation and explanation of selected computer generated penalty and interest charges.

PINEX notices must be reviewed for accuracy by the tax examiner requesting the notice. If the notice is correct it may be mailed to the taxpayer. The review should include comparison with penalty and interest on Master File. See IRM 20.1.2.2.6.1 (3), Identifying Incorrect Assessments, paragraph (3).

PINEX also provides screen displays of penalty and interest computations for an immediate response to telephone inquiries or requests at taxpayer assistance centers and field offices. IRS personnel may find the screen displays helpful in analyzing penalty and interest transactions in general. Available screen display command codes are:

See the applicable subsection of IRM 20.2.1 for more information about command codes listed above related to interest.

If a PINEX notice or screen display referenced above does not match the Master File computation, and the discrepancy cannot be traced to a pending transaction, then the penalty may need to be manually computed and adjusted, with a manually prepared explanation of the penalty computation provided to the taxpayer. See IRM 20.1.2.2.6.1 , Identifying Incorrect Assessments for additional instructions.

Prior to processing cycle 201603 for BMF tax modules, and 201604 for IMF tax modules, command code INTST with definer "D" , and PINEX FTP penalty computations, will display tax changes and credit changes separately in the FTP penalty computation table. After those cycles tax changes will be netted with changes in refundable tax credits to determine if the net amount is an increase or a decrease. A net increase will be depicted as a tax increase, and a net decrease will be depicted as a tax decrease. For example:

Carryback tax transactions will only be netted with those refundable tax credits affected by carryback adjustments.

When the tax required to be shown on a return is less than the tax shown on the return (or less than the tax previously assessed), the FTP penalty is computed on the lesser amount. See IRC 6651(c)(2).

Net tax decreases are applied against tax increases, and against tax shown on the return, in last in, first out (LIFO) order, in determining the amounts subject to the FTP penalty under either IRC 6651(a) paragraph (2) or (3).

The examples in paragraphs (4) and (5) illustrate the mechanics of this process.

Taxpayer files an original return reflecting $10,000 tax. IRS corrects a math error during processing of the return, and decreases tax to $8,000. During a subsequent examination it is determined the correct tax is $13,000, and the additional tax is assessed.

Taxpayer files an original return reflecting $8,000 tax. IRS corrects a math error during processing of the return, and increases tax to $13,000. During a subsequent examination it is determined the correct tax is $10,000, and the excess $3,000 is abated.

Remember certain refundable credits must be taken into consideration when determining tax shown and required to be shown on a return. See IRM 20.1.2.3.8.4.1 (2) and IRM 20.1.2.3.8.5.1 (2).

The period subject to the penalty for filing late under IRC 6651(a)(1) begins on the day following the latest of the following dates:

Each month subject to the penalty ends on the day of the month corresponding with the day of the month of the latest return due date as determined above, and each new month subject to the penalty shall begin the next day, with the following exceptions:

Because the penalty cannot exceed 25 percent, it is not charged for more than 5 months.

The amount subject to the penalty is the tax required to be shown on the return, reduced by the following:

The amount subject to penalty is not reduced by any payment made after the payment due date, unless paid during a period to be disregarded in determining if the payment is late. See IRM 20.1.2.2.2

IRC 6651(c)(1) provides the penalty for filing late under IRC 6651(a)(1) is to be reduced by the amount of any penalty for paying late imposed under IRC 6651(a)(2) for any month during which both penalties apply.

The above reduction does not reduce the total penalty for filing late below the minimum penalty, if applicable. See IRM 20.1.2.3.7.4.

≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

If the return is more than 60 days late, and the normal computed penalty is less than the amount listed in the table below, then a minimum penalty applies:

If the total unpaid tax on the return due date (amount subject to IRC 6651(a)(1) - see IRM 20.1.2.3.7.2) is less than the amount in the table above, then penalty is the lesser amount.

The minimum penalty applies only to income tax returns. It does not apply to employment tax, excise tax, gift tax, or estate tax returns. It also does not apply to individual income tax returns if the taxpayer was not required to file except to report the following:

Abate any excessive minimum penalty amount using Transaction Code (TC) 161 with Penalty Reason Code (PRC) 045.

IRC 6651(f) provides for an increase in the penalty rate for failure to file if the failure to file is fraudulent. The penalty rate is increased from 5 percent per month to 15 percent for each month or part of a month the return is late, and the maximum penalty is increased from 25 percent of the amount subject to IRC 6651(a)(1) (see IRM 20.1.2.3.7.2) to 75 percent of that amount.

The fraudulent failure to file (FFTF) penalty is a counterpart of the civil fraud penalty under IRC 6663 and should be investigated and asserted in the same manner.

The following factors should be considered when developing a FFTF case:

When a return was filed late due to fraud, and the return reflects a deficiency due to fraud, Area Counsel should be consulted in deciding whether to propose the civil fraud penalty under IRC 6663, or the fraudulent failure to file penalty under IRC 6651(f).

≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡≡

A criminal conviction under IRC 7203 does not prevent the taxpayer from disputing the FFTF penalty under IRC 6651(f); however, the taxpayer is collaterally estopped from challenging the regular FTF penalty under IRC 6651(a). Only a criminal conviction under IRC 7201 collaterally estops the taxpayer from disputing fraud penalties. See IRM 4.8.9.18.4, Civil Fraud Penalty, and IRM 4.8.9.18.5, Alternative to Civil Fraud Penalty, for the parallel consideration with respect to the civil fraud penalty under IRC 6663 and the criminal sanction with respect to tax evasion under IRC 7201. See also IRM 25.1.7.7, Civil Closure, on the same issue.

For periods disregarded in determining the due date used for computing the penalty, see IRM 20.1.2.2.2, Disregarded Periods.

For individuals and entities outside the United States, see IRM 20.1.2.2.3.3, Taxpayers Abroad.

For return due dates (without regard to extensions), see Document 6209, Section 2, Part 3, Due Date of Returns.

For explanatory language regarding the failure to file (FTF) penalty on a notice of deficiency, see IRM 4.8.9.18.2.4, Penalty Explanations.

For each month of the period during which each failure to pay (FTP) penalty applies, the penalty is computed by multiplying the amount subject to the penalty by the penalty rate. The total penalty is the sum of the penalties for all months to which a failure to pay penalty applies.

The basic penalty rate is generally ¹/₁ percent.

For conditions under which the basic penalty rate is increased to 1 percent, see IRM 20.1.2.3.8.1.1.

For conditions under which the basic penalty rate is decreased to ¹/₁ percent, see IRM 20.1.2.3.8.1.2.

The penalty for each underlying tax assessment may not exceed 25 percent in the aggregate. Meaning each month the penalty rate is added to the sum of the penalty rates for all preceding months subject to that penalty. The penalty rate for any month cannot be greater than the rate needed for the aggregate rate to reach 25 percent.

A separate penalty computation applies to tax shown on the return, and to each notice reflecting additional tax required to be shown on the return that was not included in a prior notice. This means the 25 percent aggregate maximum may be reached for tax shown on the return while the FTP penalty is still accruing for additional tax billed in a subsequent notice.

When the 25 percent aggregate maximum has been reached for ALL tax assessed in a module, Master File generates Transaction Code (TC) 971 with Action Code (AC) 262. If the penalty is being manually computed and assessed, TC 971 with AC 262 may need to be manually input if the aggregate maximum has been reached for all assessed tax.

IRS's computers determine "unpaid tax" by applying specific rules in the application of payments to unpaid liabilities. Manual penalty computations should follow the same rules.

For the purpose of computing the penalties for failure to pay tax, payments credited against a tax return liability are applied as of their effective date.

The following are considered payments for the purpose of this subsection:

Each payment is applied individually to individual assessments that make up the overall liability until that payment is used up, or until the overall liability is paid. Payments are applied to assessments until the assessment is paid, in the following order of priority:

The effect of refunds and offsets out of the module is to

IRC 6601(e)(3) provides no additional interest is to be imposed beyond the date of any notice and demand for payment to the extent the amount shown in the notice is paid within 21 days after the date of the notice (10 business days, if the amount in the notice is $100,000 or more). Although there is no similar provision in the law governing the penalty for paying late, IRS also will not impose additional late payment penalty computed beyond the date of notice and demand to the extent the tax shown in the notice is paid within the given time frame. To accomplish this, IRS treats payments mailed within the given time frame as made on the date of the notice. See IRM 20.1.2.2.1, When Timely Mailing Equals Timely Filing or Paying.

For the purpose of determining tax shown in a notice and demand for payment, tax abatements are applied to preceding tax assessments in "first in, first out" (FIFO) order.

After all preceding assessments have been set to zero, any remaining abatement is applied to "tax shown on the return," which may end up being less than zero.

IRC 6651(a)(2) provides for a penalty if the tax shown on any return is not paid by the due date for payment, unless the failure to pay is due to reasonable cause and not due to willful neglect.

Reasonable cause is presumed for certain taxpayers with an extension of time to file if specific criteria are met. See IRM 20.1.2.2.3.1 (5). Also see IRM 20.1.1.3, Criteria for Relief From Penalties, for a discussion of penalty relief, and IRM 20.1.2.2.4.1, Penalty Abatements and Re-assessments, for an in-depth discussion of reasonable cause considerations relating to the failure to pay tax.

This penalty applies to the following returns:

This penalty does not apply to the following:

For each month or part of a month the tax remains unpaid, the penalty is generally ¹/₁ percent of the unpaid tax. However, the penalty rate may increase to 1 percent per month, or decrease to ¹/₁ percent per month. See IRM 20.1.2.3.8.1.1 and IRM 20.1.2.3.8.1.2.

The penalty generally does not apply for any month during which a bankruptcy proceeding is pending against the taxpayer. See IRM 20.1.2.3.8.6.

IRC 6651(a)(3) provides for a penalty if tax required to be shown on a return, but which was not shown, is not paid by the date stated in the notice and demand for payment. The penalty does not apply if the failure to pay is due to reasonable cause, and not due to willful neglect. See IRM 20.1.1.3, Criteria for Relief From Penalties, for a discussion of penalty relief. Also see IRM 20.1.2.2.4.1, Penalty Abatements and Re-assessments, for an in-depth discussion of reasonable cause considerations relating to the failure to pay tax.

This section applies to additional amounts assessed as follows:

The date for payment stated in the notice is 21 calendar days following the date of the notice if the amount in the notice is less than $100,000. Otherwise the date is 10 business days after the date of the notice.

The penalty does not apply if the failure to pay is due to reasonable cause and not due to willful neglect.

For each month or part of a month during which the underlying tax remains unpaid, the penalty generally is ¹/₁ percent of the unpaid tax. However, the penalty rate may increase to 1 percent per month, or decrease to ¹/₁ percent per month. See IRM 20.1.2.3.8.1.1 and IRM 20.1.2.3.8.1.2.

The penalty generally does not apply for any month during which a bankruptcy proceeding is pending against the taxpayer. See IRM 20.1.2.3.8.6.

IRC 6658(a) prohibits the assertion of the late payment penalties while a bankruptcy proceeding is pending against the taxpayer if either of the following applies:

The prohibition in IRC 6658(a) shall not apply to any liability for an addition to the tax which arises for failure to pay or deposit a tax withheld or collected from others and required to be paid to the United States.

In the case of tax incurred before the start of a bankruptcy proceeding, a penalty for failure to pay will not be asserted for any penalty month beginning during the period during which the bankruptcy proceeding is pending. See Rev. Rul. 2005-9, 2005-1 C.B. 470 for an explanation of when a bankruptcy case is considered "pending." IRS records the period during which a bankruptcy proceeding is pending through the use of Transactions Codes (TC) 520, 521, and 522:

The following four subsections demonstrate how the penalties under IRC 6651 are to be computed.

IRM 20.1.2.3.8.7.1 shows how the penalty for failure to pay tax shown on the return is coordinated with the penalty for failure to file.

IRM 20.1.2.3.8.7.2 shows how the penalty for failure to file attributable to a deficiency is computed for inclusion on the notice of deficiency.

IRM 20.1.2.3.8.7.3 shows how the penalty for failure to pay tax upon notice and demand is computed. It also demonstrates how the increase in the penalty rate affects the penalty after issuance of a notice of intent to levy.

IRM 20.1.2.3.8.7.4 shows when and how the minimum penalty for failure to file is computed.

IDRS command code (CC) "COMPA" with definer "F" is available to compute the penalty for paying late.

The penalties under IRC 6651(a)(2) and IRC 6651(a)(3) must be computed separately when both penalties apply.

The following information must be gathered for input on IDRS:

On line one of the IDRS screen enter CC "COMPA" with definer "F" [COMPAF].

On lines 2 through 22, enter the "from" date, a space, the "to" date, a space, and the unpaid tax on the "from" date.

See IRM 2.3.29, Command Codes INTST, ICOMP, and COMPA, for more information about CC COMPA with definer "F."

Also see ELMS Learning courses 17293 and 25232 for BMF, and 17206 and 11442 for IMF. (The first listed course is the prerequisite for the second listed course respectively for BMF and IMF.)

An assessment of criminal restitution under IRC 6201(a)(4) does not constitute an assessment of an amount of tax required to be shown on a tax return specified in IRC 6651(a)(1). Therefore, the FTP penalty cannot be imposed on restitution-based assessments unless the Judgment & Commitment Order or related plea agreement specifically includes a FTP penalty. Restitution-based assessments against individuals are made on MFT 31. They are identified by Transaction Code (TC) 971 with action code 102 in the module. The assessment itself will have an adjustment reason code in the range of 141 through 146. The account or module to which the restitution-based assessment relates will be cross-referenced by a TC 971 with an action code in the range of 180 through 189. The FTP penalty can be imposed on the account or module to which the restitution-based assessment relates, if applicable, but even if it is, it cannot be imposed on the restitution-based assessment itself unless the Judgment & Commitment Order or related plea agreement specifically includes a FTP penalty.

It is important to note again a district court may include a FTP penalty in the amount of restitution ordered. When the FTP penalty is included in the amount of restitution ordered, it should be assessed on the same tax module as the restitution-based assessment. It is important that penalties and interest included in the restitution order are assessed as such, and not included with the same transaction code as tax.

The IRS may conduct a civil examination for the same tax period that has a restitution-based assessment or the taxpayer may file a delinquent return showing a tax liability for the same tax period a restitution-based assessment exists. This may result in an assessment of a civil tax liability in a different module or in the same module as the restitution-based assessment.

To prevent double collection when the restitution-based assessment is not assessed in the same module as a related civil liability, any payment credited towards the restitution-based assessment module will be cross-referenced in the related civil tax liability module using a TC 766 with a credit reference number 337; and vice versa. (Cross-referenced restitution-based assessment payments on IMF will also carry adjustment reason code 150).

When additional amounts are assessed via a quick or prompt assessment, any accrued FTP penalty must be included. The accrued FTP penalty is entered on the applicable line of Form 2859, Request for Quick or Prompt Assessment, and is assessed with TC 270.

Interest on the FTP penalty accrues beginning with notice and demand for payment of the penalty. Therefore, when demand for payment of the FTP penalty is made via the Form 3552, Prompt Assessment Billing Assembly, the amount and date of the demand must be recorded by assessing the penalty.

If the FTP penalty is not to remain restricted after the assessment, the requestor (preparer of Form 2859, or other designee) must input TC 272 for zero amount after the assessment has posted.

When deficiency procedures apply, IRS posts a "substitute for return" (SFR) Transaction Code (TC) 150 on the taxpayer's account to facilitate assessment of the deficiency.

For business returns (BMF), for tax modules containing an SFR TC 150, IRS's computers are programmed to compute the penalty for failure to pay tax shown on a return (IRC 6651(a)(2)) using the sum of the first assessment in the module, plus any tax assessed subsequently with TC 290 with Priority Code 2, or with TC 300 with Priority Code 9.

For individual returns (IMF), for tax modules containing an SFR TC 150, IRS's computers are programmed to compute the penalty for failure to pay tax shown on a return (IRC 6651(a)(2)) using the sum of all tax assessed with TC 290 with Priority Code 2, or with TC 300 with Priority Code 3 or 9.

Also see IRM 20.1.2.3.8.3, Application of Tax Abatements.

In two Tax Court cases in 2003, Cabirac v. Commissioner, 120 T.C. 63 (2003) and Spurlock v. Commissioner, T.C. Memo. 2003-124, the judge denied the IRS the assessment of the penalty under IRC 6651(a)(2), failure to pay tax shown on a return, because the requirements for a valid IRC 6020(b) return were not met. In conjunction with Chief Counsel, Form 13496, IRC 6020(b) Certification, was conceived to ensure the penalty under IRC 6651(a)(2) will be sustained in future court cases.

Specific procedures must be followed when deficiency procedures apply for the assessment of tax under IRC 6020(b). The procedures must be followed to assure the assessment of the penalty under IRC 6651(a)(2) will be sustained in court if the assessment is challenged.

When deficiency procedures do not apply, tax determined under IRC 6020(b) can be assessed in two ways:

An audited partnership that fails to make a timely push-out election with respect to a final partnership adjustment will be assessed an imputed underpayment. Unless the partnership waives the restriction, the assessment may be made no earlier than 90 days after the date of Letter 5933, Letter 5933-A; or, if a petition is filed in court with respect to the final partnership adjustment, no earlier than the date on which the court’s decision becomes final.

The imputed underpayment is assessed in the adjustment year.

Under IRC 6233, if a partnership fails to pay an imputed underpayment by the date prescribed for payment, the partnership becomes subject to the penalty for failure to pay tax shown on a return IRC 6651(a)(2). For the purpose of computing this penalty the following rules apply:

The following entities can be pass-through entities that are partners in a partnership

When a pass-through partner entity receives a push-out statement (Form 8986) from an audited partnership, it is required to file Form 8985, Pass-Through Statement-Transmittal/Partnership Adjustment Tracking Report (Required Under Sections 6226 and 6227). It is also required to either calculate and pay an imputed underpayment based on the statement it received, OR it must issue push-out statements (Form 8986) to all its partners, beneficiaries, or shareholders.

The due date for filing Form 8985 and issuing Form 8986 is the extended return due date of the audited partnership’s adjustment year return. The extended return due date for this purpose is determined without regard to the audited partnership’s filing requirement for the adjustment year, and without regard to the actual filing of an application for an extension of time to file by the audited partnership. See 26 CFR 301.6226-3(e)(3)(ii). Currently this means the due date for filing Form 8985 and for furnishing Forms 8986 is the 15th day of the 9th month following the end of the audited partnerships adjustment year.

IRC 6031 requires a partnership to include in its return all of the information which "the Secretary may by forms and regulations prescribe." The penalty under IRC 6698 may be applied if any required information is missing.

≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡

A penalty cannot be asserted under IRC 6698 for failure to attach required statements to Schedules K-1 sent to partners.

IRC 6231(a)(1)(B) exempts certain small partnerships from the unified audit procedures contained in subchapter C of chapter 63 of the IRC. However, an exemption from the unified audit procedures is not an exemption from the requirement to file a timely and complete partnership return.

Rev. Proc. 84−35 provides reasonable cause for filing a late or incomplete return will be presumed for certain small partnerships if certain criteria are met:

≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

When abating the penalty under the provisions of Rev. Proc. 84-35, advise the taxpayer the penalty will be reassessed if it is later determined any of the criteria outlined in Rev. Proc. 84-35 have not been met: Specifically, if it is found any partner was not a qualifying partner; or, if any partner filed late; or, if any partner failed to report their share of partnership income on their return, then the penalty will be reassessed.

A request for penalty abatement under Rev. Proc. 84-35 must initially be denied if it appears the partnership is under an election to be subject to the unified audit procedures. See IRM 20.1.2.4.3.1.1, Form 8893 and 8894. A response to such a denial should not be treated as an appeal if the taxpayer provides additional information with respect to the election:

Partnerships that do not qualify for abatement of the penalty under Rev. Proc. 84-35 may still qualify for abatement of the penalty under normal reasonable cause criteria.

Rev. Proc. 2003-84 allows certain partnerships investing in tax-exempt obligations to make an election that enables the partners to take into account monthly inclusions required under IRC 702 and IRC 707. Rev. Proc. 2003-84 also provides rules for partnership income tax reporting. Thus, a partnership having a monthly closing election in effect for the entire taxable year and meets the other requirements in section 8 of this revenue procedure, is not required to file a Form 1065 or issue Schedules K-1 (Form 1065).

An eligible partnership makes a monthly closing election effective as provided under section 4.02 of this revenue procedure, and all partners must consent to this election.

The monthly closing election is effective on the later of the following:

A partnership must file an abbreviated return (considered abbreviated because only certain information is required to be completed on the form) for the first taxable year during which the monthly closing election was in effect. The abbreviated return must be filed by the date the partnership’s return would ordinarily be due. The words "Filed in Accordance with Rev. Proc. 2003-84" must be typed or written across the top of the form. See Rev. Proc. 2003-84 for the specific information that must be supplied on the abbreviated return.

If a late filing penalty was assessed because the required abbreviated return was late, and the partnership does not otherwise qualify for relief under any of the criteria in IRM 20.1.2.4.3, Penalty Relief, do not abate the penalty.

If a missing information penalty was assessed, and the missing information was not required under Rev. Proc. 2003–84, abate the penalty.

If a penalty for filing a late or incomplete return was assessed for any year following the first year, abate the penalty provided the taxpayer still qualifies for the elimination of the Form 1065 filing requirement under section 8.02 of Rev. Proc. 2003-84.

A partnership that fails to satisfy all of the requirements of section 8.02 (1) of Rev. Proc. 2003–84 is required to file a complete (not abbreviated) Form 1065 and to issue Schedules K-1 (Form 1065) to its partners as required by IRC 6031(a). A partnership that fails to file a Form 1065 or to issue Schedules K-1 as required is subject to the applicable penalties under IRC 6698 and IRC 6722 for failure to file a partnership return and to furnish payee statements, as well as any other applicable penalties. Moreover, if a partnership is required to file a return under IRC 6031(a) but fails to do so, the period of limitations on assessment of tax attributable to partnership items remains open indefinitely under IRC 6229(a).

See Rev. Proc. 2003-84, 2003-2 C.B. 1159 and IRM 21.7.4.4.2.12, Form 1065 Filed under Revenue Procedure 2003-84, for more information.

IRC 6032 requires banks maintain a common trust fund (see IRC 584) to file annual information returns by April 15 following the end of the calendar year. No particular form is prescribed for making this return, but if Form 1065, U.S. Return of Partnership Income, is used, it should reflect all items of gross income and deductions of the fund, and identify all participants and their proportionate share.

The penalty under IRC 6698 does not apply to returns required to be filed under IRC 6032. Therefore, filers who use Form 1065 to meet their filing requirement under IRC 6032 are not subject to the penalty for filing a late or incomplete return under IRC 6698.

Forms 1065 submitted by common trust fund filers, and received after April 15, should have the failure to file (FTF) penalty suppressed by applying computer condition code (CCC) "R" during processing. If information or attachments to affected returns are missing, processing functions should not apply missing schedule codes to the return.

When a Form 1065 filer requests abatement of either the penalty for filing late, or the missing information penalty, review the taxpayer's correspondence and case file for evidence the taxpayer filed Form 1065 to meet their filing requirement under IRC 6032. Check for the following:

If the evidence shows Form 1065 was filed under IRC 6032, take the following actions as applicable:

Although a real estate mortgage investment conduit (REMIC) is treated as a partnership for the purpose of penalties related to filing, the return (Form 1066) can include tax imposed under Chapter 1 of Subtitle A. If tax is reported on Form 1066, U.S. Real Estate Investment Conduit (REMIC) Income Tax Return, the return is required to be filed both under IRC 6031 (relating to information returns required to be filed by partnerships), and under IRC 6012 (relating to income tax returns required to be filed by persons with income taxes under subtitle A). Therefore, when tax is reported on a late Form 1066, the return may be subject to both the penalty under IRC 6651(a)(1), and to the penalty under IRC 6698.

≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

Any TC 160 or TC 166 assessed against Form 1066 represents the failure-to-file penalty under IRC 6651. This penalty should be removed if the penalty under IRC 6698 is being imposed.

≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

Interest programming for Form 1066 (MFT 07) assumes any TC 16X on MFT 07 is a penalty assessed under IRC 6651(a)(1). Accordingly, it charges interest on TC 16X assessments beginning with the return due date on MFT 07. However, interest on the penalty under IRC 6698 does not begin until the date of notice and demand for payment of the penalty. Therefore, the TC 160 should not be used to assess the penalty under IRC 6698 against Form 1066 (MFT 07). See IRC 6601(e)(2)(A).

The return of an electing large partnership (Form 1065-B, U.S. Return of Income for Electing Large Partnerships) can include tax imposed under Chapter 1 of Subtitle A. If tax is reported on Form 1065-B, the return is required to be filed both under IRC 6031 (relating to information returns required to be filed by partnerships), and under IRC 6012 (relating to income tax returns required to be filed by persons with income taxes under subtitle A). Therefore, when tax is reported on a late Form 1065-B, the return may be subject to both the penalty under IRC 6651(a)(1), and to the penalty under IRC 6698.

≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

These provisions only apply for partnership taxable years beginning prior to January 1, 2018 to which the partnership procedures of sections 6221-6234, as enacted by the Tax Equity and Fiscal Responsibility Act of 1982 ("TEFRA" ), apply for the taxable year.

IRS programming was changed through a Unified Work Request to meet the requirements of IRC 6751(a)(1).

Penalties will now be assessed with a PRN and IRN. When the adjustment posts, it will show as a TC 240 based on the PRN used. The PRN and IRN are input so penalty information will pass to the notices.

Assessment of the penalty under IRC 6698 does not follow deficiency procedures, and the taxpayer does not have any pre-assessment appeal rights. However, examiners must make every effort to obtain sufficient information to determine if the penalty applies, or if the taxpayer's failure to comply was due to reasonable cause.

Compute the penalty using the IRC6698and6699PenaltyComputationTool.xlsm (sharepoint.com)

Once the penalty amount is figured, follow local procedures.

PRNs 722 and 723 can only be assessed when TC 290 or TC 300 is $0.00.

If removing a penalty and assessing another penalty, two separate adjustments need to be done. Input the penalty being removed first, then input the penalty being assessed with a cycle delay of one cycle.

IRC 6037 requires a S corporation to include in its return all of the information which "the Secretary may by forms and regulations prescribe." The penalty under IRC 6699 may be applied if any required information is missing.

≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡

A penalty cannot be asserted under IRC 6699 for failure to attach required statements to Schedules K-1 sent to shareholders.

When a corporation ceases to be a small business corporation because it no longer qualifies, the "S" corporation election is terminated, and the corporation is required to file two short year returns for the termination year:

≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

Follow the instructions in the table below for ALL short termination year S corporation returns:

IRS programming was changed through a Unified Work Request to meet the requirements of IRC 6751(a)(1).

Penalties will now be assessed with a PRN and IRN. When the adjustment posts, it will show as a TC 240 based on the PRN used. The PRN and IRN are input so penalty information will pass to the notices.

Assessment of the penalty under IRC 6699 does not follow deficiency procedures, and the taxpayer does not have any pre-assessment appeal rights. However, examiners must make every effort to obtain sufficient information to determine if the penalty applies, or if the taxpayer's failure to comply was due to reasonable cause.

Compute the penalty using the Penalty Computation Tool.

Once the penalty amount is figured, follow local procedures.

PRNs 722 and 723 can only be assessed when TC 290 or TC 300 is $0.00.

If removing a penalty and assessing another penalty, two separate adjustments need to be done. Input the penalty being removed first, then input the penalty being assessed with a cycle delay of one cycle.