16PBGC-22-R-0008 - Final V2.pdf

RFQ IFB RFP

WOMEN-OWNED SMALL BUSINESS

(WOSB) ELIGIBLE UNDER THE WOMEN-OWNED

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, & 30

1. REQUISITION NUMBER PAGE OF

2. CONTRACT NO. 3. AWARD/EFFECTIVE

DATE

4. ORDER NUMBER 5. SOLICITATION NUMBER 6. SOLICITATION ISSUE

DATE

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME b. TELEPHONE NUMBER (No collect calls)

8. OFFER DUE DATE/

LOCAL TIME

9. ISSUED BY

13b. RATING

14. METHOD OF SOLICITATION

CODE

15. DELIVER TO 16. ADMINISTERED BY CODE

18a. PAYMENT WILL BE MADE BY CODEFACILITY

CODE

CODE

TELEPHONE NO.

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT SUCH ADDRESS IN

OFFER

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK

BELOW IS CHECKED

SEE ADDENDUM

19.

ITEM NO.

20.

SCHEDULE OF SUPPLIES/SERVICES

21.

QUANTITY

22.

UNIT

23.

UNIT PRICE

24.

AMOUNT

(Use Reverse and/or Attach Additional Sheets as Necessary)

25. ACCOUNTING AND APPROPRIATION DATA 26. TOTAL AWARD AMOUNT (For Govt. Use Only)

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED

29. AWARD OF CONTRACT: REF.

DATED . YOUR OFFER ON SOLICITATION

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

30a. SIGNATURE OF OFFEROR/CONTRACTOR

30b. NAME AND TITLE OF SIGNER (Type or print) 30c. DATE SIGNED

31a. UNITED STATES OF AMERICA (SIGNATURE OF CONTRACTING OFFICER)

31b. NAME OF CONTRACTING OFFICER (Type or print) 31c. DATE SIGNED

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 2/2012)

Prescribed by GSA - FAR (48 CFR) 53.212

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

OFFER

13a. THIS CONTRACT IS A

RATED ORDER UNDER

DPAS (15 CFR 700)

11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

12. DISCOUNT TERMS

ARE ARE NOT ATTACHED

ARE ARE NOT ATTACHED

27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1, 52.212-4. FAR 52.212-3 AND 52.212-5 ARE ATTACHED. ADDENDA

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA

17a CONTRACTOR/

OFFEROR.

CODE

8 (A)

SIZE STANDARD:

NAICS:

% FOR:SET ASIDE:UNRESTRICTED OR

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

HUBZONE SMALL

BUSINESS

SMALL BUSINESS

10. THIS ACQUISITION IS

EDWOSB

SMALL BUSINESS PROGRAM

STANDARD FORM 1449 (REV. 2/2012) BACK

19.

ITEM NO.

20.

SCHEDULE OF SUPPLIES/SERVICES

21.

QUANTITY

22.

UNIT

23.

UNIT PRICE

24.

AMOUNT

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED ACCEPTED, AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED:

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE

41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

42c. DATE REC'D (YY/MM/DD) 42d. TOTAL CONTAINERS

40. PAID BY

32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f. TELPHONE NUMBER OF AUTHORZED GOVERNMENT REPRESENTATIVE

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

33. SHIP NUMBER 34. VOUCHER NUMBER 35. AMOUNT VERIFIED

CORRECT FOR

PARTIAL FINAL

37. CHECK NUMBER

38. S/R ACCOUNT NO. 39. S/R VOUCHER NUMBER

36. PAYMENT

COMPLETE PARTIAL FINAL

SCHEDULE Continued

ITEM NO. SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 Primary Pay Agent Services

PR NUMBER: RQ-35-22-000211

1.00 EA

PAGE 3 OF 334 16PBGC22R0008

Table of Contents

SECTION B SUPPLIES OR SERVICES AND PRICES/COSTS

B.1 Supplies or Services and Prices/Costs

SECTION C DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

C.1 Performance Work Statement

C.2 Quality Assurance Surveillance Plan

C.3 Example Service Level Agreement

SECTION D PACKAGING AND MARKING

D.1 PBGC 52.247-7000 PACKAGING AND MARKING (JAN 2012)

SECTION E INSPECTION AND ACCEPTANCE

E.1 PBGC 52.246-7000 INSPECTION AND ACCEPTANCE OF DELIVERABLES (JAN 2012)

SECTION F DELIVERIES OR PERFORMANCE

F.1 Deliveries or Performance

F.2 PBGC 52.237-7004 TRAINING (MAR 2016)

SECTION G CONTRACT ADMINISTRATION DATA

G.1 Contract Administration Data

G.2 PBGC 52.201-7000 CONTRACTING OFFICER'S REPRESENTATIVE (JAN 2012)

G.3 PBGC 52.232-7000 SUBMISSION OF INVOICES (FIXED-PRICE) (SEPT 2017)

G.4 PBGC 52.237-7008 OBSERVANCE OF LEGAL HOLIDAYS (OCT 2018)

SECTION H SPECIAL CONTRACT REQUIREMENTS

H.1 52.216-1 TYPE OF CONTRACT (APR 1984)

H.2 52.222-56CERTIFICATION REGARDING TRAFFICKING IN PERSONS COMPLIANCE PLAN (OCT 2020)

H.3 PBGC 52.204-7000 RECORDS MANAGEMENT (SEP 2017)

H.4 PBGC 52.209-7001 ORGANIZATIONAL CONFLICTS OF INTEREST (AUG 2017)

H.5 PBGC 52.209-7002 HANDLING PBGC DATA (MAY 2017)

H.6 PBGC 52.215-7001 METHOD OF AWARD (OCT 2004)

H.7 PBGC 52.237-7002 FITNESS DETERMINATION (APR 2019)

H.8 PBGC 52.237-7005 INFORMATION SECURITY TRAINING (MAR 2020)

H.9 PBGC 52.239-7000 SECTION 508 ACCESSIBILITY STANDARDS (MAR 2020)

H.10 PBGC 52.239-7006INFORMATION TECHNOLOGY MANAGEMENT (AUG 2018)

H.11 PBGC 52.242-7000 POSTAWARD CONFERENCE (SEP 2020)

SECTION I CONTRACT CLAUSES

I.1 52.202-1DEFINITIONS (JUN 2020)

I.2 52.203-3 GRATUITIES (APR 1984)

I.3 52.203-5 COVENANT AGAINST CONTINGENT FEES (MAY 2014)

I.4 52.203-6RESTRICTIONS ON SUBCONTRACTOR SALES TO THE GOVERNMENT (JUN 2020)

I.5 52.203-7ANTI-KICKBACK PROCEDURES (JUN 2020)

