Accessibility Skip to Top Navigation Skip to Main Content Home  |  Change Text Size  |  Contact IRS  |  About IRS  |  Site Map  |  Español  |  Help  

3.42.4  for Business Tax ReturnsIRS (Cont. 2)

3.42.4.7 
Signature Documents for IRS Programs

3.42.4.7.5  (01-01-2009)
PIN Registration Method for 944/941 and 940 e-file Programs

  1. This section provides the guidelines and processing steps for handling signature documents for the 944, 941 and 940 e-file Programs.

  2. For 944, 941 and 940 On-Line Programs, Reporting Agents are issued a PIN used to sign Forms 944, 941 and 940 for their clients with a Form 8655 on record with IRS. Reporting Agents must submit Form 8655 with their Agent's List to the Ogden Submission Processing Campus prior to completing their IRS e-file Application.

    Note:

    Andover e-help Desk must always research the RAF to verify if the Reporting Agent information is present on the RAF before completing the Approval Process and activating the PIN

    .

  3. The Third Party Data Store (TPDS) allows for the PIN Registration functionality for Reporting Agents to request a PIN.

  4. The PIN Registration Method is used to complete the PIN Registration process for 944, 941 and 940 On-Line Programs in XML format. Filers using the 944, 941 and 940 On-Line Programs, transmit their PIN Registration via an electronic means of submission through a "Third Party Provider" .

  5. PIN Registrations are submitted to the designated e-help site, and are only accepted from Business Taxpayers filing through a Third Party Provider (Transmitter) for the 944, 941 and 940 On-Line Programs.

  6. The designated e-help site is responsible for all PIN Registration Processing for the Business Taxpayer using the 944, 941 and 940 On-Line Programs.

  7. The CDB will automatically assign a PIN to the Business Taxpayer for signature purposes, once all of the information has been entered into the system.

  8. Capture the applicants information into the CDB and approve for the applicable program(s). Manually set each customer through the approval cycle using the Customer Management Command.

  9. Assign a status of 1 (Applied) at the time their customer profile is initialized in the CDB.

  10. Activate the PIN as soon as the letter is issued generating the PIN. PINs are assigned through the CDB for signature purposes for Business On-Line Filers only.

  11. Generate and mail status letters.

  12. For more information about program requirements for the 944, 941 and 940 e-file Programs review Publication 3823, Employment Tax e-file System Implementation and User Guide. Also review Publication 3112, IRS Application and Participation .

3.42.4.8  (01-01-2009)
Processing Business e-file Applications and Enrollment Forms

  1. Tax Examiners and Systems Administrators will use multiple systems to complete the e-file application process for Business e-file returns. This section provides processing guidelines to assist the e-help Operation with verifying Trading Partner transmissions, receipts, and acknowledgments for Business e-file Programs.

3.42.4.8.1  (01-01-2009)
e-help Desk Web Interface System

  1. Tax Examiners and Systems Administrators will use the e-help Desk Web Interface System to verify Trading Partner transmissions, receipts, and acknowledgments for Business e-file Programs through utilization of the e-help Support System (EHSS). Use this application to verify transmissions and acknowledgment files between EMS and other IRS servers.

  2. Do not use this system to create EMS trouble tickets. The EMS trouble ticket application is now obsolete.

  3. Tax Examiners should use the EMS e-help Web Interface User Manual to help complete the following activities:

    1. Obtain return reports

    2. Re-hang Acknowledgment Files

    3. Look at the log of transmissions

  4. The process of synchronization incorporates the use of scripts to duplicate and transfer records in the master data base to ECC-MEM. The synchronization is an automated process and instructions are found in the EMS e-help Web Interface User Manual.

  5. Tax Examiners and System Administrators should log into EMS via the EMS e-help Web Interface System to complete the PIN Registration Process. The PIN Registration information is input into the Customer Data Base.

3.42.4.8.2  (01-01-2009)
EHSS CRM (Customer Relationship Management) Application

  1. The "e-help Support System" is available for use as a trouble ticketing and support tracking tool. This application provides a customer's contact history with the e-help Operation, with each call, fax, e-mail, etc. received. This information is captured in what is known as an "e-case" .

3.42.4.8.3  (01-01-2009)
Form 8655, Reporting Agent Authorization

  1. Form 8655, Reporting Agent Authorization, is used by a Taxpayer to designate a Reporting Agent to prepare, sign and file specific Federal returns, electronically. The form is primarily used in conjunction with the following electronically filed returns:

    • Form 944, Employer's ANNUAL Federal Tax Returns

    • Form 941, Employer's QUARTERLY Federal Tax Returns

    • Form 940, Employer's Annual Federal Unemployment (FUTA) Tax Returns

    Form 8655 is also used for making Federal tax payments and Federal tax deposits.

  2. Form 8655 grants the Reporting Agent different authorities, as indicated on the form when originally submitted. For clarification of Reporting Agent authorization, see IRM 21.3.9.3, Authorizations (Form 8655).

  3. A Reporting Agent ("Agent" ), is an accounting service, franchiser, bank, service bureau, or other entity authorized by its client to prepare, sign and file Forms 944, Forms 941 and Forms 940, electronically. Reporting Agents also make Federal tax payments and submit Federal tax deposit information and Federal tax payment information electronically for the taxes reported on the following forms:

    • Form 720, Quarterly Federal Excise Tax Return

    • Form 940,Employer's Annual Federal Unemployment (FUTA) Tax Return

    • Form 941, Employer's QUARTERLY Federal Tax Return

    • Form 944, Employer's ANNUAL Federal Tax Return

    • Form 943, Employer's Annual Tax Return for Agricultural Employees

    • Form 945, Annual Return of Withheld Federal Income Tax

    • Form 990-PF, Return of Private Foundation or Section 4947(a)(1) Nonexempt Charitable Trust Treated as a Private Foundation

    • Form 990-T, Exempt Organization Business Income Tax Return

    • Form 1041, U.S. Income Tax Return for Estates & Trusts

    • Form 1042, Annual Withholding Tax Return for U.S. Source Income of Foreign Persons

    • Form 1120, U.S. Corporation Income Tax Return

    • Form 1120-C, U.S. Income Tax Return for Cooperative Associations

    • Form CT-1, Employer's Annual Railroad Retirement Tax Return

  4. Tax Examiners should advise applicants a separate authorization, Form 8655, must be submitted for each Taxpayer on the Reporting Agent's List and the list must contain each Taxpayer's Employer Identification Number (EIN).

  5. Advise participants to mail all Forms 8655, with the Reporting Agent's Listings to the following Ogden address:

    Internal Revenue Service
    Accounts Management Service Center
    MS 6748 RAF Team
    1973 North Rulon White Blvd.
    Ogden, Utah 84404

  6. Filers can also fax the Form 8655 to (801) 620-4142.

  7. Form 8655 is:

    • Submitted by Reporting Agents for each client

    • Authorization for the Reporting Agent to receive correspondence

    • Applicable only to electronic returns and Federal Tax Deposits (FTDs)/payments via the Electronic Federal Tax Payment System (EFTPS)

    • Stored on Reporting Agent File (RAF) data base

    • Effective for the quarter the Agent notifies IRS that the employer is added

    • In effect until revoked by the Taxpayer, terminated in writing from the Reporting Agent, or terminated by the Internal Revenue Service

    • Is used to terminate a Reporting Agent Authorization by signing with another service provider

  8. Tax Examiners and Taxpayer Service Representatives (TSRs) should honor all requests from a Reporting Agent for information or adjustments to an account for which the Taxpayer has given authorization. Check the Reporting Agent File (RAF) to determine if the Reporting Agent Authorization:

    • Is current

    • Applies to the filing period for the return in question

    • Gives authority to receive correspondence

  9. Accept any authorized instrument which clearly contains the same information required to be provided on Form 8655 as a valid authorization.

  10. Andover e-help Desk must research using Command Code RFINK to determine if an authorization is present on IDRS before completing the Form 8633 Approval Process. See Document 6209 for additional research information.

  11. When dealing with a third party, check the Centralized Authorization File (CAF) and the Reporting Agent File (RAF) before corresponding. Refer to the following:

    • Form 2848, Power of Attorney , also referred to as "POAs"

    • Form 8821, Tax Information Authorization , also referred to as "TIAs"

    • Form 8655, Reporting Agent Authorization , also referred to as "RAAs"

  12. Form 8655 doesn't affect any aspect of POA/TIA forms.

3.42.4.8.4  (01-01-2009)
Completing RAF Processing

  1. For complete RAF processing instructions for Form 8655, reviewIRM 21.3.9, Processing Reporting Agents File Authorizations .

  2. Research the RAF data base which contains all authorizations for Reporting Agents and their clients. If there is any question about the status of a Reporting Agent, this file will provide information about their clients and whether or not they are authorized to receive copies of correspondence.

  3. If the Taxpayer has authorized the Reporting Agent to receive copies of correspondence, set an indicator at Master File. This information is used by Notices Processing Unit to send correspondence to both the Reporting Agent and the Taxpayer.

  4. Research the Federal Tax Deposit Codes found on the entity records for the taxpayer to determine Reporting Agent Authorizations on file. For more information, See IRM 3.42.4.4.2.3.

  5. Authorizations granted by Form 8655 apply to returns filed electronically and for Federal Tax Deposits (FTDs). Form 8655 does not affect any aspect of POA/TIA forms which offer wider, more general authorizations that also apply to paper tax forms.

  6. For additional processing information review IRM 21.3.9, Processing Reporting Agents File (RAF) Authorizations.

