3.30.124. Campus Monitoring Reports

(1) Spreadsheets are titled, IISPMMDD, where "SP" are the first two characters of the Submission Processing Center name, with the exception of Kansas City which will use "KC," and MM and DD are the month and day of the period ending date (Friday's date) of the report.

(2) The heading area on the spreadsheets requires contact Information and telephone number of the individual (and their backup) who can respond to inquiries regarding the II Report.

(3) Use the remarks section to explain any unusual conditions regarding the report.

(4) Use the Excel spreadsheet format provided to all Submission Processing Centers that process IMF tax returns or are responsible for Director's Accountability of a consolidated Submission Processing Center whose Access and Location Number (ALN) is still used for electronic filing.

1. Use Excel formulae, macros, ranges, etc., as necessary to facilitate the preparation of the report and to minimize errors.

2. Items that are blue are for user entry.

3. Items that are green contain formulae and are not for user entry.

4. Items that turn red with a gray background and blue border indicate that a mathematical or logical inconsistency exists.

(1) Include PRIOR CUM on every report, January - December.

1. Copy, exactly, the contents of the prior week's cumulative report. For the first report in January (January 06 for 2023), the PRIOR CUM column should be zero.

2. The use of a macro or formulae to copy automatically the prior week's data is recommended to prevent errors.

3. Do not carry over inventory from the prior year into the PRIOR CUM column.

4. For those Program Numbers that do not apply to a specific Submission Processing Center, enter zero.

(2) Include ADJUSTMENTS, whenever appropriate, on any report, January - December.

1. If an adjustment is not for the preceding week, provide details of the adjustment in the remarks section of the spreadsheet. Show the week(s) affected, function and program codes and volumes (e.g.,02/04/2023; 110; 43110; +5,123).

2. Adjustments are not appropriate on the first report of the calendar year.

3. Sources include the Daily Production Report, the Block Proof Summary Report, the Batch/Block Tracking System (BBTS), and the Pipeline Inventory Monitoring System (PIMS).

Example: On the first working day of each week, run a Function Volume PIMS Report for Function 110 for each Parent Program Number, using a date range of the first day of the calendar year through the preceding Friday. Compare that with the results from the previous week. On May 15, 2023, for example, from the Function Volume Report calculate the cumulative Function 110 receipts through May 05, 2023. Compare that volume to the volume found for May 05, 2023, when the query was performed on May 8, 2023. The difference would be the adjustment attributable to prior weeks. The PIMS Monitoring Report can also be used, and may be an easier method because this report provided a running adjusted cumulative volume for each day which the Function Volume Report does not provide.

4. By definition, Full-Paid returns are filed timely (i.e., current year returns received or postmarked on or before the due date). After the report for the week (April 24 in 2023) that contains April 22nd, any change from PRIOR CUM to NEW CUM for Function 110 must be reflected in the ADJ column and not in the PERIOD column for Full-Paid Program Numbers.

5. For those Program Numbers that do not apply to a specific Submission Processing Center, enter zero.

(3) Include PERIOD on all reports. The period figures are the sum of the adjusted daily figures. Although one can determine each of the adjusted daily figures, it is easier to compare current cum to prior cum, factoring in adjustments. Thus, the template uses the following formula for PERIOD: NEW CUM minus PRIOR CUM minus ADJ.

1. Carry over inventory from the prior year should be reflected in the PERIOD column of the first report of the calendar year. Thus, for the first week's report the PERIOD column should be the same as the NEW CUM column.

2. After the report for the week (April 24 in 2023) that contains April 22nd, the PERIOD column for Full-Paid Program Numbers in the Function 110 section for the rest of the calendar year must be zero.

3. For those Program Numbers that do not apply to a specific Submission Processing Center, enter zero.

(4) Include NEW CUM on all reports.

1. For all returns, the section is labeled Function 110. For paper however, it should reflect processable receipts (i.e., those receipts that can eventually result in a Good Tape transaction). Thus, using the Daily Production Report (DPR), it is Function 180 cumulative production + Function 180 closing inventory (use zero if negative) - Function 940 cumulative receipts - Function 960 cumulative production - Function 970 cumulative production.

Note: If for some reason the DPR for Friday does not include certain estimated volumes received through Friday, those unreported estimates should be added to the results from the instructions immediately above.

2. For electronically filed returns, as a double-check, the Cum Conversion Volume from the Balance Forward Listing for Friday should equal NEW CUM for Function 110.

3. For paper returns, the source for NEW CUM for Function 950 is the Balance Forward Listing for Friday.

4. The source for NEW CUM for Function 950 is the Balance Forward Listing for Friday.

5. For all Program Numbers, the NEW CUM for Function 950 may not be greater than the NEW CUM for Function 110.

6. For those Program Numbers that do not apply to a specific Submission Processing Center, enter zero.

(5) The information in the "THRU 4/22" column is used in the May OTFP Program Completion Date (PCD) computation.

1. Report the cumulative number of Other-Than-Full-Paid (OTFP) returns (including adjustments) received up to and including April 22nd. The cumulative figure should include the volumes reported as No-Refund Sort Returns. See IRM 3.30.124.2.2.5.

2. Report this information beginning no later than the week (April 24, 2023) that includes April 22nd, and continue for each week through the end of the calendar year.

3. The initial source to use is the Daily Production Report, augmented as necessary with estimates based on current receipts, schedule, etc. Updates for subsequent weeks can be made using BBTS queries, PIMS, etc. Again, the cumulative figure should include the volumes reported as No-Refund Sort Returns. See IRM 3.30.124.2.2.5.

4. After the IMF OTFP Refund PCD, the best data source is the cumulative receipts in PIMS through April 20th less the volumes for Functions 940 and 960 as of the OTFP Refund PCD.

5. For those Program Numbers that do not apply to a specific Submission Processing Center, enter zero.

(1) Report extensions received based on the Daily Production Report for Program Codes 44700, 44720, 44730, and 44750; volumes from the Form 4868 Volume and Money report from Integrated Submission and Remittance Processing (ISRP); and the volumes provided by the Campus Lockbox Coordinator.

(2) Report extensions for each week for the entire year.

(3) Report both weekly and cumulative receipts.

(1) Compute the current operating number of days in cycle by determining the date on which the current cumulative number of returns Processed (Function 950) most closely approximated the number of returns received and counting the non-holiday Monday through Friday days between the two and adding one day each for the Functions 110 and 950 days. Use the Daily Production Report updated with BBTS queries and/or PIMS reports to obtain the information.

(2) Report operating number of days in cycle for each week beginning in January through the report (April 24 in 2023) that includes April 22nd.

(3) For those Program Numbers that do not apply to a specific Submission Processing Center, enter zero.

(1) The information on No-Refund Sort Returns is used in the PCD computation.

1. Report the inventory of No-Refund Sort Returns by Parent Program Number.

2. Report this information beginning no later than with the week's report (April 24 in 2023) that contains April 22nd through the week that contains the IMF Other Than Full Paid (OTFP) Refund PCD.

3. The source documents used for determining No-Refund Sort Returns are the Daily Production Report and/or the Batch Profile Report. This may be updated with BBTS queries or PIMS reports.

(2) The phrase "No-Refund Sort Returns" refers to the number of no-refund sorted OTFP returns that have not yet been transcribed.

1. Beginning with the week that contains April 22nd through the Friday before the OTFP IMF Refund PCD (weeks ending April 29- May 12, 2023), report the not yet transcribed inventories.

2. For the week (May 22 in 2023) that contains the OTFP IMF Refund PCD, (PCD is May 17) repeat the volumes reported the week before.

3. For the weeks beginning with the week (May 29 in 2023) following the OTFP IMF Refund PCD through the last report for the calendar year, report zero.

Note: Do not exclude the volumes reported as No-Refund Sort Returns from the cumulative receipt figure (Function 110) or the "thru 4/20" column. See IRM 3.30.124.2.2.2

(1) Report the inventory of timely filed OTFP returns in inventories as Error Resolution System (ERS) and Blocks Out of Balance (BOB) beginning the first week after the week which includes April 22nd, and continuing weekly through the week that includes PCD plus two weeks after PCD. For 2023, the first report would be for May 05 and the last report would be for June 02.

1. Source for the ERS inventory is the IMF Interest Jeopardy Report (ERS-17-46). Report document count from the line titled "Total ERS IMF Refund Returns For PCD Purposes."

2. Source for the BOB Inventory is Generalized Mainframe Framework (GMF) 94-40, PCD Monitoring List. Report the document count from the heading "BOB Inventory BOB Summary Number of Refund Docs."

(1) Maintain separate reports for receipts for the current year, the prior year, and the succeeding year.

(2) Receipts are to be reported as ISRP, Processable and Non-Processable. A Total column, by document type, will also be maintained. Receipts will be reported as follows:

1. Column 1 - Scannable/No entry is required.

2. Column 2 - Non-Scannable/No entry is required.

3. Column 3 - ISRP/Enter receipts of non-Optical Character Recognition (OCR) forms, excluding Schedules K-1 and OCR forms assigned for ISRP input.

4. Column 4 - Processable/Enter the processable portion of amount in column 3.

5. Column 5 - Non-Processable/Enter the number of forms that cannot be processed at all because the information is unclear, indecipherable or the utility of the form is minimized or eliminated (A.K.A. Unprocessable). This count should not include those receipts deemed temporarily non-processable which have had correspondence issued. This count should include only those receipts where correspondence was unable to secure processable returns.

6. Column 6 - Total/Enter the sum of Columns 4 and 5 for the total forms received.

(3) These counts are to be determined during the Function 140 sorting and should be verifiable with the information reported on the Work Planning & Control (WP&C) data for Function 140. Receipts that are deemed temporarily non-processable should be counted as processable or non-processable based on the payer's reply to correspondence. DO NOT count the temporarily non-processable documents being replaced. Any adjustments made to the WP&C data should also be reflected in this report.

(4) For Schedule K-1, enter the estimated count of the cumulative number received for each type of return (i.e., Form 1041, Form 1065 or Form 1120-S). These counts are to be maintained by the IRP Coordinator. Derive the counts by multiplying the number of Business Master File (BMF) returns received by the following average number of Schedules K-1 per return (round all counts to whole numbers):

1. Form 1041,, U.S. Income Tax Return for Estates and Trusts

2. Form 1065,,U.S. Return of Partnership Income

3. Form 1120-S,, U.S. Income Tax Returns for an S Corporation

(1) The Assigned for SCRIPS column does not require an entry.

(2) The Manually Assigned for ISRP count will be a CUMULATIVE count by document type of the number of information returns manually assigned Document Locator Numbers (DLN) by the Numbering Function.

(1) Shipped/Enter the number of returns shipped to another site. Enter the actual number if available, otherwise enter an estimate.

(2) Received/Enter the number of returns received from another site. Enter the actual number when available.

(3) To Site/Identify the campus to which shipments were sent, or from which shipments were received.

(1) The entries under Total Identified to Date will be CUMULATIVE totals based on the following:

1. "Manually Assigned for ISRP." Entry for Form 1097 series, Form 1098 series, Form 1099 series, Form 3921, Form 3922 and Form W2-G, will be based on the total combinations of those counts from entries under Section I.B, “Manually Assigned for ISRP.”

2. Entry for 1096 will be based on the CUMULATIVE count of Form 1096, Annual Summary and Transmittal of U.S. Information Returns manually assigned DLNs by the Numbering Function.

3. Entry for Schedule K-1 will be obtained by adding K-1 totals forForm 1041, Form 1065 and Form 1120-S as shown under Section I.B, "Manually Assigned for ISRP."

4. Entry for Foreign Information Returns Processing ("FIRP") will be CUMULATIVE count for FIRP documents manually numbered by the Numbering Function.

5. Entry for "Total" is combination of entries for a through d above.

6. Entries for "Total Processed to Date" is CUMULATIVE count of documents after entry through ISRP.

(1) Enter the CUMULATIVE count of information returns shipped to ECC-MTB categories specified. These counts may be obtained from Program/Run/Files PCD-03-40, IRP Block Proof Summary and Error Analysis, or PCD-03-44, Balance Forward Listing.

1. The entry for Information Return Processing will be based on the total of Cum Good Transactions entries for IRP Program number 44300.

2. The entry for "K-1" is the count shown for IRP Program number 44380.

3. The entry for "FIRP (PSPC only)" is the count shown for IRP Program 44320.

(1) No entry is required.

(1) Enter the estimated number of foreign information returns received and sorted. Also check the appropriate box to indicate whether receipts are on schedule or behind. If behind schedule, provide the estimated volume of receipts behind schedule.

(2) Enter the actual number of foreign information returns selected and numbered.

1. These counts will be maintained by the Numbering Function.

2. Counts for matchable returns will be maintained by type of return, TIN, no-TIN, IMF and BMF.

3. Counts for non-matchable returns will be maintained by TIN and No-TIN.

(1) Letter 1865C, (SC), or (SC) issued (actual).

(2) Letter 1865C, (SC), or (SC) replies received (actual).

(3) Letter 1306C or (SC) issued (actual).

(4) Problems resolved by telephone.

(5) Prior year receipts received.

(6) Other correspondence received (with taxpayers - actual).

(7) Letters issued (actual) for missing Schedule K-1 (1041).

(8) Letters issued (actual) for missing Schedule K-1 (1065).

(9) Letters issued (actual) for missing Schedule K-1 (1120S).

(10) Q-Notes issued.

(1) Spreadsheets are titled Miscellaneous Inventory Report Submission Processing (MIRSP), where "SP" are the first two characters of the Submission Processing Center name, with the exception of Kansas City which will use "KC."

(2) The heading area on the spreadsheet requires Contact Information and telephone number for the primary and back-up individuals who can respond to inquiries regarding the Report.

(3) The week ending date will always be Friday.

(1) The ERS section includes information on Workable, Pending/Unloaded, Overflow, and Day 5 and older inventories.

(2) The categories listed are IMF, BMF, and Total IMF and BMF.

(3) Beginning Workable Inventory - The Closing Workable Inventory for IMF and BMF ERS from the previous week's MIR Report.

(4) Weekly Receipts -The Weekly Receipts figure will be the sum of the daily ERS-13-41 figures, beginning with the report generated on or after Sunday night/Monday morning and ending with the report generated on or before Saturday night/Sunday morning. For a normal Monday to Friday work week, the ERS-13-41 reports to use for weekly reporting on the MIR Report will have Monday through Friday dates (e.g., 2023-03-06 through 2023-03-10).

Note: Do not report any Weekly Receipts for IRP, EPMF, or NMF.

1. For each of the IMF and BMF (master file, separately), use the "Total Error Records" item from the ERS-13-41 report, for "Days in Inventory = 0" only.

2. This figure will comprise the sum of up to 7 daily ERS-13-41 totals.

(5) Weekly Closures: Computed as Beginning Inventory + Weekly Receipts - Closing Inventory.

(6) Closing Workable Inventory is the current ERS inventory at the beginning of business Saturday morning (Sunday morning if the ERS runstream is performed Saturday night/Sunday morning).

Note: Do not report any Closing Workable Inventory for IRP, EPMF, or NMF.

1. For each of the IMF and BMF master files, separately, the figure reported will be the sum of the total error records line for each "days in inventory" page from the ERS-13-41, Error Resolution Error Inventory Summary.

2. If there is no ERS runstream performed Saturday night/Sunday morning, the ERS-13-41 report generated Friday night/Saturday morning will be used.

3. If there is an ERS runstream performed Saturday night/Sunday morning, the ERS-13-41 report generated Saturday night/Sunday morning will be used.

4. If there is an ERS runstream performed Sunday night/Monday morning, that ERS-13-41 report will not be used. Follow the instructions in b) or c) above, as appropriate.

