21.5.8. Credit Transfers

(1) Employees in the Accounts Management (AM) organization respond to taxpayer inquiries and phone calls as well as process claims and other internal requests.

(1) Per Policy Statement 5-2: We actively assist taxpayers who try to comply with the law, and work to continually improve the quality of our systems and service to meet the needs of our customers. All taxpayers whether delinquent or fully compliant are entitled to prompt and professional service whenever they deal with Service employees. The public is our customer, not just delinquent taxpayers. Our customers expect us to promote voluntary compliance by ensuring that all promptly pay their fair share.

(1) The Taxpayer Services Chief has overall responsibility for the policy related to this IRM which is published on a yearly basis.

(2) Additional information is found in IRM 1.1.13.7.3, Accounts Management, and IRM 21.1.1, Accounts Management and Compliance Services Overview.

(1) Program Reports: The program reports provided in this IRM are for identification purposes for the Accounts Management Contact Representatives (CRs) and Tax Examiners (TEs). For reports concerning quality, inventory, and aged listing, refer to IRM 1.4.16, Accounts Management Guide for Managers. Aged listings can also be viewed by accessing Control Data Analysis, and Project PCD. They are also on the Control-D/Web Access server, which has a login program control.

(2) Program Effectiveness: Program Effectiveness is determined by Accounts Management’s employees successfully using IRM guidance to perform necessary account actions and duties.

(3) Program Controls: Goals, measures, and operating guidelines are listed in the yearly Program Letter. Quality data and guidelines for measurement are referenced in IRM 21.10.1, Embedded Quality (EQ) Program for Accounts Management, Campus Compliance, Field Assistance, Tax Exempt/Government Entities, Return Integrity and Compliance Services (RICS), and Electronic Products and Services Support.

(1) The information below is a list of commonly used acronyms and terms this IRM:

• AMS - Account Management Services

• BMF - Business Master File

• CC - Command Code

• CII - Correspondence Imaging Inventory

• CP - Computer Paragraph

• DLN - Document Locator Number

• IAT - Integrated Automation Technologies

• IDRS - Integrated Data Retrieval System

• IMF - Individual Master File

• MFT - Master File Tax

• NMF - Non-Master File

• NSD - No Source Document

• SD - Source Document

• TC - Transaction Code

(2) For a comprehensive listing of IRS acronyms, refer to the Acronym Database.

(1) Refer to IRM 1.4.16.1.6, Related Resources, for information on related resources that impact internal controls.

(2) The Taxpayer Bill of Rights (TBOR) lists rights that already existed in the tax code, putting them in simple language and grouping them into 10 fundamental rights. Employees are responsible for being familiar with and acting in accord with taxpayer rights. See IRC 7803(a)(3), Execution of Duties in Accord with Taxpayer Rights. For additional information about the TBOR, see Taxpayer Bill of Rights.

(1) A Source Document (SD) is required for:

• Credit transfers between non-related accounts.

  Example: Due to IRS error, a payment is posted to an unrelated taxpayer, such as a payment posted to a corporation and taxpayer requests payment to be moved to a Partnership or an Individual account.

Note: Treasury accounts such as Excess Collection and Unidentified Remittance, that are accessed via Command Code (CC) XSINQ and CC URINQ, are considered non-related accounts.

• Related accounts resulting in a debit balance after the transfer.

  Example: The taxpayer requests a payment to be moved from a fully satisfied account to another account. Refer to paragraph 4 below for examples of related accounts.

(2) Use taxpayer correspondence as the source document (SD), or in the case of oral statement, prepare an e-4442/Form 4442, Inquiry Referral, history sheet or phone documentation sheet, and use as the SD. The SD documentation must include the following:

• Taxpayer must confirm the payment amount or the IRS endorsement information on the cancelled check,

• Payment Document Locator Number (DLN) (matching the transfer DLN),

• Tax form for the applicable Master File Tax (MFT) Code, tax period, and payment date, and,

• Any additional pertinent information the taxpayer may provide.

