4.19.26. Campus Backup Withholding Return Compliance Program Procedures

(1) ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

(1) Each year the Government Accountability Office (GAO) audits the Service’s financial statements. As a part of this audit, they review documentation for taxpayers whose balance due (including interest and penalties) is over $10 million.

(2) For each tax period where the balance due (including penalties and interest) is $10 million or more, the following documentation must be sent to the Office of Unpaid Assessments Accounting and Analysis when the case is closed.

• Form 945 signed by Payer or Manager; and

• For 6020(b) returns, the completed 6020(b) certificate.

(3) The information should be submitted via email to *IRS Financial Audit.

(1) Director Exam issued Memorandum “Sensitive Case Report Guidelines” dated March 4, 2022 advising an SCR is needed for every case when the balance due including penalties and interest is $10 million or more per tax year.

(2) For CBWH employees this includes cases for potential assessment.

(3) ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

(4) CBWH Management will follow the SCR Memorandum for actions needed.

(1) IDRS is a system which enables employees to have access to taxpayers tax accounts.

(2) Capabilities of the system include:

• Researching account information and requesting returns

• Entering transactions such as adjustments, entity changes, and so on

• Automatically generating notices, correspondence, and other outputs

(3) Cases may be controlled on IDRS in several ways. Under IDRS, any type of case may be controlled. TEs may control a case by entering the IDRS Command Code (CC) ACTON into IDRS. Follow the concept of only one TE assigned to an account.

(4) If you receive a call from a taxpayer on the BWH toll-free line and the case is assigned to another CBWH employee, take the information stated by the taxpayer and forward that information via email to the assigned employee. Copy your manager and the employee’s manager on the email. Remember to encrypt the email since it will have taxpayer’s Personally Identifiable Information (PII) included to identify the case.

(5) An open control base on a module indicates control for the purpose of initiated correspondence, and adjustment or other action. An open control base retains the module on IDRS indefinitely. Update it when necessary to reflect changes in status or in action taken. Once the control base closes, it drops from the IDRS data base provided no other criteria exists for retaining the module.

(6) Cases are controlled by various IDRS CCs. Each control base contains several elements of data, fully explained in IRM 2.3.12, IDRS Terminal Responses. The control base and history information is a very important section of TXMODA. If updated properly, the control base and history information section can give you a complete account of what transpired on a case.

(7) CBWH employees are required to use Integrated Automation Technologies (IAT) tools. IAT tools simplify taxpayer account processing by assisting the user with IDRS research and input. The required use of mandated tools applies to all CBWH Program-related telephone and inventory work.

(8) If an IAT tool is not available or an employee has a problem with the IAT Tool Manager, the case should be processed through IDRS following established procedures. It is important that employees follow their established business procedures to report problems with the IAT tools. CBWH employees should refer to the IAT Website for issues such as how to report problems with IAT tools or how to request enhancement to tools.

(9) All IAT tool users can visit the IAT website https://organization.ds.irsnet.gov/sites/WiMttIat/home/default.aspx for known issues on tools, job aids and a variety of tool related issues. Copies of the IAT newsletter (iNews) are available on the website and provide helpful tool tips and information on upcoming IAT tool retirements, pilots and tool roll outs. This site provides the link to subscribe to the newsletters.

(1) This report contains all cases controlled to an IDRS employee number and can be used to:

• Identify cases that require action

• Identify specific cases for review

• Monitor the size of the employees' inventories

• Determine if employees are working inventory in the proper order

• Set closure expectations

• Identify cases that may need management intervention

(2) This report is available on Control-D on Monday mornings, Report Name: "Overage Report", Job Name: ORCAS Report. The ORCAS coordinator will load the report through the ORCAS delivery database. Then the report will be available to the Manager and TEs.

(3) The Manager or Lead will provide TEs the page(s) of the report where the cases are controlled to their IDRS number. TEs will follow local procedures for using the ORCAS report, documenting case activities, and returning the ORCAS report to the Manager.

(4) The TE should work cases in the following priority order:

1. Cases that have received TAS OARs recommending actions the IRS should take.

2. NLUN category cases, meaning the case is in Nullified Unpostable (NLUN) category over 14 days old.

3. The statute will expire within 90 days; Quick Assessment procedures should be followed if applicable.

4. Taxpayer was contacted and purge date has passed, therefore the case requires action.

5. Remaining cases in the oldest received date order, meaning inventory is worked First In First Out (FIFO) order.

(5) Each TE must perform a Quarterly Physical Inventory Review, to ensure their ORCAS Report is verified against each case assigned to them. The results of your quarterly physical inventory reviews must be maintained by your Operation for future reviews.

(1) BWH Shared Drive "Z" gives CBWH examiners, managers, and other staff the ability to review and store information and documentation for the cases.

1. The shared drive includes a "Tax Year" (TY) folder.

2. Within the TY folder, there are subfolders by TY. Each individual TY folder has subfolders titled Payer (PR), LOP, Closed (No Change), and Closed (Resolved). Beginning with TY 2019 there is also a Closed (Screened Out) Folder. The PAYER (PR) folder has subfolders named by Employer Identification Number (EIN). The EIN folder is where all documents for that specific EIN (case) are stored.

(2) When an employee needs access to the BWH Shared Drive "Z", the manager will forward the employee’s name and their SEID to the Administrator of the BWH Shared Drive "Z".

(3) Employees granted access will be able to access the entire team folder. Access is only authorized to cases assigned to the employee and as needed to facilitate customer service when answering phone inquiries or performing work for another employee as delegated by management. Established unauthorized access (UNAX) restrictions apply.

(4) Quarterly, the BWH Shared Drive "Z" Administrator contacts the manager for them to verify employee access. If new employees arrive in the group or other employees leave the group, the manager must email the BWH Shared Drive "Z" Administrator immediately.

(5) The BWH common drive "S" is maintained by Cincinnati Campus Exam/AUR, Centralized Specialty Tax Operations Cincinnati. Contact that administrator when changes are needed to the "S" Drive.

(6) The BWH SharePoint site where the TEs upload the correspondence numbers received each week is maintained by Exam HQ Performance Planning and Analysis (PPA) so contact them when changes are needed to this site.

(7) Use approved naming conventions for electronic case files (see Exhibit 4.19.26-5, File Naming Conventions) and upload documents timely into the BWH Shared Drive "Z".

(8) Employees will comply with IRM 6.8002.6.2, Security Requirements, IRM 10.8.1, Information Technology (IT) Security, Policy and Guidance, and IRM 10.8.26, Information Technology (IT) Security, Government Furnished and Personally Owned Mobile Device Security Policy, by closing their computer’s connection to the BWH Shared Drive "Z" and any other IRS shared drives, IRS software, or internet browser windows, at the end of each workday.

(1) The Data Collection Instrument (DCI) is used by management to document the compliance plan and business results. The employees use the DCI to document a case closure.

(2) ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

(3) For TY2019 DCI, use CBWH DCI TY2019 WS1 or CBWH DCI TY2019 WS2 on SBSE Exam BWH Policy SharePoint Site to record the DCI information. Job Aids are available for each workstream of how to use and enter the data on SharePoint.

(4) Prepopulated fields in the TY2018 Workstream 1:

(5) Prepopulated fields in the TY2018 Workstream 1 from PMFOLB data:

(6) TY2018 Workstream 1 DCI fields to be completed by TE:

(1) The CBWH team uses PDF templates for the cases which are available on the SBSE Exam BWH Policy SharePoint site.

• Prepopulated forms

• CBWH letters that include the CBWH team’s return address, contact information, and signature of the Operation Manager.

• Explanation of Backup Withholding (EOB)

• Form 945

• IRC Section 6020(b) Certification Form for BWH

• Activity Record

(1) Prioritize any statute imminent cases, unpostable conditions, and cases identified by the Manager or Lead for immediate action.

(2) Use IDRS and IAT to perform IDRS actions.

(3) Forward questions or clarification needed regarding procedures to the Lead.

(4) Status for open IDRS controls-

(5) The TE, Lead or Manager, will input the following activity code on the open IDRS control when a case question is referred, or the case is returned back to the assigned TE:

(1) The TE will document all actions taken on a CBWH case on the Activity Record including incoming correspondence received, telephone calls, discussions with the Payer, signed Form 945 sent to processing, adjustments input, referrals, and so on. Consider the Activity Record as the history record of all actions taken and reasons supporting your decision on the case that documents a good action trail. See Exhibit 4.19.26-1, Activity Record, for a sample activity record for a completed case.

(2) If a case has to be referred to Appeals in the future, the Activity Record will be included as documentation to support the actions taken by the CBWH team.

(1) Section 3705(a) of the IRS Restructuring and Reform Act of 1998 (RRA 98) provides that any “manually generated correspondence” shall include the name, telephone number and unique identifying number of an employee who can be contacted with respect to correspondence. Any other correspondence shall include a telephone number of a person who may be contacted with respect to the correspondence.

(2) On tax-related matters employees are required to provide (at a minimum) the following information:

1. Telephone Contact - title (for example, Mr., Mrs., Ms., Miss), last name and badge identification (ID card) number

2. Correspondence - title (for example, Mr., Mrs., Ms., Miss); last name; IDRS, letter system or badge identification (ID card) number; and telephone number where the taxpayer's question can be answered

   Note: IDRS numbers are automatically generated when sending Correspondex (CRX) letters and are considered identification numbers.

(3) The term manually generated correspondence is defined as any correspondence issued that is non-systemically generated and must contain certain elements listed in (1) above. The IRS employee issuing the correspondence is:

1. Exercising judgment in working or resolving a specific taxpayer identified issue.

2. Requesting the taxpayer provide additional case-related information to resolve the issue and the corresponding employee is in the best position to respond to all issues raised in the taxpayer’s correspondence. The Service must use sound business judgment to determine the provision’s applicability.

(4) Manually generated correspondence may include:

• Correspondex Letters (C Letters)

• Local letters

• Form 5260, Quick notes

• Computer generated Reasonable Cause Assistant (RCA) denial letters

(5) If preparing a Form 5260, Quick Note, it must be reviewed and approved by the employee's manager or team leader. See IRM 21.3.3.4.22, Quick Notes and 3064C Letters (C-NOTES), for the requirements of a Quick Note (Form 5260).

(6) Provide an accurate balance due in manually generated correspondence when requested by a taxpayer or the authorized representative. See IRM 21.3.3.4.2.2.1, Required Information for Interim Letters and Closing Letters, regarding accounts with an installment agreement (status 60).

(1) The 10 fundamental steps (or stages) of CBWH compliance cases are:

1. Step 1: Receive Case Assignment (IRM 4.19.26.5)

2. Step 2: Consider Tax Due (IRM 4.19.26.6)

3. Step 3: Case Building (IRM 4.19.26.7)

4. Step 4: Issue Letter 6112 - First Notice (IRM 4.19.26.8)

5. Step 5: Issue Letter 6112-A - Second Notice (IRM 4.19.26.9)

6. Step 6: Review Payer’s Responses and Make Determination (IRM 4.19.26.10)

7. Step 7: Consider Penalties and Interest (IRM 4.19.26.11)

8. Step 8: Assess Tax, Penalties, and Interest (IRM 4.19.26.12)

9. Step 9: Close Case (IRM 4.19.26.13)

10. Step 10: Perform Rework When Appropriate (IRM 4.19.26.14)

(1) Manager’s responsibility to prepare a case assignment list.

(2) The manager will provide a case assignment list to the designated CBWH employee.

(1) Designated CBWH employee performing clerk’s duties is responsible to assign cases.

(2) For each case, the designated CBWH employee will:

1. Open an IDRS control on MFT 16 for the assigned TE.

2. Create a dummy module if MFT 16 tax module does not exist. .

3. Create an electronic case folder on the BWH Shared Drive "Z": BWH > TAX YEAR > TY 20YY > PAYERS > NN-NNNNNNNN, where TY 20YY is the tax period and NN-NNNNNNN is the EIN of the case.

4. Document case assignment on the Activity Record and save it in electronic PDF format in the electronic case file under the file name NN-NNNNNNN.ACT.

5. Send an email notification to the TE.

(1) TE’s responsibilities upon receipt of new case assignment are:

• Verify IDRS open control base (see IRM 4.19.26.5.1.3.1)

• Check for duplicate TXMODA MFT 16 Controls

(1) If an indicator of fraud is identified, refer the case to the designated CFC for further development.

(2) Discuss the indicators of fraud with the Manager. If the Manager concurs:

1. Prepare Form 13549, Campus Fraud Lead Sheet, Sections I, II, III, and Section V Item 1.

2. Forward package (Form 13549, IDRS research, and any outgoing and incoming correspondence related to the case) to the Front-line Manager (FLM).

3. FLM will review the package and complete Section III, line 2 of Form 13549, and forward the package to the Department Manager (DM) for review.

4. DM will review the package. If the DM agrees the case should be referred, the DM will forward the package to the Technical Advisor (TA). If the DM does not agree the case should be referred, the DM will return the package to the FLM with instructions to continue compliance procedures.

5. The TA will review and approve the referral, completing Section III, line 3 of Form 13549. The TM will return the case to the FLM with instructions to forward the referral to the Campus Fraud Coordinator (if the TA agrees with the referral) or to continue compliance procedures (if the TA does not agree with the referral).

6. The FLM or a designee will prepare Form 3210 and email it with the Form 13549 package to the CFC. The list of CFC or Campus Fraud Examination Advisors can be found at https://portal.ds.irsnet.gov/sites/vl019/Lists/FraudAwareness/DispItemForm.aspx?ID=13.

(3) When Form 13549 is first prepared and given to the Manager for review, the TE will input IDRS Activity Code FRCRDMMDD (Workstream 1) or 2FRCRDMMDD (Workstream 2), IDRS Status A and monitor for 37 days for a response from the Campus Fraud Coordinator (the extra 7 days is to allow time for the Form 13549 approval process). The Activity Code may be reinput for an additional 30 days. After 60 days, refer case to Lead for instructions.

(4) The Campus Fraud Coordinator will advise how to refer the case (for example, to Exam or to Criminal Investigation), or will reject the referral. If the case is accepted for referral to another function, TE will close the case using the appropriate Activity Code. See Exhibit 4.19.26-11, TXMOD/ACTON codes. If the case is rejected, TE will discuss next steps with the Lead.

(1) With incidents of Identity Theft (IDT) increasing each year, emphasis is being placed on the ability for programs (such as CBWH) through the IRS to provide expedited handling and to track the number of unresolved IDT cases.

(2) The IRS established Identity Theft Victims Assistance Specialized Teams (IDTVA). An IDTVA TE will be a taxpayer’s single point of contact (SPOC) for IDT and other account related issues.

