Skip to main content
Skip table of contents

ORS-PSERS - Monthly Purchase Agreement Or Payroll Authorization File - File Layout and Data Mapping

The default file name for the Monthly Purchase Agreement or Payroll Authorization file is TDA.<Entity Number>.txt.

The following table lists the positions, names, descriptions, formats, and data source or valid values of the Monthly Purchase Agreement or Payroll Authorization file.

Position

Name

Description

Format

Data Source or Valid Values

1 – 5

RU (Reporting Unit) Number

The five-digit organization number. The first four digits are the number assigned to the individual reporting unit. These should be followed by a zero except for Henry Ford Community College, which has a trailing 1.

9(5)

Retrieved from the TDP Reporting Unit Number field on the Human Resources Profile – State page.

6 – 14

Agreement Number

The employee’s TDP agreement number from the payroll authorization record associated with the TDP deduction code.

9(9)

Retrieved from the Agreement No. field on the Tax Deferred Payments (TDP) form on the Tax Deferred Payments (TDP) tab of the MI ORS-PSERS (Public School Employees Retirement) page.

15 – 22

Invoice Number

The employee’s TDP invoice number from the payroll authorization record associated with the TDP deduction code.

9(8)

Retrieved from the Invoice No. field on the Tax Deferred Payments (TDP) form on the Tax Deferred Payments (TDP) tab of the MI ORS-PSERS (Public School Employees Retirement) page.

23 – 25

SSN3

The first three digits of the employee's Social Security Number.

9(3)

Retrieved from the Social Security field on the Demographic tab on the MI ORS-PSERS (Public School Employees Retirement) page.

26 – 27

SSN2

The middle two digits of the employee's Social Security Number.

9(2)

Retrieved from the Social Security field on the Demographic tab on the MI ORS-PSERS (Public School Employees Retirement) page.

28 – 31

SSN4

The last four digits of the employee's Social Security Number.

9(4)

Retrieved from the Social Security field on the Demographic tab on the MI ORS-PSERS (Public School Employees Retirement) page.

32 – 39

Agreement Date

The employee’s TDP agreement date.

MMDDYYYY

Retrieved from the Agreement Date field on the Agreement Information form of the MI ORS-PSERS - Reference Tables - Purchase Agreements page.

40 – 48

Filler

Fill with nine zeros.

9(6)V99

The valid value is 000000000.

49 – 56

Billing Amount

The employee’s TDP billing amount.

9(6)V99

Retrieved from the Billing Amount field on the Agreement Information form of the MI ORS-PSERS - Reference Tables - Purchase Agreements page.

57 – 61

Service Credit Years Available

The number of service credit years available.

9(2)V999

Retrieved from the Service Credit Years Available field on the Agreement Information form of the MI ORS-PSERS - Reference Tables - Purchase Agreements page.

62 – 69

Filler

Fill with nine zeros.

9(6)V99

The valid value is 000000000.

70 – 74

Service Credit Purchased

The number of service credits purchased.

9(2)V999

Retrieved from the Service Credit Purchased field on the Agreement Information form of the MI ORS-PSERS - Reference Tables - Purchase Agreements page.

75 – 82

Scheduled Deduction Amount

The scheduled deduction amount.

9(6)V99

Retrieved from the Deduction Amt field on the Tax Deferred Payments (TDP) form on the Tax Deferred Payments (TDP) tab of the MI ORS-PSERS (Public School Employees Retirement) page.

83 – 84

Service Purchase Type

This field is no longer used.

Fill with two zeros.

99

The valid value is 00.

85 – 86

Frequency of Pay

The employee’s pay frequency.

99

Retrieved from the Frequency of Pay field on the Agreement Information form of the MI ORS-PSERS - Reference Tables - Purchase Agreements page.

87 – 94

Filler

Fill with nine zeros.

9(6)V99

The valid value is 000000000.

95 – 102

Billing Due Date

The billing due date.

MMDDYYYY

Retrieved from the Billing Due Date field on the Agreement Information form of the MI ORS-PSERS - Reference Tables - Purchase Agreements page.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.