3.42.4.8.5  (01-01-2009)
Maintaining e-case

  1. Maintain e-case, as required.

    Note:

    Opening an e-case is only required on telephone contacts.

  2. Ensure e-case contain all communications (written and otherwise) to and from the applicant, including the following, as applicable:

    • Original enrollment form

    • Copy of approval letter

    • Reporting Agent's List

    • PIN and Userid/Password receipts

    • Copy of letter providing permanent Electronic Transmitter Identification Number (ETIN), LOGIN, Test Access Code and Test Password

      Note:

      Only Transmitters and Software Developers receive a test Access Code

    • Record of any difficulties encountered in processing

    • Other related correspondence or telephone contact information

  3. Andover e-help Desk must complete the following actions before generating the approval letter:

    1. Validate the Form 8655 information on RAF

    2. Add comments to the TPDS and use the EHSS Application to update the taxpayer's e-case, if applicable

3.42.4.9  (01-01-2009)
Receiving and Controlling e-file and MeF Test Transmissions

  1. This section provides the general guidelines for the Testing Process used for the e-file and MeF business programs. The e-help Manager must ensure all duties regarding Receiving and Controlling Test Transmissions are performed correctly and all the test transmissions received are reviewed for completeness. Tax Examiners, e-help staff and others assigned will complete the actions described throughout this section, as applicable.

  2. All electronic filing applicants who plan to develop software and or transmit return data directly to the IRS, must go through the testing process before the IRS will accept them into IRS e-file .

  3. e-file and MeF participants should notify e-help Operations at 1 (866) 255-0654 when they are ready to test. If the site receiving the call is not the testing site then an e-case must be opened and transferred to the correct site.

  4. Advise prospective participants of the following information, as applicable:

    • A test transmission must be submitted for compatibility testing as required by the applicable revenue procedure. These test transmissions should be received well in advance of the return due date.

    • Test data must be transmitted on the same medium that will be used when transmitting live data.

    • Participants must complete applicable testing to ensure the returns they transmit are formatted according to IRS specifications.

    • Test transmissions must be in the same blocking configuration format that will be used for live production.

    • Software Developers must complete testing of software to ensure the software meets the specifications provided by IRS.

    • Reporting Agents that transmit returns must begin testing after receiving the validated Reporting Agent’s List .

    • To contact the Processing Campus when he/she is ready to begin testing.

    • The transmission of a test file does not constitute filing of a tax return. The test only ensures the participant knows how to use the software packages.

    • A successfully completed test transmission is required for all forms and schedules they intend to file.

  5. If an Applicant's test file fails to meet the evaluation criteria, the Applicant must transmit a new test file within 15 days of the Service's notification of the failure or they must contact the e-help Desk to make other arrangements.

  6. For a list of applicable Revenue Procedures and other reference materials, See IRM 3.42.4.1.2.

3.42.4.9.1  (01-01-2009)
Electronic Specifications and General e-file and MeF Testing Due Date Information

  1. Applicable Electronic Specifications must be followed by participants in order to complete a successful transmission test. Advise filers of the business publications with file specifications and program criteria, as follows:

    • Publication 1437, Procedures for 1041 e-file Program, U.S. Income Tax Returns for Estates and Trusts

    • Publication 1438, File Specifications, Validation Criteria, & Record Layouts for the Form 1041 e-file Program, U. S. Income Tax Return for Estates and Trusts

    • Publication 3823, Employment Tax e-file System Implementation and User Guide

    • Publication 4162, MeF Test Package for Form 1120/1120-S/1120-F/7004 for Tax Year 2008

    • Publication 4163, MeF Information for Authorized IRS e-file Providers for Business Returns

    • Publication 4164, MeF Guide for Software Developers and Transmitters

    • Publication 4205, Modernized e-File Test Package for Exempt Organization Filings, Tax Year 2008

    • Publication 4505, MeF Test Package for Forms 1065/1065-B

    • Publication 4594, MeF Test Package for Forms 2290, 8849 and 720

  2. Testing Due Dates are determined by the type of return that will be filed. The following subsections contain the applicable testing due dates by e-file and MeF Program.

  3. Advise electronic filers required to test of the following:

    • To submit test transmissions by the dates specified in the applicable revenue procedure

    • To notify the e-help Operation when the electronic filer is ready to test

    • To expect notification of any changes to testing due dates

  4. Advise Software Developers of the following:

    • When software packages and communication systems are used by more than one Transmitter, they need to pass an assurance test only once a year

    • Their systems must provide the same software capabilities to all the users

    • Once communication systems and software packages have tested successfully, they may then be used by all accepted participants

  5. See the chart below to determine when to request a replacement transmission or when to disapprove an application.

    e-file Test Transmissions

    If Then
    Unacceptable test transmission request replacement
    Still unacceptable after 30 days application must be disapproved

  6. If the e-help Manager can determine that the electronic filer has a reasonable explanation for the delay in responding to the request for a replacement file, the approval process may continue without duplicating steps already completed.

3.42.4.9.2  (01-01-2009)
94x e-file Program Assurance Testing System (ATS) Transmissions

  1. Assurance Test (ATS) Transmissions for 944, 941e-file, including 941 OnLine Filing:

    • Are not limited - the 94x XML Schema design does not limit the number of returns in a transmission file

    • Can be completed using "live data" for testing

    • Should be completed following electronically published XML Schemas and Test Scenarios that can be used with the Employment Tax e-file System

    • May contain any combination of return types; however, the PIN Registration must be filed separately

  2. For 944, 941 and 940 e-file Programs, IRS will provide test scenarios to Software Developers, or Software Developers can use their test return data. Software Developers/transmitters are not required to test every year. They only have to retest when there have been major changes to the Form 940, Form 941 or Form 944. The form that has the actual changes is the only form that will be tested if they file all three forms.

  3. See Publication 3823 for 944, 941 and 940 specific details. Also visit the IRS web site at www.irs.gov/efile for more information.

  4. Assurance Test (ATS) Transmissions for 940 e-file and 940 OnLine Programs

    • Are not limited and cannot be transmitted during months when returns are being transmitted

    • Can be completed using "test data"

  5. Form 944, 941 and 940 e-file participants should notify the e-help Operations at 1 (866) 255-0654 when they are ready to test. If the site receiving the call is not the testing site then an e-case must be opened and transferred to the correct site.

3.42.4.9.2.1  (01-01-2009)
Form 944, 941 and 940 e-file Testing Due Dates

  1. Advise all Form 941 filers they must transmit a successful test transmission by the test due dates preceding the corresponding quarter due dates as indicated in the chart below.

    Form 941 e-file, Test Due Dates

    If 941 Quarter Ends Then Test File Due Date =
    March 31st April 10th
    June 30th July 10th
    September 30th October 30th
    December 31st January 10th

  2. Subsequent test files may be transmitted at any time except during the months of May, August, November and February, unless granted an exception by the e-help Manager or e-help Operation.

  3. Advise all Form 944 and 940 e-filers that they must transmit a successful test transmission prior to the return due date.

  4. If a Form 941, 944 and 940 prospective filer has not completed testing by the testing completion date or before the end of the quarter/year for which the forms will be filed, notify the e-file applicant, informing him/her to file returns on paper in order to meet the filing due date.

3.42.4.9.3  (01-01-2009)
MeF Assurance Testing System (ATS), Communications Testing & Test Assurance and Documentation (TAD) Criteria and Due Dates

  1. This section provides information for completing the MeF Assurance Testing System (ATS) process. For all MeF Forms, refer to Publication 4164, Modernized e-File Guide for Software Developers and Transmitters . Refer to the following table for the MeF System Programs and applicable Electronic Specifications. All Software Developers are required to perform MeF System testing. For 2009, MeF System Assurance Testing begins November 3, 2008.

    MeF System Programs Electronic Specifications
    (for testing criteria )
    MeF Excise Tax e-Filing & Compliance (ETEC) forms 720, 2290 and 8849 Refer to Publication 4594, MeF Test package for Forms 2290, 8849 and 720
    Forms 990/990-EZ/990-N/990-PF/1120-POL/8868 (Exempt Organization Filings) Refer to Publication 4205, Modernized e-File Test Package for Exempt Organization Filing
    Forms 1065 and 1065-B Refer to Publication 4505, MeF Test Package for 1065 and 1065-B
    Forms 1120, 1120-F, 1120-S, and 7004 Refer to Publication 4162, MeF Test Package for 1120, 1120-S/1120-F/7004 for Tax Year 2008

  2. All Transmittersmust perform a Communications Test and be accepted. Communications Testing with approved software begins anytime after November 3, 2008.

  3. Test Assurance and Documentation (TAD) will begin on October 30, 2008 for the 1065/1065-B MeF Programs.

  4. Prior to testing, all Software Developers and Transmitters must receive through the application process the following:

    • Electronic Transmitter Identification Number (ETIN)

    • Electronic Filer Identification Number (EFIN)

    • Password

    The password is an eight digit alphanumeric password that is used for testing and production.

  5. All MeF System participants should notify the e-help Operation at 1(866) 255-0654 when they are ready to test. If the site receiving the call is not the testing site then an e-case must be opened and transferred to the correct site.