(3) Referrals to the IDTVA are made through the BMF ID Theft Liaison. All functions have established BMF ID Theft Liaisons to assist in the coordination and working of BMF ID Theft cases. The list of liaisons can be found on the SERP IRM Supplement Tab on the BMF Identity Theft page. See BMF ID Theft Liaison Listing (http://serp.enterprise.irs.gov/databases/who-where.dr/idt-liaison-listing.html).

(4) TEs must make a referral for assistance to the BMF ID Theft Liaison if a taxpayer states they are a victim of identity theft. IRM 25.23.9, BMF Identity Theft Processing, requires extensive research which is beyond the scope and training of CBWH personnel. Under IRM 25.23.9.4(2)I, the case must be referred to the appropriate BMF ID Theft Liaison who will perform the required research, validating the taxpayer’s allegation of BMF identity theft, and provide instructions to the CBWH Manager on needed actions to either close the case to IDTVA (if identity theft is validated) or continue processing the case normally (if identity theft is not validated).

(5) An allegation or claim of identity theft is identified by the presence of Form 14039, Business Identity Theft Affidavit, a police/law enforcement incident report, ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

(6) If you receive an allegation of BMF identity theft, prepare Form 14566, BMF Identity Theft Referral, and forward it with a zipped case file, including all case research and any other documents (notices, letters, correspondence, activity record, and so on) to the CBWH Manager for routing to the appropriate BMF ID Theft Liaison. Input IDTL_MMDD (for Workstream 1) or 2IDTL_MMDD (for Workstream 2), Case History Status Code A, to monitor for 30 days. If guidance is not received from the BMF ID Theft Liaison within 30 days, follow up with Manager. The Activity Code may be re-input as needed until guidance is received.

(7) If the BMF Identity Theft Liaison instructs you to transfer the case to the IDTVA, input Activity Code CLOSEIDTVA (for Workstream 1) or 2CLOSIDTVA (for Workstream 2) and Case History Status Code C to close the case to the to IDTVA. The designated CBWH employee will send any paper case files to the IDTVA with Form 3210.

(8) For more information about assisting a taxpayer with an identity theft matter by telephone, see IRM 4.19.3.22.1.26.2, IDT Claims – Telephone.

(9) For more information about assisting a taxpayer with an identity theft matter by written correspondence, see IRM 4.19.3.22.1.26.3, IDT Claims – Responses.

(1) Individuals impersonating IRS employees may make unsolicited threatening telephone calls and/or send fraudulent emails or letters to taxpayers. They may use the threat of arrest to obtain money from victims by falsely representing that the victims owe back taxes or other fees. The perpetrators demand that the victims send them money via prepaid debit cards, money orders, or wire transfers from their banks. See https://www.treasury.gov/tigta/docs/IRS%20Impersonation%20Scam%20Flyer.pdf.

(2) If a taxpayer calls the BWH toll-free line to discuss a CBWH letter, but there is no record in IDRS or the shared drive of any notice or letter for the tax year in question, advise the taxpayer to take appropriate actions using the guidance in IRM 4.19.3.5.8.1.1, Online Fraud and Other Scams (PHISHING).

(1) ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡

(2) ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

(1) Workstream 1: The Payer filed information returns for Payees without TINs. The Computed Tax Liability will be primarily or entirely backup withholding. The Computed Backup Withholding amount will be the Payees’ Reportable Payments times the Applicable Backup Withholding rate. See IRM 4.19.26.2.2, Back-up Withholding Rates.

(2) Workstream 2: The Payer reported federal income tax withholding on filed information returns but did not file the relevant taxable return Form 945. The Payer may also have filed information returns for Payees without TINs. The Computed Tax Liability will be:

1. Payees with TINs: The Computed Federal Income Tax Withholding, meaning the actual amount of federal income tax withheld, as reported by the Payer on the Payees’ information returns; PLUS,

2. Payees with Missing TINs (if any): The Computed Backup Withholding amount, meaning the Reportable Payments times Backup Withholding Rate. See IRM 4.19.26.2.2, Back-up Withholding Rates.

(1) Run IDRS reports for case EIN as follows:

• AMDIS

• BMFOLI

• BMFOLT for MFT 16

• BMFOLZ

• ENMOD

• INOLES

• INOLEX (if applicable)

• PMFOLB (for compliance year)

• PMFOLS (for compliance year and two prior years)

• SUMRY

• TXMODA for MFT 16

(2) Place PDF prints of the IDRS research in the electronic casefile on the BWH Shared Drive "Z" prior to closing the case. It is not necessary to place a pdf print of an unavailable report in the electronic casefile.

(1) ENMOD may contain in the upper right hand corner a designation of Potentially Dangerous Taxpayer (PDT) or Caution Upon Contact Taxpayer (CAU) indicator. The IRS has two service-wide employee safety programs to warn employees of taxpayers who have been designated as potentially dangerous or should be approached with caution.

(2) If the PDT or CAU indicator is present, notify the Manager for instructions.

(3) For more information on the PDT and CAU programs, see:

• IRM 25.4.1, Potentially Dangerous Taxpayer

• IRM 25.4.2, Caution Upon Contact Taxpayer

(1) Verify the name and address on INOLES is consistent with all case data.

(2) Check (CC) ENMOD for any pending name or address changes

(1) ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

(2) ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

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

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

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

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

(3) ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

(1) Check for an identity theft indicator on ENMOD (TC 971 AC 522 IDTCLM).

(2) If present, notify Lead and consider referral to IDTVA. See IRM 4.19.26.5.4.2, Referral to Identity Theft Victims Assistance Specialized Teams (IDTVA).

(1) If a Payer has an SSN instead of an EIN, search for a cross-reference EIN.

(2) If no EIN is found, discuss with Lead and consider requesting an EIN from Customer Accounts Services and Submission Processing. See IRM 21.7.13.3.8, Receiving EIN Applications from Field Compliance. If an EIN is requested, TE will input Activity Code EINREQMMDD (for Workstream 1) or 2EINRQMMDD (for Workstream 2) and Case Status History Code A to monitor for 7 days for EIN assignment. If the EIN is not assigned within 7 days, discuss with Lead for next steps.

(1) If a Payer has more than one assigned EIN, forward the case to the Lead.

(2) If more than one EIN is confirmed, the Lead will follow IRM 3.13.2.14, Multiple EINs, and forward the case to Entity. BMF Entity is the only section within the campus authorized to consolidate EINs.

(1) Verify that BMFOLI does not show that Form 945 was filed for the year under inquiry under the Payer’s EIN and MFT 16 (Form 945).

(2) Check TXMODA for a pending TC 150 on MFT 16.

(3) If no return is filed for the year under the TIN, then look for a cross-reference (X-REF) TIN. On CC INOLES, look for X-REF EIN in the bottom right hand corner. On CC ENMOD, look for a Parent EIN in the upper left hand corner. INOLEX lists all cross-referenced TINs and whether they are subsidiaries (SB) or a parent (PR).

(4) If a X-REF TIN is found, then input CC BMFOLI to search for a filed Form 945 (MFT 16) under that (X-REF) TIN.

(5) If Form 945 was filed (TC 150 posted or pending), then refer to the chart below.

(6) TEs use MeF to obtain copies of Form 945. Refer to "How to Access MeF" Job Aid on the SBSE Exam BWH Policy SharePoint Site.

(1) Review CC BMFOLZ for prior Form 945 examination (MFT 16) with a TC 300 amount.

(2) Review CC ENMOD and CC TXMOD for prior CBWH cases with a TC 150 amount. Prior compliance "no change" cases may have fallen off IDRS when the dummy TXMOD was closed. Look for evidence of Letter 96-C issued in the prior period, and/or a history note describing the "no change" closing. If a prior CBWH case is found, review the prior case files on the BWH Shared drive "Z."

(3) Review CC PMFOLB for the number of Forms 1099 filed with missing, unassigned and mismatched TINs as well as the years that the Payer received a CP2100 Notice.

1. To recreate CP2100 notices, follow IRM 4.23.8.13.2, Procedures for Backup Withholding Examinations.

2. EPSS-TSO receives a very large volume of recreate requests and a request can take up to six weeks to fulfill. All requests are fulfilled in the order received, and there is no method available to prioritize a CBWH request over the requests from other IRS employees. Therefore, TEs should discuss with their manager whether CP2100 notices would be necessary for the compliance case and obtain managerial approval for requesting CP2100 notices.

(4) Review CC PMFOLD.

1. If there is more than one entry in CC PMFOLD, then look for any difference in the TCC (Transmittal Control Code). Each Payer filing information returns is assigned a unique TCC, but there may be multiple Payers filing under one EIN. This can occur when there are multiple departments or units issuing payments within a large business or entity. Where there are multiple TCC’s, each Payer may not be aware of all of the other Payers. A determination of whether multiple TCC’s are valid should be made before identity theft is considered.

2. PMFOLD also displays various codes (for example, OTTL, ATTL) which provide additional information as to the timing of the information return filing and whether they may have been subject to delinquency penalties. For additional information pertaining to these codes, refer to http://serp.enterprise.irs.gov/job-aids/command-code/pmfol-detail.html.

(5) If the Payer’s account shows significant continued noncompliance despite prior examinations of MFT 16, or worsening noncompliance, then this may be an indicator of negligence or civil/criminal fraud. For example, the Payer may continuously file information returns without TINs or with improper TINs despite notification from the IRS. Discuss case with Lead who will determine if a possible referral to the field is warranted.

(6) If there was a previous MFT 16 examination (TC 300 present on IDRS), discuss with the Manager or Lead whether to contact Exam to discuss the prior examination and continued noncompliance. Use the PBC, SBC and EGC to locate the correct Exam contact.

(1) Review CC AMDIS for an "-L" Freeze on MFT 01 (Form 941), MFT 10 (Form 940), MFT 11 (Form 943), MFT 14 (Form 944), or MFT 16 (Form 945). Review CC BMFOLT or CC TXMODA for an audit indicator TC 420 or 424, not reversed by TC 421. This indicates the return is currently requested or under audit by Exam.

(2) Refer cases to Field Exam whenever Freeze Code "–L" is present. Do not continue a compliance case if there is an open examination (TC 420 or 424) for Form 945 (MFT 16) in any year. These cases must be referred to Exam. See IRM 4.19.26.5.2, Refer cases with "-L "freeze to Field Exam.

(3) If there is suspicion of fraud or identity theft, see IRM 4.19.26.5.4, Consider Referral for Fraud or Identity Theft.

(1) When a disaster occurs in a particular state, the President may declare a federal disaster or emergency. These freeze codes "-O" or "-S" appear on IDRS.

(2) To verify whether a disaster or emergency freeze is in place, enter the Payer’s zip code in the Integrated Customer Communications Environment (ICCE) IRS Disaster Assistance Program Website to determine if there is a current disaster freeze present. The zip code search tool may provide more timely results than IT systemic programming for an affected taxpayer. See http://www.icce.irs.gov/fema/.

(3) "-O" freeze indicates the U.S. President has declared a federal disaster or emergency in the Payer’s area [ENMOD TC 971 AC 086 or 087]. An "-O" freeze provides systemic filing and payment relief to taxpayers with a filing or payment due date or extended due date, by postponing those due dates. The "-O "freeze also suspends collection and examination activities, including under reporter activity. Generally, an affected taxpayer is eligible for compliance relief unless certain conditions necessitate the continuation of compliance activity, such as imminent statute. For more information, see IRM 25.16.1.7.2, "-O" freeze.

(4) -S freeze identifies tax returns filed within a declared disaster area ENMOD TC 971 AC 688. For more information, see IRM 25.16.1.7.1, "-S" freeze.

(5) If Payer has not been contacted, and an "-O" or "-S" freeze are present, close the case as a Screen Out. See IRM 4.19.26.13.2, Close Case - Screen-Out.

(1) If after you have started the case, you identify a"-V" freeze indicating the Payer has filed for bankruptcy, for example, TC 520, refer the case to the Lead.

(2) Bankruptcy proceedings impose deadlines for action for both the debtor (taxpayer) and the creditor (IRS). The deadline for filing proofs of claim is called the "bar date." The IRS will not receive payment for unfiled returns or open exam cases unless they are listed as estimates on a proof of claim. The IRS’ failure to meet the bar date (or bar date extension) may result in the IRS’ claim being disallowed. This means the IRS may not recover from the debtor personally upon discharge. Thus, the IRS must ensure that it files accurate claims with the court in a timely manner.

(3) The Lead will contact the in Technical Services Bankruptcy Coordinator to obtain the name of the Insolvency Bankruptcy Specialist. The Technical Services Bankruptcy Coordinator can be found at https://portal.ds.irsnet.gov/sites/vl051/Lists/Technical%20Services%20Bankruptcy%20Coordinator%20Listing/Bankruptcy%20Coordinator%20by%20State.aspx.

(4) Input RFRLDMMDD (for Workstream 1) or 2RFRLDMMDD (for Workstream 2) and Case History Status Code A and monitor the case for 7 days. The Activity Codes may be re-input if a response has not been received from Insolvency within 7 days.

(5) Generally, the CBWH program does not work bankruptcy cases, so the Insolvency Bankruptcy Specialist must tell the Lead where to close the case. The Lead will close the IDRS base.

(6) For the proof of claim, the Lead will provide to Insolvency any potential deficiencies, and a copy of the 6020(b) package (if any) including the Stampted/Signed Form 945, 6020(b) Certificate, and Explanation of Backup Withholding with List of Payees.

(1) The "-W" freeze, in combination a TC 520 and (CC) (closing code) other than 81 indicates litigation other than bankruptcy.

(2) Discuss the case with the Lead before transferring the case and then transfer the case to the Lead. The Lead will coordinate discussion of the case with the Manager and Counsel. The CBWH Manager will send an email inquiry to the TE/GE Area Counsel in whose jurisdiction the Payer is located based on the address of record as shown in INOLES. The CBWH Manager will describe the CBWH case, including taxpayer (Payer) name, EIN, and freeze code, and ask whether the CBWH compliance activities can continue or if the case should be closed as a screen out or no change or transferred to another IRS compliance function or unit. See Area Counsel contact information.

(3) Input RFRLDMMDD (for Workstream 1) or 2RFRLDMMDD (for Workstream 2) and Case History Status Code A and monitor the case for 14 days. The Activity Codes may be re-input if a response has not been received from Counsel within 14 days.

(4) Counsel will provide instructions to continue processing or to transfer or close the compliance case. If the case is transferred or closed, document the action on the Activity Record and close as a Screen Out or No Change, whichever is applicable. For more information for closing as a Screen Out see IRM 4.19.26.13.2, Close Case - Screen Outs, and for closing as a No Change see IRM 4.19.26.13.3, Close case – Any Non-Appealed Case (Excluding Screen Outs).

(1) The "-Z" or "Z-" freeze indicates the taxpayer’s account is currently being reviewed by Criminal Investigation (CI) function.

(2) ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡"≡ ≡ ≡"≡ ≡ ≡"≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

(3) When this freeze code is present, close the case as a Screen Out if prior to sending a letter. For more information regarding closing as a Screen Out see IRM 4.19.26.13.2, Close Case - Screen Outs. If CI involvement is identified after the letter is sent, close as no change with IDRS Activity Code CLOSETOCI (for Workstream 1) or 2CLOSETOCI (for Workstream 2). For more information regarding closing as a no change see IRM 4.19.26.13.3, Close case – Any Non-Appealed Case (Excluding Screen Outs).

(1) TEs must ensure that the person contacting the IRS is the Payer. In most cases, the Payer will be a business entity, and the contact must be either an officer of the Payer (such as the Chief Financial Officer of a Corporation) an owner, partner, member, or authorized under Form 2848 to discuss the Payer’s tax matters.

(2) If an unauthorized individual wants to discuss the tax matter, then request the individual submit a Form 2848 or Form 8821 and do not discuss the tax matter with that individual until they do.

(3) If the Payer or representative submits a Form 2848 or Form 8821, verify that it is completed correctly. If incomplete or improperly prepared, return the form to the Payer with Letter 3064-C, selecting paragraph I. See IRM 21.3.7.5.1, Essential Elements for Form 2848 and Form 8821, for instructions. TE will input Activity Code 3064C (for Workstream 1) or 23064C (for Workstream 2), Case History Status Code A.

(4) If the Form 2848 or Form 8821 is completed correctly, prepare fax coversheet and EEFax the form to the Central Authorization File (CAF) unit.

1. Fax to Memphis or Ogden CAF Unit based on the state mapping.

2. See CAF Contacts (https://www.irs.gov/businesses/small-businesses-self-employed/caf-unit-addresses-fax-numbers-and-state-mapping)

(5) Place an electronic PDF print of the annotated Form 2848 or Form 8821, and electronic PDF print of the EEFax confirmation, in the case file on the shared drive.

(6) Update the activity record that the Form 2848 or Form 8821 to reflect actions taken. See Exhibit 4.19.26-1, Activity Record.

(7) For representatives not yet on CFINK, when sending Power of Attorney Correspondex letters through the IAT Letters tool select "Y" under CAF Copy. This will allow manual entry of the name and address of the representative.

(8) If you are preparing a template letter, enter the POA information manually and save the letter to the BWH Shared Drive "Z" in the PAYER (PR) folder under the appropriate EIN folder, for example, Letter 937.

(1) The initial contact is the first contact with the Payer. ALL initial Payer contacts must be made by mail using approved form letters.

(2) All responses that would potentially reduce the amount of backup withholding under consideration or otherwise materially affect the compliance adjustment must be provided in writing. If the Payer or representative wants to provide payee TINs, or make a statement, request that information in writing by mail, fax, or email. See Pub 1281, Backup Withholding on Missing and Incorrect Name/TINs, for more guidance.

(3) Return a Payer's telephone call within two business days, and if possible, within 24 hours.

(4) When returning the Payer’s phone call and leaving a voice mail message, do not mention the tax matter. Simply state "This is Ms. [Surname] returning your phone call. Call the backup withholding toll-free line for more information (state the number)." This ensures unauthorized persons will not know it is the IRS calling.

(5) All telephone discussions with a Payer or the Payer’s representative, including voicemail from and/or attempts to contact the Payer or representative, must be documented contemporaneously in the electronic case activity record.

(6) Enter a history note in AMS to describe what was discussed with the Payer.

(1) Taxpayer responses may occur at any time during compliance procedures, and the nature of responses and procedures will be similar no matter when the response occurs.

(2) The recipient will scan and upload all correspondence received from a Payer (mail or EEFax) to the Payer (PR) folder for the Payer’s TIN on the shared drive. The recipient will place the paper correspondence in the Payer’s case file.

(3) The recipient will input Activity Code REPLYMMDD (for Workstream 1) or 2REPLYMMDD (for Workstream 2), Case History Status Code A, to notify the assigned TE that Payer correspondence is available for review. The purge date MMDD is seven business days from the date the Payer’s response is received in the CBWH Unit.

(4) If it can be determined that a Payer has submitted original documents, the recipient will make a copy for the paper case file and mail the originals back to the taxpayer with Letter 96-C, Acknowledgement Letter for General Use/Inquiry. The recipient will update the Activity Record to indicate the originals were mailed back to the Payer.

(5) In general, you must respond to Payer correspondence within 30 days from receipt. See Exhibit 4.19.26-6, Timely Actions. Exceptions include:

1. A signed return is not considered correspondence. See IRM 21.3.3.2, What is the Definition of Correspondence? - Policy Statement P-21-3 Exclusion List. If the correspondence is a signed Form 945, without regard to whether the Form 945 was prepared by the TE or by the Payer, process and submit the signed return within 5 business days to Submissions Processing. See IRM 4.19.26.12.2.1, Delinquent Return Procedures.

2. Payer responses that are received within 5 days of or on the purge date to respond to Letter 6112, should be worked within 10 days and the results should be communicated to the Payer on the EOB and Form 945 enclosures to the Letter 6112-A mailed to the Payer. However, if the Payer provided missing return information for all of the payees, close the case No Change and issue Letter 96-C to the Payer; Letter 6112-A is not necessary.

3. Correspondence on cases within 183 days of statute expiration must be worked within 7 days of receipt.

(6) Issue Letter 2645-C, Interim Letter, if unable to respond to correspondence within 30 days from the earliest stamped IRS received date. Select paragraphs A, B, E and/or K, X, and k. Populate paragraph X with an expected date the correspondence will be resolved. The promised resolution date may be any number of days and can vary depending on workload.

(7) If a Form 2848 or Form 8821 is on file for the Payer, prepare and mail Letter 937 to the representative with a copy of any correspondence including enclosures sent to the Payer. Use the prepopulated Letter 937 available on the shared drive.

(8) If the representative is not listed on (CC) CFINK, forward Correspondex letters by selecting Y under CAF copy in the IAT Letters tool and fill in the representative’s information. For detailed instructions, see IRM 2.4.6.6.2, CAF Indicator.

(9) Place a copy of all correspondence (including Letter 937) in the electronic case file on the shared drive.

(10) Document all correspondence to or from a Payer or the Payer’s representative in the activity record.

(1) Faxing and/or Enterprise Electronic Faxing ("EEFax") of tax information to taxpayers and/or their authorized representatives within the United States, U.S. possessions, commonwealths, and territories, is permitted consistent with existing internal rules.

(2) As a general rule, copies of case documents or transcripts should be mailed and not faxed or EEFaxed to taxpayers, since faxing presents more security vulnerabilities than mailing of tax information. The facts and circumstances of each case and the requirements of IRC 6103 should be considered prior to making a disclosure via facsimile transmission.

(3) If the Manager in writing approves faxing or EEFaxing copies of case documents to the taxpayer or the taxpayer’s representative, follow the procedures for facsimile transmissions of tax information to taxpayers and their authorized representatives in IRM 21.1.3.9, Mailing and Faxing Tax Account Information.

(1) USPS provides mail forwarding orders for a period of 12 months, after which time the order will expire. For six months immediately following expiration, mail sent to the taxpayer at the old address will be returned to the sender with a yellow label showing the new address and the reason for non-delivery.

(2) USPS sends all undeliverable First Class Mail to the IRS return address on the envelope.

(3) The address on the yellow label ("Yellow Label") is the taxpayer’s current address of record in the USPS system and indicates that the taxpayer provided the USPS with a Change of Address (COA) that differs from the address used by the IRS.

(4) The National Change of Address (NCOA) program links with the USPS change of address requests received from postal customers. The NCOA run updates Master File with the address provided by the postal customer/taxpayer. The DLNs from these changes will be shown on CC ENMOD:

• BMF XX963-995-77766-Y

• IMF XX263-995-99999-Y

(1) It is important that all undeliverable mail is worked as a priority to ensure that correspondence is mailed to the taxpayer’s current address. A taxpayer could challenge an assessment in the appeals process or in the courts if the IRS did not attempt to locate the taxpayer’s last known address.

(2) Upon receipt of undelivered correspondence, the recipient will scan the envelope without opening it, and place the electronic image in the case file on the BWH Shared Drive "Z" in the PAYER (PR) folder under the appropriate EIN folder.

(3) The recipient will update the TXMOD activity code as follows for undelivered correspondence:

(4) The purge date is seven days from the date the undeliverable was received in CBWH.

(5) The recipient will review CC INOLES, ENMOD, and NAMEE to see if there is a new address on file.

1. If there is a new address, re-mail the undeliverable to the new address.

2. Include the original envelope and correspondence sent the first time.

(6) If the taxpayer’s name printed in the letter and what is shown on the "Yellow Label" affixed by the USPS to the envelope are exactly the same, but the address is different, use the "Yellow Label" address.

(7) Discuss the following unusual situations with the Lead:

1. The "Yellow Label" states that the addressee is deceased, and there is no POA for the taxpayer in CFINK.

2. The undeliverable letter was refused by the addressee.

3. The undeliverable letter was returned without a "Yellow Label" but there is other information written on the envelope.

4. Freeze codes on IDRS indicating recent bankruptcy or criminal investigation.

5. You are unable to find a current address.

6. If an Identity Theft (IDT) indicator is present, do not use the address on the Yellow Label. Refer the undeliverable to the Lead, who will discuss the undeliverable with the ID Theft Liaison.

(8) If you are unable to find a current address, the Lead or Manager will provide guidance.

(9) Staple the two pages of Form 8822-B together with the instruction page on top and highlight the following paragraph on the instruction page. "The use of this form is voluntary. However, if you fail to provide the IRS with your current mailing address, you may not receive a notice of deficiency or a notice and demand for tax. Despite the failure to receive such notices, penalties and interest still continue to accrue on the tax deficiencies."

(10) If there is more than 15 days remaining in suspense period for the returned correspondence, then leave the original purge date. If the purge date has expired, then suspend the case for an additional 15 days after re-mailing.

(11) Update the activity record to indicate the actions taken to resolve undeliverable letters.

(1) Taxpayers have a right to receive information concerning any federal taxes assessed against them. The IRS is required to exercise due diligence to find and use a taxpayer’s last known address.

(2) A taxpayer’s "last known address" is defined in 26 CFR 301.6212-2(a) as the address on the taxpayer’s most recently filed and properly processed return unless the IRS has been given clear and concise notification of a different address.

(3) Generally, the last known address is the address on Master File. However, under 26 CFR 301.6212-2(b)(2), an address may be changed by information received from the United States Postal Service, National Change of Address (NCOA) database, unless the taxpayer provides clear and concise notification of a change of address (as set out in Rev. Proc. 2010-16) or the IRS properly processes a taxpayer’s federal income tax return with a different address.

(1) “"Clear and concise notification"” is defined in Rev. Proc. 2010-16, and can be written, electronic, or oral. TEs are most likely to encounter written or oral notification of a change of address.

(2) Clear and concise written notification includes:

1. A written statement signed by the taxpayer and mailed to an appropriate IRS address informing the IRS that the taxpayer wishes the address of record changed to a new address. It must contain the taxpayer’s full name, old address, and TIN, and be specific as to a change of address.

   Note: A new address reflected in the letterhead of taxpayer correspondence will not be itself serve to change a taxpayer’s address of record.

2. A written statement signed by the taxpayer and mailed to an appropriate IRS address informing the IRS that the taxpayer wishes the address of record changed to a new address. It must contain the taxpayer’s full name, old address, and TIN, and be specific as to a change of address.

   Note: A new address reflected in the letterhead of taxpayer correspondence will not be itself serve to change a taxpayer’s address of record.

3. Form 8822-B, Change of Address or Responsible Party – Business.

(3) Clear and concise oral notification is a statement made by a taxpayer in person or directly via telephone to an IRS employee who has access to the IRS Master File informing the IRS employee of the address change. The taxpayer must provide the new and old address, full name, and TIN. The IRS employee must follow established procedures to verify the taxpayer’s identity, and inform the taxpayer that the new address, and not the former address, will be used by the IRS for all purposes, not just the Form 945 compliance matter.

(1) A Payer's mailing address will not be updated unless clear indication of a change from the Payer or the Payer’s representative is received.

(2) Any correspondence from a Payer requesting an address change must be signed by the Payer or their authorized representative before the TE will consider updating IRS records.

(3) Before updating any field of the Entity module, research to determine if an Identity Theft Indicator (IDT) indicator is present.

(4) IDT is identified by TC 971 AC 522 IDTCLM posted to TXMODA.

(5) If IDT indicator is present, refer the address change and documentation to support the request to BMF IDT Campus Mailboxes at http://serp.enterprise.irs.gov/content/irm-supplements/identity-theft-bmf.html.

(6) Ensure the email clearly states an IDT indicator is present, the taxpayer has requested an address change, and CBWH not authorized to input the address change.

(7) Enter the action taken on the Activity Record for the CBWH case.

(1) If a taxpayer requests an address change while the case is open in CBWH, then the assigned TE will be responsible for updating the address.

(2) (CC) BNCHG is used to update a taxpayer’s address of record. See Exhibit 4.19.26-12, IDRS Command Codes (Job Aid), for graphic of screen layout. Required fields are:

1. Taxpayer Identification Number: Input the Taxpayer’s 9-digit EIN.

2. Document Code: Input 63, if the field does not autogenerate 63.

3. Transaction Code (TC): The TC for an address change is 014, however it is not necessary to input the TC as it will autogenerate when the transaction posts. See IRM 21.7.13.6.5.1, Changing an Address.

4. In-Care-Of Name: Identifies the name of an additional person responsible for the account. Enter a percent sign (%) in the first position. $$ deletes information in this field.

   Note: Note: Never alter the "Care of Name" if the entity is a Partnership or LLC and the "Care of Name" field contains the name of a partner or member.

5. Foreign Street: Enter the number and street name for a new United States street address. $$ deletes the foreign address.

6. Mail Street Address or Foreign City / ZIP Code: Enter the number and street name or PO box for a new United States street address. Enter the foreign city and ZIP Code for a new foreign address.

   Note: If the Taxpayer provides both a PO Box and a physical address, then input the physical address as the location (see below) and the PO Box as the mailing address.

7. Mail City/State/ZIP Code or Foreign Country: Enter the city, state, and ZIP Code for a new United States street address. Separate all fields by commas. Enter the foreign country if a foreign address, followed by a comma and a period (,.) in place of the state and ZIP Code information.

8. Location Street Address: Enter the number and street name of the actual location of the business, if different than the mailing address and if provided by the Taxpayer.

   Note: If the Taxpayer provides both a PO Box and a physical address, then input the physical address as the location and the PO Box as the mailing address (see above). Only a trust or estate is authorized to have a PO Box as a location address.

9. Location City/State/ZIP Code: Enter the city, state, and ZIP Code of the actual location of the business, if applicable. Separate all fields by commas. Enter the foreign country if a foreign address, followed by a period (.) in place of the state and no ZIP Code.

10. Remarks: Provide a brief explanation for the completion of this section see IRM 4.19.26.10.4.4.1, BNCHG Remarks Section.

(3) After verifying the input is correct as entered on the screen, press [Page Up] to submit. Print the confirmation screen as an electronic PDF document and save in the Payer’s electronic case file in the shared drive.

(4) When an EIN has employment tax filing requirement codes (FRC) and an address change occurs, CP 148A generates to the taxpayer’s new address and CP 148B generates to the taxpayer’s previous address. Unless instructed to do so by your Manager, do not suppress notices by entering a "Z" in the PARA-SEL-CD> field.

(1) The Payer's address will be updated from every return received per Rev. Proc. 2010-16.

(2) Take care not to update the BMF address to a previous address. For delinquent returns, ensure the address has not changed in more recent years.

(3) If a secured delinquent return has not yet received a DLN, then it is not necessary to update Master File with the address on the return as Submissions Processing will update the address from the return.

(1) 26 CFR 301.6109-1(d)(2)(ii) requires any entity with an EIN to report a change in its responsible party on lines 8 and 9 of Form 8822-B within 60 days of the change. Use of Form 8822-B is voluntary for purposes of reporting a change of address, but the EIN entity must include its current mailing address and telephone number on its filed returns, pursuant to 26 CFR 20.6011-1.

(2) Entities using BMF SSNs -- filers of Form 706 and 709 series, which are estate, gift, and generation-skipping transfer tax returns - may use Form 8822, Change of Address, to request an address change, as will IMF taxpayers (individuals). Use of Form 8822 is voluntary by these taxpayers.

(3) Every field of Form 8822-B must be completed before it is considered processable. However, a location address is not required of every taxpayer. Required fields are:

• Change of Address: Items 1-7 and Item 10

• Change of Responsible Party: Item(s) 4 and 8-10

(4) An individual TIN (SSN or ITIN) must be provided for the responsible party. Business entities cannot be considered the responsible party of a business entity other than a government entity.

(5) Signatures on Form 8822-B, on Form 8822, and on other written request for address change, will be accepted prima facie. "Prima facie" means at first appearance, at first view, or before investigation. If there is no contradicting evidence to dispute the authority of that person, the signature must be accepted. See IRM 3.13.2.2(10), BMF Entity – General. This policy applies to signatures accompanied by titles such as owner, president, and so on. This authority does not apply to third party requests. A Form 2848 is required for a third party not listed on CC CFINK. See IRM 3.13.2.2 for definitions of an authorized representative.

(6) Written requests for change of address that are not on Form 8822-B may be accepted if they contain the same information as required on Form 8822-B. These include:

1. A letter signed by the taxpayer or an authorized representative that includes the taxpayer’s full name and correct EIN; and

2. Correspondence sent by CBWH that is returned by the taxpayer with corrections marked on the taxpayer’s address information (signature is not required).

(7) The designated CBWH employee or TE will scan all written requests for change of address and place the electronic scans in the appropriate case file in the shared drive.

(8) Written requests for change of address that have been processed have a defined retention period and will be stored in the Files Operation in an Alpha File. Each request must be name controlled and contain an audit trail in the lower left margin of the document. The designated CBWH employee will forward all processed forms to Files Operation on a Form 3210 indicating "Alpha File." If the written request was not processed (for example, because it was rejected back to the taxpayer or referred to the Identity Theft Liaison) it is not sent to Files.

(9) A hard copy of the written request for change of address, including audit trail is placed in the paper case file.

(1) Written requests for change of address may be evaluated as follows:

(1) If a Payer makes an oral request for change of address, follow the guidance below:

1. They must be able to authenticate their identity. IRM 21.1.3.2.3, Required Taxpayer Authentication, IRM 21.1.3.2.4, Additional Authentication, or IRM 21.1.3.3, Third-Party Authentication, for procedures on authenticating the caller before inputting the address change.

2. Follow the procedures outlined in IRM 21.1.3.20.1, IMF and BMF Oral Statement Address Changes, and IRM 21.1.3.20.2, Oral Statement Documentation Requirements, for mandatory items to be entered on the Remarks portion of the IDRS CC INCHG screen.

(2) If an address change is necessary and the taxpayer requests an address change using oral statement, the IAT Address Tool is highly recommended for both research and inputting a change of address request.

(3) If the taxpayer cannot pass the authentication, the address change cannot be updated via oral statement. Request they complete Form 8822-B, Change of Address or Responsible Party – Business, and mail to the address on the form based on their state. Advise the taxpayer they can get this form at "www.irs.gov."

(1) Oral Statements by a Payer that it was for any reason not required to backup withhold or is not liable for backup withholding, are not sufficient return information.

(2) If a Payer wants to make a statement, advise the Payer to provide that statement in writing.

(3) Sufficient return information is a signed Form 945 reporting the applicable tax as shown in the LOP. If the Payer wants to show there is no liability for the tax, the Payer must provide additional sufficient return information.

(4) For Missing Payee TINs, additional sufficient return information consists of a written statement, signed by the Payer, that the Payee TINs were on hand at the time the Reportable Payment was made, accompanied by the missing Payee TINs.

1. Missing Payee TINS may be provided as a written list of Payee names and associated TIN(s), or copies of information returns as originally filed showing the Payee TINs, or similar listings, forms, or schedules. However, TEs will not specify the method by which the Payer provides the missing Payee TINs.

2. The Payer is not required to provide any books, records, or other substantiation, but may provide other documents for consideration.

(5) For FITW, additional sufficient return information consists of a credible written statement, signed by the Payer, explaining why FITW is not due, accompanied by copies of amended information returns correcting FITW reported by the Payer, that the Payer filed before the end of calendar year in which the reportable payments were made, along with a statement that FIT actually withheld from payees was refunded before the end of the calendar year. See IRM 4.19.26.10.7.5, The Payer withheld federal income tax in error or incorrectly reported federal income tax as withheld on the information return.

(1) If the Payer provides an incomplete response (for example, the Payer provides a written statement but does not provide the missing return information such as Payee TINs), the TE will issue Letter 3064-C to explain why the response cannot be accepted to reduce backup withholding liability and describe the missing information.

(2) Generally, the case will not be suspended to provide additional time for the Payer to provide a more complete response, unless the Payer requests a one-time 30-day extension of time to respond.

1. If the Payer provides an incomplete response after receiving Letter 6112, TE will issue Letter 3064-C with Letter 6112-A. The tax liability shown on the LOP will not be reduced.

2. If the Payer provides an incomplete response after receiving Letter 6112-A, Examiner will issue Letter 3064-C and proceed with assessment. The tax liability shown on the LOP and EOB will not be reduced.

3. If Letter 3064-C is issued, TE will input Activity Code 3064C (for Workstream 1) or 23064C (for Workstream 2), Case History Status Code A.

(3) Payers may not truncate TINs that they provide to CBWH Program. If a Payer tries to provide missing return information, but provides a truncated TIN, it should be rejected as insufficient.

(1) If the Payer submits additional return information on or by the Letter 6112 or Letter 6112-A purge dates, then the TE will consider it and make any adjustments necessary. It is not necessary to wait until the expiration of the purge date to communicate the results of the TE’s determination.

(2) If a response is received and additional return information is still needed, the TE may telephone the taxpayer to explain the missing return information.

(3) The TE will process additional return information provided by the Payer as follows:

(4) Do not re-send the first or second notice or extend the response dates for the notices. Provide revisions as described above and move continually toward the next step in the compliance process. However, the Payer’s request for a one-time 30-day extension of time to respond will be accommodated at any time during the compliance case, unless there is a statute issue that requires Quick Assessment (see IRM 4.19.26.12.3, Quick Assessment).

(1) TEs will conform to Policy Statement P-21-3 requirements to respond to the Payer. See IRM 1.2.1.13.3, Policy Statement 21-3 (Formerly P-6-12), Timeliness and Quality of Taxpayer Correspondence.

(2) The general guidelines of Policy Statement P-21-3 / Action 61 are:

1. A quality response is an accurate and professional communication which, based on information provided, resolves the taxpayer’s issues, requests additional information from the taxpayer, or notifies the taxpayer we have requested information from outside the IRS.

2. A quality response is timely when initiated within 30 calendar days of the earliest stamped IRS received date.

3. When a quality response cannot be issued timely, an interim response is initiated by the 30th calendar day from the earliest stamped IRS received date. Issue a Letter 2645-C, Interim Letter.

4. The promised resolution date may be any number of days and can vary depending upon the program being worked. The promised resolution date does not have to be in increments of 30 days.

(3) CBWH TEs issue interim Letter 2645-C by the 30th day from the earliest stamped IRS received date on all open replies, Reworks if 30 days have passed since the Payer’s correspondence was received.

(4) CBWH TEs also issue a follow up Letter 2644-C, Second Interim Response, on all open replies and Reworks if the promised response date in Letter 2645-C will not be met.

(5) CBWH TEs will issue Letter 288-C, Interim Reply: Adjustment Request Considered, if the Payer’s response has been accepted and account will be adjusted within five days. The letter notifies the Taxpayer that there will be a delay between adjusting the account and receiving a notice of the adjustment and instructs the Taxpayer to ignore any notices the Taxpayer might receive that don’t include the adjustment.

(1) If a Payer calls Customer Account Services (CAS) and the account has an open control in any status beginning with 02803, the employee will direct the taxpayer to call the BWH toll-free line 833-534-3075. If the Payer does not want to call CBWH, the employee will prepare a Form 4442, Inquiry Referral, and EEFax 855-386-1138.

(2) If CAS identifies taxpayer correspondence relating to the proposed and/or assessed backup withholding or federal income tax withholding, the employee will EEFax the correspondence to CBWH at 855-386-1138.

(3) See IRM 21.7.2.4.10, Form 945, Annual Return of Withheld Federal Income Tax.

(1) If the Payer provides a written or oral response that indicates that the Payer does not understand the law or the adjustment, contact the Payer by telephone to explain the compliance issue and how to resolve it. Refer the Payer’s issue to the Lead or Manager if necessary.

(2) You may provide the following information sources to the Payer:

• Pub 15, (Circular E), Employer’s Tax Guide

• Instructions for Form 945

• IRM 4.19.26, Liability Determination, Campus Backup Withholding Return Compliance Program Procedures

• Other publications or guidance, as approved by Manager

(1) The Payer will not be subject to backup withholding if the Payer provides a written statement that it was in possession of the Payee(s) TIN(s) at the time the reportable payments were made. This statement is only sufficient where the Payer also provides the Payee(s) TIN(s).

(2) A Payer may state that a missing TIN was omitted from an information return in error for various reasons such as: a glitch in their accounting software, change in accounting software, or change in a member of their accounting department. These statements alone do not indicate that the TIN(s) were on file at the time the reportable payment was made.

(3) The Payer may provide the Payee(s) TIN(s) in any format (for example, as a list of Payee names and TINs, copies of information returns as originally filed by the Payer, amended information returns, or copies of Form W-9, Request for Taxpayer Identification Number and Certification).

(4) The Payer is not required, and the TE must not ask the Payer, to provide the missing return information in a particular form such as Form W-9.

1. The Treasury Regulations require provision of Form W-9 only in response to the IRS notifying the Payer of a "mismatched" TIN on notice CP2100.

2. A Payer is not liable for backup withholding when the failure is due to reasonable reliance on a Form W-9 or another acceptable substitute. See 26 CFR 31.3406(h)-3(e).

3. If the Payer voluntarily provides a Payee’s Form W-9 to the CBWH program, review the form. Dates reflected on the form may show when the Payer was in possession of the TIN. If the Form W-9 is dated on or before the payment is made, then the Payer is not subject to backup withholding for that Payee, even if the payee TIN is incorrect. Revise the LOP, column "Payments Removed from LOP Because Missing Payee Information Provided," to reflect the Payer's response.

4. The Form W-9 may also show whether the Payee was exempt from information return reporting at the time the reportable payment was made.

5. If the information return has a "second notice" indicator box checked, the Payer has received two CP2100 Notices in the past three years for the Payee, and the Payee is subject to mandatory backup withholding on all payments made to the Payee. The TE will issue Letter 3064-C to explain that Form W-9 is insufficient for this reason. Input Activity Code 3064C (for Workstream 1) or 23064C (for Workstream 2), Case History Status Code A.

(5) TE must not research Payee transcripts or base a determination of whether the Form W-9 will be accepted on the Payee’s transcript. See discussion of unauthorized access and unauthorized disclosure in IRM 4.19.26.10.7.13, Payer Submits Form 4669 for Relief of Liability Under IRC 3402(d).

(1) If the Payer responds that it was not required to backup withhold because the payee was exempt or because the payment was exempt, then TE should review the Payer’s statement to see if it is reasonable.

(2) Refer to the instructions on Form W-9, for a description of payees who may be exempt from BWH and for which information reporting may not be required. In some cases, the payer may only treat the payee as exempt if it certifies to the exemption on Form W-9.

(3) If warranted, the TE can perform internet research to confirm the payee likely is an exempt payee.

(4) If the Payer cites the Code or Regulations as support for claimed exemption from information return reporting and/or backup withholding, discuss the Payer’s citations with the Lead or Manager.

(5) If the Payer actually withheld income tax from payments to the Payee and reported the income tax withholding on an information return, the fact that the Payee or payments is or are exempt is irrelevant. The Payer must report such voluntary withholding on Line 1 of Form 945 and must deposit the tax.

(1) A Payer may state that a missing TIN was omitted in error from an information return for various reasons including:

1. A processing or programming error in accounting software

2. A change in accounting software

3. A change in their accounting staff or outside representation

(2) Pertaining to a Payee’s TIN, an "error" as defined in the Treasury Regulations can only exist where a TIN was actually entered incorrectly on an information return. See the examples discussed in 26 CFR 31.3406(d)–5(c)(3)(iii), in which a TIN was actually obtained but was entered incorrectly on an information return. An "error", regardless of its type, does not pertain to missing TINs, and cannot excuse the Payer from obtaining a TIN before or at the time the reportable payment was made.

(3) While software, staff, or representatives may make errors and omit TINs from information returns, the assertion that the TIN was omitted in error does not automatically relieve the Payer from backup withholding. Instead, the Payer must affirm in writing and by providing the missing return information that the Payer was in possession of the Payee(s) TIN(s) at the time the reportable payment was made.

(1) 26 CFR 31.6413(a)–3(b) governs refunds of amounts erroneously withheld by a Payer or broker under IRC 3402 and IRC 3406. These regulations provide that if a Payer or broker withholds from a payee in error (including withholding more than the correct amount, as described in paragraph (a) of this section), the Payer or broker may refund the amount erroneously withheld to the payee if the refund is made prior to the end of the calendar year and prior to the time the payer or broker furnishes a Form 1099 to the payee with respect to the payment for which the erroneous withholding occurred.

(2) The purpose of this regulation is to ensure that a payee is not incorrectly provided an information return that reports income tax withholding which can be used by the payee to offset their income tax liabilities.

(3) Once a Form 1099 is issued to the payee and filed with the Service, the income tax reported as withheld from the payee is considered to have been withheld and is available for use by the payee for income tax liability purposes under IRC 31.

(4) If the Payer does not reimburse the payee nor file a corrected Form 1099 with the IRS before the close of the calendar year in which the remuneration was paid, the Payer is obligated to file a Form 945 reporting the amount of income tax withholding reported on Form 1099 and is liable for the tax pursuant to IRC 3403.

(5) Other documents, such as cancelled checks, general journals, or check ledgers, presented as evidence that an error was made in the preparation of the Form 1099; are insufficient. Absent a corrected information return the backup withholding taxes and the federal income tax withholding on filed information returns should be reported on Form 945.

(6) When the Payer asserts that it made an error on information returns, TE’s should inquire whether and when the Payer filed corrected information returns. Document the Payer’s answer.

(7) Request a copy of the corrected information returns from the Payer and compare them to IDRS CC IRPTRI. Discuss any inconsistencies with the Lead or Manager.

(8) PMFOLD will provide the date information returns were filed.

(9) If the TE determines that the Payer is still liable for reported FITW (for example, because the Payer did not file corrected information returns and refund any withheld taxes prior to the calendar year end for which the Payer reported the tax withheld, IRC section 3402(d) relief may apply. The Payer will qualify for IRC section 3402(d) relief from liability for the taxes that have been reported as withheld if the Payer can demonstrate that:

1. Affected payees reported the reportable payments on their income tax returns; and

2. Affected payees actually paid the tax due with respect to the reported payments (rather than offsetting their tax liabilities against the withholding reported on the Forms 1099).

(10) The Payer can have the tax abated by providing Form 4670 and Form 4669 signed under penalties of perjury by the payees. IRC 3402(d) does not provide relief of liability from penalties and interest; the Payer would still be liable for interest and penalties for failure to file and failure to pay the tax that should have been deposited and reported on the Form 945.

(1) If the information returns were paper-filed, request that the Payer provide a copy of the Form 1096 and the information returns that appear on the LOP.

(2) Compare the information returns to IRPTRI and PMFOLD. If there any questionable items (for example, if the copy provided by the Payer appears to have been altered):

1. Follow IRM 2.3.62, IDRS Terminal Responses, Command Code ESTAB modifier S (ESTABS), to obtain an image of the paper-filed returns.

2. Under IRM 2.3.62.5, Command Code ESTAB — Type Of Request codes, use D to obtain the 1096. This should also provide the Form 1099s.

3. Save a copy of the completed ESTAB in the case file.

4. Input Activity Code ESTABMMDD (for Workstream 1) or 2ESTABMMDD (for Workstream 2), where MMDD is 90 days from the date of request, Case History Status Code A.

5. Update your activity record to reflect these actions.

(3) Prior to making any reduction to the LOP due to transmission or processing errors, discuss with your Lead or Manager whether to make a referral to the Campus Fraud Coordinator. See IRM 4.19.26.5.4, Consider Referral for Fraud or Identity Theft.

(4) If the information returns were filed electronically, refer the case to Employment Tax Policy via your Manager. See IRM 4.19.26.5.3, Consider Referral to Employment Tax Policy.

(1) Filing corrected information returns with CCBWH will not automatically relieve the Payer of liability for backup withholding or non-payroll federal income tax withholding under IRC 3403.

1. For backup withholding, the Payer must provide the missing return information (for example, the payee TINs and a written statement that the Payer possessed the payee TINs at the time the reportable payments were made). Corrected information returns may include the payee TINs, but that will be insufficient to relieve liability by itself.

2. For federal income tax withholding, the Payer will not be relieved of liability except as discussed above, under Payer withheld federal income tax in error or incorrectly reported federal income tax as withheld on the information return.

(2) Corrected information returns filed with CCBWH must be sent to Submission Processing. If the Payer provides corrected information returns, the TE will:

1. Verify the Payer and Payee information and that the income matches the original information return.

2. Obtain from the Payer or prepare Form 1096, Annual Summary and Transmittal of U.S. Information Returns. Write Corrected Returns - Secured by Examination in red ink in the space at the bottom of the Form 1096.

3. Do not enter E (Exam) in the first box under Official use only, because CCBWH does not consider or assert information return penalties under IRC 6721 and IRC 6722.

4. Do not make any markings in the top margin of Form 1096, which would interfere with the processing of these documents.

5. Prepare a separate transmittal Form 1096 for each type of information return.

6. Scan the Form(s) 1096 and corrected information returns and place an electronic copy in the Payer folder on the shared drive.

7. Send original Form 1096 and the appropriate information return(s) to the appropriate address as indicated in IRM 20.1.7.5.1, Field Examination Delinquent Information Return Procedures, via Form 3210.

(3) Corrected information returns filed after the Payer received Letter 6112 may be fraudulent. Discuss with Lead or Manager whether to make a referral to the Campus Fraud Coordinator. See IRM 4.19.26.5.4, Consider Referral for Fraud or Identity Theft.

(1) Information returns do not report federal income tax withholding and backup withholding separately. When reported on Form 945 Federal income tax withholding is reported on line 1 and backup withholding is reported on line 2. Total taxes, Line 3, equals the totals of lines 1 and 2.

(2) A Payer may assert that what the TE has characterized as backup withholding is actually income tax withholding, or vice versa. TEs will not revise the LOP based on this assertion.

(3) For Payees without TINs, backup withholding at the appropriate rate is required. If backup withholding was required because the Payer did not possess a Payee’s TIN at the time a reportable payment was made, and if the Payer failed to withhold or withheld less than the required amount of backup withholding computed using the appropriate backup withholding rate, the Payer will be liable for the backup withholding that was not withheld.

(4) FIT that was actually withheld will be considered backup withholding to the extent it does not exceed the backup withholding rate. Any amount above the backup withholding rate will be treated as voluntary FITW.

(5) Workstream 1 focuses primarily on failure to file Form 945 for backup withholding on Payees with no TINs. For Workstream 1, most if not all tax will be reported on Form 945 Line 2, Backup withholding. However, there may be voluntary FITW agreements in this Workstream, where withheld taxes in excess of backup withholding will be reported on Form 945 Line 1.

(6) Workstream 2 focuses primarily on failure to file Form 945 for voluntary Federal income tax withholding reported on information returns. For Workstream 2, most if not all tax will be reported on Form 945 Line 1, Federal income tax withheld from pensions, annuities, IRAs, gambling winnings, etc. However, there may be backup withholding in this Workstream reported on Form 945 Line 2.

(7) Do not research the Payee’s account to see if they reported income tax withholding or paid the tax. See discussion of unauthorized access and unauthorized disclosure in IRM 4.19.26.10.7.13, Payer Submits Form 4669 for Relief of Liability Under IRC 3402(d).

(1) If the Payer states that the Form 945 was filed under a different EIN, and provides a signed copy of the Form 945, or the EIN under which the Form 945 was filed, then research IDRS for the different EIN using (CC) BMFOLI and (CC) BMFOLT.

(2) Under (CC) BMFOLT - look for a return filed (TC 150) under MFT 16 for that tax year. Compare the tax due on the TC 150 to the tax computed on the list of payees or the amount of reportable payments multiplied by the applicable backup withholding rate.

(3) Obtain a copy of the Form 945 from MeF and place it in the paper case file and electronic case file on the shared drive.

(1) A Payer may refuse to participate in a compliance check without penalty. The IRS has the option of opening a formal investigation, whether or not the Payer agrees to participate in a compliance check.

(2) If the Payer declines to participate in the compliance check, or to provide missing return information, continue with the compliance process as though there was no response from the Payer.

(1) If the Payer submits a Form 945 that the Payer prepared, the recipient will stamp it with an “IRS Received Date” stamp, and scan and upload it to the appropriate Payer’s TIN folder Payer (PR) Folder on the shared drive.

(2) The recipient will place the original paper return in the paper case file or route it to the TE to do so. This return will be sent by the designated CBWH employee with Form 3210 to Submission Processing after the TE reviews it.

(3) If the Form 945 is signed, the recipient will input Activity Code RTNRCMMDD (for Workstream 1) or 2RTNRCMMDD (for Workstream 2), with Case History Status Code A, to notify the assigned TE that a signed Form 945 has been received. The purge period for reviewing and, if applicable, processing the Form 945 with Submission Processing is 5 days from the date the Form 945 was received in the CBWH Unit.

(4) TEs will review the Form 945 and follow these review procedures:

(1) If the Payer submits a Form 945 tax return that the TE prepared, the recipient will stamp it with an "IRS Received Date" stamp, and scan and upload it to the appropriate Payer’s TIN folder Payer (PR) Folder on the shared drive.

(2) The designated CBWH employee will place the original paper return in the paper case file or route it to the TE to do so. This return will be sent by the designated CBWH employee with Form 3210 to Submission Processing after the TE reviews it.

(3) If the Form 945 is signed, the designated CBWH employee will input Activity Code RTNRCMMDD (for Workstream 1) or 2RTNRCMMDD (for Workstream 2), with Case History Status Code A, to notify the assigned TE that a signed Form 945 has been received. The purge period for reviewing and, if applicable, processing the Form 945 with Submission Processing is 5 days from the date the Form 945 was received in the CBWH Unit.

(4) TEs will review the Form 945 and follow the procedures below:

(1) If the Payer deducts less than the correct amount of backup withholding, it is nevertheless liable for the correct amount of tax that it was required to withhold, unless and until the Payee pays the tax. Under IRC 3402(d), the Payer may avoid liability if the Payee has filed an income tax return and paid the tax due. Under IRC 3406(h)(10), backup withholding is treated as if deducted and withheld under IRC 3402.

(2) IRC 3402(d) relief from liability for backup withholding tax does not extend to penalties and interest and is not available for employers who actually deducted and withheld federal income tax withholding or backup withholding from payments to Payees but failed to report and/or deposit the withheld taxes with the IRS. See IRM 4.23.8.4, IRC 3402(d) - Relief for Employer When Employees Have Paid Income Tax on Wages.

(3) Payers are required to use Form 4670, Request for Relief from Payment of Income Tax Withholding, along with one or more Form 4669, Statement of Payments Received, to obtain this relief. "Relief from payment" means that the Payer has not paid the tax yet.

(4) The Payer must secure signed Form 4669 from the Payees and payments that are the subject of the compliance check. The Payer must obtain a separate Form 4669 from each Payee for each tax year. The Payer then prepares, and signs Form 4670 indicating the tax year and the number of Form 4669 secured and submits the forms together to the IRS to request section 3402(d) relief from payment.

(5) The Forms 4669/4670 submission can be considered by CBWH unless Form 945-X is submitted with the request. If Form 945-X is included in the taxpayer’s response, the request for IRC 3402(d) relief must be submitted with the Form 4669 and Form 4670 and forwarded to Ogden Submission Processing, as required by IRM 1.2.1.6.18, Policy Statement 5-133, Delinquent returns—enforcement of filing requirements, which specifies that all delinquent returns submitted by a taxpayer, whether upon their own initiative or at the request of a IRS representative, will be accepted. See IRM 4.19.26.14.4.3, Specific Guidelines for Abatements.

(6) Where IRC 3402(d) relief applies, tax will be assessed in a "two-step" process-

1. TE will assess the gross tax reflected on Payer-signed Form 945 or the Manager-signed 6020(b) Form 945 return

2. TE will abate the tax (but not penalties or interest) based on the accepted Forms 4669/4670

(7) IRC 3402(d) relief should not be offered where the Payer has failed to report on Form 945 and deposit tax that was actually withheld (Workstream 2 cases).

(8) A 30-day extension of time to secure and return the forms will be granted if the Payer has not already received a 30-day extension. The Payer may return the forms with the response to Letter 6112-A, or subsequently.

(1) It is common for a Payer to discontinue doing business with a Payee for consecutive years.

(2) Where the Payer failed to secure the Payee’s TIN, a continuing business relationship is not a factor in determining the Payer’s liability for backup withholding.

(3) A Payer is required to secure the Payee’s TIN at the time of a reportable payment and backup withheld at that time if the Payee’s TIN was not secured, under IRC 3406(a)(1). IRC 3406(h)(10) requires the Payer’s liability for backup withholding to be treated as if it were required to be deducted and withheld under IRC 3402. Under IRC 3402(d), if the Payer was required to backup withhold on the reportable payment, but did not, the Payer nevertheless remains liable for the backup withholding.

(4) In contrast, for a name/TIN mismatch, the Payer would be required to start backup withholding on payments to a Payee thirty days after receiving notice CP2100 from the IRS to begin backup withholding, or if there were either no responses to the B-Notice solicitations from the Payer, or if the Payer never sent the B-Notices to the Payee. If the Payer failed to start backup withholding under these circumstances, the Payer would remain liable for any backup withholding it failed to withhold from reportable payments. Going forward, if the Payer discontinues the business relationship and makes no further payments to that Payee, then there would be no remuneration on which to backup withhold.

(5) Where the Payer withheld income tax from the Payee and reported the income tax withholding on an information return, the Payer should have deposited and reported the withholding on Form 945. It is irrelevant if the Payee is either out of business or the Payee no longer does business with that Payer.

(1) Indicators that the Payer is out of business should be seen while conducting preliminary IDRS research. See IRM 4.19.26.7.2, Perform IDRS Research.

(2) If a Payer responds that they are no longer in business, corroborate the Payer’s statement by IDRS research or verify that the Payer has checked the “final return” box on Forms 1120, 1120-S, or 1065.

(3) If the Payer is also an employer, the Payer’s employment tax returns may also indicate a final return:

1. Form 941 final return the box on line 17 is checked and the final date wages are paid is entered. A statement is attached to the return showing the name of the person keeping the payroll records and the address where those records will be kept.

2. Form 943 final return the box above line 1 is checked.

3. Form 944 final return the box on line 14 is checked and the final date wages are paid is entered. A statement is attached to the return showing the name of the person keeping the payroll records and the address where those records will be kept.

(4) Despite being out of business, the Payer will generally remain liable for backup withholding in any year they were in business, and they did not secure a Payee TIN at the time of making a reportable payment. The Payer will also remain liable for income tax actually withheld from payments made to Payees, whether that tax is backup withholding or federal income tax withheld under a voluntary withholding agreement.

(1) If the Payer indicates their records were lost, destroyed or not accessible due to a disaster, close the case as No Change. See IRM 4.19.26.13.3, Close Case – Any Non-Appealed Case (Excluding Screen-Outs).

(2) Document the Activity Record with the explanation received from the Payer.

(1) If the Payer claims hardship and/or asks for a referral to the Taxpayer Advocate, perform the procedures under IRM 4.19.26.5.5, Consider Referral to the Taxpayer Advocate Service.

(2) If assigned, perform the procedures under Form 12412, Operations Assistance Request (OAR), from Taxpayer Advocate Service. Refer to IRM 4.19.26.14.4.5, Specific Guidelines for Form 12412, Operations Assistance Request (OAR) from Taxpayer Advocate Service (TAS).

(1) IRC 7803(a)(3), Execution of duties in accordance with taxpayer rights, provides the taxpayer the right to appeal an IRS decision in an independent forum. The actions required by CCBWH employees to forward a case to the Independent Office of Appeals are outline in IRM 4.19.26.13.4, Close Case - Appealed Case.

(1) TEs will not solicit payment of any kind, including tax, penalties, and/or interest.

(2) If the Payer provides a payment, cash, checks or other remittance, immediately give to the Manager for processing with the Teller Unit. Document the payment/remittance in the Activity Report.

(1) If at any time during the inquiry the Payer submits a request for an Installment Agreement (Form 433-D, Installment Agreement, Form 433-B, Collection Information Statement for Businesses, or written statement requesting a payment plan), EEFax the documentation to CSCO Memphis at 855-381-6514.

(2) If the Payer verbally requests an installment agreement, instruct the Payer to call the telephone number on the balance due notice or they may call 1-800-829-4933 to request an installment agreement.

(1) After assessment, if a collection hold is not input, the IRS will send a series of notices or letters and take other actions to collect the debt.

(2) If the taxpayer’s account is in the collection process and the taxpayer requests a correction of the backup withholding adjustment, you must determine the collection status of the account and input a Collection Hold or contact Collections to do so. See IRM 4.19.26.14.3, Inputting a Collection Hold (STAUPS).

(1) ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

(2) ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

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

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

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

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

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

(1) At each notice purge date, if the Payer has not responded the TE will proceed to the next step in the compliance process. See Exhibit 4.19.26-6, Timely Actions, for a job aid of Timely Actions that must be taken in the CBWH program.

(1) A SFR IRC 6020(b) return must be prepared before penalties can be considered.

(2) Penalties to be considered if no return is filed:

• Failure to File Penalty (IRC 6651(a)(1)); and either the

• Failure to Pay Penalty (IRC 6651(a)(2)), or the

• Failure to Deposit Penalty (IRC 6656).

(1) A secured delinquent return is a Form 945 prepared and filed by a taxpayer. An IRC 6020(a) return is a Form 945 prepared by an IRS employee and filed by a taxpayer (whether that filing is the Form 945 return signed by the CBWH Manager or filed in another manner).

(2) Penalties to be considered on secured delinquent returns and IRC 6020(a) returns are:

1. Failure to File Penalty (IRC 6651(a)(1)); and either the

2. Failure to Pay Penalty (IRC 6651(a)(2)), or the

3. Failure to Deposit Penalty (IRC 6656).

(3) TEs will consider the Fraudulent Failure to File penalty (IRC 6651(f)), instead of the Failure to File Penalty (IRC 6651(a)(1)), where there are significant indications of fraud.

1. The burden of proof is on the government to establish fraud. Refer to IRM 4.19.10.4, Fraud Referrals, for example of Fraud indicators and for general guidance on referring returns to the Campus Fraud Coordinator.

2. See IRM 4.19.26.5.4.1, Referral to Campus Fraud Coordinator, for referral procedures.

(1) If the Payer has withheld either federal income tax withholding or BWH tax but failed to deposit the taxes withheld (for example, Forms 1099 show federal income tax withheld in box 4) but there were no deposits made to the MFT 16 (Form 945 module), then the failure to deposit penalty (and not the failure to pay penalty) will apply to the taxes that were withheld but not deposited.

(1) It is the employee’s responsibility to have a fair and consistent approach to penalty administration. See IRM 20.1.1.2.2, Fair and Consistent Approach to Penalty Administration. Employee’s responsibilities in penalty cases include, but are not limited to:

1. Consistency: Consistent treatment of similarly situated taxpayers.

2. Accuracy: Accurate determination and computation, with sufficient attention given to corrections if needed.

3. Impartiality: Impartial and fair enforcement of the tax laws.

4. Representation: Adequate consideration of the taxpayer’s position.

(2) Employees should use each penalty case as an opportunity to educate the taxpayer, help the taxpayer understand their legal obligations and rights, assist the taxpayer in understanding their appeal rights, and in all cases, observe the taxpayer’s procedural rights.

(3) The CBWH program encourages voluntary compliance by supporting the standards of behavior required by the IRC, specifically preparing an accurate return, filing it timely, and paying any tax due. Penalties are asserted on behavior that fails to meet any or all of these obligations.

(4) In most cases, failure to file and failure to pay penalties will be considered for cases when the Payer fails to file Form 945 and fails to pay backup withholding (Workstream 1). Where the Payer actually withheld federal income tax, failure-to-file and failure-to-deposit will be considered (Workstream 2). However, there may be cases where both failure-to-pay and failure-to-deposit penalties are assessed if the Payer fails to pay backup withholding and also fails to deposit withheld tax.

(1) Most of the cases in Workstream 1 and 2 will involve returns that have not been filed and taxes have not been paid. IRC 6651 provides for additions to tax for failure to file returns required to be filed to report tax, and for failure to pay tax required to be reported on those returns. See IRM 20.1.2.2(2), Failure To File/Failure To Pay Penalties – Overview.

(2) If the Payer filed a return or paid tax, evaluate whether the return was timely filed and/or the tax was timely paid using the criteria under IRC 7502. See IRM 20.1.2.2.1, When Timely Mailing Equals Timely Filing or Paying (Received Date vs. Filing/Payment Date).

1. Taxpayers qualifying for disaster relief based on their zip code will receive TC 971 with Action Code 086, 087, or 688 posted on BMFOLE. Two dates will be identified – the beginning and ending date of the disaster period. If the normal due date for filing or paying falls within the disaster period, the Payer’s return or payment will be considered on time if it is mailed by ending date of the disaster period. See IRM 20.1.2.2.2.2, Federal Disaster Area - IRC 7508A.

2. If the Payer requested an extension of time to file, see IRM 20.1.2.2.3.1, Extensions of Time to File. An extension of time to file appears in TXMODA or BMFOLT with a TC 460 carrying the extended due date.

3. If the Payer filed Form 1127, Application for Extension of Time for Payment Due to Undue Hardship, see IRM 20.1.2.2.3.2, Extensions of Time to Pay - IRC 6161. The failure-to-pay or failure-to-deposit penalty must be manually computed if the Payer was granted an extension under IRC 6161.

4. If the Payer qualifies under 26 CFR 1.6081-5 for an automatic extension of time to file and pay because Payer qualifies as a "Taxpayer Abroad" (for example, a foreign corporation that maintains an office or place of business within the United States, a partnership whose records and books of account are kept outside the United States and Puerto Rico, and so on) see IRM 20.1.2.2.3.3, Taxpayers Abroad.

(1) The failure-to-file penalty under IRC 6651(a)(1) is 5% per month for each month or part of a month the return is late, for up to five months. The penalty is computed on the tax required to be shown on the return that the Payer didn’t pay by the original return due date, without regard to extensions.

(2) The failure-to-pay penalty under IRC 6651(a)(2) is ¹⁄₂% for each month or part of a month. The penalty is computed on the net unpaid non-withheld tax at the beginning of each penalty month following the payment due date for that tax.

(3) When the failure-to-pay penalty applies for the same month as the failure-to-file penalty, the amount of the penalty for filing late for that month is reduced by the amount of the penalty for paying late for that month. This reduction is not made if the tax was actually withheld, and both the failure-to-file and failure-to-deposit penalties apply.

(4) The failure-to-deposit penalty applies to any failure by the Payer to timely and properly remit withheld taxes. IRC 6656 provides the applicable percentage for failure to deposit:

(1) For most but not all penalties, written supervisory approval must be obtained prior to issuing any written communication of penalties to a taxpayer that offers the taxpayer an opportunity to sign an agreement, or consent to assessment or proposal of the penalty. IRC 6751(b)(1).

(2) Where supervisory approval is required, the initial determination of the penalty must be personally approved in writing by the immediate supervisor, dated, and retained in the case file. Supervisory approval may be documented on a penalty approval form, in the form of an email, memo to file or electronically. The approval must cover all tax years and penalties.

(3) The Manager’s signature may be handwritten or electronic. Managers should use Adobe Acrobat to create digital signatures that meet the requirements of IRM 10.10.1.3.1, Requirements for Legally Binding Electronic Signatures. Department of the Treasury digital certificates must be used when digitally signing per IRM 10.8.52.4(2), Certificate Usage. See the IT4U guide, How to Identify, Personalize and Use Adobe Acrobat Department of the Treasury Certificates to Sign Documents in Adobe Acrobat DC and Reader DC.

(4) With respect to penalties asserted in the Campus Backup Withholding Program, under IRC 6751(b)(2), any penalties automatically calculated through electronic means. do not require supervisory approval.

(5) A penalty is only considered to be "automatically calculated through electronic means" if an IRS employee did not make an independent determination with respect to the applicability of the penalty. Therefore, CBWH employees will not manually compute or suppress penalties so the system will automatically calculate them. The exception is Failure to File penalty must be manually computed when preparing Form 2859, Request for Quick or Prompt Assessment, for prompt/quick assessment.

(6) If the failure-to-file (FTF) penalty under IRC 6651(a)(1) is automatically calculated through electronic means Managerial approval is not required for the FTF penalty. If the FTF penalty must be manually computed that managerial approval is required.

(7) If the failure-to-deposit (FTD) penalty is computed solely with CC FTDPN without any independent judgement, the penalty does not require supervisory approval All manual FTD penalty assessments require managerial approval.

(8) If a taxpayer submits a response, written or otherwise, that challenges the penalty or the amount of tax to which the penalty is attributable, and a TE reviews the case, written supervisory approval under IRC 6751(b)(1) is required before any subsequent written communication that includes the penalty. The exception for penalties automatically calculated through electronic means no longer applies once an IRS employee makes an independent determination to assert a penalty or to assert adjustments to tax on which a penalty is applicable.

(9) The fraudulent-failure-to-file penalty requires both supervisory and IRS Counsel approval. See IRM 20.1.2.3.7.5.1, FFTF Penalty Assessment-Procedural Requirements.

(1) There are some situations where the taxpayer may be entitled to relief from penalties.

(2) Penalty relief due to First Time Abatement and/or Reasonable Cause should only be considered if the Payer provides a written request.

(3) Payers may request correction of the penalty computation which may be a statutory exception, First Time Abatement, and/or waiver of the penalty due to reasonable cause.

(4) TEs will consider first whether the penalty is accurately computed, second whether there is a statutory or regulatory exception (which includes consideration of whether the return is timely filed), third whether the Payer qualifies for First Time Abatement, and fourth whether reasonable cause applies.

(5) Penalty relief may be considered either before or after assessment of the penalties. If a request for relief is received before sending the return for processing, then it should be considered before the tax is assessed.

(6) Penalty and interest computation and assessment will normally be automatically generated when the tax is assessed through delinquent return or 6020(b) assessment procedures. TEs must use IAT for penalty and interest abatement if IAT is available. Use of the IAT Reasonable Cause Assistant is required for all cases requesting penalty and interest abatement.

(1) If the Payer requests penalty relief and the penalty has been manually computed, the TE will review the computation to verify it is accurate.

(2) A penalty that has been automatically generated does not require manual recomputation. However, if tax has been assessed incorrectly, then the penalty will be adjusted if the tax is adjusted.

(1) If the Payer requests penalty relief and the penalty is correctly computed, the TE will consider whether a statutory exception applies by reviewing the timeliness of filing or payment and other statutory considerations. See IRM 20.1.1.3.3.1, Statutory and Regulatory Exceptions. Applicable exceptions may include:

(2) If the Payer has proof of timely filing and/or paying from a designated private delivery service, then it must be one that is defined by the IRS. At the time of this guide, the designated private delivery services are DHL Express, FedEx and UPS.

(3) See IRM 20.1.2.2.1 through IRM 20.1.2.2.3.3 for other guidelines for timely filing and timely payment.

(1) If the Payer requested penalty relief and statutory exception does not apply, the TE will consider First Time Abatement (FTA). See IRM 20.1.1.3.3.2.1, First Time Abate (FTA).

(2) The FTA is an administrative waiver for penalty abatement available for failure-to-file, failure-to-pay, and failure-to-deposit penalties to a taxpayer with a clean compliance history.

(3) FTA may apply on every backup withholding case with a Payer-filed Form 945. These include secured delinquent returns and 6020(a) returns (Forms 945 prepared by the TE and signed and return (or filed) by the Payer).

(4) Criteria for allowing First Time Abatement of penalties:

(5) A Payer is not eligible for FTA of the FTD penalty if any of the following is true:

1. A total of four or more FTD penalty waiver codes are present in the taxpayer’s three-year penalty history. Waiver codes, if posted, are shown in Command Code (CC) BMFOL definer R with the literal FTD PEN WAIVER CD.

2. The FTD penalty is charged for EFTPS avoidance. However, if the taxpayer made some deposits electronically by EFTPS as required but not all and all other FTA criterion are met, then any portion of an FTD penalty not attributable to EFTPS avoidance can be removed or suppressed. If the portion of the penalty attributable to EFTPS avoidance meets IRM 20.1.4.3, Restrictions on Assessments, criteria, then the penalty asserted by CBWH may be abated in full under FTA.

(6) To determine eligibility for the FTA waiver or abatement, use the command codes SUMRY, TXMOD, BMFOLI and BMFOLT:

1. Research the three prior years,

2. Research all current periods, and

3. Document the clean compliance history of the Payer.

(7) Also review in the three prior years for a TC 290 with Penalty Reason code of 018. The TC 290 with a Penalty Reason code of 018 means that FTA was already given, and the taxpayer would therefore not be eligible in this year.

(1) If the Payer asks for abatement of penalties and it does not meet the criteria for First Time Abate, then the TE may consider if the Payer has reasonable cause. See IRM 20.1.1.3.2, Reasonable Cause.

(2) A taxpayer may establish reasonable cause by providing facts and circumstances showing the taxpayer exercised ordinary business care and prudence (taking the degree of care that a reasonably prudent person would exercise), but nevertheless was unable to comply with the law. Ordinary business care and prudence includes making provision for business obligations to be met when reasonably foreseeable events occur.

(3) A taxpayer has the burden of showing that a failure to file timely returns was due to reasonable cause and not willful neglect. A mere showing that the delinquency in filing the returns was not due to willful neglect is not sufficient. There must also be reasonable cause. See IRM 20.1.2.3, Failure to File a Tax Return or to Pay Tax—IRC 6651.

(4) 26 CFR 301.6651-1(c)(1) provides that if a taxpayer exercises ordinary business care and prudence and is nevertheless unable to file the return within the prescribed time, then the delay is due to a reasonable cause. Although the regulation does not explain what constitutes "ordinary business care and prudence," at a minimum, it must mean an absence of fault. A taxpayer must prove that their failure to file on time is the result neither of carelessness, reckless indifference, nor intentional failure.

(5) Under 26 CFR 301.6651-1(c)(1), if a taxpayer exercised ordinary business care and prudence and was nevertheless unable to file the return within the prescribed time, then the delay is due to a reasonable cause. Although the regulation does not explain what constitutes "ordinary business care and prudence," the Supreme Court in United States v. Boyle, 469 U.S. 241, 245 (1985), emphasized that, at a minimum, it must mean an absence of fault (“neither … carelessness, reckless indifference, nor intentional failure”).

(6) IRM 1.2.1.4.2, Policy Statement 3-2 (Formerly P-2-7), Reasonable cause for late filing of return or failure to deposit or pay tax when due, provides specific examples of reasonable cause, including but not limited to:

1. Death or serious illness of the taxpayer or a death or serious illness in their immediate family. In the case of a corporation, estate, trust, and so on, the death or serious illness must have been of an individual having sole authority to execute the return or make the deposit or payment or of a member of such individual's immediate family.

2. Unavoidable absence of the taxpayer. In the case of a corporation, estate, trust, and so on, the absence must have been of an individual having sole authority to execute the return or make the deposit or payment.

3. Destruction by fire or other casualty of the taxpayer's place of business or business records.

(7) Acceptable explanations of delinquency are not limited to the examples in Policy Statement 3-2, since any reason for delinquency in filing or making deposits or payments which established that the taxpayer exercised ordinary business care and prudence but was nevertheless unable to comply within the prescribed time will be accepted as reasonable cause. See IRM 1.2.1.4.2(3) and (4).

(8) Explanations that generally do not meet the ordinary business care and prudence standards of reasonable cause include (see IRM 20.1.1.3.2, Reasonable Cause):

1. Mistake was made: Generally, a mistake is not in keeping with ordinary business care and prudence standard and does not provide a basis for reasonable cause.

2. Erroneous Advice or Reliance: Reliance on another party or that another party provided erroneous advice is generally, not a basis for reasonable cause since the taxpayer is responsible for meeting their tax obligations and that responsibility cannot be delegated.

3. Ignorance of the Law: In some instances, taxpayers may not be aware of specific tax obligations. The ordinary business care and prudence standard requires that taxpayers make reasonable efforts to determine their tax obligations.

4. Forgetfulness: Reasonable cause by claiming oversight by the taxpayer or a third party is not keeping with ordinary business care and prudence standard.

(9) The taxpayer faces a “heavy burden” to show that it exercised ordinary business care and prudence. See United States v. Boyle, 469 U.S. 241, 245 (1985). The facts and circumstances required to establish reasonable cause must be particularly compelling.

(10) In determining if the taxpayer exercised ordinary business care and prudence in providing for the payment of their tax liability, consideration will be given to the nature of the tax that the taxpayer has failed to pay. A heightened standard for reasonable cause applies when trust fund taxes are at issue.

(11) Because corporations act only through their employees and agents, they cannot rely upon those agents or employees, acting within the scope of authority, to escape responsibility for the nonperformance of nondelegable tax duties.

(12) Forgiveness of penalty assessments levied against taxpayer who could exert greater controls and exercise greater levels of personal responsibility would only encourage late filings and payments to the IRS. As noted by the Supreme Court in Boyle, “prompt payment of taxes is imperative to the Government, which should not have to assume the burden of unnecessary and ad hoc determinations. Id., citing Boyle, 469 U.S. at 249.

(13) See IRM 20.1.1.3.2.2, Ordinary Business Care and Prudence, for additional discussion of reasonable cause factors to consider.

(1) Update the activity record to describe consideration of penalty relief and the results of that consideration:

1. Note whether the penalty computation was manually computed, and if so whether the computation was correct or requires correction.

2. Indicate whether the taxpayer qualifies for statutory or regulatory relief, and if applicable identify the statute or regulation and describe the reasons the taxpayer meets the requirements for penalty relief.

3. Indicate whether the taxpayer qualifies for First Time Abatement and if applicable provide a brief summary of the Payer’s compliance history. Indicate if the taxpayer does not qualify for FTA because the Form 945 is an SFR 6020(b) return.

4. Indicate whether the taxpayer qualifies for Reasonable Cause and, if so, the reason.

(1) If the Payer provided a completed signed Form 945 to TE, and the return has not been sent to Submission Processing- then sent the return to be processed and monitor for it to post.

(2) After the return is posted, then process the taxpayer’s written request for penalty abatement.

(1) Underpayment (debit) interest, at the underpayment rate established under IRC 6621, is charged on an outstanding liability from the due date of the unpaid liability to the date fully paid. Since taxpayers are required to pay the tax due on or before the due date of the return, any interest charged is computed from the return due date.

(2) IRC 6621 provides the interest rates on overpayments and underpayments of tax, which are tied to the federal short-term interest rate. Interest rates are determined quarterly based on changes to the federal short-term rate. Underpayment interest rates are determined quarterly.

(3) Interest on the failure to file penalty assessed under IRC 6651(a)(1) begins to accrue on the return due date (including extensions).

(4) Interest on the failure to pay penalty begins to accrue on the date of notice and demand for payment of that penalty.

(5) Interest will accrue on a liability (tax, penalties, additions to tax and/or interest) until it is fully paid.

(6) Interest accruals are not assessed (recorded) on the transcript [Command Code (CC) TXMOD/IMFOL/BMFOL] until one of the following conditions occurs:

1. Input of an adjustment (for example, TC 29X or TC 30X), or

2. Posted payment is in excess of tax and/or penalties, or

3. Issuance of annual reminder notices (for example, IMF - CP 71, 71A, 71C, 71D; Spanish versions CP 771, 772, 773, 774; BMF - CP 160, 163, 171, 187), or

4. Input of a TC 290 for zero ($.00) with Priority Code (PC) 5, provided Hold Code 2, 3, or 4 is not used.

   Note: Input of a TC 342 for zero ($.00) without Priority Code 5 will not update interest accruals.

(7) The input of TC 290 for zero and Priority Code 5, with the appropriate hold code on an unrestricted (not blocked from systemic calculation) tax module, will post any accrual of interest. When adjusting with ADJ54, use Hold Code 0, so notices are issued. Refer to Section 8C.2(3) of Document 6209, IRS Processing Codes and Information, for information on hold codes. This information can be found on-line at http://serp.enterprise.irs.gov/content/6209/section-8c-2-3.html.

(1) If the Payer returns the signed the Form 945, whether it is a Form 945 prepared by the Payer (for any amount of $0.00 or more) or prepared by the TE, it will be reviewed and sent to Submission Processing as soon as possible, but not more than 5 days after the received date of the tax return.

(2) The recipient will date stamp the return and notify the TE that it has been received.

(3) The TE will review the return. If the return appears complete and is signed under penalties of perjury by the Payer, the TE will accept the return as required by IRM 1.2.1.6.18, Policy Statement 5-133, Delinquent returns—enforcement of filing requirements, which specifies that all delinquent returns submitted by a taxpayer, whether upon their own initiative or at the request of a IRS representative, will be accepted.

(4) After the return has been reviewed and accepted by the TE, the designated CBWH employee will:

1. Prepare Form 3210, Document Transmittal.

2. Remarks box must state: "Form 945 for processing."

3. Maximum of 12 returns on one Form 3210 (do not prepare packages with more than one Form 3210, for example, Page 1 of 1).

4. Include the whole 10-digit EIN when listing the return, Name Control, Tax Year, and MFT 16.

5. Print and/or associate it with signed Form 945 and EOB.

6. Mail the package to OSC R&C at:

Internal Revenue Service
1973 Rulon White Blvd
M/S 6054 Bldg ARKA
Ogden, UT 84201

(5) It is possible that the tax return may take 6-8 weeks to post. If the return unposts, then the TE must resolve the unpostable. Refer to Section 8B.4 of Document 6209, IRS Processing Codes and Information, for BMF Unpostable Codes and Definitions. This information can be found on-line at http://serp.enterprise.irs.gov/content/6209/section-8b-4.html. For detailed instructions on resolving unpostable conditions, see IRM 3.11.6.12, Unpostable Conditions, and IRM 21.5.5, Account Resolution – Unpostable Conditions.

(6) At the purge date, if the return has posted close the case using the appropriate closing procedure found in IRM 4.19.26.13, Step 9: Close Case. If the return has not posted at the first purge date (60-days), re-input the activity code to monitor for an additional 30 days.

(7) Due to the COVID-19 impact, social distancing, and evacuation order, the IRS is taking all measures possible to protect the employees. This can cause longer delays in getting the returns processed so it can take 12 - 16 weeks for Submission Processing to work through their inventory of processing these returns

(1) For a case that is an assessment of $1 million or more, the TE will refer the case to the Manager. The Manager will discuss with the Operations and Department Managers. Update the TXMODA Activity control to REF$1M for Workstream 1 and 2REF$1M for Workstream 2 when referring to the Manager.

(2) Prepare the Form 945 for IRC 6020(b) processing, by writing the following statements on the bottom of the return: "This return was prepared and signed under the authority of Section 6020(b) of the Internal Revenue Code. Apply condition code 4."

(3) Complete section 1 of the IRC Section 6020(b) Certification Form. See Exhibit 4.19.26-10, IRC Section 6020(b) Certification Form for BWH.

(4) The TE will follow local procedures to route the 6020(b) return package for Manager review and signature.

(5) The Manager will review the Letter 6112-A date, the TE’s activity record, and the electronic case file, to ensure that a signed Form 945 has not been received. The Manager will electronically sign the Form 945, complete Section 2 of the IRC Section 6020(b) Certification Form. The Manager will follow local procedures to route the completed and signed 6020(b) return package for Submission Processing.

(6) The TE will place a copy of the Manager-signed Form 945 and the completed IRC 6020(b) Certification Form in the Payer (PR) TIN Folder on the BWH Shared Drive "Z.".

(7) The TE is responsible for ensuring that a complete Form 945 6020(b) package is retained in case workpapers and case electronic files. A complete Form 945 6020(b) return package consists of:

1. Completed Form 945 containing 6020(b) stamp and signed by the Manager,

2. Completed 6020(b) Certification Form, and

3. EOB and LOP.

(8) The designated CBWH employee will prepare Form 3210, Document Transmittal, associate it with the complete Form 945 6020(b) package, and send it to Submission Processing at:

Internal Revenue Service
1973 Rulon White Blvd
M/S 6054 Bldg ARKA
Ogden, UT 84201

(9) The Form 945 6020(b) package must be shipped to Submission Processing within five days from the Letter 6112-A purge date.

(10) Input Activity Code WT150MMDD (for Workstream 1) and 2WT150MMDD (for Workstream 2), with Case History Status Code A, to monitor posting for 30 days. If the return has not posted at the first purge date, reinput the Activity Code to monitor posting for an additional 30 days.

(11) It is possible that the tax return may take 6-8 weeks to post. If the return unposts, then the TE must resolve the unpostable. Refer to Section 8B.4 of Document 6209, IRS Processing Codes and Information, for BMF Unpostable Codes and Definitions. This information can be found on-line at http://serp.enterprise.irs.gov/content/6209/section-8b-4.html. For detailed instructions on resolving unpostable conditions, see IRM 3.11.6.12, Unpostable Conditions, and IRM 21.5.5, Account Resolution – Unpostable Conditions.

(12) Due to the COVID-19 impact, social distancing, and evacuation order, the IRS is taking all measures possible to protect the employees. This can cause longer delays in getting the returns processed so it can take 12 - 16 weeks for Submission Processing to work through their inventory of processing these returns.

(13) When the return posts, close the case using the appropriate closing procedure found in IRM 4.19.26.13, Step 9: Close Case.

(1) Cases that close "no change" (no tax adjustment is made) will occur in certain circumstances (for example, if the Payer provides missing return information so that the backup withholding is reduced below Tolerance).

(2) The TE will forward a PDF copy of the "no change" case to the designated CBWH employee to have a folder created and the paper case stored in a locked cabinet in the office.

(3) This will allow "no change" case information to be physically retrieved at a later date, and complies with requirements the Federal Records Act of 1950, as amended, pursuant to 44 USC 3102. See IRM 1.15.2, Types of Records and Their Life Cycles. Also refer to Document 12990, Records Control Schedules 29, for guidance on the retention and disposition of CBWH cases.

(1) For procedures see IRM 4.19.26.12.1, Pre-Assessment Review.

(1) Only the first page is to be completed on Form 2859, Request for Quick or Prompt Assessment.

(2) The following items and actions must be completed.

(1) Prepare Form 3210, Document Transmittal, electronically.

(2) One Form 3210 should be prepared for up to 20 Forms 2859 with the same 23C date and same tax period.

(3) Do not combine Forms 2859 with different 23C dates or different tax periods. If there are more than 20 Forms 2859, or more than one 23C date and/or tax period, prepare the appropriate number of Forms 3210 listing only one 23C date, one tax period, and up to 20 Forms 2859 on each Form 3210.

(4) Enter on Form 3210:

• To:

Internal Revenue Service
Attn: Wendy Hadley
1973 N. Rulon White Blvd
Ogden, UT 84404

• Remarks:
  QUICK ASSESSMENTS
  TAX EXAMINER’S NAME
  23C MM/DD/YY VOL ##

  Reminder: MM/DD/YY is the 23C date and ## is the number of Forms 2859 included on the Form 3210.

• Document Identification: for up to 20 Forms 2859, enter XX-XXXXXXX NCTL, where XX-XXXXXXX is the Payer’s EIN and NCTL is the Payer’s name control.

• Releasing official: Enter TE’s name.

• Originator Telephone Number: Enter TE’s telephone number

• From: Enter TE’s address.

(5) Save and name the Form 3210 in the same folder as the Forms 2859 to be signed by the Manager. For Form 3210, use the naming convention:
NCTL TTIN 20XX12 MMDDYYYY Multi, where NCTL is the first name control on the Form 3210, TTIN is the last four digits of the EIN for the first Payer entered on Form 3210, 20XX12 is the tax period of the adjustment, MMDDYYYY is the 23C date, and "Multi" one Payer is included on the Form 3210 (if applicable).

(6) Email the Manager that Forms 2859 are waiting for signature on the "S" drive.

(1) The Manager will electronically sign Form 2859 the same or next day and will change the filename to end with a "1" indicating that the form has been signed.

(2) Move each signed Form 2859 to the Payer’s electronic case file on the shared drive and print an electronic PDF copy to your desktop so that it can be combined with other Forms 2859 to be processed.

(3) Move the signed Form 3210 to your desktop. Combine the Forms 3210 and 2859 in Adobe Acrobat, placing Form 3210 on top. Uncheck the box for Save as PDF Portfolio. Verify that all listed Forms 2859 are included in the combined file.

(4) After combining, use the same file name for the Form 3210 to re-save the Form 3210/2859 package.

(1) Map to the Ogden Accounts Management shared folder using the instructions in the Shared Drive (X) for Uploading Manual Assessments job aid.

(2) Open the Cincinnati folder using the following pathway:
CFM (\\VP0SENTSHRCMN60.ds.irs.net.gov\Common) (X:)
> RACS_Xtml
> Ogden
> Manual Assessments (F2859) EXAM-STATUTE
>Exam
>Cincinnati

(3) Select the current month’s folder. Within the current month’s folder are folders for each day of the month. You may upload files into the current day’s folder until 5 p.m. ET, when Ogden stops pulling files to process:

1. Before 5 p.m. ET: Upload the Form 3210/2859 package into the folder for today’s date.

   Example: If today was 02/02/2021, you would upload the Form 3210/2859 package into the folder for 02/02/2021.

2. After 5 p.m. ET: Upload the Form 3210/2859 package into the folder for the day after today’s date.

   Example: If today was 02/02/2021, you would upload the Form 3210/2859 package into the folder for 02/03/2021.

3. Always upload files into the current day’s date or a future date. Never go backwards to a date earlier than the date on which you upload files.

4. Ogden processes quick assessments on every calendar day. It is not necessary to refrain from uploading to a folder for a weekend or holiday date.

(1) Ogden employees will rename the Form 3210/2859 package by adding RCVD to the end of the file name. This means they have received the file and it has been pulled to be processed.

(2) If after two business days RCVD has not been added to the file name, notify the Lead TE to contact Ogden for follow up.

(1) TEs will monitor their own quick assessments every workday. When RCVD is added to the end of the file name, update the Activity Code to 2859MMDD (for Workstream 1) or 22859MMDD (for Workstream 2) with Case History Status Code A to monitor for 7 days for receipt of quick assessment DLN. This Activity Code will distinguish the assessment from a Form 945 that was sent to Submission Processing.

(2) If the adjustment has not posted or has rejected at the end of 7 days, you must follow up with Ogden to resolve, as discussed below. If the submission rejects, you must immediately correct any errors and resubmit. If the adjustment is resubmitted, reinput the Activity Code and monitor for posting for 7 days.

(3) Posting the assessment will generate a DLN, which the Ogden employee will add next to the Payer’s name control and EIN on Form 3210. The first Payer listed will have the full DLN (all digits). Only the last digits will be included for the remaining Payers on the same Form 3210. Any missing digits are the same as listed for the first Payer’s DLN.

(4) The Ogden employee will upload the completed Form 3210 in the 23C date folder shown on the Form 3210/2859 package. To access the file, open the Cincinnati folder, the month folder of the 23C date, and the 3210 folder. Save an electronic copy of the 3210 in the shared drive in folder "3210 with DLN."

(5) If the F3210/2859 file in the 23C date folder shows the submission was rejected, copy the electronic copy to your computer and make the necessary corrections to Form 2859. Save the corrected F3210/2859 package using the same naming convention as before but adding CORR to the end of the file name to indicate it is correction. Upload the corrected F3210/2859 file to the Ogden folder for today’s date (if before 5 p.m. ET) or the next day’s date (if after 5 p.m. ET). Never load the corrected file to a date earlier than the date on which you upload the corrected file.

(6) Upon receipt of the F3210/2859 file with DLN(s), input Activity Code WTG370MMDD (for Workstream 1) or 2WT370MMDD (for Workstream 2), with Case History Status Code A, to monitor posting of TC 290 and TC 370 for 14 days. Quick assessments generally take 4 to 6 weeks to post to IDRS but can take up to 8 weeks. If posting has not occurred by the purge date, reinput the Activity Code to extend the monitoring period for 14 days. You may extend the monitoring period twice. If the assessment has not posted after three monitoring periods, notify the Lead to contact Ogden personnel to resolve the delayed posting.

(1) If applicable, prepare Form 945 6020(b) Substitute for Return package. See IRM 4.19.26.12.2.2, Form 945 6020(b) Substitute for Return, for what is a complete Form 945 6020(b) package. Obtain electronic signature of Manager.

(2) Once the TC 290 and TC 370 post to the account, associate the signed Form 945 and 6020B with the DLN of the TC 290 and close the case.

(1) A TC 150 indicates a return was filed and posted to the Master File. The TC 150 amount is the tax assessed when an original return, delinquent return, or 6020(b) substitute for return is filed.

(2) TC 29X indicates a non-examination adjustment to the tax after the original return was filed (for example, TC 150). TC 290 indicates additional tax assessment, and TC 291 indicates abatement of previously assessed tax. These amounts are added or subtracted from the original assessment (i.e., TC 150) to determine the total tax on the return.

(3) TC 976 indicates a duplicate return has posted to a module already containing a return (TC 150). IDRS generates an -A freeze which prevents any refund or offset from the module until an adjustment (TC 29X) is made.

(4) If the duplicate return is an amended Form 945, there will be a posted TC 150, TC 971 Action Code (AC) 010, and -A freeze. An amended return requires an adjustment to release the -A freeze. The adjustment will be a TC 29X with the appropriate Credit Reference Numbers (CRNs), Item Reference Numbers (IRMs), and Hold Code.

(5) A 6020(b) return is identified on TXMOD by Computer Condition Code (CCC) 4 and the literal "6020b" at the end of the TC 150 assessment DLN.

(1) The most common reasons for filing duplicate or amended returns related to CBWH compliance include:

1. Taxpayer filed Form 945 directly with Campus before 6020(b) return was processed by Submission Processing.

2. Taxpayer filed Form 945 directly with Campus after 6020(b) return was processed by Submission Processing.

3. Taxpayer provided Form 945 directly to CCBWH after 6020(b) return was sent for processing to Submission Processing.

4. After delinquent Form 945 or 6020(b) return posted, taxpayer filed one or more Form(s) 945 or 945-X with either Submission Processing or CCBWH.

(2) TEs should obtain and review copies of any unknown returns, preferably by using CIS. If the image is not available in CIS, TEs should contact the Payer to request a copy of the unknown return.

(1) The Correspondence Imaging System (CIS) is used to manage scanned images of amended returns and incoming correspondence for Accounts Management (AM) to work.

(2) When a duplicate/amended return (TC 976) is present, IDRS CC: TXMODA will display an indicator 1 in the CIS-IND field indicating that a CIS document is available.

(3) If a CIS document is indicated, TEs should obtain the image by accessing AMS and downloading a copy of the CIS case for their case file.

(1) In each case, TEs will evaluate the duplicate returns to determine which return is correct. TEs may use the following table as a guide. Please note that a "valid" Form 945 is a return that is complete and is signed by the taxpayer under penalties of perjury. A valid Form 945 is not necessarily correct.

(1) TE must retain a copy of the duplicate return in the electronic case files.

(2) TEs must document all activities related to duplicate return resolution on the case Activity Record.

(1) TEs should prioritize closing work, using the following general guidelines:

1. Short statute cases with fewer than 60 days remaining on the ASED.

2. Short statute cases with fewer than 6 months remaining on the ASED.

3. Oldest taxable cases, in the order of greatest tax assessment first to lowest tax assessment last.

4. Oldest cases with zero dollar adjustments

5. Workstream priority as determined by Manager

(2) These priority guidelines are subject to change as determined by CBWH Management.

(1) After submitting a quick assessment SFR/6020(b) package to Campus Case Processing (CCP), or forwarding a delinquent Form 945 to Submissions Processing, the TE will keep the case in the TE’s IDRS number until it closes.

(2) TEs will monitor and verify posting of normal assessment or quick assessment in ORCAS, prior to closing the base control. Normal assessment is any assessment or adjustment, other than a quick assessment, that has been submitted to CCP or Submissions Processing for posting of assessment

(3) For normal assessments, Activity Code WT150MMDD (for Workstream 1) or 2WT150MMDD (for Workstream 2), monitor assessment by running a weekly ORCAS report and checking TXMOD for the TC 150 assessment at the expiration of the monitoring period.

(4) For quick assessments, there are two monitoring periods. The first, Activity Code 2859MMDD (for Workstream 1) or 22859MMDD (for Workstream 2), monitors 7 days for assignment of a DLN. The second, Activity Code WTG370MMDD (for Workstream 1) or 2WT370MMDD (for Workstream 2), monitors 14 days for posting of Transaction Codes 370 and TC290.

(5) After assessment posts, if the balance due is $10 million dollars or more including penalties and interest, email a PDF copy of the Signed Form 945 and 6020(b) certification form to the Office of Unpaid Assessments Accounting and Analysis at *IRS Financial Audit (irsfinancialaudit@irs.gov). Update the Activity Record that the copy has been sent to the IRS Financial Audit office.

(1) If the taxpayer provided a response during the monitoring period, IRM 4.19.26.10, Step 6: Review Payer’s Responses and Make Determination, and input any Rework adjustments (see IRM 4.19.26.14, Step 10: Perform Rework.)

(2) The Form 945 submitted by CBWH does not have a Record of Federal Tax Liability (ROFTL) attached so the Failure to Deposit (FTD) penalty is calculated on the assessed TC 150 amount.

(3) If the assessment posted through prompt/quick assessment procedures with TC 370 and TC 290, a FTD penalty is not assessed so you do not need to manually calculate the FTD penalty when inputting a TC 291.

(4) If the assessment posted with TC 150, then you must manually calculate and decrease the FTD (TC 186) penalty with a TC 181 when inputting a TC 291.

(5) If there is only one TC 186, then the penalty was calculated at 10%. The abatement (TC 181) amount would be 10% times the tax decrease (TC 291) amount. If there is a second TC 186, then the additional 5% was assessed. The abatement (TC 181) amount would be 15% times the amount of tax decrease (TC 291) amount.

(6) The other method to calculate the FTD amount is to use IDRS CC FTDPN. IRM 20.1.4-9, Instructions for Command Code FTDPN, provides the instructions for IDRS CC FTDPN.

(7) ITM has Course 17300 (rev 11/22/2021), BMF Introduction to FTDPN, that Tax Examiners can take to learn about input of IDRS CC FTDPN.

(8) It is not necessary to close the control base and then reopen it prior to inputting adjustments.

(1) If posting has been completed, and if there are no further known taxpayer responses to be considered or adjustments or abatements to be input, check TXMODA for duplicate returns or freeze codes that would prevent closing.

(2) If there is a posted or pending TC 150 on TXMODA that is neither the SFR/6020(b) adjustment nor a delinquent return assessment known to CBWH, or if there is an -A freeze on TXMOD, indicating an amended or duplicate return has posted, secure a copy of the unknown return:

1. Search for a copy of the return on AMS (CIS case).

2. If there is an -A freeze, this indicates a duplicate or amended return and those are scanned into the CIS Inventory and sent to Accounts Management to be worked.

3. If the open control is a CIS case (for example, CISXXXXXXX) contact AM and request they close their IDRS base notating that Campus Backup Withholding will work the case. Remember to access AMS and upload a PDF copy of the CIS case to the casefile.

4. Look for a second TXMOD control. Find the IRS employee’s name and phone number by entering the IDRS employee number with CC FIEMP. Contact the employee for a copy of the unknown return if you do not locate it on AMS CIS.

(3) If the return is different from the SFR/6020(b) adjustment or delinquent return assessment or has caused or will cause an erroneous or duplicated adjustment or assessment, return to IRM 4.19.26.10, Step 6: Review Payer’s Responses and Make Determination and IRM 4.19.26.12.4, Duplicate Return Procedures, and input any Rework adjustments (see IRM 4.19.26.14, Step 10: Perform Rework).

(4) If the return is the same as the SFR/6020(b) adjustment or delinquent return assessment (duplicate return), and if the TC 150 adjustment or assessment has posted and there has been no erroneous or duplicated assessment or adjustment, continue to close normally.

(5) After closing your control on TXMODA, print the complete TXMODA detail to PDF and upload to the casefile.

(6) If there is any other freeze code on TXMOD that was not previously addressed in compliance procedures, perform the appropriate procedures under IRM 4.19.26.7, Step 3: Case Building, to address the freeze code. If the freeze code is not addressed in procedures, discuss with the Lead how to proceed.

(1) Verify that all case file documents are present in the electronic case file, that they are appropriately named and complete, and that they are signed by the Manager if required (for example, Form 945 and 6020(b) certification, if applicable).

(2) Ensure that the PDF of the DCI screen is completed if TY2018.

(3) The designated CBWH employee inputs all DCI information from the PDF DCI screen into the BWH Database (DCI) for TY2018.

(4) The Tax Examiner will input the DCI data on CBWH DCI SharePoint for TY2019 and subsequent years. There are separate CBWH DCIs on SharePoint for Workstream 1 and Workstream 2.

(1) This step will be performed by the designated CBWH employee when working remotely due to Campus closure, and by the TE when working at the Campus Post of Duty.

(2) Print the case documents that are not already printed. If there is an original paper document, such as taxpayer correspondence, there is no need to print the scanned copy. Include the original in the case file.

(1) Definition of Rework. In the CBWH Program, any adjustment to increase or abate tax, penalty, and/or interest, that a TE makes after the original return assessment is considered a Rework. Among other reasons, adjustments often occur when:

1. TE must use the two-step process to assess backup withholding in full in order to properly compute penalties and interest, and then abate tax (only) due to the Payer’s provisions of Forms 4669.

2. Payer sends a late reply including missing return information which changes the assessment.

3. Payer prepares and files a zero-dollar Form 945 but does not provide missing return information to indicate that the Payer is not responsible for backup withholding and/or federal income tax withholding as shown on the List of Payees.

(2) A Rework occurs when any Payer response is received that might change the original assessment.

(1) The designated CBWH employee, Lead, or Manager will assign a Rework to the TE who was most recently assigned to the case, unless impracticable.

(2) If a Rework is received before the case control base has closed, it is not necessary to close the control base before assigning the case Rework to the TE.

(3) Update the IDRS control base activity with REWORK.

(4) Use the earliest stamped IRS received date for the open control.

(1) After assessment of backup withholding, a BMF taxpayer receives a series of three automatically generated notices from the IRS requesting payment for the tax balance owing. Since the notices are automatically generated, they are part of the Automated Collection System (ACS). Each notice generally provides 21 days to respond and is issued a month after the last notice if the taxpayer does not pay the debt or respond.

(2) If the BMF taxpayer does not respond to the initial notices, Collection Inventory, Delivery & Selection will evaluate and categorize the account and route it to one of the following:

1. ACS is a computerized inventory system and telephone call center. After a case arrives in ACS, the IRS checks for levy sources, telephone numbers, and other characteristics. These actions result in additional computer-generated notices to taxpayers. ACS Customer Service Representatives respond to phone calls from taxpayers to resolve balance due account.

2. Field Collection involves Revenue Officers making contact with taxpayer by issuing various notices and visiting taxpayers personally in the field to resolve balance due accounts.

3. The Queue is an electronic holding area for taxpayer delinquent accounts that are held until assignment to field Revenue Officers.

4. Shelved cases are those not actively being worked by the IRS, but they may be assigned at a later date to ACS or Field Collection or sent to Private Debt Collection. While in shelved status, penalties (up to the maximum allowed by law) and interest continue to accrue.

(3) If the case is sent to Private Debt Collection (PDC), ENMOD will show a PDC code of 1 to 99. The number indicates which private debt collecting company received the account.

(4) The TXMODA status code or freeze code will show whether the BMF taxpayer has responded by satisfying the balance due via payment or offset, or has entered into collection alternatives:

(5) A Collection SC of 48 indicates that STAUPS has been input on the taxpayer’s account and balance due notices will not be mailed. IDRS balance due notices or TDA/BAL DUE issuance is suppressed for the requested number of cycles (up to 15).

(6) If you encounter a Collection SC that is not on this list, Refer to Section 8A.3 - MF and IDRS Collection codes in Document 6209, IRS Processing Codes and Information. This information can be found on-line at http://serp.enterprise.irs.gov/content/6209/section-8b-4.html.

(1) If the Collection SC is 58, the taxpayer has received CP504, Final Notice. On BMF accounts, the first and final notices are the only notices issued. After the final notice, the next notice will be a levy and/or lien, and the Status Code will change to Collection SC 22, ACS Collection. In order to stop the lien and levy, you must input CC STAUPS to stop the collection process from moving beyond Collection SC 58, CP504 Final Notice.

(2) If collection activity has progressed beyond Collection SC 58, Final Notice, you will need to contact the appropriate Collections area -- ACS (Collection SC 22) or Field Collection (Collection SC 24 or 26) and ask them to place a hold on collection, discuss the case, and coordinate your actions on the case. ACS or Field Collection may have information you do not have that would change the result of your review and may want to review the taxpayer’s submission before you process it.

(1) Collection SC 22 is assigned to ACS, Collection SC 24 is in the queue waiting assignment of a Revenue Officer, and Collection SC 26 is assigned to a Revenue Officer.

(2) Review the Master File (MF) and IDRS Service Center Collection SC. These codes are shown on CC TXMODA. Refer to IRM 2.3.11-12, Command Code TXMOD Valid Response, which shows the current Service Center Collection SC is located on line 5 item 1 and the current MF SC is located on line 6 item 1.

(3) CC SUMRY shows the current SC Collection Status Code. Refer to IRM 2.3.11-8, Command Code SUMRY Tax Module Summary Data, which shows it is located on line 3 item 5.

(4) Review the Collection Assignment Number. CC TXMODA and CC SUMRY shows the Collection Assignment Number in the CTRL-ASGMT field. To locate the filed in CC TXMODA refer to IRM 2.3.11-12, Command Code TXMOD Valid Response, which shows it is found on line 9 item 6. To locate the field in CC SUMRY refer to IRM 2.3.11-5, Command Code SUMRY Other Heading Data—IRAF, which shows it is found on line 7 item 1.

(1) Work Process for BMF Taxpayer:

(1) If the case is in Collection SC 22, ACS, Contact the ACS Liaison to request a hold on collection. Explain the case and the taxpayer’s request and coordinate any action on the taxpayer’s account with the ACS Liaison. On the Activity Record, note the hold date given by the ACS Liaison.

(2) The ACS Liaison may be aware of taxpayer actions that do not yet appear on IDRS, which would have an effect on your review.

4.19.26.14.3.5.1 (10-24-2022)

Finding the ACS Liaison

(1) If the case is in Collection SC 22, ACS, go to the SERP Who/Where Tab (http://serp.enterprise.irs.gov/content/who-where/who-where.html) and click on "ACS Support and Status 22 TAS Liaisons":

(2) When you select "ACS Support and Status 22" the "ACS Support and Status 22" screen should appear. Using the drop down menus, select:

• Business Operating Division (BOD): SBSE

• State: The state in which the Taxpayer is located.

• Does the case have TAS involvement? Yes or No. (Usually it will be "No").

(3) Click the "Find" button. The system will display the ACS Liaison name, phone, EEFax, and email.

(1) If the case is in Collection SC 24, Queue, or 26, Field Collection, go to the SERP Who/Where Tab (http://serp.enterprise.irs.gov/content/who-where/who-where.html) and click on RO by TSIGN/ZIP/STATE. This will bring up the RO Lookup tool:

(2) In the "Search by" field, select "Assignment Number"

(3) In the next field, enter the first 6 digits of the Revenue Officer’s 8-digit Assignment number.

(4) Click the Search button.

(5) The system will display the address, phone number, and fax number of the Revenue Officer’s Group.

(6) Contact the Group to identify the assigned Revenue Officer. Ask the Revenue Officer to place a hold on collection. Explain the case and the taxpayer’s request and coordinate any action on the taxpayer’s account with the Revenue Officer. On the Activity Record, note the hold date given by the Revenue Officer.

(7) As for accounts in ACS, the Revenue Officer will direct coordination, and may want to review the taxpayer’s response before you consider the request. The Revenue Officer may be aware of taxpayer actions and responses that do not yet appear on IDRS or AMS.

(1) The purpose and function of CC STAUP is to interrupt, delay, accelerate, or skip routine notice issuance.

(2) Inputting CC STAUPS will delay generation of the next sequential notice and update to the next collection status. You must input the number of cycles to delay before issuing the next notice.

(3) When the number of cycles delay has expired, the weekly update to the module will cause generation of the next notice. Therefore, as the STAUPS collection hold expire, you must continue to input STAUPS to delay collection while the case is open in Campus Backup Withholding.

(1) In IDRS, input:
STAUPSnn-nnnnnnn
SC 15

1. nn-nnnnnnn is the taxpayer’s EIN

2. SC is the collection SC 21, 20, 56, or 58. (See Note below)

3. 15 is the number of cycles to delay collection action

(2) The collection status will change to 48 on TXMODA when STAUPS are input.

(3) If the collection SC is 22, 24, 26, you must contact ACS or Field Collection to place a collection hold on the account, as described above. You should see the collection status code change to SC>47 indicating there was a TC 470 input on TXMODA to stop ACS and Field collection.

(1) If the control base is closed in TXMOD, the designated CBWH employee will assign the control base in TXMOD and forward the correspondence to the TE (or put it in the case file, actually). If a Rework is received before the case control base has closed, it is not necessary to close the control base before the Rework Activity Code is input.

(2) TE will monitor the ORCAS report for Activity Code REPLYMMDD (for Workstream 1) and 2REPLYMMDD (for Workstream 2), indicating correspondence was received and scanned by the recipient, and is available for review.

(3) TEs should review and respond to correspondence within five days whenever possible. If a response is not possible within 30 days from the earliest stamped IRS received date, issue Letter 2645-C, Interim Letter. See IRM 4.19.26.10.6.4, Timeliness - Policy Statement 9-21-3 (this also referred to as "Action 61.")

(4) TE will review the Payer’s response using the guidelines under IRM 4.19.26.10, Step 6: Review Payer’s Response and Make Determination, and IRM 4.19.26.11.2, Consideration of Penalty Relief.

(5) For a Rework, TE will input Activity Code REWORK (for Workstream 1) or 2REWORK (for Workstream 2) upon beginning the review of the Payer’s correspondence.

(6) As needed, the TE will re-perform IDRS research (see IRM 4.19.26.7.2, IDRS Research). The extent of research will generally depend on the time that has elapsed since the research was last performed. At a minimum, the TE should:

1. If the correspondence is from a third party, ensure that the third party is an authorized representative, and Form 2848 is processed with Centralized Authorization File (CAF).

2. Verify that the assessments on the BMFOL/TXMOD agreed to the tax, penalty, and interest reflected in the case file.

3. Verify whether any tax, penalty, and/or interest already has been changed, and obtain the supporting information for those adjustments if not present in the case file.

4. Check for amended and duplicate returns and obtain a copy of the return if not present in the case file. See IRM 4.19.26.12.4, Duplicate Return Procedures.

5. Check for freeze codes and if present on the Payer’s transcript perform necessary research.

(7) Once the research and review is completed, TE will:

1. Obtain Managerial approval for any adjustment (either increase or decrease) and retain the approval in the case file.

2. Ensure that the original assessment (including tax, penalty, or approval) has posted in full (TC 370 and/or 150) before inputting the adjustment.

3. If applicable, TE will input the adjustment. To suppress notices, TE will input Hold Code 4 in connection with the adjustment.

4. See IRM 4.19.26.14.5, Processing Rework Adjustments.

5. If no adjustment is required, or after ensuring that the adjustment has posted, perform appropriate case closing procedures.

(1) Any reply that is received in an account with an active Collection status code (22, 24, or 26) on IDRS must be coordinated with the responsible function(s) prior to the Rework being performed.

1. Collections must input TC 470 cc 90 to remove the case from collection status while under Rework.

2. If there are any other Collection issues that need to be addressed, such as a remaining balance due, Installment Agreement request, and so on, Collections must work that portion of the Payer’s response.

3. At the end of Rework process, the TE will either input a TC 29X (which automatically ensures a case that has a balance due remaining on the module is put back into collection status), or a TC 472 with no closing code.

(1) If the Payer paid the tax and files Form 4669 requesting abatement and refund, the Payer must provide Form 945-X that agrees to the Form 945 minus the Forms 4669 accompanying the request for abatement.

1. If the Payer did not provide Form 945-X, issue Letter 21-C to request Form 945-X.

2. Enter Activity Code 21CMMDD (for Workstream 1) or 221CMMDD (for Workstream 2), with Case History Status Code A, to monitor the response date of 30 days ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡.

3. If the Form 945-X is provided, enclose the Forms 4669 and forward to Submission Processing.

4. If the Form 945-X is not provided, issue Letter 3064C to explain that the Forms 4669 cannot be processed because Form 945-X was not provided. Update the Activity Code to 3064C (for Workstream 1) or 23064C (for Workstream 2), then close the case as a no change (IRM 4.19.26.13.3, Close Case - Any Non-Appealed Case (Excluding Screen Outs)).

(2) Activity Code - For Rework abatements, TE will input REWORKMMDD (for Workstream 1) or 2REWRKMMDD (for Workstream 2) to monitor for posting of the abatements for 14 days. The Activity Code may be re-input as needed. TE must monitor for unposting of the adjustment and resolve if necessary.

(1) If a taxpayer responds to CBWH compliance requests by filing Form 945 for $0 or for a tax amount that is less than the amount shown on the list of payees, but the taxpayer has not provided missing return information sufficient to demonstrate that the tax is not due, then the tax must be adjusted to the amount shown on the list of payees previously provided to the taxpayer.

(2) For workstream 1, this adjustment is made because a taxpayer is liable for backup withholding under IRC 3406 where it failed to obtain the payee’s TIN prior to making a reportable payment to the payee. For workstream 2, this adjustment is made because a taxpayer is liable for federal income tax withholding from reportable payments under IRC 3402.

(3) The adjustment will equal the difference between the amount of tax shown on the list of payees and the total amount of tax liability reported by the Payer on Form 945 line 3.

(4) The adjustment is the gross amount of tax for which the Payer is liable before consideration of Forms 4669.

(5) If the list of payees has been revised – for example, the taxpayer demonstrated that the payees or payments were exempt from information return reporting requirements – then the adjustment should reflect the most recent revision.

(6) The TE will input the adjustment using normal REQ54 procedures, with Case History Status Code "A" to keep the case in active status. Print a REQ54 "completed" or summary screen for the electronic workpapers.

(7) Activity Code - For Rework adjustments that are increases, 3064CMMDD (for Workstream 1) or 23064CMMDD (for Workstream 2) to monitor for 30 days for posting of adjustment and taxpayer’s response to the related Notice. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡. TE must monitor for unposting of the adjustment and resolve if necessary.

(8) Notice to Taxpayer to explain abatement actions:

1. TE will notify the Payer of the increase using Letter 3064-C, Special IDRS Letter. Letter 3064-C is for use when a short narrative reply specifically tailored to the individual taxpayer is needed, as approved by local management.

2. Specific notification paragraphs should be inserted using selectable paragraphs L and M. See Exhibit 4.19.26-4, Letter 3064-C - Notification of Tax Increase, for the wording of these paragraphs. The wording in these paragraphs can be changed only with approval of the Lead or Manager, and care must be taken to provide all of the information needed to appropriately notify the Taxpayer without exceeding the character limitation of each paragraph.

(1) A Form 12412, Operations Assistance Request (OAR), is used by Taxpayer Advocate Service (TAS) to request the IRS take an action on an account that TAS does not have delegated authority to act upon. The OAR will be sent to the Campus Exam TAS Liaison who will forward and assign the OAR to the CBWH Manager. An OAR can be received by fax, mail or E-mail and will have a Form 3210, Document Transmittal, attached.

(2) The OAR will contain the name, telephone, and fax number of the TAS employee making the request. An OAR will include an explanation of what TAS is requesting and documentation to support the request.

(3) The CBWH Manager or a designated employee will acknowledge receipt of OAR. Expedited OARs, TAS Case Criteria 1 – 4, Economic Burden (see IRM 13.1.7.3.1, AS Case Criteria 1–4, Economic Burden) must be acknowledged within 1 business day. TAS Case Criteria 5 – 7, Systemic Burden (see IRM 13.1.7.3.2, TAS Case Criteria 5 – 7, Systemic Burden), must be acknowledged within 3 business days. OARs are acknowledged on the Form 3210 sent with the OAR and will include the name and phone number of the Manager and the assigned TE.

(4) Upon receipt of the OAR, the Manager or a designated employee will enter on the CBWH open IDRS control Activity Code TA_OARMMDD (for Workstream 1) or 2TAOARMMDD (for Workstream 2), with Case History Status Code A.

(5) The OAR Requested Completed Date is shown in Section IV, Box 3 of the Form 12412.

(6) Once received, the instructions on an OAR must be carried out within the following time frames:

1. For an expedited OAR, MMDD is three business days.

2. For a non-expedited OAR, MMDD is the due date for OAR Requested Completed Date in Section IV, Box 3, or a date that has been negotiated by the Manager if applicable. Negotiated Completion Date must be entered on the OAR in Section IV, Box 4.

(7) The TE will complete sections V and VI of Form 12412, including any actions taken and the reasons behind those actions. The Manager will sign and return the OAR once it is completed.

(8) The TE will place an electronic copy of the completed and signed OAR in the electronic case files on the shared drive. The Manager will keep an administrative copy for 6-months.

(9) The Manager will return the completed OAR package to the TAS employee.

(10) If you are assigned an OAR, your Manager will also provide instructions for any document review and rework adjustments you will make. Perform the review and/or process the adjustments as instructed by the Manager.

(1) Use IAT REQ54 to input the appropriate adjustments to close the case. If the IAT REQ54 tool is not available, use TXMOD overlay REQ54. Note:

(2) Complete the entries in the IAT Adjustment Calculator screen. Required inputs are shown in IRM 4.19.26.14.5.1.1, Required Inputs for the IAT Adjustment Calculator.

(3) After entering the inputs as described above, submit the inputs via the TRANSMIT button on the IAT Tool or the PAGE UP button for the IDRS Overlay screen.

(4) IAT REQ54 Adjustment Tag. Print an electronic PDF print of the IAT REQ54 Adjustment Tag or "Request Completed" screen and place it in the electronic case file on the shared server. If working at the Campus post of duty, print a copy of Form 10023-B for the case file to be sent to the Files function, and attach it on top of the file.