(3) When changing a payment date, and the payment is ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡, a source document and managerial approval are not required. If the payment is ≡ ≡ ≡ ≡ ≡ ≡ ≡, both managerial approval (signature) and a source document are required. Refer to the If and Then Table in IRM 21.5.8.4.2, Determining Correct Credit Transfer Format.

(4) No Source Document (NSD) is required on credit transfers within the same TIN, or between related accounts if a credit is available.
Examples of related accounts include:

• Parent submits payment for minor child, but payment is applied to parent’s account.

• Taxpayer submits a payment intended for business account (sole proprietor), but it is applied to a personal account.

• Corporation with several subsidiaries submits a payment which is applied to the wrong Employer Identification Number (EIN).

• Spousal accounts - transfers between primary and secondary tax accounts; see IRM 21.5.7.3.2.2, Spousal Payments.

(5) Enter the appropriate information in the "Remarks" section of your credit transfer tool. Follow procedures in IRM 21.5.2.4.6, Remarks Field, and IRM 21.5.2.4.7, Remarks on Type of Adjustment, for proper use of remarks. Indicate the oral statement or back-up information for your actions. Additional information regarding oral statement remarks can be found in IRM 21.1.3.20.2, Oral Statement Documentation Requirements.

(1) Prior to making a credit transfer adjustment, at least one of the tax modules involved must be present on IDRS. To initiate credit transfers, two command codes (CCs) are used in the following sequence:

1. SUMRY and/or TXMOD (with definer)

2. ADDnn or ADCnn (nn = document code 24, 34, or 48)

(2) The tax module accessed with CC TXMOD/SUMRY is the primary account for the credit transfer. Determine if the tax module should be:

• Debited, use CC ADDnn

• Credited, use CC ADCnn

(3) Input CC ADDnn or ADCnn and overlay the taxpayer identification number (TIN), MFT, tax period, and name control with the information relating to the other portion of the credit transfer (referred to as the secondary account). The secondary account may or may not reflect the same TIN, MFT, and tax period.

(4) When inputting credit transfers, you may need to use a non-IDRS Indicator listed in table below in the “NON-IDRS-IND>” field to indicate the secondary account/module is not on IDRS:

• Primary − TXMOD overlay with CCs ADD24/ADC24, ADD34/ADC34, or ADD48/ADC48

• Secondary − The other side of the credit transfer

(5) Use designated payment code (DPC) "00" when transferring a misapplied payment (TC 640, 670, 680, 694, 690, and 700) without a DPC.

(6) Refer to IRM 5.19.1.6.4.6.3, User Fee Payment Transfer/User Fee Abatements, for User Fee payment transfer procedures.

(7) The credit transfer programming does not allow an IRS received date that is more than 1 year old. When inputting a credit transfer and the IRS received date is more than 1 year old use the current date as the IRS received date. This ONLY pertains to the IRS received date NOT the payment date.

(1) For general information regarding credit transfer formats, refer to IRM 2.4.17, Command Codes ADD24/34/48, ADC24/34/48, FRM34 and DRT24/48.

(2) Use CC ADD24/ADC24, when:

1. Changing a payment date, override code "2" is required.

If	Then
Payment amount is over ≡ ≡ ≡ ≡	Obtain written managerial approval before changing the date. Source Documentation (SD) is required. Employees with access to CII should use Case Notes on CII to obtain managerial approval. The Case Note should state - "Managerial approval required for payment date change".
Payment amount is zero on a TC 610	Do not change the date.
Payment is a Federal Tax Deposit (FTD)	Follow instructions in IRM 20.1.4.24.2, Misdated Deposits.

2. Changing the transaction code of the payment (e.g., TC 610 to TC 670).

   Note: Remittance Processing System (RPS) Freeze "R-" generates if a credit balance is created when a TC 610 is transferred to a module already containing a RPS TC 610. If possible, change the payment to a TC 670. Otherwise, input TC 290 for zero to release the "R-" Freeze after transferring the payment as a TC 610.

3. A secondary TC is needed (e.g., TC 570 or TC 180).