3.42.4.9.4  (01-01-2009)
Form 1041 Criteria for Business Acceptance Testing System (BATS)

  1. Advise 1041 filers of Form 1041 Criteria for completing Business Acceptance Testing System (BATS), as detailed in this section.

  2. Review Publication 1437 and Publication 1438 for 1041 e-file Program specific details.

  3. Business Acceptance Testing System (BATS) Transmissions for 1041e-file Program:

    • Are limited to a total of "20" test returns, with a minimum of "10" returns

    • Can be completed using self-prepared returns for testing

    • Cannot be completed using "live data" for testing

  4. Form 1041 e-file Business Acceptance Testing is required each year, even if the participant took part in the program previously.

  5. Form 1041 e-file participants should notify the e-help Operations at 1 (866) 255-0654 when they are ready to test. If the site receiving the call is not the testing site then an e-case must be opened and transferred to the correct site.

  6. Form 1041 e-file Testing Period is 12/01/2008 - 09/30/2009.

3.42.4.9.5  (01-01-2009)
Receipt of the Initial e-file Test Transmission for 94x and 1041 e-file Returns

  1. The e-help Manager will complete the following actions, upon receipt of the initial e-file test transmission from the applicant:

    1. Assign a Tax Examiner to handle and resolve all problems, throughout the testing, until the applicant is accepted. This can be done by state, district, ETIN, etc.

    2. Assign a Back-up Tax Examiner in case the primary is not available, to ensure continuity in communicating with the applicant.

    3. Maintain a list of Tax Examiner assignments for easy reference.

    4. Contact the applicant and advise of the name and telephone number for the assigned Tax Examiner and Back-up Tax Examiner.

    5. Assure the applicant of available assistance at any time for any problems they may have.

  2. IRS automatically accepts the software the Transmitter will use to create and transmit returns, once testing has been successfully completed.

  3. Use the client/participant's list to pull the folders of the applicants who will not be required to test with the IRS.

  4. Take the Electronic Filing System (EFS)+6 prints and data dumps for the 94x and 1041 returns to the designated person for final acceptance.

    Note:

    MeF returns are worked off EUP electronically.

3.42.4.9.5.1  (01-01-2009)
Accepted Business Legacy e-file Test Transmissions

  1. Complete the review of the test transmissions and provide feedback to the applicant of any errors encountered in the transmission. Advise applicant to correct any errors before retransmitting the test file. For details on receiving a transmission and correcting e-file problems, See IRM 3.42.4.10, Communicating and Correcting

  2. Review of EFS output for accuracy ensures electronic returns are processed correctly. Review the following IRM sections for additional details:

    • See IRM 3.42.4.16.

    • See IRM 3.42.4.17.

  3. Issue an e-mail via EHSS and the e-case granting official acceptance into the e-file program for IRS e-file Programs (1041 and 94x) once testing is successfully completed. Acceptance is only valid for the forms, schedules and the year specified in the acceptance letter. Additionally, generate a production Access Code/Userid/Password and send it to the electronic filer (Transmitter/Software Developer) as applicable, in a letter with security guidelines.

  4. Change the Transmitter’s Access Code to a production Access Code and set the test/production indicator to the test/production indicator "P" in the Third Party Data Store (TPDS).

    Note:

    A Software Developer will always stay in test mode.

  5. Annotate the date of acceptance and the date the e-mail was sent to the applicant. Ensure the letter was generated and sent to the participant through an e-case for the IRS e-file Programs (1041 and 94x).

3.42.4.9.5.2  (01-01-2009)
Handling Unacceptable Legacy e-file Test Transmissions

  1. Advise Providers that IRS monitors performance and counsels participants accepted into the electronic filing programs.

  2. Providers must follow the applicable IRS e-file Program guidelines regarding sending in returns and transmissions in an acceptable manner.

  3. Requesting Replacement Transmissions - If an unacceptable transmission is submitted, request a replacement transmission. If no acceptable transmission is received at least one month before the return due date, advise the participant a paper return must be submitted no later than the return due date.

  4. Previously Submitted Accepted Transmissions - If a current electronic filer submits a bad transmission but has submitted acceptable transmissions in the past and has made no equipment or format change, request a replacement transmission or paper returns be submitted within 30 days. If filer is a Reporting Agent, the Reporting Agent must be notified.

  5. If the subsequent transmission is unacceptable, process the paper returns (if available) and notify the electronic filer. The electronic filer must submit a test transmission prior to the next filing period. The guidelines in item (2) above must also be followed.

  6. Paper Returns Not Required - Do not request paper returns unless:

    • no acceptable test transmission is received prior to the return due date, or

    • the replacement transmission is unacceptable.

    Note:

    If paper returns are requested and processed, consider them as timely filed.

  7. Need for Paper Return - In instances where a current electronic filer has made equipment changes but failed to submit a test transmission prior to filing tax data, and problems occur, request that paper returns be filed within 30 days. If received, consider the paper returns as timely filed. Advise this filer a test transmission must be submitted prior to the filer's next filing. If no test transmission is received a second time, revoke the electronic filer's privilege to file these returns electronically. However, if the electronic filer submits a test prior to the next filing, the guidelines in (2) and (3) above apply.

  8. Failure to Comply - If the electronic filer has failed to comply with the applicable revenue procedure requirement to submit a test transmission in compatible format and problems result, do not request a replacement transmission. Under these circumstances, paper returns must be filed, and the filer (including Reporting Agents) must reapply for electronic reporting. As of 2003, other than sending in paper returns, there is no other option.

  9. Applications for Magnetic Media Programs are no longer being accepted by the IRS.

  10. If the e-help Manager determined that the potential e-file participant had a reasonable explanation for the delay, the approval process may continue without duplicating steps already completed.

  11. Advise participants of the following rules:

    1. 5 days are allowed to retransmit 944/941/940 and 1041 files when electronically filed returns are transmitted timely and the returns rejected.

    2. All MeF e-filers have a 20 day Rule concerning tax returns (not extensions or claims) to retransmit when electronically filed returns are transmitted timely and the returns rejected.

    3. Participants must contact the appropriate SPC for information when the acknowledgment report is not received within 2 days after the transmission for legacy 94x and 1041 e-file returns and within 24 hours for MeF returns.

    4. No actions are required of the participant when returns are processed late due to IRS computer problems, or when an acknowledgment report has been created but not sent to the participant as required.

    5. Advise filers that a paper return must be prepared and mailed directly to the appropriate Submission Processing Campus, if IRS cannot process an electronic return.

3.42.4.9.6  (01-01-2009)
Creating Test Drains for Legacy 1041e-file

  1. Creating Test Drains require completion of the actions described in this section to complete the testing process.

  2. The EMS Analyst must:

    • Create 1041 test drains once daily or as needed

    • Load the "acknowledgment" files for the electronic filer to ACK pick-up, after the applicable 1041 Programs and EFS runs are completed

  3. The e-help Desk Assistor must:

    • Contact the electronic filer, if testing failed, regarding the error condition based on the Programs EFS output information

    • Offer assistance with correcting error conditions, if testing failed, based on an unsuccessful transmission, or other translation failure

    • Advise Electronic filers when and if they can retransmit for another test

3.42.4.10  (01-01-2009)
Communicating and Correcting e-file and MeF Problems

  1. This section provides guidelines for Tax Examiners, regarding communicating and correcting problems in processing of e-file applications, testing requirements and returns.

  2. Use e-help Support System (EHSS) to provide support to IRS external customers. To log into the system, a User ID and Password are required. Complete an On-Line 5081 Application to get a User ID and Password. Review IRM 3.42.7 for complete guidelines.

  3. Tax Examiners assigned to handle the processing of the electronic Test transmissions should complete the following actions:

    1. Call the applicant and give them your name and phone number.

    2. Let applicants know that you will be their contact at the Submission Processing Campus.

    3. Ensure the applicant understands that you are there to help with any problem they have and that they can call you any time.

    4. Explain that if you are not there, they may leave you a message or they may call the backup person who has also been assigned.

  4. Tax Examiner's time spent to help the tester varies as follows:

    • Time needed to help applicants will be different based on what's required by the applicant.

    • Experienced applicants may need very little help.

    • Less experienced or new applicants may want you to go over every error step-by-step.

  5. Tax Examiners should try to get participants to correct their own errors as much as possible.

  6. Tax Examiners should complete the following actions.

    1. Call the contact person listed on the application for clarification of all Worklist items.

    2. Generate a status letter to advise the applicant of the issues that need to be resolved, if two telephone calls have been unsuccessful, one in the morning and one in the afternoon.

    3. Request the applicant to provide the information needed to complete the application. Worklist items remain on the system as assigned to the employee until completed.

  7. Tax Examiners should adhere to the following:

    1. List all Worklist items on the data base if the application is incomplete.

    2. Work all Worklist items until completed. If the applicant does not provide the missing or corrected information for the application, he or she cannot participate in the Electronic Filing Program.

    3. Enter or update the information from the application which will be stored in the TPDS, if the application is complete.

    4. Ensure all Worklist items are closed on the system, when finished.

  8. Tax Examiners should complete the following actions once the signed and completed application is received:

    1. Include the applicant's name on the mailing list and send out the appropriate procedures, file specifications, and record layouts as required by the applicable program. The mailing list is also used to ensure that the applicants are included in dissemination of any updates to the applicable documents.

    2. Generate an acknowledgment letter, prepared at the Submission Processing Campus, to the applicant.

    3. Maintain a record of all the phone calls to each applicant via the EHSS via the applicant's e-case. Any time you are unable to obtain the needed information to return a call timely, inform the applicant of the status and reason for delay.

    4. Keep a record any time an applicant indicates there has been a change to the information we have previously recorded. Ensure the database has been updated via the EHSS, and via the applicant's e-case.

  9. The Lead Tax Examiner will review the records to determine recurring problems.

