MetLife Interface and Transmittal

Purpose:  Use this document as a reference for how to understand the MetLife interface andtransmittal's relationship to PeopleSoft at a high level in ctcLink.

Audience:  Benefits Administrators, Payroll Adminitrators

Before MetLife File Gets to PeopleSoft

  1. A report is sent to the technical team at SBCTC containing all college data, both schools in Legacy and PeopleSoft
    • This report contains more detail that the information loaded into PeopleSoft, including all changes since the last file was sent to the technical team
    • A process is run that splits the file ( called “bursting”)
  2. The report is split out by the technical team at SBCTC by college
  3. Once the report is split, the file becomes available in SUE (Secure Upload Engine) for PeopleSoft to grab using the nightly inbound process
  4. After the split is run, a report is generated and offered to ctcLink colleges for validation in SUE
    • College administrators will need to access SUE to retrieve their validation CSV file
    • Confirm the CSV changes match entries in PeopleSoft
    • Generally an email will come from SBCTC (currently from jboesenberg) to announce the upload has occurred
    • Another email follows the first with your login and password
    • New administrators should send in a service desk ticket to request access (and it will be vetted for security purposes)
SBCTC Upload File Manager section

MetLife Inbound File

Navigation:  Main Menu > Benefits > CTC Custom > CTC Intrfaces > Inbound MetLife Billing

  1. This is a change only (add, change, remove) file sent from MetLife with deduction data.  Any change to deduction data, would cause an employee to be included in the file.
    • Specifics of the file construction can be found in the interface technical document I-119
    • SSN is used as the employee identifier
  2. The file is generally produced 4 days prior to payroll, but is scheduled to run every night so a human being does not necessarily need to run this process.
    • The Inbound file, like the Outbound file, includes all colleges so once the file is generated and loaded there will be no new file until the next pay period
  3. Generally, new data will result in new effective dated records being added to the general deduction for that employee, but it is possible that corrections will be sent requiring the update of an existing record.  These would be recognized using the dates based on pay period end date.  
    • This can start the deduction, change the deduction, or stop the deduction

Note: PeopleSoft table PS_CTC_MET_REMIT maintains the billing file pay end dates that have been processed and will need to be updated for any reruns required.

Inbound MetLife Billing page

MetLife Outbound File

Navigation:  Main Menu > Benefits > CTC Custom > CTC Interfaces > Outbound MetLife Remit

Note: The outbound process is consolidated, so all runs of a specified payroll must complete successfully at all colleges specified.  If all colleges specified have not completed the specified payroll, do not send the MetLife Remit file.

  1. Outbound file covers all people who had MetLife Insurance deduction 000065 taken from their paycheck that pay period.
    • Specifics of the file construction can be found in the interface technical document I-120
  2. This run is completed by a specific employee in SBCTC, and is not run by the colleges themselves
Inbound MetLife Billing page