I.6 52.203-11 CERTIFICATION AND DISCLOSURE REGARDING PAYMENTS TO INFLUENCE CERTAIN FEDERAL

TRANSACTIONS (SEP 2007)

I.7 52.203-12LIMITATION ON PAYMENTS TO INFLUENCE CERTAIN FEDERAL TRANSACTIONS (JUN 2020)

I.8 52.203-13CONTRACTOR CODE OF BUSINESS ETHICS AND CONDUCT (NOV 2021)

I.9 52.204-4 PRINTED OR COPIED DOUBLE-SIDED ON POSTCONSUMER FIBER CONTENT PAPER (MAY 2011)

I.10 52.204-9 PERSONAL IDENTITY VERIFICATION OF CONTRACTOR PERSONNEL (JAN 2011)

I.11 52.204-10REPORTING EXECUTIVE COMPENSATION AND FIRST-TIER SUBCONTRACT AWARDS (JUN 2020)

I.12 52.204-13SYSTEM FOR AWARD MANAGEMENT MAINTENANCE (OCT 2018)

PAGE 4 OF 334 16PBGC22R0008

I.13 52.204-14 SERVICE CONTRACT REPORTING REQUIREMENTS (OCT 2016)

I.14 52.204-19 INCORPORATION BY REFERENCE OF REPRESENTATIONS AND CERTIFICATIONS (DEC 2014)

I.15 52.204-24REPRESENTATION REGARDING CERTAIN TELECOMMUNICATIONS AND VIDEO SURVEILLANCE SERVICES OR

EQUIPMENT (NOV 2021)

I.16 52.204-25PROHIBITION ON CONTRACTING FOR CERTAIN TELECOMMUNICATIONS AND VIDEO SURVEILLANCE

SERVICES OR EQUIPMENT (NOV 2021)

I.17 52.204-26COVERED TELECOMMUNICATIONS EQUIPMENT OR SERVICES--REPRESENTATION (OCT 2020)