3.42.4.10.1  (01-01-2009)
Use of Fax and Signature Stamps in Taxpayer Submissions

  1. In May 2003, the Tax Administration Council (TAC) approved the expanded use of faxes for receiving information and documents from taxpayers and practitioners in circumstances where contact with the taxpayer has been made and documented, and faxed signatures are legally sufficient.

3.42.4.11  (01-01-2009)
Handling e-file Incomplete Forms 8633

  1. There are several actions required to handle the receipt of incomplete Forms 8633. Review IRM 3.42.10, Authorized IRS e-file Providers for instructions on completing the required actions.

3.42.4.12  (01-01-2009)
e-file Application Approval Process

  1. This section provides guidelines for completing the e-file Application Approval Process. For 2009, all EPSS e-help Desks can handle enrollment forms for any e-file and/or MeF Program.

  2. Before approving participation in the Business e-file Programs, all applications must be fully processed. This means that the RAF must be reviewed to ensure the Reporting Agent information is present before generating the approval letter. If the Reporting Agent information is missing or not correct, notify the OSPC RAF Unit so the RAF can be updated.

  3. Ensure testing has been successfully completed, as applicable by:

    • Transmitters

    • Reporting Agents (that transmit returns only)

    • IRS Financial Agents

    • Software Developers

  4. Taxpayers filing through a third party Transmitter are not required to test.

  5. Federal Agencies filing via FEDTAX II do not need to test.

  6. Electronic Return Originators filing via the Employment Tax e-file System do not need to test. EROs filing via the Employment Tax e-file System are filing using a Third Party Provider that did complete testing.

  7. Any approval remains in effect unless the electronic filer:

    • Fails to comply with the requirements set forth in the Revenue Procedure, and/or

    • Is suspended from the Business e-file Programs

  8. Review IRM 3.42.10, Authorized IRS e-file Providers for instructions on completing the required actions.

3.42.4.12.1  (01-01-2009)
e-file Approval for Software Developers

  1. Approval for a Software Developer as an electronic filer:

    1. Establishes only that the electronic test transmissions are formatted properly and may be processed by the Service,

    2. Is not an endorsement of the software by the Service or the quality of services provided by the Software Developer, and

    3. Does not entitle the Software Developer to electronically file electronic forms unless the Software Developer applies and is also accepted into the electronic filing programs as a Reporting Agent and or as a Transmitter.

3.42.4.12.2  (01-01-2009)
Suspension From IRS e-file Programs

  1. This section provides guidelines for suspension of participants from IRS e-file Programs for the e-help Desk. It also describes the rights of the participant and the rights of the IRS to access penalties.

  2. All decisions on revocation or denial of filing privileges must be documented within the e-case and the e-file participant must be notified in writing of the decision. The letter should reference the following points:

    • The governing Revenue Procedure

    • Indication of acceptance of a specific tax return, (if applicable)

    • Reason for revocation or denial of filing privilege with specific section of revenue procedure which was not fulfilled satisfactorily, (if applicable)

    • Name and telephone number of the e-help Manager

  3. The letter should also be prepared for the signature of the Submission Processing Campus Director, if the permission to file is revoked or denied.

  4. The e-help Manager, as applicable, should notify the SPEC Territory Manager whether or not the participant is to stay in the program.

  5. If the participant is to remain in the program:

    1. Caution the participant , and

    2. Maintain documentation in the e-case

    When the participant is removed or suspended from the program,

    1. Telephone the participant explaining that he or she can no longer file electronically with the Service.

    2. Confirm the removal or suspension by issuing a letter signed by the Director, EPSS within 3 working days.

    3. Immediately inform the SPEC Territory Manager of the removal or suspension.

  6. The Service reserves the right to deny or suspend an Electronic Filer from the Electronic Filing Programs for violation of the governing revenue procedures.

  7. Some of the general reasons for suspension are as follows:

    • Submission of returns for which the service did not receive authorization

    • Transmission format deterioration

    • Cumulation of unacceptable error rate

    • Violation of advertising standards

    • Preparation of returns using unethical practices

    • Misrepresentation of tax return information on the return

    • Submission of untimely, incomplete, illegible, altered or unapproved applicable forms such as the enrollment form, signature document, etc.

    • Demonstration of conduct that adversely reflects on the electronic filing programs

    • Failure to comply with request for missing information

    • Significant complaints about performance as an Electronic Filer

    • Conviction of any criminal offence under the revenue laws of the United States or of a state or other political subdivision

    • Review other reasons to deny participation in Publication 3112, IRS e-file Application and Participation .

  8. A participant who is suspended has the right to an administrative review of the suspension. The participant should send the request for administrative review to:

    Office of Professional Responsibility
    Internal Revenue Service
    1111 Constitution Avenue, NW
    Washington, DC 20224

  9. ERO Administrative reviews go to Appeals.

  10. IRS counsels suspended participants about the requirements for reinstatement into the electronic filing programs.

    Note:

    This section only covered general information. For specific details and complete guidance about suspension from electronic filing, refer to Rev. Proc. 2007-40, Authorized IRS e-file Provider Responsibilities and any other applicable revenue procedures for the electronic filing program used. Also review Publication 3112, IRS e-file Application and Participation

3.42.4.13  (01-01-2009)
e-file Requirements for Penalties and Waiver Procedures

  1. This section provides a brief description of applicable IRS Treasury Regulations and penalties regarding IRS e-file and provides procedures for granting or denying waiver requests.

3.42.4.13.1  (01-01-2009)
Penalties

  1. Penalties are assessed as specified in the Treasury Regulations.

  2. Rules for assessment of penalties for disclosure or use of information by preparers of the returns are specified in Treasury Regulations 301.7216-1(a).

  3. Civil penalties are detailed in Sections 7213 and 7216 of the Internal Revenue Code.

  4. A definition of who is a preparer (and therefore subject to preparer penalties) is given in the Treasury Regulation 301.7701-15.

3.42.4.13.2  (01-01-2009)
Penalty Policy Statement P-1-18

  1. The Service will design, administer, and evaluate penalty programs solely on the basis of whether they do the best possible job of encouraging compliant conduct.

  2. In accordance with this Policy Statement, the IRS administers a penalty system that is designed to:

    1. Ensure consistency

    2. Ensure accuracy of results in light of the facts and the law

    3. Provide methods for the Taxpayer to have his or her interests heard and considered

    4. Require impartiality and a commitment to achieving the correct decision

    5. Allow for prompt reversal of initial determinations when sufficient information has been presented to indicate that the penalty is not appropriate

    6. Ensure that penalties are used for their proper purpose and not as bargaining points in the development or processing of cases

  3. Penalties support the Service's mission only if they enhance voluntary compliance. This is accomplished by:

    1. Helping Taxpayers understand that compliant conduct is appropriate and that non-compliant conduct is not

    2. Deterring non-compliance by imposing costs on it

    3. Establishing the fairness of the tax system by justly penalizing the non-compliant Taxpayer

  4. The Service maintains an ongoing effort to develop, monitor, and revise programs designed to assist Taxpayers in complying with legal requirements and, thus, in avoiding penalties.

  5. To ensure consistency, the Service prescribes and uses a single set of guidelines set out within IRM 20.1, Penalty Handbook, which will be followed by all operational and processing functions.

  6. Prior to implementation, changes to the Penalty Handbook must be reviewed for consistency with Service policy and approved by the Office of Penalty Administration.

  7. The Service collects statistical and demographic information to evaluate penalties and penalty administration and how they relate to the goal of voluntary compliance.

  8. The Service continually evaluates the impact of the penalty program on compliance and recommends changes when the statutes or administration of penalties are not effectively promoting voluntary compliance.

  9. For additional information review the applicable program publications.