(7) Pending/Unloaded Inventory - Pending/Unloaded (IMF and BMF) is inventory that was available to be loaded to ERS "yesterday" but was not selected to be loaded to ERS.

1. The figure reported will be the figure from the ERS-03-40, Error Resolution Unselected Records Inventory, "Grand Total Error Records" item.

2. If there is no ERS runstream performed Saturday night/Sunday morning, the ERS-03-40 report generated Friday night/Saturday morning will be used.

3. If there is an ERS runstream performed Saturday night/Sunday morning, the ERS-03-40 report generated Saturday night/Sunday morning will be used.

4. If there is an ERS runstream performed Sunday night/Monday morning, that ERS-03-40 report will not be used. Follow the instructions in b) or c) above, as appropriate.

(8) Current Overflow Inventory is the inventory from the Overflow file, a condition that only occurs when the number of ERS records ordered for processing causes the ERS database to exceed preset limits. (The ERS-13-41 plus the ERS-13-42, Error Resolution Workable Suspense Inventory, plus the Quality Assurance held records, comprise the inventory on the ERS database.)

1. The figure reported will be the figure from the ERS-13-49, ERS 13 Run Control Sheet, ERS DB "Overflow Records" item.

2. If there is no ERS runstream performed Saturday night/Sunday morning, the ERS-13-49 report generated Friday night/Saturday morning will be used.