4. Transferring between Master Files (e.g., IMF and BMF).

5. Transferring with a TC 820.

(3) Use CC ADD34/ADC34, when:

1. Transferring within the same Master File. The posting routine of the CC ADD34/ADC34 prevents partial Master File posting of the transaction (e.g., the credit side posts but the debit side goes unpostable). For this reason, use CC ADD34/ADC34 whenever possible.

2. A secondary transaction is not necessary. A credit transfer notice (CP 62 for IMF and CP 225 for BMF) is generated to the taxpayer when the “CORRESP-DT” field is overlaid with the inquiry date. In general, the taxpayer receives the credit transfer notice within four weeks from the date the credit transfer was input. Multiple credit transfers are combined, and the taxpayer receives only one notice.

(4) Use CC ADD48/ADC48, when:

1. Transferring credits have already offset or applied as credit elects.

If	Then
Credit elect overpayment transfer is the total of remaining credits, after the tax is paid, dated by the due date plus grace period. Refer to IRM 21.5.1.4.2.5, Received Date - Grace Periods.	Transaction date of the TC 830 (debit) and TC 710 (credit) is the due date of the overpaid return, without regard to extensions. Example: TY 202212 is overpaid by 1,500.00; the taxpayer requests that the overpayment be applied to TY 202312. Using the IAT Credit Transfer Tool, input CC ADD48/ADC48 on TY 202212, input a TC 830 04152023 1,500.00 and on TY 202312 input a TC 710 04152023 1,500.00-. Exception: If the transfer is for a Form 1120 (MFT 02) module with a tax period ending in June, or an MFT 02 tax period beginning prior to 201601, the earliest dates for the debit (TC 830) and credit (TC 710) fields is one month past the un-extended due date of the return. Refer to IRM 21.7.4.4.4.2.1, Form 1120 Corporate Series Return Due Dates - Tax Years Beginning after December 31, 2015. Exception: If the transfer is for Form 941-X, Adjusted Employer’s Quarterly Federal Tax Return or Claim for Refund, refer to IRM 21.7.2.4.5.6.1, Form 941-X Tax Decreases - Adjusted Employment Tax Return; if the transfer is for Form CT-1 X, Adjusted Employer’s Annual Railroad Retirement Tax Return or Claim for Refund, refer to IRM 21.7.2.6.5.10.1, Form CT-1X Decreases - Adjusted Employment Tax Return.
Credit elect overpayment transfer consists of a credit or partial credit dated after the due date of the return plus grace period. Refer to IRM 21.5.1.4.2.5, Received Date- Grace Periods.	Transaction date of TC 830 (debit) and TC 710 (credit) is the posting date of the payment. Input separate transfers to accommodate multiple late payments, or when an overpayment is comprised of both timely and late payments/credits. Exception: If the transfer is for a Form 1120 (MFT 02) module with a tax period ending in June, or an MFT 02 tax period beginning prior to 201601, the earliest dates for the debit (TC 830) and credit (TC 710) fields is one month past the un-extended due date of the return. Refer to IRM 21.7.4.4.4.2.1, Form 1120 Corporate Series Return Due Dates - Tax Years Beginning after December 31, 2015. Exception: If the transfer is for Form 94XX employment tax returns, refer to the appropriate section of IRM 21.7.2, Employment and Railroad Tax Returns.

Note: For additional information on determining the availability dates for overpayments refer to IRM 20.2.4.4, Availability Dates for Overpayments.

2. When transferring or reversing an overpayment, the credit must be available before the TC 830 can be used to transfer the credit. BPI "0" must be input on CC ADD48/ADC48/DRT48 credit transfers.

   Exception: If multiple actions (such as ADJ54 adjustment and a credit transfer) are necessary and the correct overpayment is determined, all actions can be input at the same time. Refer to IRM 21.5.8.4.6, Posting Delay Code.

