1545-1837_supporting_statement_20160115(NW)

1545-1837_supporting_statement_20160115(NW).doc

Revenue Procedure 2003-36, Industry Issue Resolution Program

OMB: 1545-1837

Document [doc]
Download: doc | pdf

SUPPORTING STATEMENT

Revenue Procedure 2003-36

OMB #1545-1837



  1. CIRCUMSTANCES NECESSITATING COLLECTION OF INFORMATION


Revenue Procedure 2003-36 describes procedures for business taxpayers, industry associations, and other interested parties to submit issues for consideration under the IRS’s Industry Issue Resolution (IIR) Program. The objective of the program is to identify frequently disputed or burdensome tax issues that are common to a significant number of business taxpayers that may be resolved through published or other administrative guidance.


  1. USE OF DATA


The collection of information is required to submit and request for the IRS to consider an issue under the IIR Program. This information will be used to enable the Service to determine whether the issue is suitable for determination under the IIR Program.


  1. USE OF IMPROVED INFORMATION TECHNOLOGY TO REDUCE BURDEN


There are no plans to provide electronic filing because electronic filing is not appropriate for the collection of information in this submission.


  1. EFFORTS TO IDENTIFY DUPLICATION


We have attempted to eliminate duplication within the agency wherever possible.


  1. METHODS TO MINIMIZE BURDEN ON SMALL BUSINESSES OR OTHER SMALL ENTITIES


There are no small entities affected by this collection.


  1. CONSEQUENCES OF LESS FREQUENT COLLECTION ON FEDERAL PROGRAMS OR POLICY ACTIVITIES


If the IRS did not collect this information, the IRS would not be able to identify frequently disputed or burdensome tax issues that are common to a significant number of business taxpayers that may be resolved through published or other administrative guidance. Therefore, the IRS would not be able to determine whether the issue is suitable for determination under the IIR Program.



  1. SPECIAL CIRCUMSTANCES REQUIRING DATA COLLECTION TO BE INCONSISTENT WITH GUIDELINES IN 5 CFR 1320.5(D)(2)


There are no special circumstances requiring data collection to be inconsistent with Guidelines in 5 CFR 1320.5(d)(2).


  1. CONSULTATION WITH INDIVIDUALS OUTSIDE OF THE AGENCY ON AVAILABILITY OF DATA, FREQUENCY OF COLLECTION, CLARITY OF INSTRUCTIONS AND FORMS, AND DATA ELEMENTS


Revenue Procedure 2003-36 was published in the Internal Revenue Bulletin on May 5, 2003 (2003-18 IRB 859).


We received no comments during the comment period in response to the Federal Register notice 80 FR 69778, dated November 10, 2015.


  1. EXPLANATION OF DECISION TO PROVIDE ANY PAYMENT OR GIFT TO RESPONDENTS


No payment or gift has been provided to any respondents.


  1. ASSURANCE OF CONFIDENTIALITY OF RESPONSES


Generally, tax returns and tax return information are confidential as required by 26 USC 6103.


  1. JUSTIFICATION OF SENSITIVE QUESTIONS


No personally identifiable information (PII) is collected.


  1. ESTIMATED BURDEN OF INFORMATION COLLECTION


The filing requirements are in Sections 6 and 7 of the revenue procedure. This information is required to submit a request for the IRS to consider an issue under the IIR Program. It is estimated that 50 respondents will submit issues under the IIR Program annually. The estimated average reporting burden per respondent is 40 hours. The estimated reporting burden is 2,000 hours.


Estimates of the annualized cost to respondents for the hour burdens shown are not available at this time.




  1. ESTIMATED TOTAL ANNUAL COST BURDEN TO RESPONDENTS


There are no start-up costs associated with this collection.


  1. ESTIMATED ANNUALIZED COST TO THE FEDERAL GOVERNMENT


There are no known annualized costs to the federal government.


  1. REASONS FOR CHANGE IN BURDEN


There is no change in the paperwork burden previously approved by OMB. We are making this submission to renew the OMB approval.


  1. PLANS FOR TABULATION, STATISTICAL ANALYSIS AND PUBLICATION


There are no plans for tabulation, statistical analysis and publication.


  1. REASONS WHY DISPLAYING THE OMB EXPIRATION DATE IS INAPPROPRIATE


We believe that displaying the OMB expiration date is inappropriate because it could cause confusion by leading taxpayers to believe that the revenue procedure will sunset as of the expiration date. Taxpayers are not likely to be aware that the IRS intends to request renewal of the OMB approval and obtain a new expiration date before the old one expires.


  1. EXCEPTIONS TO THE CERTIFICATION STATEMENT


There are no exceptions to the certification statement for this collection.




Note: The following paragraph applies to all of the collections of information in this submission:


An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless the collection of information displays a valid OMB control number. Books or records relating to a collection of information must be retained as long as their contents may become material in the administration of any internal revenue law. Generally, tax returns and tax return information are confidential, as required by 26 U.S.C. 6103.




3



File Typeapplication/msword
File Title#1545-1837 supporting statement
AuthorInternal Revenue Service
Last Modified ByDepartment of Treasury
File Modified2016-01-20
File Created2016-01-20

© 2024 OMB.report | Privacy Policy