3. If there is an ERS runstream performed Saturday night/Sunday morning, the ERS-13-49 report generated Saturday night/Sunday morning will be used.

4. If there is an ERS runstream performed Sunday night/Monday morning, that ERS-13-49 report will not be used. Follow the instructions in b) or c) above, as appropriate.

5. If an ERS database overflow condition exists at any time during the week, address the situation in the Comments portion of your weekly Miscellaneous Inventory Report.

(9) Total Error Inventory is the sum of Closing Workable Inventory, Pending/Unloaded Inventory, and Current Overflow Inventory at the beginning of Saturday morning (Sunday morning if the ERS runstream is performed Saturday night/Sunday morning). The figure reported should be the sum of items 6, 7, and 8 above.

(10) Total Day 5 or Older - The current ERS inventory at the beginning of business Saturday morning (Sunday morning if the ERS runstream is performed Saturday night/Sunday morning), which have been in inventory for more than three days.

1. For each of the IMF and BMF master files, separately, the figure reported will be the sum of the total error records line for each page where the "days in inventory" number is "5" or higher from the ERS-13-41, Error Resolution Error Inventory Summary.

2. If there is no ERS runstream performed Saturday night/Sunday morning, the ERS-13-41 report generated Friday night/Saturday morning will be used.

3. If there is an ERS runstream performed Saturday night/Sunday morning, the ERS-13-41 report generated Saturday night/Sunday morning will be used.

4. If there is an ERS runstream performed Sunday night/Monday morning, that ERS-13-41 report will not be used. Follow the instructions in b) or c) above, as appropriate.

(11) Comments are to be provided for any fluctuations in inventory levels, differences in sources data, and any changes that have impact on the inventories.

(1) The Rejects Inventory includes paper registers and workable/unworkable suspense records, and is reported weekly with Friday as the normal cut-off date.

1. If there is no ERS runstream performed Saturday night/Sunday morning, the ERS reports generated Friday night/Saturday morning will be used as the cut-off.

2. If there is an ERS runstream performed Saturday night/Sunday morning, the ERS reports generated Saturday night/Sunday morning will be used as the cut-off.