3.42.4.13.3  (01-01-2009)
Certain Corporations and Tax Exempt Organizations Waiver Procedures

  1. For 1120 (series) and 990 (series) MeF waiver information, review the following:

    • Regulations Regulations in T.D. 9363, 2007-49 I.R.B. 1084, requiring certain corporations and tax exempt organizations to e-file returns of organizations required under Section 6033 on magnetic media under Section 6011(e) of the Internal Revenue Code (Code).

    The final regulations, T.D. 9363 dated November 13, 2007 provide the applicable dates for implementation based on the entity’s taxable year ending date. They also provide how an entity’s assets are determined and how the methods for determining if the requirement for the 250 returns threshold is met. These regulations also provide hardship waiver information.

  2. Corporations and tax exempt entities with total assets exceeding $10 million that are also required to file over 250 returns per fiscal period with IRS are required to file their annual return electronically. Final regulations provide for waiver of the requirement to file electronically if the exempt organization can establish undue economic hardship or hardship due to technology issues preventing the tax exempt entity from filing their returns electronically. See the following:

    • Notice 2005-88

    • LEM 20.1.7.9

  3. To request a waiver, the corporation or tax exempt entity must file a written request containing the following information:

    1. A notation at the top of the request stating, in large letters, "Form 1120 MeF (series) or Form 990 Me-F (series) Waiver Request"

    2. The name, federal tax identification number, and mailing address of the entity

    3. The type of form for which the waiver is requested

    4. The taxable year for which the waiver is requested (A waiver request can only be for a specific tax period. Acceptance of a waiver does not waive the requirement for future tax periods)

    5. The value of the entity’s total assets at the end of the taxable year as reported on the entity’s Forms 1120 (series) or Forms 990 (series)

    The Waiver Request must include a detailed statement which lists all of the following:

    • The steps the entity has taken in an attempt to meet its requirement to file its return electronically

    • Why the steps were unsuccessful

    • The hardship that would result by complying with the electronic filing requirements, including any incremental cost to the entity of complying with the electronic filing requirements. Incremental costs are those costs that are above and beyond the costs to file on paper. The incremental costs must be supported by a detailed computation. The detailed computation must include a schedule detailing the costs to file on paper and the costs to file electronically.

    • A statement as to what steps the entity will take to assure its ability to electronically file its return for the next year

    • The relief sought by the waiver request, e.g., failure to file return electronically

    A statement (signed by an officer authorized to sign the return, as defined in section 6662 of the Code) indicating:

    1. "Under penalties of perjury, I declare that the information contained in this waiver request is true, correct and complete to the best of my knowledge and belief."

  4. Requests from the tax advisor/preparer of corporate and tax exempt entities must be accompanied by a valid power of attorney.

  5. The corporation and tax exempt entity is encouraged to file the waiver request at least 45 days prior to the due date of the return, including extensions.

  6. To obtain the waiver, the filer must show:

    1. The nature and severity of problems and efforts to correct in a timely fashion

    2. The timely and consistent effort(s) exercised by responsible officials within the organization to monitor problems and execute corrective action

    3. The efforts undertaken by the filer to meet filing obligations, including but not limited to: contracting out to third parties, and/or filing the returns on paper to meet the due date

    4. The steps the filer has taken and will take to enable it to file electronically in future years

    If the filer is claiming undue economic hardship, detailed computations of the incremental cost to file electronically above and beyond the costs to file on paper must be attached, including the following:

    1. Detailed descriptions of filer’s efforts to develop self-prepared electronic media, if any

    2. Detailed descriptions of filer’s attempts to contract out electronic filing, if any

    3. Detailed estimated costs for either self preparing or contracting out electronic filing compared to their estimate of the cost for filing on paper

  7. A waiver "MAY" be granted if:

    1. The software vendor used by the taxpayer is unable to produce the software needed to e-file any return or schedule within two months before due date of the year for which the return is to be filed, determined without extensions

    2. The taxpayer discovers significant flaws in either the developer's software program or its own self-developed software during the first three months of the year in which the return is to be filed that prevent the taxpayer from filing

    3. The taxpayer after significant testing determines the need to switch software vendors in order to comply with the e-filing mandate and is unable to do so to file timely

    4. The filer attempted to develop the contract out the electronic filing, and the incremental cost was prohibitive. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Incremental costs are those costs that are above and beyond the costs to file on paper.

    In considering whether to grant the hardship waiver, research whether the filer received a waiver in a prior year,

    1. If the filer received a waiver in a prior year, the filer must provide information concerning why the steps it proposed to take in the prior year did not enable it to electronically file in the current year.

    2. Waivers granted due to undue hardship will be determined on a case by case basis and not ordinarily be established for any subsequent year.

  8. Within 30 days after receipt of the waiver request, send Letter 4069C (or equivalent local letter) to the corporation and/or tax exempt entity either approving or denying the request for waiver. The entities may not appeal a denial of a waiver request.

  9. If a waiver is granted, input TC 971 with Action Code 322 into the Master File. Send Letter 4069C (or equivalent local letter) to the organization indicating their request for waiver has been approved. Include appropriate selective paragraph(s) instructing the organization to file their paper return by the return due date (or extended due date) in order to avoid failure to file penalties.

  10. If the waiver is NOT granted, input TC 971 with action 323 into the Master File. Send Letter 4069C (or equivalent local letter) to the organization indicating their request for waiver has been denied and reason for denial. Include appropriate selective paragraph(s) instructing the organization to file their return electronically by the return due date (or extended due date) in order to avoid failure to file penalties.

  11. If the waiver request is accompanied by a power of attorney (POA), forward the POA to the CAF unit asking them to input the POA information into the CAF.

  12. Use the matrix that follows to determine when to approve or deny a waiver request for the 1120/1120-F/1120S MeF Returns:

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

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡   ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

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

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

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

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

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

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

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

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

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

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

    ≡ ≡ ≡ ≡ "≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ "≡ ≡ ≡ ≡ ≡ ≡ " ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ "

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

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

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

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    ≡ ≡ ≡ ≡ ≡


















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

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











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

    ≡ ≡ "≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ "

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

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

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

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

    ≡ ≡ ≡ ≡ "≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ "

    ≡ ≡ ≡ ≡ "≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ "

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
      ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

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

    ≡ ≡ ≡ "≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ "

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

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

    ≡ ≡ ≡ "≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ "

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

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

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

    ≡ ≡ ≡ "≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ "≡ ≡ ≡ ≡ ≡ ≡ " ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ "
    ≡ "≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ "

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

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

    ≡ ≡ ≡ ≡ ≡ ≡ "≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ "
    ≡ ≡ ≡ ≡ "≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ "

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

3.42.4.13.4  (01-01-2009)
1065 MeF Penalties and Waiver Information

  1. Advise 1065 e-filers of Failure To Electronically File (FTEF) Penalties. Section 1224 of the Taxpayer Relief Act of 1997 requires partnerships with more than 100 partners (Schedules K-1) to file their returns on magnetic media (electronically as prescribed by the Commissioner of the Internal Revenue Service). Final regulations under the IRC 6011(e), provide for a penalty to be assessed for partnerships that meet the requirement and fail to file their return electronically for tax year's ending December 31, 2000 and subsequent years. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

  2. Advise parties involved in the transmission of electronic filing of Form 1065 returns that they may be liable for failure to file penalties due to the following:

    • Missing information on the return

    • Incomplete information on the return

    • Unsigned signature forms

  3. Advise partnerships, based on the number of partners, they may incur a penalty for not using the correct method for filing the return.

  4. Advise 1065 e-filers of Waiver Information. Section 301.6011-3(b) of IRS regulations, permits the IRS Commissioner to waive the electronic filing requirement if a partnership demonstrates that a hardship would result if it were required to file its return electronically.

  5. Advise 1065 filers (Partnerships) interested in requesting a waiver of the mandatory electronic filing requirement to file a written request in the manner prescribed by the Ogden Submission Processing Campus (OSPC). For complete guidelines regarding the waiver request requirements or removal of a penalty charged for not filing electronically Review IRM 21.7.4, Business Tax Returns and Non-Master File Accounts. The OSPC should be contacted at the toll free number, 1-866-255-0654 for additional instructions and if they have questions regarding the waiver. All written requests should be mailed to:

    Ogden Submission Processing Campus (OSPC)
    e-file Team, Stop 1057

    Ogden, UT 84201

  6. Use the matrix that follows to determine when to approve or deny a waiver request for the 1065/1065-B MeF returns:

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

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

      ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

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

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

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

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

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

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

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

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

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

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

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

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡
    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

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

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

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

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

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

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

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

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

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

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

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

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

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

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

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

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

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡
    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

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

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡
    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

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

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

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

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