(5) When inputting an adjustment creating a credit and a credit elect at the same time, you must use either a hold code "1" or hold code "2" on your adjustment to prevent an erroneous refund. Refer to IRM 21.4.5, Erroneous Refunds, for additional information. When adjusting a Mixed Entity or ID Theft account, refer to IRM 25.23.4.4, Taxpayer Inquiries Involving Identity Theft. When the credit elect posts to the account (TC 830), the -K freeze is released, and an adjustment notice is sent to the taxpayer. No additional correspondence is needed. Refer to IRM 21.5.2.4.15, Rules on Hold Codes (HC), for more information on using hold codes.

(6) When transferring an Electronic Federal Tax Payment System (EFTPS) payment, input the EFTPS indicator of "1" on CC ADD/ADC24. Refer to IRM 21.5.8.4.7, Avoiding Credit Transfer Unpostables, for additional information. To assist in identifying EFTPS payments, refer to IRM 3.17.277.5.3, EFT Number, for EFTPS number configuration.

(1) CP 62, Notice of Credit Transfer - We Credited Your Account, generates if the “CORRESP–DT” field on CC FRM34 is overlaid. This notice is similar to the Letter 672C, Payment(s) Located and/or Applied. When CC ADD34/ADC34 is used and the credit transfer fully resolves the taxpayer’s inquiry and no other issues were involved, the CP 62 is an adequate response.

(2) Overlay the CORRESP–DT field with the taxpayer contact date (correspondence date/inquiry date) if known. If contact date is unknown, enter the IRS received date. On multiple transfers, a date must be entered in this field for each payment transferred.

(3) A CP 62 is not generated in the same cycle as an adjustment notice. The adjustment notice cannot be suppressed and generates when:

• An adjustment (CC ADJ54) is input, or

• Timely payments are credited to a tax module causing recomputation of posted Failure to File (FTF) and/or Estimated Tax (ES) penalties.

(4) When the CP 62 is not generated, written notification to the taxpayer is necessary, such as Letter 672C, Payment(s) Located and/or Applied.

(5) When inputting IMF credit transfers using DRT24/DRT48, which places the module into debit balance over ≡ ≡ ≡ ≡, CP 60, We Removed a Payment Erroneously Applied to your Account - Balance Due, automatically generates to the taxpayer. In general, the taxpayer receives a CP 60 within four weeks from the date the credit transfer was input. Multiple credit transfers are combined, and the taxpayer receives only one notice.

(1) CP 225, Missing Payment Has Been Applied, generates when CC ADD34/ADC34 is used and the “CORRESP–DT” field on CC FRM34 is overlaid. There are two versions of this notice, complete and partial.

(2) On multiple credit transfers, enter a date in the “CORRESP-DT” field for each payment transferred.

(3) The complete CP 225 notice is similar to the Letter 672C, Payment(s) Located and/or Applied, and fully explains the payment transfer and balance due on the module.

(4) The partial CP 225 notice generates if another adjustment notice, such as the CP 210, Examination (Audit) or Data Processing Tax Adjustment - Balance Due, Overpayment, or Even Balance, or CP 220, Examination (Audit) or Data Processing Tax Adjustment - Balance Due, Overpayment, or Even Balance, is generated in the same cycle The partial CP 225 details the payment transaction and status of account (even balance or overpaid).

(5) Transferring timely credits into a module containing a posted TC 166 (Failure to File penalty), TC 176 (Estimated Tax penalty), TC 186 (Federal Tax Deposit penalty), or TC 276 (Failure to Pay penalty) causes these penalties to recompute and generate an adjustment notice CP 210/CP 220. Other penalties may also recompute but will not generate an adjustment notice.

(6) An incomplete CP 225 and a CP 210/220 generates when:

• A timely payment is transferred into a module AND

• A recomputation of the FTD, FTF, FTP, and/or ES penalties occurs AND

• CC FRM34 is used to transfer the payment(s) with the CORRESP-DT field completed.

(7) When adjusting and transferring credit(s) into the same module using CC FRM34 with no CORRESP-DT, input a posting delay code of one cycle on the adjustment (ADJ54). In three weeks, the taxpayer will receive a notice of adjustment with the correct module balance.