3. If there is an ERS runstream performed Sunday night/Monday morning, those ERS reports will not be used as the cut-off. Follow the instructions in a) or b) above, as appropriate.

(2) The categories listed are IMF, BMF, and Total IMF and BMF.

(3) Beginning Inventory - The Closing Inventory from the previous week's MIR Report.

(4) Weekly Receipts are from GMF-11-40, Reject Display Run Print File, GMF-11-43, Reject Inventory List, or GMF-11-45, Reject Register Summary for paper registers; ERS-17-40, Error Resolution New Suspense List (which shows everything coming into Rejects - both workable and unworkable). In addition, ERS-17-48, Error Resolution New Suspense List Summary, provides the receipt totals by program number.

(5) Weekly Closures: Computed as Beginning Inventory + Weekly Receipts - Closing Inventory.

(6) Closing Inventory is from GMF-11-40, Reject Display Run Print File, GMF-11-43, Reject Inventory List, or GMF-11-45, Reject Register Summary for paper registers; ERS-07-41, Error Resolution Unworkable Suspense Summary, and ERS-13-43, Error Resolution Workable Suspense Inventory Summary (verify by using ERS-17-47, Error Resolution Inventory Control report).

(7) Early Filed Inventory is the portion of Closing Inventory which cannot be worked (and must be held in inventory) until the tax period ending date.

(8) ERS Unworkable Suspense Portion is from ERS-07-41, Unworkable Error Resolution Suspense Inventory Listing.

(9) ERS Workable Suspense Portion is from ERS-13-43, Error Resolution Workable Suspense Inventory Summary.

(10) SCRS Suspense Portion is from GMF-11-43, Reject Inventory List.

(11) ERS Aged is from ERS-31-40, Error Resolution Unworkable Suspense Aged Report and ERS-31-41, Error Resolution Workable Suspense Report.

(12) SCRS Aged is from GMF-11-42, BMF Reject Aged List.

(13) Total Early Filed >= 120 is from ERS-31-40, Error Resolution Unworkable Suspense Aged Report and ERS-31-41, Error Resolution Workable Suspense Report.

(14) Comments are to be provided for any fluctuations in inventory levels, cases 120 days or older, differences in sources data, and any changes that have impact on the inventories, counts for International correspondence, which is aged before suspense time expires, and counts for programming problems when advised by HQ.

(1) All data MUST be extracted from Generalized Unpostable Framework (GUF) reports: GUF-53-40, Unpostable Control Report, GUF-53-41, Unpostable Workload Report and GUF-55-40, Employee Assigned Age List, GUF 55-42 Unpostable Employee Assignment/Aged Summary. No internal or local inventory reports should be used in lieu of the above-mentioned GUF reports when preparing this inventory report.

(2) Cycle - This should be changed each week (including the Dead Cycles) and should correspond to the ECC-MTB Posting Cycle of the week ending date. The format is YYYYNN.

(3) Beginning Inventory - This should match the Closing Inventory for Unpostables from the previous week's MIR Report.

1. During Dead Cycles, for each master file, separately, repeat the Closing Inventory from the last cycle of the previous year. Dead Cycles for BMF are cycles 01 and 02 each year. For IMF, the Dead Cycles are cycles 01, 02, and 03 each year.

2. When Beginning Inventory does not match Closing Inventory for the previous week's MIR Report, comments are to be provided to explain the differences.

(4) Current Receipts; Transfers-In; Closed This Week; Transfers-Out; Current Ending Inventory; Aged Inventory; Subsequent Closing Total; and Workable Inventory should all come directly from GUF-53-41.