3.42.4.14  (01-01-2009)
Handling e-file Inquiries

  1. This section provides the applicable points of contact for handling inquiries relating to electronic filing. It also describes the appropriate procedures for handling inquiries received by Field Office Operations.

  2. Each IRS Field Office Operations has a Coordinator and/or others assigned, to answer questions from the public, as applicable.

  3. When handling inquiries, IRS has found that the reference or use of the term "tax practitioner" or "practitioner" to mean every 3rd party representative external to IRS is confusing to external contacts. As a result of this, to reduce the confusion IRS will use the term "tax professional" in all future correspondence or other written material and when speaking to tax professionals.

  4. Advise participants who need to resolve account related issues that involve the electronic return to call the Business and Speciality Tax Line toll free telephone number, 1 (800) 829-4933.

  5. Advise callers that they may write to the following addresses or call other numbers listed below for receiving assistance, as appropriate:

    Handling e-file Inquiries

    Point of Contact Center Subject Telephone Number
    Andover & Austin e-help Desks e-file Application Process and Processing Questions 1 (866) 255-0654
    Cincinnati & Andover e-help Desks MeF ETEC Program Questions
    1 (866) 255-0654
    Cincinnati e-help Desk PIN Registration Questions 1 (866) 255-0654
    Andover, Ogden & Cincinnati, e-help Desks 94x e-file Program Questions 1 (866) 255-0654
    Austin, Cincinnati & Ogden e-help Desks 1120, 1120-F, 1120-S, 7004, 990, 1041 and 1065 Electronic Filing Program Questions 1 (866) 255-0654
    Martinsburg Computing Center (MCC) Filing Information Returns Electronically
    (FIRE) Program
    1 (866) 455-7438

    Addresses for e-file Inquiries when responding in writing

    Electronic Filing Submission Processing Campuses Mailing Addresses
    Andover e-help Desk
    Internal Revenue Service
    Andover e-help Desk Planning and Analysis Staff
    310 Lowell Street
    Andover, MA 01812
    Austin e-help Desk Internal Revenue Service
    Stop 6380 AUSC
    P. O. Box 1231
    Austin, TX 78767-1231
    Cincinnati e-help Desk Internal Revenue Service
    Cincinnati e-help Desk
    201 W. Rivercenter Blvd
    Covington, KY 41012
    Attn.: e-help Operation, Stop 2701
    Ogden e-help Desk Internal Revenue Service
    Stop 6052
    1160 West 1200 South
    Ogden, UT 84201
    Martinsburg Computing Center (MCC) Internal Revenue Service
    Martinsburg Computing Center
    Information Reporting Program
    230 Murall Drive
    Kearneysville, WV 25430

  6. Advise filers to call the Business and Specialty Tax Line at 1-800-829-4933 for inquiries regarding Business Electronic Payments. Calls will be handled by Taxpayer Service Representatives (TSRs) and others, as appropriate, at local Tax Assistance Centers. The Tax Assistance Centers will answer the following type of inquiries from taxpayers, IRS Agents, Federal Agencies, software vendors, foreign governments, representatives, Congressional offices, and others, as appropriate, according to IRM 21, Customer Service Manual:

    1. Federal Tax Deposits

    2. Electronic Funds Withdrawals

    3. Credit Card payments

  7. Coordinators also respond to inquiries that could not be answered by Customer Service Representatives.

  8. When a request is received at the Submission Processing Campus from a Field Office Operation, regarding the status of an electronically filed return, the Submission Processing Campus must complete either the following actions within 48 hours:

    • Confirm receipt of the return

    • Provide the status of the return to the Field Office Operations Coordinator

  9. Territory Offices must complete the following actions:

    1. Require Customer Service Representatives to answer procedural questions concerning electronic filing programs, products and services offered.

    2. Require Customer Service Representatives to contact their Electronic Filing Coordinator if they cannot resolve a problem regarding electronic filed returns.

    3. Notify the applicable governing site about the information obtained from the Customer Service Representative, regarding unresolved electronic filing inquiries. This will facilitate the applicable governing site's awareness of Taxpayer inquiries.

  10. Territory Managers will complete the following actions:

    1. Contact the Electronic Filing Project Manager at the appropriate Submission Processing Campus to resolve any problems.

    2. Notify the applicable governing site of all requests submitted, permitting Territory Offices to be aware of any situations they may need to address later.

  11. Territory Offices must complete the following actions as required:

    1. Reject or suspend electronic filing program participants who have violated governing procedures based on recommendations from the applicable governing site or the Submission Processing Campus.

    2. Notify ANSPC when rejection and suspension letters are to be issued.

    3. Perform compliance functions.

3.42.4.14.1  (01-01-2009)
Previously Accepted e-file Applicants

  1. e-help Desk Assistors must complete the following action:

    • Advise previously accepted e-file applicants, who contact the Service to request participation in IRS e-file , they do not need to submit an application unless the information previously provided has changed. Advise them to call the e-help Desk site to let IRS know of any changes.

  2. The e-help Operation must update the data base as required below, when the applicant notifies IRS about changes.

    1. Record all telephone conversations with applicants regarding application data into the applicant's e-case, using the EHSS.

    2. Maintain the information in the applicant's e-case by referencing each contact with the applicant.

3.42.4.14.2  (01-01-2009)
e-file PIN Registration Change of Address Requests

  1. e-file PIN Registration Change of Address Requests can be handled On-Line via e-services. It can also be changed by calling the e-help Desk at 1 (866) 255-0654. For additional information review IRM 3.42.8, e-services Procedures for e-help Desk Assistors

  2. Process e-file PIN Registration requests for address changes for Reporting Agents, if the Taxpayer "signed" a Change of Address (Form 8822) request.

3.42.4.14.3  (01-01-2009)
Receiving e-file Addition or Deletion Lists

  1. The Reporting Agent will submit requests to add or delete filers from the e-file Programs, as necessary. These filers must be listed in duplicate, same as on the initial application.

  2. The e-help Desk will complete the following actions:

    1. Record the validated list accounts by date and Agent in Entity Control.

    2. Maintain the request as part of the applicant's e-case.

  3. A Reporting Agent does not always know at the time the return is filed for an employer that it is the final return. When the determination is made that the previous transmission contained the final return, IRS must be notified by the Agent or employer in writing or via the toll free number, 1-800-829-4933.

3.42.4.15  (01-01-2009)
Submission Processing Campus Live Processing of e-file & MeF Returns

  1. Electronically transmitted return data is received in "several" different e-help Desk sites for the Business e-file and MeF Programs. This section will provide a general overview of the means for receiving and verifying the filing of electronically filed returns at each of the campuses and the applicable procedures necessary to resolve processing problems encountered. The e-help Manager, as applicable, must ensure these procedures are performed by the receiving e-help Desk site.

  2. Once the application is received and testing is completed, participants are ready to file "live" electronic returns.

  3. The instructions for live processing are identical to those used for assurance testing along with those described below and in the following sections.

  4. Tax Examiners must:

    1. Analyze the Acknowledgment Report for Reject Codes

    2. Research the Reject Codes in the file specifications

    3. Notate any remarks in the taxpayer's e-case on EHSS

    4. Document all contacts in the EHSS e-case

    5. Track Acknowledgment Reports through the e-case on EHSS

    6. Monitor the Applicant's e-case on EHSS

    7. Advise Management of any electronic filing participants who may need warning letters regarding their non-compliance with IRS procedures

3.42.4.15.1  (01-01-2009)
Other e-file Live Processing Responsibilities

  1. The following actions are those of the EPSS Manager and e-help Operation, as applicable. The titles or functional areas may differ depending on the Submission Processing Campus.

  2. Ensure the following processing steps for all programs are completed by the Operations Branch or other designated functional area:

    1. Schedule computer runs for all returns processing,

    2. Run the Validation Program, Code and Edit Program and the Acknowledgment Program,

    3. Create separate output files containing Schedules K-1 and the applicable parent Form 1041 with associated forms and schedules for subsequent Loading onto the local area TRDB,

    4. Report problems to the appropriate project coordinator concerning electronic filing,

    5. Produce and provide the specified program reports to the Electronic Filing Unit or ELF Processing Support Section, and

    6. Maintain system audit trails and data control printouts according to standard IRM.

  3. Ensure availability of vendor User Guides, Computer Operator Handbooks (COH) and any local System Operation Procedures (SOP) for additional information.

3.42.4.15.2  (01-01-2009)
Business e-file and MeF Processing

  1. Business e-file returns are electronically transmitted either:

    • via the Internet using terminal emulation software which supports Secure Socket Layer (SSL) 3.0 with Telnet/S (this is not a web-based system) through the IRS Common Communications Gateway (CCG), or

    • using a dedicated/leased line and encrypted router both of which are purchased and installed in the IRS computing center by the transmitter.

  2. The EMS is located at ECC-MTB and ECC-MEM. Refer to EMS e-help Web Interface Manual for additional EMS processing information.

  3. MeF returns flow into the MeF System through the Internet from the internet filers (received through the Registered User Portal (RUP) infrastructure). The MeF System is located in Martinsburg Computing Center (MCC).

  4. The following actions are those of the e-help Manager, e-help Operation and or Electronic Filing Support Group, as applicable.

    Note:

    MeF returns are not processed on Unisys; therefore, some of the actions in this section may not be applicable to MeF returns.

    1. Advise Providers to call 1-866-255-0654 to reach the e-help Desk to schedule an electronic transmission session, as applicable. Contact the e-help Desk for Excise forms 720, 2290 and 8849; 944 and 941 (Employment Tax) Programs; and 940 (Unemployment Tax) Programs; 1041 (Fiduciary Returns); 1065 (Partnership Returns); 1120 (Corporate Returns); and 990 (Exempt Organization Returns). The caller is directed to a person who can assist them based on the prompt they choose when dialing the number. If the caller chooses the wrong prompt, the caller can be transferred or an e-case can be created and routed to the correct person.

    2. Provide the Provider the authorized telephone number to call to connect to the modem for the e-help Desk site that should receive his/her transmitted returns, as applicable.

    3. Advise the Provider he/she must telephone the applicable e-help Desk site on the scheduled day and time.

    4. Once the Provider makes contact as scheduled, authenticate the filer. Advise the filer to place a data transmission call, and a return transmission session will commence. Data transmission costs will be borne by the transmitter.

    5. Continue to poll the Provider for returns during the session until the final record is sent. After receiving the final record of the session, the IRS Submission Processing Campus modem will be disconnected.

    6. Store the data received by the EMS and or MeF System at the Submission Processing Campus then process the return in the same manner as other returns received directly from participants.