(8) When transferring a misapplied payment, you must check the filing requirements on CC ENMOD to determine if the misapplied payment established the filing requirement. If it did, remove the filing requirement using CC BNCHG or the IAT Tool for CC FRM49. If you are unable to determine if the filing requirement should be removed through IDRS research, request the information from the taxpayer either verbally or in writing.

(9) When inputting credit transfers using DRT24/DRT48 that will place the module into debit balance over ≡ ≡ ≡ ≡, CP 260, An Erroneous Payment Previously Applied to Your Account Has Been Reversed - Balance Due, automatically generates to the taxpayer.

(1) Use a bypass indicator (BPI) "1" or Transaction Code (TC) 570 to override the unpostable condition 305/198. Unpostable condition 305/198 is created when a credit:

• Attempts to post to a full paid module, or

• Is greater than the balance due on the account.

(2) The transaction codes affected by the unpostable condition are:

• IMF - 430, 660, 670, 760

• BMF - 650, 660, 670, 760

(3) The bypass indicator (BPI) field is a mandatory field. Follow the chart below to determine the correct BPI.

(4) Follow the chart below for the debit portion of the transfer:

(5) Do not freeze a credit without a valid reason. The employee inputting the TC 570 must ensure the freeze is released when applicable. If monitoring is needed, prepare an in-house e-4442 and include instructions for the remaining credit so that the -R freeze can be released.

(6) To reverse a TC 570, input TC 571 on CC REQ77 with a posting delay code of one cycle. Refer to IRM 2.4.19, Command Codes REQ77, FRM77 and FRM7A.

(1) Use a posting delay code (PDC) on an adjustment or credit transfer when multiple transactions are required to adjust an account, and some must post in later cycles.

(2) You can use the PDC with all credit transfer formats.

(3) Input CC ADD34/ADC34 with PDC on the debit side only. The credit transaction does not attempt to post until at least one cycle after the debit posts.

(4) On BMF accounts, use PDCs to bypass Unpostable 316 when:

1. Transferring multiple TCs 826 with the same payment date and the computer splits the corresponding credit into multiple TCs 706 causing a money mismatch. Reverse the largest TC 706 first and use PDCs on the remaining TCs 706.

   Reminder: When you are also adjusting an account, use a HC 3 to suppress additional notices to the taxpayer, when using PDCs to cycle the remaining TC(s) 706.

2. Transferring multiple credits or payments with the same payment date and the amounts are equal to, or less than, the posted payment amount. Transfer the largest payment first, then cycle the subsequent payments using PDCs.

(5) The PDC extends the IDRS "PN" status. It does not post with the transaction or appear with the IDRS pending transaction.

(1) To avoid unpostables, use the correct reversal transaction codes and correct dates as applicable. When using CC DRT24, include the EFTPS-ELEC-DPST-IND "1" when the original payment was received through EFTPS. For non-electronic payments, do not include the EFTPS-ELEC-DPST-IND indicator.

(2) Input a bypass indicator (BPI) "1" or TC 570 when transferring payments to an account in zero or credit balance. Follow procedures in IRM 21.5.8.4.5, TC 570 and Bypass Indicator.

(3) Use CC ADD34/ADC34 to transfer EFTPS payments, unless required to use CC ADD24/ADC24. Do all preliminary research to locate EFTPS payments using CC EFTPS before performing a credit transfer. For additional information for this command code refer to IRM 2.3.70, Command Code EFTPS.

(4) Research IDRS for a generated transfer such as TC 666 and TC 667 before reversing the credit elect TC 712 (including re-sequence transactions, Command Code IMFOLQ).

(5) Ensure the account is active. Refer to IRM 21.5.2.4.13, Reinstating Retention Register Accounts, for reinstating retention register accounts.

(6) When a credit transfer is input incorrectly, the same person who input the credit transfer can use the Command Code TERUP the same day to delete the credit transfer. Only the Debit TIN should be deleted; it is not necessary to delete the Credit side since the Debit is the primary and controlling transaction. Refer to IRM 2.4.13, Command Code TERUP.

(7) Do not move payments until they post.