1. For each workload category (Criminal Investigation, Entity Control, Examination, Statutes, Unpostable Function, Employee Plans Master File (EPMF) Entity, Exempt Organization, and Return Integrity & Verification Office (RIVO) of Return Integrity and Compliance Services (RICS), and Appeals, Beginning Inventory plus Receipts plus Transfers-In less Transfers-Out less Closures should equal Closing Inventory.

2. For the All Combined summary, for each master file, separately, the volume for Transfers-In must equal the volume for Transfers-Out.

3. During Dead Cycles, for each master file, separately, enter zero for Receipts; Transfers-In; Transfers-Out; and Closures. Also, during Dead cycles, for each master file, separately, for Aged Inventory, Subsequent Closing Total, and Workable Inventory repeat the volumes for the last Live Cycle.

Exception: During the week, when there are multiple GUF-53-41 reports for multiple cycles, the data for some entries will need to be combined for all cycles for that week, so that the ending inventory matches the ending inventory from the most recent cycles’ GUF-53-41 report. Data should be combined for the following entries: current receipts, transfers- in, closed this week, and transfers-out. For the aged inventory, subsequent closing total and workable inventory, that data should come from and match the most recent cycles’ GUF-53-41 report.

(5) Closing Inventory - The template contains formulae which calculate the Closing Inventory as follows: Beginning Inventory + Receipts + Transfers-In - Transfers-Out - Closures. During Dead Cycles, for each master file, separately, the Closing Inventory should equal the Beginning Inventory. Since Closing Inventories on the template are calculated, compare the Closing Inventories on the template with the Closing Inventories found in the GUF-53-41. They should match. If the figures do not match:

1. Check for transcription errors and correct any found.

2. Check for out of balance messages in the GUF-53-41. If found, leave the calculated figures in the template and note the out of balance message(s) in the comments section.

3. Re-check last week's Closing Inventory against last week's GUF-53-41 for unnoticed imbalance. If found, contact the MIR Analyst and enter a note in the comments section.

4. Add a note to the comments section when none of the three items above apply.

(6) Aged - 15 cycles or less aged and Unacceptably Aged - 15 cycles or more aged - For each Submission Processing Unpostable functional area (Unpostables, Exempt Organization, Entity Control, and EPMF Entity), enter the number of items, for each aged range separately, that are less than 15 cycles overage, as well as those 15 cycles or more aged. The source report is the GUF-55-42,

(7) Comments are to be provided for any fluctuation in inventory levels, differences in sources data, and any changes that have impact on the inventories.

(1) Entity information can be obtained from the Entity Batch Tracking module in the Batch/Block Tracking System (BBTS), or by physical count if BBTS is not operational.

(2) The broad categories listed are IMF, BMF, EO, and EPMF. Each of the broad categories contains individual rows for item breakdown that coincide with categories in BBTS. If a new category is added to BBTS, combine it with the appropriate "Other" row until a new MIR template is issued.

(3) Beginning Inventory must equal the ending inventory of the prior week. If not, state the reason in the Entity Comments portion of your Miscellaneous Inventory Report.

(4) Adjustment - The amount (positive or negative) by which the Closing Inventory from the previous week was incorrect.

(5) Weekly Receipts - All receipts must be reported (added to inventory) when received. Receipts should NOT be added to inventory when the case becomes workable. When receipts are received in the campus via tape or disk, it should be included in inventory within one week.

(6) Weekly Closures, Closing Inventory, and Overaged should come directly from BBTS.

(7) Comments are to be provided for any fluctuations in inventory levels, differences in sources of data, and any changes that have impact on the inventories. Those significant changes or unmanageable inventories (i.e., exceed the 5% or 20% guidelines) will require explanations by the campus. The boiling point threshold is 30%.

1. Comments should explain the change and the reason for the unmanageable condition.

2. Comments should provide the actions that will be (or were) taken to correct the unmanageable condition.

3. Submission Processing Centers should be able to provide this data within ONE DAY of receiving a telephone call from the National Office.

(1) Submission Processing Centers are to report all BOB inventory, including BOB Code "Ps".

(2) Beginning Inventory - The Closing Inventory for IMF and BMF BOB from the previous week's MIR Report.

(3) Weekly Receipts - The receipts figure will be the sum of the daily GMF-09-03, Block-Out-of-Balance ID List, figures, beginning with the first report generated on or after Friday night/Saturday morning and ending with the last report generated on or before Thursday night/Friday morning.

1. For each of the IMF and BMF master files, separately, use the "Total Today's New BOB" plus Total ReBOBsfor Blocks and "Total Computer Count" for Documents.

2. This figure will comprise the sum of up to 7 daily GMF-09-45 totals.

(4) Weekly Closures - The closure figure will be the sum of the daily GMF-09-03, BOB Correction Control List, figures, beginning with the report generated on or after Saturday night/Sunday morning and ending with the report generated on or before Friday night/Saturday morning.

1. For each of the IMF and BMF master files, separately, use the "Number of Blocks" for Matched Block DLN plus Number of Blocksfor Deleted Block DLN for Blocks and "Old Computer Doc Count" for Matched Block DLN plusOld Computer Doc Count for Deleted Block DLN for Documents.

2. This figure will comprise the sum of up to 7 daily GMF-09-46 totals.

   Note: To filter for the GMF-09-03 in Control-D, input GMF-09-03 in the Job Name field with the corresponding letter for the appropriate site (Austin - GMF-09-03C, Ogden - GMF-09-03I, Kansas City - GMF-09-03G).

(5) Closing Inventory is the current BOB inventory at the beginning of business Saturday morning.

1. Using the last daily GMF-09-03, BOB Correction Control list, for each of the IMF and BMF master files, separately, use the "Number of Blocks" item for Non-Matched Block DLN for Blocks and "Old Computer Doc Count" item for Non-Matched Block DLN for Documents.

2. It is unlikely that this figure will repeatedly be zero.

(6) Current Inventory <= 2 Weeks is the current BOB inventory at the beginning of business Saturday morning that is less than or equal to two weeks old. For each of the IMF and BMF master files, separately, for each row that has a Non-Matched Block DLN, compare the Julian Date column to the current Julian Date to determine the number of Blocks and Documents where the comparison is 14 days or less.

(7) Current Inventory > 2 Weeks is the current BOB inventory at the beginning of business Saturday morning that is greater than two weeks old. For each of the IMF and BMF master files, separately, for each row that has a Non-Matched Block DLN, compare the Julian Date column to the current Julian Date to determine the number of Blocks and Documents where the comparison is greater than 14 days.

(8) Comments are to be provided for any fluctuation in inventory levels, differences in sources of data, and any changes that have impact on the inventories.

(1) The SCCF section includes information on the number of documents and money amounts in aged inventory. These figures are reported, separately, by master file. The money amounts should be reported in dollars and cents. Inventory of items and money amounts are from SCF-07-52, SCCF Aged Summary.

(2) The MISTLE line at the bottom of the Total SCCF Aged Summary contains all of the following information required for reporting:

• Items Aged 1-3 Months

• Items Aged 4 Months

• Items Aged 5 or more Months

(3) Having items in the 1 to 3 Months category is normal. Routinely having items in the 4 Month category is an indication of insufficient attention or of a lack of urgency in getting cases resolved. Having items in the 5 or more Months category is considered unacceptable.

(4) Any item reported in the 4 and 5 or more months category require an explanation in the comments section. Annotate the SCCF Aged Lists with detailed explanations.

1. If the case will be closed before the next report is due, notate closed by and put the expected closing date.

2. If not, identify what form is it, what is the problem, and what is being done to resolve the issue? For example: missing return, special search requested on MM/DD//YY.

3. To save time for identical remarks, you can use ditto marks or vertical lines.

4. Rejects will provide an annotated report to the Data Control Unit in Accounting for items they are working. For additional information refer to "Researching the SCCF Aged List" in IRM 3.12.37.44.3.1 and/or IRM 3.12.38.5.3.3.1.

(5) Early Filed Returns Aged 5 or more Months - For each master file, separately list the number of items and money amounts for items SCCF Aged 5 or more months, which cannot yet be worked because they are early filed returns.

(6) Comments are to be provided for any fluctuation in inventory levels, differences in sources of data, and any changes that have impact on the inventories.

(1) The DCF section includes information on the number of documents and money amounts in inventory. The money amounts should be reported in dollars and cents. The data sources are the sections titled "Service Center Total" in the daily DCF-01-40 and monthly DCF-50-40.

(2) There are two sub-sections for DCF:

1. Weekly Reporting for DCF is by cycle which normally runs Thursday through Wednesday. Reporting this weekly information is required during the months of March, April, and May. It is optional to report this information during the other nine months.

2. Monthly Reporting which is reported on a calendar month basis.

Note: Although the data will change only once per month, the report for the last full month should be included (and should be identical) in each weekly MIR Report. Usually the monthly data will change on a report for the first Friday of the new month. However, the data will change on the report for the last Friday of the old month when that Friday is the last working day of the month. That is, when a month ends on a Saturday, Sunday, or a holiday Monday, report the new monthly data on the MIR Report for the preceding Friday. For example, in 2023, begin reporting the monthly information for March with the report for week ending March 31, 2023. In 2023, this last Friday of the month reporting occurs in the months of March, April, June, September and December.

Note: When a month ends on a Monday, that is not a holiday, do not report the new monthly data on the MIR Report for the preceding Friday.

(3) Prior Balance - For the Weekly Report, this is the New DCF Balance from the previous week's MIR Report. For the Monthly Report:

1. If it is not the week to enter the information for the new month, this is the Prior Balance from the previous week's MIR Report.

2. If this is the week to enter the information for the new month, this is the New DCF Balance from the previous week's MIR Report.

(4) New Accounts Added; Increased Amounts; Accounts Closed; Partial Applications; Unproc Write-Off to the 1510 Account; Voided Accounts; Partial Voided Accounts; Decreased Amounts; and Unidentified Checks.

1. For the Monthly Report, for each of these categories, it is the value reflected for the corresponding line from the Monthly DCF-50-40.

2. For the Weekly Report, when the last two Thursdays fall in the same month, for each of these categories, use the current week's (Thursday date) DCF-01-40. Subtract the previous week's (Thursday date) totals from the current week's totals, which will represent the activity for the current week.

3. For the Weekly Report, when the second previous Thursday was the last work day (non-holiday Monday through Friday) of the month, use the data from the current week's (Thursday date) DCF-01-40.

4. For the Weekly Report, when the last two Thursdays fall in different months and the second previous Thursday was not the last work day of the month, start with the DCF-01-40 for the last day of the month and subtract the previous week (Thursday date) totals. This will represent the portion of the current week activity which took place last month. The totals on the most recent Thursday’s DCF-01-40 will represent the portion of the current week's activity which took place in the new month. Add the two results together.

(5) New DCF Balance - For both the weekly and the monthly reports, it is the value reflected on the last report of the reporting period.

(6) Aged Inventory - Shall be reported and submitted as described in IRM 3.17.10, at Revenue Receipts IRM 3.17.10.2.22(3).

1. For the weekly report, for each category, use the DCF-09-40. Sort aged items into two categories: 22-65 Days and 66 Days or more. For each of the two categories, sum the money amounts and the item counts separately.

2. For the monthly report, use the DCF-09-40 dated the last work day of the month. Sort Aged items into two categories: 22-65 Days and 66 Days or more. For each of the two categories, sum the money amounts and the item counts separately.

(7) Comments are to be provided for any fluctuation in inventory levels, differences in sources of data, and any changes that have impact on the inventories.

(1) The XSF section is only to be updated monthly. The MONTHLY Excess Collection File Analysis - which is part of the MONTHLY Unidentified Remittance File Analysis Report (URF-01-15) - should be used as the source data for input. Do not use the Daily file which only says "Unidentified Remittance File Analysis Report." The Excess Collection section of the Miscellaneous Inventory Report includes information on the number of documents and money amounts in inventory. The money amounts should be reported in dollars and cents. The data should be entered from the "Service Center Totals" portion of the Monthly Excess Collection File Analysis report.

(2) There are two sub-sections in the Miscellaneous Inventory Report for XSF:

• Monthly Excess Collection 6800 File Analysis.

• Monthly Excess Collection 9999 File Analysis.

Note: Although the data will change only once per month, the report for the last full month should be included (and should be identical) in each weekly MIR Report. Usually the monthly data will change on the report for the first Friday of the new month. However, the data will change on the report for the last Friday of the old month when that Friday is the last working day of the month. That is, when a month ends on a Saturday or Sunday, or a holiday Monday, report the new monthly data on the MIR Report for the preceding Friday. For example, in 2023, begin reporting the monthly information for March with the report for week ending March 31, 2023. In 2023, this last Friday of the month reporting occurs in the months of March, April , June,September and December.

Note: When a month ends on a Monday, that is not a holiday, do not report the new monthly data on the MIR Report for the preceding Friday.

(3) Prior Balance

1. If it is not the week to enter the information for the new month, this is the Prior Balance from the previous week's MIR Report.

2. If this is the week to enter the information for the new month, this is the New XSF (6800 or 9999 as appropriate) Balance from the previous week's MIR Report.

Note: For the XSF 6800 for month ending October 31, the Prior Balances will appear on the URF-01-15 as Count 0 and Amount $0.00. Rather than using those values, use the New XSF 6800 Balance from month ending September 30. We will address the transfer of those values to XSF 9999 in (5) and (6) below.

(4) New Accounts Added; URF Accounts Added; Statute Expired Cases Added; Increased Amounts; Accounts Closed; Partial Application; Open Accounts Dropped; Voided Accounts; and Decreased Amounts.

(5) For XSF 6800 - Transfer to 9999 Accounts - 10/31 Only. This row does not appear on the Monthly URF-01-15 for XSF 6800. Enter data on this line only for month ending October 31. Enter the new XSF 6800 Balance from month ending September 30. The values entered must be the same as what appears in (6) below.

(6) For XSF 9999 - 6800 Accounts Added - 10/31 Only. This row does appear on the Monthly URF-01-15 for XSF 9999. However, this row only appears on the report for month ending October 31. Enter the values found on the URF-01-15. The values entered must be the same as what appears in (5) above and must match the New XSF 6800 Balance from month ending September 30.

(7) New XSF (6800 or 9999 as appropriate) Balance - For each of the two files, it is the value reflected for the corresponding line for the appropriate section of the URF-01-15.

(8) Comments are to be provided for any fluctuation in inventory levels; differences in sources of data, and any changes that impact the inventories.

(1) The Unidentified Remittance section includes information on the number of documents and money amounts in inventory. The money amounts should be reported in dollars and cents.

(2) Beginning Inventory - The Closing Inventory (count and amount) from the previous week's MIR Report.

(3) Weekly Receipts - Subtract the total of New Accounts Added and Increased Amounts of the immediately prior week’s Friday work daily URF-01-15/URF Analysis (Service Center Totals) from corresponding fields of the current week’s Friday work daily URF-01-15/URF Analysis (Service Center Totals).

(4) Weekly Closures - Subtract the total of Accounts Closed, Partial Application, Closed Excess Collection, Dishonored Checks, Voided Accounts and Decreased Amounts of the immediately prior week’s Friday work daily URF-01/URF Analysis (Service Center Totals) from corresponding fields of the current week’s Friday work daily URF-01/URF Analysis (Service Center Totals).

(5) Closing Inventory - The Count and Amount columns for the New URF Balance row from the final URF-01-15 Service Center Totals. Mathematically, the Closing Inventory should equal Beginning Inventory + Weekly Receipts - Weekly Closures. If not, first verify the input for accuracy and mathematical correctness. If no errors are found, explain the source of the mathematical inconsistency in the Unidentified Remittance Comments portion of your weekly Miscellaneous Inventory Report.

(6) Comments are to be provided for any fluctuation in inventory levels, differences in sources of data, and any changes that have Impact on the inventories.

(1) The Manual Refunds section includes information on the inventories worked by Submission Processing.

(2) This inventory will be reported showing the volumes submitted by each Business Operating Division (BOD) and will include the volumes for Form 5792Request for IDRS Generated Refund (IGR), and , Form 3753, Manual Refund Posting Voucher.

(3) Beginning Inventory - This will be the previous week's Closing Inventory.

(4) Adjustments - This column represents the volume by which the Closing Inventory from the previous week was incorrect.

(5) Weekly Receipts - This volume includes the total volume of Form 5792 that are received for the REFAP process, as well as the Form 3753 that are received.

(6) Rejects, no IDRS Control - This volume includes the volume of Form 5792 and Form 3753, , which were rejected back to the originator because no IDRS Control was established.

(7) Rejects, All Other - This volume includes the volume of Form 5792 and Form 3753 , which were rejected back to the originator to correct a defect other than no IDRS Control established.

(8) Weekly Closures - This volume represents the volume of Form 5792 completed, via REFAP, and the Form 3753 scheduled, via SPS, for payment.

(9) Closing Inventory - This includes any inventory received and not scheduled for payment. Generally, this volume represents Form 3753 receipts. Mathematically, it must equal Beginning Inventory + Adjustments + Weekly Receipts - Rejects, no IDRS Control - Rejects, All Other - Weekly Closures.

(10) Comments are to be provided for any fluctuation in inventory levels, differences in sources of data, and any changes that have impact on the inventories.

(1) The Manual Refund 10 Cases per Month Monitoring section is only to be updated monthly. Capture and record data on 10 randomly selected manual refund requests (i.e., Form 5792, Request for IDRS Generated Refund, or Form 3753, Manual Refund Posting Voucher) and determine if the cases are monitored by the manual refund requestor (or Team), up to 30 days (or when the Transaction Code (TC) 840 posted).

(2) The cases monitored will be listed by each Business Operating Unit (BOD).

(3) Cases Selected - This volume represents the number of Form 5792 or Form 3753 randomly selected. The total of Cases Selected for all BODs should total 10.

(4) Cases Monitored - This volume represents the total number of manual refund requests monitored by the manual refund requestor (or Team), up to 30 days (or when the TC840 posted).

(5) Cases Not Monitored - This volume represents the total number of manual refund requests that were not monitored by the manual refund requestor (or Team), up to 30 days (or when the TC840 posted).

(6) Comments are to be provided if the number of cases reviewed this month do not total 10.

(1) The Files section includes information on inventories worked by Submission Processing.

(2) Beginning Inventory - This must match the Ending Inventory from the previous week's MIR Report.

(3) Adjustment - The amount (positive or negative) by which the Ending Inventory from the previous week was incorrect.

(4) Weekly Receipts - New Receipts from Saturday through Friday.

(5) Weekly Closures - Items closed from Saturday through Friday.

(6) Ending Inventory - Mathematically Beginning Inventory + Adjustment + Weekly Receipts - Weekly Closures.

(7) Oldest Date not Completed - For each category, separately, the oldest date on which an item still in inventory entered Files inventory.

(8) Items Overage - The number of items in Ending Inventory that are overage.

(9) Comments are to be provided for any fluctuation in inventory levels, differences in sources of data, adjustments, aged, and any changes that impact on the inventories. For any aged inventories, a comment is required as to why the inventory is aged, what plan of action the site will take to get the inventory current (i.e., move employees around, work overtime, etc.) and when the site anticipates being current on the inventory. For any adjustments made to inventories, a comment is required explaining why the adjustment was made..

(1) The Return and Income Verification Service (RAIVS) section includes information on RAIVS inventories worked by Submission Processing.

(2) Beginning Inventory - This should match the Ending Inventory from the previous week's MIR Report.

(3) Adjustment - The amount (positive or negative) by which the Ending Inventory from the previous week was incorrect. For transshipments to another site, the sending site should make a minus adjustment on their MIR with a comment, “On date, we transshipped number of RAIVS to the name of the receiving site” .The receiving site should make a plus adjustment on their MIR with a comment, “ On date, we received a transshipment of number of RAIVS from the name of the sending site”.

(4) Weekly Receipts - New receipts from Saturday through Friday.

(5) Weekly Closures - Items closed from Saturday through Friday.

(6) Ending Inventory - Mathematically Beginning Inventory + Adjustment + Weekly Receipts - Weekly Closures.

(7) Items Overage - The number of items in Ending Inventory that are overage.

(8) Overage - The number of items in Overage that fall into each of three categories - 1-10 work days overage; 11-20 work days overage; and more than 20 work days overage.

(9) Comments are to be provided for any fluctuation in inventory levels, differences in sources of data, adjustments, aged, and any changes that have impact on the inventories. For any aged inventories, comments are required as to why the inventory is aged, what action(s) the site is taking to get the inventory current (i.e., leveraging employees, working overtime, etc.) and a date as to when the site anticipates being current on the inventory. In addition, for any aged inventories, a comment is required including the oldest date of inventory and the volume for that date. For any adjustment made to inventories, comments are required explaining why the adjustment was made, details and background of the adjustment, and the difference in the original amount. For any overtime worked, a comment is required stating what days overtime was worked with the number of closures. For transshipments to another site, the sending site should make a minus adjustment on their MIR with a comment, “On date, we transshipped number of type of RAIVS Requests to the name of the receiving site”.The receiving site should make a plus adjustment on their MIR with a comment, “ On date, we received a transshipment of number of type of RAIVS Requests from the name of the sending site”.

(1) The Amended returns section includes information on inventories worked by Submission Processing.

(1) The EO Photocopy section includes information on inventories worked by Submission Processing.

(2) Beginning Inventory - This must match the Ending Inventory from the previous week's MIR Report.

(3) Adjustment - The amount (positive or negative) by which the Ending Inventory from the previous week was incorrect.

(4) Weekly Receipts - New receipts from Saturday through Friday.

(5) Weekly Closures - Items closed from Saturday through Friday.

(6) Ending Inventory - Mathematically Beginning Inventory + Adjustment + Weekly Receipts - Weekly Closures.

(7) Uncontrolled Inventory - The items included in the Ending Inventory which are not controlled.

(8) Controlled Inventory - The items included in the Ending Inventory which are controlled and suspended. .

(9) Items Overage - The number of Items in Ending Inventory that are overage.

(10) Overage - The number of items in Overage which fall into each of three categories - 1-30 overage days; 31-60 days overage; and >60 days overage.

(11) Comments are to be provided for any fluctuation in inventory levels, differences in sources of data, adjustments, aged, and any changes that have impact on the inventories. For any aged inventories, a comment is required as to why the inventory is aged, what plan of action the site will take to get the inventory current (i.e. move employees around, work overtime, etc.) and when the site anticipates being current on the inventory. In addition, for any aged inventory, a comment is required including the oldest date of inventory and the volume for that date. For any adjustment made to inventories, a comment is required explaining why the adjustment was made.

(1) The heading area on the spreadsheets requires Contact Information or the name and telephone number of the individual (and their backup) who can respond to inquiries regarding the Report.

(2) Use the remarks section to explain any unusual conditions regarding the report.

(3) Use the Excel spreadsheet format provided by the PMPA staff.

1. Use Excel formulae, macros, ranges, etc., as necessary to facilitate the preparation of the report and to minimize errors.

2. Items that are blue are for user entry.

3. Items that turn red indicate that a mathematical or logical inconsistency exists.

(1) Data sources include:

• Daily Production Report (PCC-22-40)

• Balance Forward Listing (PCD-03-44) or Block Proof Summary and Error Analysis (PCD-03-40)

• Pipeline Inventory Monitoring System (PIMS)

(2) Include data, for both Functions 110 and 950, for the following Program Numbers: 10100, 10110, 10130, 10140, 10150, 10170, 10180, 10200, 10220, 11100, 11140, 11180, 11200, 11210, 11250, 11280, 11300, 11500, 11520, 11540, 11550, 11600, 11610, 11650, 11660, 11680, 11700, 11710, 11800, 11810, 11900, 11910, 11930, 11950, 12100, 12110, 12200, 12210, 12220, 12300, 12340, 12400, 12410, 12500, 12700, 13110, 13120, 13130, 13140, 13160, 13170, 13180, 13190, 13210, 13330, 13350, 13370, 13380, 13390, 13410, 13420, 13450, 15540, 15550, 15560, 72840, 72860, and 72880.

(3) Include PRIOR CUM on every report, January - December.

1. Copy, exactly the contents of the prior week's cumulative report.

Note: Do not carry over inventory from the prior year into the PRIOR CUM columns. For the first report in January (Cycle ending January 06, 2023) the PRIOR CUM column should be zero.

2. The use of a macro or formulae to automatically copy the prior week's data is recommended to prevent errors.

3. For those Program Numbers that do not apply to a specific Submission Processing Center, enter zero.

(4) Include ADJUSTMENTS, whenever appropriate, on any report.

1. If an adjustment is not for the preceding week, provide details of the adjustment in the remarks section of the spreadsheet. Show the week(s) affected, function and program codes and volumes (e.g., 02/04/2022; 110; 11500; - 43,068).

2. For those Program Numbers that do not apply to a specific Submission Processing Center, enter zero.

(5) Include PERIOD on all reports (calculated field).

(6) Include NEW CUM on all reports (calculated field).

1. For all returns, the section is labeled Function 110. For paper however, it should reflect processable receipts (i.e., those receipts that can eventually result in a Good Tape transaction).

   Note: From the Daily Production Report (DPR) (PCC-22-40) the NEW CUM is calculated using the following formula: Function 180 cumulative production + Function 180 closing inventory (use zero if negative) - Function 940 cumulative receipts - Function 960 cumulative production - Function 970 cumulative production.

   Note: If for some reason the DPR for Wednesday does not include certain estimated volumes received through Wednesday, those unreported estimates should be factored into the instructions immediately above.

2. The source for NEW CUM for Function 950 is the PCD-03-44 Balance Forward Listing for the cycle cut-off day.

3. For all Program Numbers, the NEW CUM for Function 950 may not be greater than the NEW CUM for Function 110.

   Note: Form 940 is the only exception since they can be processed under two different program numbers (ISRP program 11100 or SCRIPS program 11140). When a document originally processed through SCRIPS needs to be re-input, the document will be processed through ISRP to retain the original document locator number (DLN). The receipts (Function 110) would be in program 11140 while the production (Function 950) would be in program 11100.

4. For those Program Numbers that do not apply to a specific Submission Processing Center, enter zero.

(7) The information in the THRU RDD column is used in the Program Completion Date (PCD) computation.

1. Report the cumulative number of returns (including adjustments) received up to and including the return due date .

2. Report this information, by Program Number, no later than the week that includes the return due date and continue for each week through the end of the calendar year.

3. The initial source is the PIMS Monitoring Report

4. For those Program Numbers that do not apply to a specific Submission Processing Center, enter zero.

(1) Compute the current number of days in the BBTS Accomplished Cycle by determining the date on which the current cumulative receipts for a campus most closely approximated the total number of returns released from Function 610 through the ending date, and counting the non-holiday Monday through Friday days between the two including the Functions 110 and 610 days.

1. To obtain the information, utilize PIMS (Function Volume Reports for Function 110) or the Daily Production Report (PCC-22-40).

2. By Program Number, report the current number of days in the BBTS Accomplished Cycle for each week beginning in January.

3. For those Program Numbers that do not apply to a specific Submission Processing Center, enter zero.

(1) Ensure that the appropriate template is employed for the data reported:

• Form 8453-X/Program 16011

• Form 8872/Program 16012

(2) Enter the date from the preceding work date (i.e., non-holiday Monday through Friday).

(1) Function 110

1. Period Receipts from the Daily Production Report

(2) Function 390

1. Period Receipts from the Daily Production Report

2. Closing Inventory from the Daily Production Report

3. Volume 2 days or more in Function from the Batch Profile Report

(3) Function 300

1. Period Receipts from the Daily Production Report

2. Closing Inventory from the Daily Production Report

(4) Function 360

1. Period Receipts from the Daily Production Report

2. Closing Inventory from the Daily Production Report

3. Volume 2 days or more in Function from the Batch Profile Report

(5) Function 390 Unprocessable

1. Period Closures from Correspondence Suspense File

2. Closing Inventory from Correspondence Suspense File

(1) Receipts - Period Receipts for Function 110 from the Daily Production Report

(2) Inventory - Sum of Closing Inventory for Functions 390, 300, and 360 from the Daily Production Report added to the Closing Inventory for Function 390 Unprocessable from the Correspondence Suspense File.

(3) Volume 2 days or more in Function - Sum of volume 2 days or more in function from Batch Profile Report for Functions 390 and 360.