3.42.4.15.3  (01-01-2009)
Processing Schedule K-1 for e-file and MeF Programs

  1. SPC Managers, as applicable, must ensure the following actions are completed:

    Note:

    MeF returns are not processed on Unisys; therefore, some of the actions in this section may not be applicable to MeF returns.

    • Verify Schedule K-1 counts to determine that the total transmitted matches the total on the associated summary record.

    • Verify the EIN to substantiate whether it is the same on the Schedule K-1 and on the parent return.

    • Verify additional entity data and some numeric fields have been added for verification.

    • Reject the return and the Schedule K-1, if there is a mismatch. Advise the Transmitter to correct the error(s) and retransmit the return, including the Schedule K-1.

  2. When the return is accepted by the Validation Program, it will be processed and the Unisys will produce two tapes:

    • Accepted returns

    • Schedule K-1 plus statement records (preceded by page 1 of the corresponding parent return)

    Note:

    Schedule K-1 selected data is input into the IRP system via GMF.

  3. When the return is accepted into the system, a tape which includes the Schedule K-1 will be loaded to the TRDB.

3.42.4.15.4  (01-01-2009)
Processing Return & Entity Data for e-file and MeF Programs

  1. The e-help Managers and e-help Staff, as applicable, must complete the following actions during the application or return process:

    Note:

    Do not provide entity information without proper authorization from the taxpayer. The account's entity is considered return information and a Power of Attorney (POA) must be on file or the caller authorized to receive this information. Disclosure rules apply.

    1. Advise the electronic filer that entity data about the returns that are going to be filed electronically must be transmitted correctly.

    2. Advise filers that entity information should be transmitted on the same medium that is used when transmitting the returns.

    3. Advise the participant to transmit the information based on the format provided in the applicable program procedures.

    4. Advise this information is used to verify IRS entity data.

    5. Verify the tax entity data to help prevent unpostable returns and errors.

    6. Notify the electronic filer of any discrepancies before allowing live tax return data to be transmitted.

    For additional Disclosure guidelines review, the following:

    • Chapter 3 of IRM 21, Customer Account Services

    • IRM 11.3, Disclosure of Official Information

    • IRM 3.42.7.7, Standardized Telephone Procedures

  2. The entity data for MeF is validated against the NAP files residing on MeF.

  3. Reasons information would not match are:

    1. Account has not been established on Master File

    2. EIN is incorrect

    3. Name Control is incorrect

    4. Filing requirement is not established or correct

  4. EROs must try to fix any entity reject problems that occur. If the ERO cannot resolve the problems and he calls for assistance then an assigned Tax Examiner will review entities that are identified as mismatched and notify the authorized parties of any corrections that must be made, as applicable.

  5. Since December 20, 2000, services rendered to a federally-recognized Indian Tribal Government (or its political subdivision) are exempt from the FUTA (Federal Unemployment Tax Act) tax, subject to the tribe's compliance with applicable state law.

3.42.4.15.4.1  (01-01-2009)
Indian Tribal Government Entity Review Process

  1. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ Code and perfect the following returns as "Non-Taxable and Final" :

    • Indian Tribal Government for Tax Years 200012, 200112 and subsequent

    • Announcement 2001–16

    • The Community Renewal Tax Relief Act of 2000

    • H.R. 5662, incorporated in H.R. 4577, the Consolidated Appropriations Act, 2001

    • Public Law No. 106-554, 114 Stat. 2763

    • Internal Revenue Code Section 3309(d)

    • Similar explanation, such as, if the Taxpayer is claiming a refund for Federal Tax Deposits, ensure that the return is perfected by editing / deleting all transcription lines so the overpayment is refunded to the Taxpayer.

  2. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

  3. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ "≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ " ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

  4. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

  5. For more information see Announcement 2001-16 and Internal Revenue Code Section 3309(d). Also for additional information regarding Code and Editing Indian Tribal Government returns, review IRM 3.11.154and IRM 3.12.154.

3.42.4.15.5  (01-01-2009)
Extensions to File for e-file and MeF Programs

  1. Certain business electronic filers may apply for an "Extension to File" the return. If an extension is requested, advise the participant to indicate on the return record that they applied for an extension. Returns processed after April 15th, or the designated due date, will require entry of a specific processing date by the Computer Operator.

  2. Employment Tax Returns are not given an automatic extension to file due to a disaster or emergency. An extension is granted based on a case by case process by IRS, in response to the taxpayer's statement giving a reasonable cause for the delinquency.

  3. The Employment Tax e-file System will allow "late returns" to be "accepted" through April 30th via the following programs:

    • 940 e-file Program (XML format)

    • 940 On-Line Program (XML format)

    • 944 e-file Program (XML format)

    • 944 On-Line Program (XML format)

    Note:

    Filing late returns may result in having penalties assessed.

  4. Late returnsare acceptedfor users of the 941e-file Program (XML format) for the current quarter and 3 prior quarters.

  5. Form 8868, Application for Extension of Time to File an Exempt Organization Return is accepted through the MeF System.

  6. Use Form 7004, Application for Automatic Extension of Time to File Certain Business Income Tax, Information, and Other Returns for the following:

    • Forms 1120, 1065,1041 and 990 family of returns

    • Forms 2758, 8736 and 8800 for firms listed on Extensions through MeF

  7. If attachments are required to identify the Taxpayer's presence in a presidentially declared disaster area, a paper return must be filed. Returns late for any reason must be filed on paper, except for MeF returns. For MeF returns the return may be filed electronically with attachments scanned and attached to the file.

  8. Disaster Contingency: In the case of a nationwide system failure due to a disaster, contact the ETA manager for the Strategic Services Division, OS:CIO:I:ET:S, immediately.

  9. For further instructions on disaster recovery, see IRM 25.16, Disaster Assistance and Emergency Relief .

  10. Review IDRS for the following extension indicators for the applicable programs:

    Extension Indicators for Business e-file

    Extension Indicators for Business e-file
    720 MeF ETEC No Extensions allowed Not applicable
    940 e-file Programs 10 Day Extension allowed As applicable, based on Deposit Rule
    941 e-file Programs 10 Day Extension allowed As applicable, based on Deposit Rule
    944 e-file Programs 10 Day Extension allowed As applicable, based on Deposit Rule
    990 MeF Family of Programs Form 8868 and
    Form 7004

    Note:

    Extensions are not valid for Form 990-N

    Transaction Code (TC) 460 or TC 620 will show with the extension due date
    1041 e-file Program Form 7004 (Automatic 5 Month Extension) Transaction Code (TC) 460 or TC 620 will show with the extension due date
    1065 and 1065-B MeF Programs Form 7004 (Automatic 5 Month Extension) Transaction Code (TC) 460 or TC 620 will show with the extension due date
    1120, 1120-F and 1120-S MeF Programs Form 7004 (Automatic 6 Month Extension) Transaction Code (TC) 460 or TC 620 will show with the extension due date
    2290 MeF ETEC Extensions allowed - May file for a 6 Month extension by filing a written request prior to the due date of the return. The tax must be paid timely. See Page 3 of Form 2290 instructions. Internal customers should contact Centralized Excise Operations to verify an extension has been approved.
    8849 MeF ETEC No extensions allowed Not applicable

3.42.4.15.6  (01-01-2009)
Receipt and Processing Time Limitations for e-file and MeF Programs

  1. The Submission Processing Campus must acknowledge arrival of an electronically transmitted file for Business Tax Returns within "48 hours of receipt" .

  2. The Submission Processing Campus must confirm arrival of an electronically transmitted file for Business Tax Returns resubmitted on paper within "10 days of receipt" .

  3. Verify the Reporting Agent's List, schedule MGT runs and review run control reports. Within "90 days of receipt" of the data, return the Reporting Agent's information.

  4. When specification changes are made in the revenue procedures, and the revenue procedures specifically require a compatibility test from current Reporting Agents, the Reporting Agents are required to submit a test transmission no later than two months prior to the return's filing date.

  5. The normal BMF pipeline time limits will be followed for processing the returns which appear on the Error Resolution System.