I.18 52.209-6PROTECTING THE GOVERNMENT`S INTEREST WHEN SUBCONTRACTING WITH CONTRACTORS DEBARRED, SUSPENDED, OR PROPOSED FOR DEBARMENT (NOV 2021)

I.19 52.209-10 PROHIBITION ON CONTRACTING WITH INVERTED DOMESTIC CORPORATIONS (NOV 2015)

I.20 52.212-4CONTRACT TERMS AND CONDITIONS--COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES (NOV 2021) 107

I.21 52.212-5CONTRACT TERMS AND CONDITIONS REQUIRED TO IMPLEMENT STATUTES OR EXECUTIVE ORDERS--

COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES (MAY 2022)

I.22 52.215-8 ORDER OF PRECEDENCE--UNIFORM CONTRACT FORMAT (OCT 1997)

I.23 52.219-4NOTICE OF PRICE EVALUATION PREFERENCE FOR HUBZONE SMALL BUSINESS CONCERNS (SEP 2021).107

I.24 52.219-8 UTILIZATION OF SMALL BUSINESS CONCERNS (OCT 2018)

I.25 52.219-28POST-AWARD SMALL BUSINESS PROGRAM REREPRESENTATION (SEP 2021)

I.26 52.222-3 CONVICT LABOR (JUN 2003)

I.27 52.222-21 PROHIBITION OF SEGREGATED FACILITIES (APR 2015)

I.28 52.222-35EQUAL OPPORTUNITY FOR VETERANS. (JUN 2020)

I.29 52.222-36EQUAL OPPORTUNITY FOR WORKERS WITH DISABILITIES (JUN 2020)

I.30 52.222-37EMPLOYMENT REPORTS ON VETERANS (JUN 2020)

I.31 52.222-40 NOTIFICATION OF EMPLOYEE RIGHTS UNDER THE NATIONAL LABOR RELATIONS ACT (DEC 2010). 107

I.32 52.222-50COMBATING TRAFFICKING IN PERSONS (NOV 2021)

I.33 52.223-18ENCOURAGING CONTRACTOR POLICIES TO BAN TEXT MESSAGING WHILE DRIVING (JUN 2020)

I.34 52.223-22 PUBLIC DISCLOSURE OF GREENHOUSE GAS EMISSIONS AND REDUCTION GOALS--REPRESENTATION

(DEC 2016)

I.35 52.225-13RESTRICTIONS ON CERTAIN FOREIGN PURCHASES (NOV 2021)

I.36 52.229-3 FEDERAL, STATE, AND LOCAL TAXES (FEB 2013)

I.37 52.232-9 LIMITATION ON WITHHOLDING OF PAYMENTS (APR 1984)

I.38 52.232-33 PAYMENT BY ELECTRONIC FUNDS TRANSFER--SYSTEM FOR AWARD MANAGEMENT (OCT 2018)

I.39 52.232-34 PAYMENT BY ELECTRONIC FUNDS TRANSFER--OTHER THAN SYSTEM FOR AWARD MANAGEMENT (MAY

1999)

I.40 52.242-13 BANKRUPTCY (JUL 1995)

I.41 52.244-2SUBCONTRACTS (JUN 2020)

I.42 52.244-6SUBCONTRACTS FOR COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES (JAN 2022)

I.43 52.245-1GOVERNMENT PROPERTY (SEP 2021)

I.44 52.245-9 USE AND CHARGES (APR 2012)

I.45 52.252-1 SOLICITATION PROVISIONS INCORPORATED BY REFERENCE (FEB 1998)

I.46 52.204-7 SYSTEM FOR AWARD MANAGEMENT (OCT 2018)

I.47 52.204-16COMMERCIAL AND GOVERNMENT ENTITY CODE REPORTING (AUG 2020)

I.48 52.204-17OWNERSHIP OR CONTROL OF OFFEROR (AUG 2020)

I.49 52.204-18COMMERCIAL AND GOVERNMENT ENTITY CODE MAINTENANCE (AUG 2020)

I.50 52.204-21BASIC SAFEGUARDING OF COVERED CONTRACTOR INFORMATION SYSTEMS (NOV 2021)

I.51 52.209-9 UPDATES OF PUBLICLY AVAILABLE INFORMATION REGARDING RESPONSIBILITY MATTERS (OCT 2018)111

I.52 52.215-1INSTRUCTIONS TO OFFERORS--COMPETITIVE ACQUISITION (NOV 2021)

I.53 52.215-19 NOTIFICATION OF OWNERSHIP CHANGES (OCT 1997)

I.54 52.217-2 CANCELLATION UNDER MULTI-YEAR CONTRACTS (OCT 1997)

I.55 52.217-8 OPTION TO EXTEND SERVICES (NOV 1999)

I.56 52.217-9 OPTION TO EXTEND THE TERM OF THE CONTRACT (MAR 2000)

I.57 52.222-22 PREVIOUS CONTRACTS AND COMPLIANCE REPORTS (FEB 1999)

PAGE 5 OF 334 16PBGC22R0008

I.58 52.222-24 PREAWARD ON-SITE EQUAL OPPORTUNITY COMPLIANCE EVALUATION (FEB 1999)

I.59 52.222-25 AFFIRMATIVE ACTION COMPLIANCE (APR 1984)

I.60 52.222-26 EQUAL OPPORTUNITY (SEPT 2016)

I.61 52.224-1 PRIVACY ACT NOTIFICATION (APR 1984)

I.62 52.224-2 PRIVACY ACT (APR 1984)

I.63 52.224-3 PRIVACY TRAINING (JAN 2017)

I.64 52.227-14 RIGHTS IN DATA--GENERAL (MAY 2014)

I.65 52.232-39 UNENFORCEABILITY OF UNAUTHORIZED OBLIGATIONS (JUNE 2013)

I.66 52.233-1 DISPUTES (MAY 2014)

I.67 52.233-2 SERVICE OF PROTEST (SEP 2006)

I.68 52.233-3 PROTEST AFTER AWARD (AUG 1996)

I.69 52.233-4 APPLICABLE LAW FOR BREACH OF CONTRACT CLAIM (OCT 2004)

I.70 52.239-1 PRIVACY OR SECURITY SAFEGUARDS (AUG 1996)

I.71 52.249-1 TERMINATION FOR CONVENIENCE OF THE GOVERNMENT (FIXED-PRICE) (SHORT FORM) (APR 1984).125

I.72 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

I.73 52.252-5AUTHORIZED DEVIATIONS IN PROVISIONS (NOV 2020)

SECTION J LIST OF ATTACHMENTS

J.1 J.1 Mandatory Requirements Certification

J.2 J.2 Mandatory Volume Requirements

J.3 J.3 Past Performance Questionnaire

J.4 J.4 Paying Agent Services PWS Attachments

SECTION K REPRESENTATIONS, CERTIFICATIONS AND OTHER STATEMENTS OF OFFERORS

K.1 52.204-19 INCORPORATION BY REFERENCE OF REPRESENTATIONS AND CERTIFICATIONS (DEC 2014)

K.2 52.225-25PROHIBITION ON CONTRACTING WITH ENTITIES ENGAGING IN CERTAIN ACTIVITIES OR TRANSACTIONS

RELATING TO IRAN--REPRESENTATION AND CERTIFICATIONS (JUN 2020)

K.3 52.209-7 INFORMATION REGARDING RESPONSIBILITY MATTERS (OCT 2018)

K.4 52.212-3OFFEROR REPRESENTATIONS AND CERTIFICATIONS--COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES

(NOV 2021)

SECTION L INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

L.1 Instructions to Offerors

L.2 52.204-6 UNIQUE ENTITY IDENTIFIER (OCT 2016)

L.3 52.204-22 ALTERNATIVE LINE ITEM PROPOSAL (JAN 2017)

L.4 PBGC 52.215-7006 PROPOSAL REVISIONS (OCT 2004)

SECTION M EVALUATION FACTORS FOR AWARD

M.1 Evaluation Criteria

M.2 52.217-4 EVALUATION OF OPTIONS EXERCISED AT TIME OF CONTRACT AWARD (JUN 1988)

M.3 52.217-5 EVALUATION OF OPTIONS (JUL 1990)

M.4 52.222-54EMPLOYMENT ELIGIBILITY VERIFICATION (MAY 2022)

M.5 52.222-55MINIMUM WAGES FOR CONTRACTOR WORKERS UNDER EXECUTIVE ORDER 14026. (JAN 2022)

M.6 PBGC 52.215-7009 REFERENCE AND EVALUATION (OCT 2004)

PAGE 6 OF 334 16PBGC22R0008

SECTION B

SUPPLIES OR SERVICES AND PRICES/COSTS

B.1 Supplies or Services and Prices/Costs

PAGE 7 OF 334 16PBGC22R0008

Section B: Supplies or Services and Prices/Costs

1. Description of Services:

The contractor shall provide Primary Pay Agent Services in accordance with the Performance Work Statement.

2. Pricing Schedule:

Base Period

CLIN Services QTY Unit Unit Price

(FFP)

Total Amount

(FFP)

0001 Work in accordance with the PWS

12 Month $ $

Option Period 1

CLIN Services QTY Unit Unit Price

(FFP)

Total Amount

(FFP)

1001 Work in accordance with

Option Period 2

(FFP)

Total Amount

(FFP)

2001 Work in accordance with

Option Period 3

(FFP)

Total Amount

(FFP)

3001 Work in accordance with

PAGE 8 OF 334 16PBGC22R0008

Option Period 4

CLIN Services QTY Unit Unit Price

(FFP)

Total Amount

(FFP)

4001 Work in accordance with

Option Period 5

(FFP)

Total Amount

(FFP)

5001 Work in accordance with

Option Period 6

(FFP)

Total Amount

(FFP)

6001 Work in accordance with

Option Period 7

(FFP)

Total Amount

(FFP)

7001 Work in accordance with

Option Period 8

(FFP)

Total Amount

(FFP)

8001 Work in accordance with

PAGE 9 OF 334 16PBGC22R0008

Option Period 9

CLIN Services QTY Unit Unit Price

(FFP)

Total Amount

(FFP)

9001 Work in accordance with

PAGE 10 OF 334 16PBGC22R0008

SECTION C

DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

C.1 Performance Work Statement

PAGE 11 OF 334 16PBGC22R0008

SECTION C: PERFORMANCE WORK STATEMENT (PWS)

C. 1 PERFORMANCE WORK STATEMENT

1.1 Introduction

The Pension Benefit Guaranty Corporation (PBGC) maintains its own pension recordkeeping system and benefits administration infrastructure for more than 1.5 million participants. The system packages payment changes (adds and updates) and transmits them to the Primary Paying Agent’s (PA) pension payment system several times each month.

PBGC/PA disburses about 860,000 benefit payments each month totaling approx.

$48.33M per month, or about $5.8 billion annually to retirees in over 5,000 terminated private-sector single-employer defined benefit pension plans.

The PA performs the gross- to-net calculation, manages federal income tax withholdings, deposits, and reporting, manages exception processing associated with payments (stop and reissue checks, ACH notice of change, returns, reclamations, adjustments), supports financial management activities associated with benefit payments, provides PBGC users access to their pension payment system and provides PBGC retirees access to their retiree self-service system via Web services. The PA contract is overseen by the Benefit Payments Division (BPD) of the Participant Services Department (PSD) within the Office of Benefits Administration (OBA).

1.2 PBGC Background

PBGC is a federal corporation established under the Employee Retirement Income Security Act (ERISA) of 1974, as amended. It guarantees payment of basic pension benefits earned by nearly 40 million of America’s workers and retirees participating in nearly 24,000 private sector defined benefit pension plans. PBGC receives no funds from general tax revenues. Operations are financed by insurance premiums paid by companies that sponsor defined benefit pension plans, investment income, and assets acquired from terminated plans.

PBGC administers two insurance programs. The single-employer program protects about 30 million workers and retirees in over 22,000 pension plans. The multiemployer program protects over 10 million workers and retirees in about 1,400 pension plans. (Note:

Financial assistance to insolvent multiemployer plans is outside the scope of this contract.)

More information about PBGC is available via our website, www.PBGC.gov:

Annual Report: https://www.pbgc.gov/about/annual-reports/pbgc-annual-report-2020 Fact Sheet: https://www.pbgc.gov/about/factsheets

1. Performance Work Statement for Paying Agent (PA) Services

PAGE 12 OF 334 16PBGC22R0008

1.4.1 The PA shall disburse benefit payments to PBGC payees.

1.4.1.1 Disburse benefit payments to PBGC payees via Electronic Funds Transfer (EFT) Prearranged Payment and Deposit (PPD) and International ACH Transaction (IAT) entries, Wire Transfers and by paper checks.

1.4.1.2 PBGC benefit payments include:

o Monthly annuities and other payments payable on the first of the month.

o Lump sum distributions, back payments and other special payments weekly.

Currently PBGC is accustomed to transmitting weekly payment files to the PA on Wednesday for payments dated Friday.

o Monthly or one-time unique-situation payments (e.g., legal settlements and unusual plans).

1.4.1.3 PBGC payees include pension plan participants, beneficiaries, alternate payees, authorized third parties and estates located either in or outside of the United States and its territories.

1.4.1.3.1 Any given payee can have multiple “roles” (e.g., participant in plan A, participant in plan B, surviving spouse of a participant in plan A, surviving spouse of a participant in plan B, alternate payee of a participant in plan A, alternate payee of a participant in plan B, etc.) each with its own benefit.

1.4.1.4 The normal settlement date for PBGC benefit payments is the first of each month.

1.4.1.5 When the first of the month is not a banking day, ACH settlement is normally on the last banking day of the prior month with the exception of January, when the settlement date is the first bank day of January.

1.4.1.6 Gross-to-net calculation for individual payments:

o PBGC provides gross payment amount (exception: for overpayment recoupments, PBGC currently transmits net amount after recoupment).

o PBGC provides most deduction information (exceptions: medical/life deductions, overpayment recoupment deductions).

o PA calculates federal income taxes to be withheld (see 1.4.2).

o PA deducts federal income taxes, IRS levies, Qualified Domestic Relations

Orders (QDRO) and other PBGC-sponsored deductions.

o PA deducts medical and/or life deductions for plan families specified in section

1.4.2.7

1.4.1.7 Serve as PBGC’s Originating Depository Financial Institution (ODFI) for electronic funds transfer (EFT) payments (a.k.a. electronic direct deposit – EDD, Automated Clearing House – ACH, direct deposit):

1.4.1.7.1 Adhere to NACHA Operating Rules (OR) and Operating Guidelines (OG).

1.4.1.7.2 Originate Pre-arranged Payment and Deposit (PPD) entries to transfer PBGC benefit payments into domestic Receiving Depository Financial Institution (RDFI) accounts or Direct Express Debit card © held by PBGC payees.

PAGE 13 OF 334 16PBGC22R0008

1.4.1.7.3 Originate International ACH Transaction (IAT) entries to transfer PBGC benefit payments into international RDFI accounts held by PBGC payees.

1.4.1.7.4 Create the ACH file, formatted per NACHA requirements:

- Identify the source of ACH payments as “USPBGC-” followed by as many characters of the modified PBGC plan name as allowed by the file format. The “modified plan name” is the official plan name with certain text re-ordered for clarity (e.g., “XYZ Pension Plan” instead of an official plan name of “Pension Plan for XYZ”).

- Include sufficient data to map each ACH entry to the associated payment in PBGC’s system. At least one way this could be accomplished is by including the PBGC Payable SID (PAYBL_SID).

1.4.1.8 Issue paper checks:

1.4.1.8.1 Ensure that all checks (including unused check stock, mutilated checks, etc.)

are accounted for and provide monthly reconciliation report (BPD Reports see 1.4.12.3).

1.4.1.8.2 Provide payee positive pay cash management service to deter fraud by matching check number, amount and payee name on checks issued to checks presented for payment. Any checks considered to be potentially fraudulent are to be examined by the PA.

1.4.1.8.3 Check stock shall include security features to defend against alteration, erasure, toner removal, photocopying, and counterfeiting.

1.4.1.8.4 Checks shall be void after 180 days. On a monthly basis, the PA shall stop payment on checks that have been outstanding for more than 180 days, return the funds to PBGC and provide a purged check report (BPD Reports see 1.4.12.6).

1.4.1.8.5 On a quarterly basis the PA shall provide a report of all outstanding checks (BPD Reports see 1.4.12.7).

1.4.1.9 Annual key dates schedule: The PA shall collaborate with BPD in the development of an annual schedule of key payment dates to include the dates listed below. The annual schedule is to be published each September for the following calendar year.

1.4.1.9.1 Check run for annuities and special checks is the date when PA creates the ACH file and the check print file for the vast majority of payments scheduled for the upcoming first of the month.

1.4.1.9.2 OBA cutoff: Deadline for approving changes so that they are included in the PBGC trial balance process. On this date:

PBGC transmits the “cutoff file” to the PA by an agreed upon time and PA transmits the trial balance projection file to PBGC (see section 1.4.4.3).

1.4.1.9.3 Trial balance variance distribution from BPD to benefit processors: Typically, this is the business day after OBA cutoff.

PAGE 14 OF 334 16PBGC22R0008

1.4.1.9.4 Last file transmission date: This is the day of the last file for monthly and NFDE files (see 1.4.4.1) for the upcoming first of the month payments. Typically, this is two business days before the annuity check run.

1.4.1.9.5 Check mail date: This is the date when paper checks are mailed. Typically, this is three mail days before the first of the month.

1.4.1.9.6 ACH settlement date: Typically, this is the first of the month unless the first is not a business day (see 1.4.1.5).

1.4.1.10 Monthly payment schedule: The PA shall collaborate with BPD in the development of a monthly schedule of payment dates to include, but not be limited to, the dates listed below. The monthly schedule for the upcoming month’s activities is to be published the day after the annuity check run (1.4.1.9) in any given month. For example, the schedule published after the annuity check run in October identifies activities to be performed in November for benefit payments that will be made on December 1.

o Dates when Spectrum and NFDE files (see 1.4.4.1) will be transmitted to the PA by PBGC.

o Dates when trial balance projection files (see 1.4.4.3) will be transmitted to PBGC by the PA.

o Dates of each individual check run (1.4.1.9) for annuities, lump sums, special payments, etc.

o Dates when payment history files (see 1.4.4.4) will be transmitted to PBGC by the PA.

o Dates when funding requests and backup documentation are delivered by the PA to PBGC (see 1.4.9.6).

o Date range when ACH deletions (see 1.4.5.1) can be processed for the upcoming first of the month payments.

o Date range during which stop and reissues (see 1.4.5.3) can be processed.

1.4.1.11 In unusual circumstances, the PA shall collaborate with BPD to re-schedule file transmissions, check runs and other events on short notice in response to operational anomalies.

1.4.2 The PA shall manage tax withholdings and other deductions.

1.4.2.1 Calculate and withhold federal income taxes (including taxes for Non-Resident Alien (NRA)) based on input data (e.g., gross benefit amount, withholding exemptions, marital status) provided by PBGC (see also 1.4.1.6).

1.4.2.2 Withhold for IRS tax levies that have been explicitly approved by PBGC. See also 1.4.5.13

PAGE 15 OF 334 16PBGC22R0008

1.4.2.3 Remit withheld federal income taxes to the Internal Revenue Service (IRS) on PBGC’s behalf in accordance with IRS requirements.

1.4.2.4 Recover overpayments of federal income taxes to the IRS (or net from future remittances) and refund the affected payees.

1.4.2.5 Report taxes withheld to the IRS on the required forms (e.g., IRS form 945).

(Reports see 1.4.15.1) Note: Reporting taxes withheld to individual payees is covered at 1.4.6.3.

1.4.2.6 Provide technical assistance to BPD personnel regarding tax withholding issues.

1.4.2.7 Establish an agreement directly with the insurance provider(s) whereby premiums are withheld and remitted for a select number of PBGC trusteed pension plans.

PBGC by policy does not withhold insurance premiums. Special negotiations with these plans created limited exceptions.

1.4.2.7.1 If overpayments to insurance providers occur, the PA shall recover the funds and make any necessary adjustments to individual payees’ payment history.

1.4.3 The PA shall maintain a copy of certain PBGC payee data on the PA pension payment system and provide access to PBGC employees.

1.4.3.1 Maintain PBGC sensitive data, including personally identifiable information (PII) for PBGC payees, on a contractor-owned pension payment system hosted within the United States with sufficient safeguards to ensure PBGC sensitive data is only accessible to authorized employees from within the United States. Information security is covered in more detail at 1.4.10.

1.4.3.2 Store sufficient data in the pension payment system on recurring (monthly, quarterly, annual, and semi-annual) PBGC benefit payments to continue the payments until PBGC transmits an approved change.

1.4.3.3 Establish accounts to accommodate the 5,000 plus plans in the Paying Agent pension payment system upon PBGC request.

1.4.3.4 Establish a record for each of about 800,000 existing PBGC payees in the pension payment system. After the transition into the new contract, additional payee record creations are covered in 1.4.4.1.

1.4.3. 5 Provide web access to the PA pension payment system for PBGC employees.

1.4.3.5.1 Read-only access for about 500 PBGC users for viewing the real-time status of pending payments, the full payment history for each individual payee, images of negotiated checks, and images of individual payee tax forms.

1.4.3.5.2 Limited read-write access to about 10 BPD users for initiating certain exception processing transactions (See 1.4.5.1for more about how these transactions are managed.)

1.4.3.6 Conduct an annual account review to verify with management that all employees with a particular level of access (e.g., read-only, read write, administrative, etc.) to PBGC sensitive data stored in the PA pension payment system still require access at that level. (BPD Reports 1.4.12.8)

PAGE 16 OF 334 16PBGC22R0008

1.4.3.6.1 PA management will verify that PA employees (including subcontractors) who have either regular user accounts or privileged user accounts with access to sensitive PBGC data still require that level of access.

1.4.3.6.2 PBGC management will verify PBGC employees based on the list of account holders provided by the PA.

1.4.3.6.3 Promptly deactivate (e.g., for separated employee) or downgrade (e.g., from read-write to read-only) user accounts in accordance with management’s responses regarding employees who no longer have the correct level of access.

1.4.4 The PA shall exchange data between PBGC’s benefit administration systems and the PA pension payment system.

1.4.4.1 Approved payment changes from PBGC: Receive from PBGC and process electronic files containing approved changes (adds and updates) including new payees, changes in monthly gross benefit amount (including benefits that have ended), tax withholding, payment destination (EFT vs. check), RDFI information and home address.

o The vast majority of these changes originate in PBGC’s Spectrum (e.g., new retirees), QuEST (e.g., payment destination changes triggered by phone calls), or MyPBA (e.g., self-service home address changes) systems, are approved in PBGC’s Approval Worklist Application (AWA), and are packaged for transmission to the PA system by the Spectrum application. See 1.4.8.5.1 for additional information about PBGC systems. For Spectrum file formats, see attachment 18.

o A small portion of these changes originate in PBGC’s Non-Spectrum Forms Data Entry (NFDE pronounced “Nifty”) application. They are manually approved via a signed or authorized form (approvals are validated by BPD employees) and are packaged for transmission to the PA in the format of an Excel spreadsheet called the adjustment file. For NFDE file formats, see attachment 24, but note that by design the NFDE file format can be easily modified.

- The vast majority of NFDE transactions received by the PA are transmitted electronically.

- In unusual situations (see 1.4.5.6.1) the transactions are received by the PA via a SharePoint collaboration tool.

1.4.4.2 Acknowledgement of approved changes to PBGC: Transmit to PBGC electronic files acknowledging each PBGC-approved change. For the cutoff file (see 1.4.1.9.2) the acknowledgement must be received the same day. For other files in 1.4.4.1 the acknowledgement must be received by the next business day. For Spectrum acknowledgement file formats, see attachment 24 (NFDE uses the same format).

(Performance Standards 1.4.16.1):

o Identify each transaction that was correctly processed in the PA pension payment system.

o Identify each transaction that was not correctly processed in the PA pension payment system and provide an error code and description.

PAGE 17 OF 334 16PBGC22R0008

1.4.4.3 Trial balance projection to PBGC: Transmit to PBGC an electronic file containing a projection of payments to be made in the upcoming monthly or weekly payment cycle to support PBGC’s Trial Balance process. For trial balance file format, see attachment 27. (Performance Standards 1.4.16.1).

1.4.4.4 Payment history to PBGC: Transmit to PBGC electronic payment history files (participant sub-ledgers) containing the details of all PBGC payments made in a given check run and all adjustments to payee records effected in the relevant time period (1.4.1.9) to support PBGC’s Post Balance and other processes. Records in these files are matched to corresponding records in PBGC’s system based on a unique payment identifier and are visible to Spectrum users. For payment history file formats, see attachment 28. (Performance Standards 1.4.16.1)

1.4.4.5 ACH Returns and NOCs: Transmit ACH return (1.4.5.4) and ACH Notices of

Change (NOC) (1.4.5.7) files to PBGC at least once per week. For ACH NOC and return file formats, see attachment 22. (Performance Standards 1.4.16.1). Note: The ACH return file described here is in addition to the ACH return notification for PBGC (1.4.5.4.1).

1.4.4.6 Data synchronization: Transmit a quarterly reconciliation file to PBGC.

o The goal of Data Synchronization is to minimize any data differences between the paying agent’s system and PBGC’s system.

o The PA transmits a defined extract from the PA’s pension payment system and PBGC loads that into the enterprise database and compares it against a similar extract from PBGC’s system. Differences are identified and BPD advises CSD on the appropriate corrective action. The current file format is included as attachment 23 for reference.

1.4.4.7 MyPBA: Provide a Web service for PBGC’s MyPBA online self-service system (www.pbgc.gov/mypba) to serve payment history data (payee sub-ledgers) and images of checks and tax forms (e.g., 1099-R) to PBGC payees (see attachment 6).

1.4.4.8 Testing: Upon PBGC request, participate in tests of changes or releases of PBGC’s or the PA’s systems including, but not limited to, the following types of testing:

1.4.4.8.1 Full pay cycle: Processing a full check run (1.4.1.9.1) from start to finish, including file transmissions and acknowledgments, balancing, and running a test check run.

1.4.4.8.2 Regression testing to ensure that the changes applied to the application have not adversely affected previously tested functionality.

1.4.4.8.3 Performance testing to ensure that the application performs to customer expectations (response time, availability).

1.4.4.8.4 Parallel check runs reproducing a production check run in the test environment and justifying all unexpected results.

1.4.4.8.5 Transmission of files to and from the PA’s and PBGC’s systems.

1.4.4.8.6 Setting up test data and testing environment for PBGC’s use.

1.4.4.9 Tax forms, check images, daily settlement data: PBGC may wish to import tax forms and check images into PBGC’s Image Processing System (IPS, see 1.4.8.5.1) and daily

PAGE 18 OF 334 16PBGC22R0008

settlement data into Spectrum. If so, this will be handled by a fixed price work order (see 1.4.16).

1.4.5 The PA shall provide exception processing services.

1.4.5.1 Use exception processing work queues established in the PBGC collaboration tool (SharePoint): Many exception-processing requests (e.g., stop payments) are initiated by PBGC employees via electronic forms (called eCARFs) residing on the PBGC collaboration tool (see eCARF entry in glossary). PBGC, not the PA, maintains and supports the collaboration tool.

o Initiators fill out electronic forms specific to each particular type of transaction.

o When the initiator saves the form, it populates the appropriate work queue overseen by BPD employees for some types of transactions or PA employees for other types of transactions.

o Fulfilling an eCARF request in a BPD or PA employee’s work queue may involve data entry into the PA’s pension payment system, or some other action.

Pull ACH (ACH Deletion) Return To Trust (Benefit Payment Check) Return to Trust (ACH Replacement Check) Return to Trust (Deduction Check) Stop and Reissue (Benefit Payment Check) Stop and Reissue (Benefit Payment Check) with Address Change Stop and Reissue (ACH Replacement Check) with Address Change Stop and Reissue (Deduction Check) with Address Change o When the BPD or PA employee completes the action and saves the eCARF, an automatic email generated by the collaboration tool alerts the initiator of the status of the request.

o The initiator prints the completed eCARF and scans it into the payee’s file where it is visible via the PBGC’s Image Processing System. PBGC may automate this process in the future.

o Stop pending ACH payments before submission to the ACH Operator upon PBGC eCARF request (“ACH deletions”) (see section 1.4.16.2 Performance Standards).

o Stop payment on already issued checks upon PBGC eCARF request (see section

1.4.16.2 Performance Standards).

1.4.5.2 After all approved changes have been processed, but prior to creating the ACH or paper check file, provide pre-check run exception reports to PBGC to prevent improper payments and other anomalies (BPD Reports see, 1.4.12.9). The exact nature of these reports is dependent upon the PA’s pension payment system. The following categories are provided as examples:

1.4.5.2.1 Potential duplicate payments.

PAGE 19 OF 334 16PBGC22R0008

1.4.5.2.2 Payment records without the necessary unique payment identifier needed to match the payment to PBGC’s system.

1.4.5.2.3 Payment status disagrees with PBGC’s system.

1.4.5.2.4 Deductions exceed gross payment.

1.4.5.2.5 Other exceptions (e.g., SSN changes that cannot be transmitted electronically).

1.4.5.3 Issue checks to PBGC payees to replace stopped payments upon PBGC request (Performance Standards 1.4.16.2).

1.4.5.3.1 Reissue stopped checks to permanent address.

1.4.5.3.2 Mail reissued checks upon PBGC request.

1.4.5.3.3 Issue replacement checks for stale-dated (1.4.1.8.4) checks and

1.4.5.3.4 Issue manual checks in rare situations.

1.4.5.4 Process ACH returns.

o Process ACH return entries from the ACH Operator and RDFIs, transmit electronic files containing sufficient information on returns so that they can be matched to the associated records on PBGC’s system (see 1.4.4.5).

o If the payee is not deceased, issue a replacement payment for ACH returns to a verified destination Performance Standards 1.4.16.2).

1.4.5.4.1 Provide a mechanism to notify PBGC of the returns (BPD Reports see 1.4.12.10).

1.4.5.5 Return funds to PBGC Account for cancelled payments

1.4.5.5.1 Checks stopped but not reissued.

1.4.5.5.2 Stale-dated checks (1.4.1.8.4).

1.4.5.6 Process, control, and document a very limited number of manual changes requested by approved BPD personnel to avoid improper payments.

1.4.5.6.1 In urgent situations these changes are communicated to the PA by:

- a faxed NFDE form (see 1.4.4.1); or

- a request submitted via PBGC’s collaboration tool; or

- an email from an authorized BPD employee. The email is imaged into the payee’s file which can be viewed by PBGC employees via PBGC’s IPS system;

or

- a phone call from an authorized BPD employee followed by an email which is imaged into the payee’s file.

1.4.5.6.2 Once each quarter, the PA shall email the BPD Manager requesting re-certification of the BPD personnel authorized to request these last minute manual changes. (BPD Reports see 1.4.12.11)

PAGE 20 OF 334 16PBGC22R0008

1.4.5.7 Process ACH Notices of Change (NOCs) and transmit electronic files with sufficient information on NOCs so that they can be matched to the associated records on PBGC’s system (see 1.4.4.5).

1.4.5.8 Recover ACH payments from RDFIs (Performance Standards 1.4.16.2).

1.4.5.8.1 Process and track ACH reclamations upon PBGC request to reverse payments made to deceased individuals.

1.4.5.8.2 Process and track ACH recoveries upon PBGC request to reverse payments made in error.

1.4.5.8.3 Process and track written demands (a.k.a. Letters of Indemnification – LOI) for payment to RDFIs upon PBGC request for payments not subject to ACH reclamation or subsequent to an unsuccessful reclamation or recovery.

1.4.5.8.4 Provide a monthly aging report for ACH reclamations, recoveries, written demands for payment, and fraud investigations still in process. (BPD Reports see 1.4.12.14)

1.4.5.9 Process and track ACH traces to determine the status of electronic payments upon PBGC eCARF request.

1.4.5.10 Provide copies of paid checks (front and back) not available to PBGC via the PA’s pension payment system upon PBGC eCARF request.

1.4.5.11 Adjust the electronic payment history of individual payees to accurately reflect the events that occurred (stopped payment, reissued payment, funds returned, etc.)

upon PBGC request (see section 1.4.16.2 Performance Standards).

1.4.5.12 Issue checks to PBGC payees or other entities to refund non-benefit payments upon PBGC request.

1.4.5.13 Process IRS tax levies deductions upon PBGC request.

1.4.5.14 Forward subpoenas, IRS tax levies, QDROs and other legal documents to PBGC for processing.

1.4.5.15 Assist with investigation of individual payment-related fraud upon PBGC request.

1.4.6 The PA shall support written and oral communications with or involving PBGC payees.

1.4.6.1 Print/mail checks, check stubs and statements with custom PBGC messages:

o Messages:

- Encourage a switch to direct deposit and usage of MyPBA on annuity checks (see center current check stubs).

- Direct questions to PBGC’s 800 number (see upper right of current check stubs).

- Instructions for address changes (upper right).

PAGE 21 OF 334 16PBGC22R0008

- Additional message promoting direct deposit on annuity checks (upper right).

- Statement that PBGC is a U.S. Government Corporation (upper right).

1.4.6.2 On check stubs include the year-to-date accumulation for each payment source (taxable, non-taxable, estimated, and guaranteed).

1.4.6.3 Print/mail required tax forms (e.g., 1099-R, 1042-S and 480.7C) to individual PBGC payees in accordance with IRS standards including corrected tax forms to account for payment adjustments authorized by PBGC (see 1.4.5.13). (Reports 1.4.15.2)

1.4.6.4 Print/mail paper statements to payees (Reports 1.4.15.3):

o When payee receives their first ACH payment (new payee or payee who previously received paper checks).

o When net benefit amount changes from one recurring ACH payment to the next (“net change of advice”).

o When net benefit amount is zero due to deductions equaling gross benefit (“advice of distribution”).

o When trustee to trustee transfers (e.g., IRA rollovers) are processed.

1.4.6.5 Insert ad hoc written communications with checks or other standard mailings upon PBGC request. Example inserts:

1.4.6.6 Use PBGC’s Document Management Center’s (DMC) address as the return address and the PBGC Customer Contact Center (CCC) phone number on outgoing written communications to individual PBGC payees. Do not include the PA address or phone number on these mailings, unless instructed by the COR.

1.4.6.7 Forward incoming mail and phone calls from PBGC payees to PBGC’s Document Management Center (DMC) and Customer Contact Center (CCC) respectively.

o In the event that (despite 1.4.6.6) the PA receives mail associated with individual

PBGC payees (e.g., subpoenas, levies, family members returning checks, etc.), the PA shall securely forward the documents via express mail to the PBGC Document Management Center (DMC) for processing.

o In the event that (despite 1.4.6.6) the PA receives phone calls from individual PBGC payees, the PA shall advise the caller to contact the PBGC Customer Contact Center (CCC).

o If the PA receives a check payable to the PA, intended to repay PBGC for a benefit overpayment, the PA shall mail a check made payable to PBGC the OBA lockbox.

1.4.7 PBGC may request the PA to support PSD with onboarding payees in newly terminated pension plans (a.k.a Plan Assumption).

PAGE 22 OF 334 16PBGC22R0008

1.4.7.1 Work closely with pension plan administrators and the plan’s paying agent to ensure a smooth transition of the benefit payment administration functions to PBGC.

PBGC estimates support would be needed for approximately 40 newly trusteed pension plans each year.

o Contact plan’s paying agent to inform that PBGC will transfer payment responsibility and notify of the date of the first payment. This contact would mostly be telephone communications.

1.4.7.2 Obtain check registers or other sources of payment data to be used for the payee data loading into PBGC systems.

o Provide the plan’s administrator or paying agent information on items needed in both paper and electronic format (encrypted “raw” data in ASCII delimited text format) that is to be sent to PBGC.

1.4.8 The PA shall use certain PBGC systems.

1.4.8.1 For communication, use PBGC’s email system and collaboration tool.

1.4.8.2 For exception processing, use PBGC’s web collaboration tool (eCARF portlets, etc.

– see 1.4.5.1).

1.4.8.3 For individual-payee research use PBGC’s Spectrum, and IPS.

1.4.8.4 For performance and other reporting, use PBGC’s web collaboration tool (PA

Acquisition Support Metrics – PAASM).

1.4.8.5 Additional details

1.4.8.5.1 Benefit Administration (BA) is PBGC’s pension recordkeeping system. BA consists of a collection of PBGC IT applications that maintain records for over

1.5 million participants in trusteed pension plans. BA applications include:

- NFDE (“Nifty”) is used for transmitting approved changes to the PA system and are described in section 1.4.4.1.

- The eCARF functionality of the PBGC web collaboration tool is used for exception processing and is described in section 1.4.5.1.

- The PAASM (PA Acquisition Support Metrics) functionality of the PBGC collaboration tool is the mechanism through which the PA uploads scheduled reports and other deliverables and BPD measures the PA’s performance.

- Spectrum is a web-based application which provides PBGC users with the ability to create, manage, edit, and review customer information and benefits data. Spectrum enables PBGC users to create/edit customer benefits and payments, suspend/resume customer payments, terminate/reinstate customer benefits, and view customer payment history information. 1.4.4.1 describes how benefit changes made in Spectrum flow to the PA.

- The IPS (Image Processing System) suite of products enables PBGC users to scan, index, and commit documents to the IPS repository and to retrieve them as necessary to support various business processes.

PAGE 23 OF 334 16PBGC22R0008

1.4.9 The PA shall support financial management activities in accordance with PBGC’s

Financial Operations Department (FOD) requirements.

1.4.9.1 Cash accounts: Establish cash accounts, each with a unique identifier, sufficient to segregate PBGC funds to the extent necessary to fulfill contract requirements and to efficiently account and provide reports for PBGC funds as well as to optimize cash management for PBGC’s benefit.

1.4.9.2 Short Term Investment Fund: Under PBGC’s direction, invest the benefit payment funds transferred to the PA in a Short Term Investment Fund (STIF). Draw down the STIF in an amount only large enough to cover payments presented. All income from the STIF must accrue to PBGC and be transferred to the appropriate PBGC U.S. Treasury account by the second business day of the following month.

The contractor shall provide financial statements for this fund including transaction reports and trial balance to PBGC every month. (FOD Reports see 1.4.14)

1.4.9.3 Insurance: The contractor shall obtain insurance for the disbursement account(s) to the maximum amount held in the account(s) on any given day. PBGC will wire transfer or transfer by ACH all funds needed to cover benefit payments. (BPD Reports see 1.4.12.12)

1.4.9.4 Cash Reconciliations: Provide monthly cash reconciliations for each account maintained on PBGC’s behalf for benefit payments within 30 calendar days of the following month. (FOD Reports see section 1.4.14). The reconciliations shall include the following:

o Beginning and ending cash balance.

o Funds transferred into the account, returned checks, returned ACH payments, stopped checks, purged checks, interest earned and anything else that increases the balance.

o Funds transferred out of the account to other PBGC accounts, checks cashed, ACH payments settled, tax remittances and anything else that decreases the balance.

o Outstanding checks, deposits in transit.

o Checks cashed prior to issuance date.

o Control log entries.

o Errors with explanations and other items affecting the reconciliation; and o Make all adjustments and reconcile them monthly

1.4.9.5 Calculate funding: After the final transmission and balancing of approved payment-related changes from PBGC associated with a given payment date, calculate total funding needed from PBGC for each of the following categories.

1.4.9.5.1 First of the month payments

- Corporate monthly pension

- Corporate monthly lump sum

- Corporate monthly lump sum split (e.g., part of the payment sent to the individual, part rolled into an IRA)

PAGE 24 OF 334 16PBGC22R0008

- Fleming monthly pension

- Fleming monthly lump sum

- Page-Collins monthly lump sum

- Other special situation monthly pension and

- Other special situation monthly lump sum

1.4.9.5.2 Weekly payments

- Corporate weekly pension

- Corporate weekly lump sum

- Corporate weekly lump sum split

- Fleming weekly pension

- Fleming weekly lump sum

- Page-Collins weekly lump sum

- Other special situation weekly lump sum

1.4.9.5.3 Daily payments (rare)

- Corporate manual checks and

1.4.9.6 Request funding: Submit requests for PBGC to transfer funds to support benefit payments to PBGC via PBGC’s collaboration tool no less than four business days prior to the first of the month. (FOD Reports see 1.4.14) (For sample funding requests, see attachments 15 and 16). PBGC will not pay overdraft or related service fees resulting from PA errors in the funding request process. If such fees accrue due to PBGC errors, they cannot be paid from benefit payment funds, they must be invoiced as a service upon approval by the COR. Each funding request must:

o Uniquely identify the funding request in accordance with PBGC’s numbering scheme.

- BP-PN-23-001 (first pension funding request for FY2023).

- BP-LS-23-001 (first lump sum funding request for FY2023) and

- BP-MN-23-001 (first manual funding request for FY2023).

o Identify the total predicted payment the PA will issue on PBGC’s behalf for this group of payments o Identify the account number to which PBGC should wire the funds o State the date the funds are to be deposited.

o Show the breakdown of the total amount to be funded into different PBGC funds

(1, 2, 7), programs (e.g., Missing Participants) and settlements (e.g., Page-Collins, Rettig). See 1.4.9.7 and 1.4.9.8 for more details.

o Include backup documentation evidencing how the funding was calculated based on benefits approved by PBGC and transmitted to the PA. Backup documentation must include:

PAGE 25 OF 334 16PBGC22R0008

- A report that ties each request for funds to a specific check run (1.4.1.9) that identifies the type of payment production run, the total number of payments and gross dollar amounts issued, total deductions and total net.

Documentation that covers adjustments or corrections (when funds are requested that do not produce a benefit payment. For example: bookkeeping adjustments, corrections for over-withholding of federal income tax, returns to the trust fund in error, etc.)

1.4.9.7 Separate Accounting: Separately account for benefit payments associated with different PBGC funds (1, 2, 7), programs (e.g., Missing Participants), settlements (e.g., Page-Collins, Rettig), special plans (e.g., Fleming) and within each fund separately account for different categories of benefit payments.

1.4.9.8 Single-Multi Report (see attachment 17): Provide PBGC’s Financial Operations Department (FOD), via the collaboration tool, a monthly report showing the following information about benefit payments: (FOD Reports see 1.4.14) (Performance Standards 1.4.16.3) o The number of PBGC plans, the number of payees and the total dollar amount of the following classes of benefit payments: - Recurring payments (monthly, annual, quarterly, semi-annual).

- Lump sum payments.

- Special payments (back payments and off-cycle payments) and

- Federal taxes withheld.

o For each of the following funds, programs, or settlements:

- Fund 1: Single employer plans with DOPT before 10/1/1988.

- Fund 2: Terminated multiemployer plans.

- Fund 7: Single employer plans with DOPT on or after 10/1/1988.

- Missing Participants Program.

o The multiemployer plans in Fund 2 are listed below:

- Millinery Workers Ret Fund (10000100)

- Millinery Retirement Plan (10000200)

- Millinery Retirement Fund Local 98 (10000300)

- Milk Industry Local 680 Pension Plan (10000400)

- Barbers Union Local 760 Pension Plan (10000800)

- Barbers Union Local 123 Pension Plan (10001200)

- Chicago Electrotypers Pension Plan (10001700)

- Local 50 Candy And Confectionery Union Ind Pension (10004300) and

- S&L Novelty Retirement Plan (10032700)

1.4.9.9 Return of funds to PBGC: Provide PBGC’s Financial Operations Department (FOD) and/or PBGC’s custodian bank a periodic report of monies intended to fund benefit payments that have been returned for the following reasons (FOD Reports see 1.4.14 regarding recoupments):

PAGE 26 OF 334 16PBGC22R0008

o Stop payments on checks (and check not reissued).

o ACH returns (but no replacement check was issued.

o Checks not cashed after 180 days and therefore no longer negotiable (purged or stale dated checks):

o Other reason (with explanation).

1.4.10 The PA shall perform all services in observable compliance with PBGC Enterprise

Cybersecurity Office (ECD) policies and procedures.

1.4.10.1…