3.42.4.15.7  (01-01-2009)
Requesting e-file Replacement Files

  1. The e-help Manager, as applicable, should request e-file retransmissions of files under the following conditions:

    • A transmission file contains an unacceptable proportion of errors and is rejected

    • An electronic transmission causes a processing interruption (an abnormal termination of a program run caused by the electronic data submitted)

    • An entire transmission has been rejected

  2. Determine if a file contains an "unacceptable" proportion of errors, or if the file is "incompatible," if so, notify the electronic filer of the problems involved.

  3. Advise the electronic filer to correct errors and retransmit the return(s) on the same calendar day.

  4. If the electronic filer chooses not to have the previously rejected return(s) retransmitted, or if the return(s) still cannot be accepted for processing, advise the filer to file a paper return.

  5. Advise the filer the paper returns must be filed by the later of the due date of the return or within the(time frames referenced below in Paragraph 9) of the rejection or notice that the return cannot be retransmitted. Advise filer to attach an explanation as to why the return is being filed after the due date.

  6. If necessary, relief of Program Completion Date (PCD) for these returns should be requested through the National Office. Returns should be considered timely filed if the subsequent file(s) is also unacceptable.

  7. If it is determined that there is a reasonable explanation for the delay in returning requested missing information, continue the approval process without duplicating steps already completed.

  8. In all cases, the deadlines mentioned are the maximum times allowed for submission of replacement files. Filers are encouraged to submit initial and replacement files well in advance of the return due date. However, decisions to revoke or deny filing privileges are based on the time limits.

  9. Advise participants of the following:

    1. 5 calendar days are allowed to retransmit 944/941/940, 1041 and 7004 files when electronically filed returns were transmitted timely, but the returns rejected

    2. 10 calendar days are allowed to retransmit 1120, 1065/1065-B and 990 files when electronically filed returns were transmitted timely, but the returns rejected

    3. 20 days are allowed to retransmit other MeF files when electronically filed returns were transmitted timely, but the returns rejected.

    4. Participants must contact the appropriate e-help Desk for information when the acknowledgment report is not received by the 5 days after the due date of the return.

    5. No actions are required of the participant when returns are processed late due to IRS computer problems, or when an acknowledgment report has been created but not sent to the participant as required.

    6. A paper return must be prepared and mailed directly to the appropriate Submission Processing Campus, if IRS cannot process an electronic return.

3.42.4.15.8  (01-01-2009)
Handling and Disposing of Paper Returns Received by e-help Desk

  1. An e-file return that rejected and was retransmitted as a Paper return received by the e-help Desk will continue to be processed.

  2. The e-help Desk must ensure the following actions are completed:

    1. Release the paper returns into the pipeline for processing only when necessary

    2. Forward computer-generated facsimiles to the Files function to be filed, as all other returns

3.42.4.16  (01-01-2009)
Detecting Legacy e-file EMS and EFS Transmission Problems

  1. This section describes how to detect Legacy "EMS and EFS Transmission Problems" and how to resolve them.

  2. TRANA, TRANB and RECAP Records are not the same for the different business e-file programs.

  3. Electronic transmission errors can be received through front end processors. Front-end transmission errors are received from the EMS through the Enterprise Computing Center at Memphis (ECC-MEM) for the 1041 e-file Program.

  4. Errors in transmission can be corrected by using the information in Publication 1438, File Specifications, Validation Criteria and Record Layouts for the 1041 e-file Program, U.S. Income Tax Returns for Estates and Trusts .

  5. Tax Examiners should complete the following actions:

    1. Refer the participant to the page number in the applicable publication and explain the information, if necessary

    2. Begin the transmission review at the TRANA Record

    3. Ensure that each field contains the correct data through and including the RECAP Record

  6. Review ensures that the participant can meet the requirements of the applicable specifications.

  7. Reviewing a Transmission - The following is a list of some of the things to watch for:

    1. When one record format is incorrect, subsequent records may be corrupted

    2. After locating initial error, check the records following the error, field by field, against the record layouts for accuracy

    3. Check fixed record formats by cross-checking the byte count (character count) on the data dump with the record layouts

    4. When byte counts do not match, the participant has transmitted an incorrect record

    5. Check variable length formats by cross-checking the field number with the record layout

    6. All money fields should be reviewed for correct format (sign-gain/loss), as applicable

    7. Review for an entry in a no entry field or no entry in a required entry field, as applicable

    8. Certain fields must be in a specific format (YYYYMM, left justified, etc.) and must be made as specified

    9. When the record layouts state the field entry must contain a specified range (00-12) or value (X or blank), the participant cannot enter data outside the specified range or value

    10. When the same Reject Codes appear throughout the transmission, tell the transmitter a program problem could exist within their software rather than a data entry error

    11. # sign used in data causes entire transmission to reject - Recap record missing is the message on the Error Acknowledgment

  8. Since this list is general, other problems may exist. Request the Lead Tax Examiner to help with review problems.

3.42.4.16.1  (01-01-2009)
Identifying 94x XML EMS Errors

  1. The "Error Codes" applicable to the 94x XML Program are identified in Publication 3823, Employment Tax e-file System Implementation and User Guide .

3.42.4.16.2  (01-01-2009)
Identifying Legacy 1041 e-file EFS Errors

  1. The "Error Codes" applicable to the 1041 e-file Program are "3 digit codes" . Detailed information for the 1041 e-file Program is referenced in Publication 1438, File Specifications, Validation Criteria, and Record Layouts for the 1041 e-file Program, U.S. Income Tax Return for Estates and Trusts .

3.42.4.16.3  (01-01-2009)
e-file Error Resolution System (ERS) Procedures

  1. Errors on e-file returns that are identified by the Error Resolution System (ERS) are corrected by employees assigned to the Submission Processing Campus Error Resolution Unit. Returns that require error resolution can be viewed for error correction purposes using the IDRS command code "TRDBV" .

  2. See IRM 3.42.4.19. and subsection for detailed information regarding using the IDRS command code "TRDBV" . For information about requesting a print-out of the e-file return for review See IRM 3.42.4.20..

  3. The Submission Processing Campus Error Resolution Unit must use the ERS edit mode using the IDRS TRDBV command code to make corrections. Correct only lines and entries that would be transcribed on DIS for a paper return. This creates a shadow page.

  4. Errors on MeF returns can be viewed via the EUP.

  5. All correspondence, audit trail, and timeliness instruction applies to Electronic return corrections. For example, the Error Resolution Tax Examiner working an error condition on an Electronic return must annotate the Electronic return's comments/history sheet with the reason for the suspense code and any action taken.

  6. If problems in the Error Resolution Unit prevent corrections, suspend with Action Codes as appropriate.

  7. The ERS Unit Tax Examiner will contact the e-help Desk when it is necessary to communicate with the Electronic participant for clarification of information on ERS cases.

  8. The e-help Desk Assistor will record in the taxpayer's e-case, the response to telephone contacts and will provide the information to the ERS Tax Examiner, as required. These notes can be especially helpful if an Electronic participant makes recurring errors unknowingly.

3.42.4.16.4  (01-01-2009)
Handling Adjustment Documents for 941e-file

  1. Any Form 941 filed electronically in need of an adjustment to preceding quarters must be supported by a written statement or Form 941c, Supporting Statement to Correct Information . For 2009, Form 941c is not obsolete for the 94x e-file Program.

  2. A Reporting Agent must send the paper supporting documents to the CSPC for manual processing.

  3. Adjustment documents must be taken to the Error Resolution function. The Error Resolution Function or e-help Manager will distribute the original of all Forms 941c (where social security and medicare adjustments are involved) to the Taxpayer Relations Branch or the Adjustment function (at the discretion of the Director of the Submission Processing Campus).

3.42.4.16.4.1  (01-01-2009)
941c for e-file FEDTAX II Program

  1. Use the following procedure to handle Forms 941c received from Federal Agencies that file returns using the 941 e-file Program via the FEDTAX II Financial Agent to ECC-MEM.

  2. TCC should forward paper Forms 941c to the CSPC for manual processing. CSPC will process the 941c through e-help or other support staff under the operation of the Management Support Branch. For questions about the FEDTAX II Program or these procedures, contact the FEDTAX II Coordination Desk, Management Support Branch.

  3. The CSPC e-help Operation or other support staff must complete the following actions:

    1. Advise the Federal Agency to use the telephone number 1 (877) 477-0569 to fax the Form 941c directly to the FEDTAX II Coordination Desk, Management Support Branch.

    2. Advise the Federal Agency to fax the Form 941c on the same day that their 941 return is accepted into 941 e-file .

    3. Once the Form 941c is received by the FEDTAX II Coordination Desk, send a copy of the Form 941c to the Error Correction Function for use when correcting Error Code 550 on the 941 e-file return.

    4. After processing has been completed by the Error Correction Function, release the original 941c to the Taxpayer Relations Branch for processing.

3.42.4.16.5  (01-01-2009)
1041 e-file Error Resolution

  1. The Submission Processing Campus Error Resolution Unit must access the ERS edit mode on the form viewer. Correct only lines and entries that would be transcribed on ISRP for a paper return. This creates a shadow page.

  2. All correspondence, audit trail, and timeliness instructions apply to Electronic return corrections. For example, the error resolution Tax Examiner working an error condition on an Electronic return must annotate the Electronic return's comments/history sheet with the reason for the suspense code and any action taken.

  3. If problems in the Error Resolution Unit prevent corrections, suspend with Action Codes as appropriate.

  4. The ERS Unit Tax Examiner will contact the e-help Desk when it is necessary to communicate with the participant for clarification and or information on ERS cases.

  5. The e-help Desk Assistor will record on the EHSS the response to telephone contacts and will provide the information to the ERS Tax Examiner. These notes can be especially helpful if participant makes recurring errors unknowingly.


More Internal Revenue Manual