PERS Employer Outreach, Communication and Education

Welcome!

Spring 2016 Employer Outreach Adjusting posted DTL1 & DTL2 data.

1

V3 March 14, 2016

Contents • Congratulations and thanks for your fine work!

2015 reporting statistics. • Reporting contributions.

Contribution reporting changes effective January 1, 2016. • Adjusting Employment History.

Requesting adjustments via Demographic Correction Request (DCR). Hire Intent. Position type. Termination, rehire and waiting time.

• Adjusting Posted Wage, Hour & Contribution Data. Wage code use and adjustments. Who uses Work Period Begin/End Dates.

• As the end of a PERS career approaches: DTL1-02 Termination record. Final DTL2 record.

• Employer Statement Review. • Invoice Payment. • 2016 Regular Report Dates, by report frequency. • 2016 ACH Transfer Dates.

2

Congratulations and Thanks for your fine work!

3

At the close of the Annual Reconciliation process for these years: 2014 2015

Total records submitted: 3,552,457 3,684,865 1% Increase

Total records Unposted: 8564 5681 34% Decrease

Reporting Contributions. (Procedural changes effective January 1, 2016)

4

Records: DTL2 Wage and Service Reporting contributions for the first pay date after membership is established.

• Effective January 1, 2016 statute will be amended to require contributions for wages attributable to services performed during the first full pay period following the six month wait time. The procedure applies to all who establish

membership on, or after, January 1, 2016. The procedure is described in Employer

Announcement #97

5

Records: DTL2 Wage and Service Reporting contributions for the first pay date after membership is established.

6

Example 2: On or after January 1, 2016: Reporting contributions for the first pay date on or after OPSRP membership is established: An employer’s pay period begins December 28, 2015 and ends January 8, 2016, with a January 22, 2016 pay date. A reported individual becomes an OPSRP member January 1, 2016. The individual works 80 hours for the two-week period for a reported salary of $2000.00 Reporting by a Local Government employer: Reporting by a non-Local Government employer: For this pay period WPBED are used on both of the Non-local government employers NEVER use WPBED. two required DTL2 records. Salary on the 1st record is For this pay period, salary is “Non-subject” and no “Subject” and salary on the 2nd record is “Non-subject”. contributions are entered. Contributions are entered on neither record.

12/28/2015 01/01/2016 01/08/2016 12/28/2015 01/01/2016 01/08/2016

Waiting Time Active Service Waiting Time Active Service

DTL2 #1: DTL2 #2: Pay Date: 01/22/2016 Pay Date: 01/22/2016 Work Period Begin Date: 12/28/2015 Work Period Begin Date: 01/01/2016 Work Period End Date: 12/31/2015 Work Period End Date: 01/08/2016 Hours Worked: (Regular) 40.00 Hours Worked: (Regular) 40.00 Reported Wage Code: 01 Reported Wage Code: 01 Subject Salary, Regular: 1000.00 Subject Salary, Regular: (blank) Non-Subject Salary: (blank) Non-Subject Salary: 1000.00 Contributions: (blank) Contributions: (blank)

DTL2: Pay Date: 01/22/2016 Work Period Begin Date: (blank) Work Period End Date: (blank) Hours Worked: (Regular) 80.00 Reported Wage Code: 01 Subject Salary, Regular: (blank) Non-Subject Salary: 2000.00 Contributions: (blank)

12/28/2015 12/31/2015 01/01/2016 01/08/2016

Adjusting Employment History.

7

Changes during a member’s career. The Demographic Change Request (DCR)

8

Correcting posted DTL1 records. Employers can change a member’s name, address and very carefully , a Social Security number, but employers cannot change posted employment history. Employers must ask PERS staff to change a member’s posted employment history, and that request is made using the Demographic Correction Request form. The DCR is an online form, and can be found by two different methods: 1) Begin by clicking the “View Employee Info” link: 2) Begin by clicking the “Work List” link:

1A) Enter the member’s PERS I.D. or SSN and click “Search”

1B) The member’s employment history with you, the employer, appears. Click the “Work with Demographic Correction Request” link. On the next page…

…and the Demographic Correction (DCR) History appears. Click the “Create Demographic Correction Request (DCR)” link… and the member’s employment history appears.

2A) On the Work List page, click the “Create Demographic Correction Request (DCR)” link. 2B) Enter the member’s PERS I.D. or SSN and click “Search”…

1C) Click the “Create Demographic Correction Request” link…

Changes during a member’s career. The Demographic Change Request (DCR)

9

Correcting posted DTL1 records. The member employment history is with you, the employer; no other employer history is included. A member employment history may have many job segments.

1) Click the job segment to be changed.

2) The change format appears. Enter ONLY the changes you want made; its not necessary to fill every field. 3) After you’ve entered your desired changes, add comments to clarify what you want done. If you’ve requested a Position Type change or requested action which will alter a Contribution Start Date, please enter the contribution type (MPPT, MPAT or EPPT) in effect during the time period affected by the requested change. Adding comments is always helpful and can prevent the need for additional clarification. When in doubt, please add comments. 4) When all required changes and relevant comments have been entered, click “Save” which will route this form back to your ESC Account Team representative. Your ESC Account Team representative will make the requested changes or route the form to other PERS sections to have changes made. When all changes have been made, you will receive an EDX e-mail message indicating your DCR is complete.

1)

2)

3)

4)

“Hire Intent” • The employer’s expectation of hours to be worked by

any employee in a specific position in any calendar year. “Would any employee in this position normally be

expected to work 600 or more hours in any calendar year while working for me, the employer?”

If “yes” the position “hire intent” is “qualifying”. DTL1 status code is 01. DTL2 wage code is 01.

Wage codes 04, 05, 08 are used in periods of “qualifying” service for specific reporting requirements.

If “no” the position “hire intent” is “non-qualifying”. DTL1 status code is 15. DLT2 wage code is 02.

10

Changing “Hire Intent” or “Position Type” • 1) States the employer’s expectation of present and

future hours of service per calendar year by anyone in that position. Hire intent for an employment segment will not change

unless the employer makes a change by terminating and rehiring into a segment with different hire intent, or submits a DCR asking PERS staff to make a change.

• 2) Sets the “position type” for at least the year of hire. Position type can change each calendar year based on total

service time that year. 600 hours total service in any calendar year would require the

member account to have an active (qualifying) position for that year.

11

“Hire Intent”

12

Example: A) Hire Intent: Non-qualifying B) Position Type:

650 hrs. 540 hrs. 600 hrs. 550 hrs.

Year 1 Year 2 Year 3 Year 4 Qualifying Non-qualifying Qualifying Non-qualifying

Employment segment hire intent will not change unless the employer makes a change (termination and rehire) or asks PERS staff to make a change. Position Type can change each calendar year based on total service time in that year.

13

When “Position Type” is changed in any calendar year:

• For “Position Type” change from “non-qualifying” to qualifying”: Posted DTL2 wage code 02 records will be changed to wage code 01. Contributions for the year up to the change date will be calculated and

invoiced. • For “Position Type” change from “qualifying” to “non-qualifying”:

Posted DTL2 wage code 01 records will be changed to wage code 02. Contributions withheld up to the change date will be credited to the

employer. • Find these changes:

Through “View Year-to-date Wage and Contribution Summary” link in each EDX page site nav. area

As invoices or credits on employer statements after PERS corrections are complete

• Any difficulties with posting adjustment records may be addressed with your ESC account representative

Termination, Rehire and Waiting Time.

14

• Termination, rehire and waiting time: An employer can change position hire intent by terminating the employee and rehiring the employee into another position with different hire intent.

• Waiting time will continue unbroken if the individual is terminated and rehired with the same employer with a break of less than 30 working days (a working day is any day the employer is open for business. This will be assumed to be any day PERS is open for business, Monday - Friday, unless the employer communicates a different date). If the break is greater than 30 working days, the waiting time will start over, with another full six calendar months to be completed. A period of reported Leave w/o Pay (LWOP) will not restart the waiting time period for Tier One/Tier Two members at any point or for OPSRP members on or after 11/23/2007, just extend the waiting time by the duration of the LWOP period.

• The 30 working day break DOES NOT apply to summer break for education employers IF the employer-employee relationship continues throughout summer break. If the employer-employee relationship continues the waiting time also continues. If an education employer terminates an individual who is still in their waiting time when a school year ends and 30 consecutive working days elapse before the individual is hired for the fall term, the waiting time starts over at the fall term hire date. This will affect an employee’s OPSRP Contribution Start Date (CSD) and service credit.

Adjusting Posted Wage, Hour and Contribution Data

15

16

DTL2 Wage Codes and Their Use

Wage Code:

Description and Use Use with service type: Must salary be entered?

Must hours be entered?

Must contributions be entered?

Use permitted during LWOP?

01 Regular wages: Report employee wages for periods of qualifying service.

Qualifying; can be used during waiting time.

Yes Yes Yes, after waiting time completion.

NO

02 Regular/Non-Qualifying: Report employee wages for periods of non-qualifying service.

Non-Qualifying ONLY Yes Yes NO NO

04 Retroactive Payment * See use outlined below. A retroactive payment should be reviewed with the employer’s ESC Account Team representative prior to submission.

Qualifying; can be used during waiting time.

Yes Yes Yes, after waiting time completion

NO

05 Positive Adjustment: Report a positive difference between previously posted information and revised information.

Qualifying; can be used during waiting time.

May be used without salary.

Hours must be entered if salary

is entered.

Yes, after waiting time completion.

NO

06 Negative Adjustment: Used with a “mirror image” of the previously posted record to “back out” originally posted information.

Qualifying; can be used during waiting time.

May be used without salary.

May be used without hours.

Yes YES

07 Retired/No Contributions: The only wage code used to report retiree wages.

Retirement ONLY Yes Yes NO NO

08 Contributions/No Service: Used to report wages and contributions for periods of service without hours. Hours cannot be entered with this wage code.

Qualifying ONLY Yes NO Yes YES

11 USERRA Qualifying Wages: Use this code as directed by your ESC Account Team representative. These are wages that would have been paid if the member had not been called to military service.

USERRA ONLY Yes Yes Yes N/A

14 Negative Adjustments/No Contributions: Used to make negative adjustments to previously posted wage code 02-Regular/Non-Qualifying or 07-Retired/No Contributions records.

Non-qualifying & Retirement ONLY

Yes NO NO YES

16 Negative Adjustment-USERRA Wages: Used to adjust previously posted USERRA wages.

USERRA ONLY Yes NO Yes N/A

* Retroactive payments: ORS238.008(1): “…salary includes retroactive payments of wages made to an employee to correct a clerical error.” (2):“…salary includes retroactive payments of wages made to an employee pursuant to a judgment, administrative order, arbitration award, conciliation agreement or settle agreement that resolves a dispute or claim based on the employee’s right under employment or wage law or under a collective bargaining agreement.”

Adjusting posted wage, hour and contribution data.

17

Correcting Posted DTL2 records: 1) Correcting posted DTL2 records is done with DTL2 positive or negative adjustment wage codes. The adjustment codes are: 05- Positive adjustment (used with wage codes 01 and 04). 02- Positive adjustment (used with wage code 02). 06- Negative adjustment (used with wage codes 01, 08, 04 and 05). 14- Negative adjustment (used with wage codes 07 and 02). 16- Negative adjustment (used with wage code 11, USERRA wages). DO NOT submit an adjustment record unless the original record has posted. Un-posted records can be edited until correct. Positive adjustments are a single-step process, adding only the positive differences between originally posted data and what should have been posted. Negative adjustments are a two-step process: 1) Remove (“back out”) the previously posted data with a record identical to the posted original (a “mirror image”) but using a negative adjustment wage code, then… 2) Re-post the corrected, reduced values using a positive adjustment wage code. Do all negative adjustments for a posted record before any positive adjustments for that record. Let each adjustment post before submitting the next adjustment. INCLUDE in any adjustment record: A) The paydate and member Social Security number used in the previously posted record. B) The same Work Period Begin/End Dates in the previously posted record, if they were used in that record.

1)

18

Adjusting posted wage, hour and contribution data.

• Wage code 04, Retroactive Payment Includes wages paid outside the normal reporting

process due to clerical error or pursuant to judgment, administrative order, arbitration award or settlement agreement.

If statutory requirements are met, such wages are allocated to (and deemed paid in) period(s) in which hours were worked (or would have been worked). Allocation must be determined by PERS staff. Always contact your ESC Account Team representative before

posting records with wage code 04. Retro wages do not include:

Back wages paid pursuant to new wage rates reached by collective bargaining and applied to prior periods.

19

Adjusting posted wage, hour and contribution data.

• Wage code 07, Retired/No Contributions. Used only to report retirees returning to work as retirees, with or without a calendar

year work hour limit. Used only in Regular reports.

• Wage code 08, Contributions/No Service. Report wages with no hours worked.

Example: Reporting payments for teachers during summer break. At termination, to report LSP or LSVP for Tier1/Tier2 (with contributions) or

OPSRP (no contributions) members if no hours were worked. Must be used to report any LSP or LSVP payments made to a member who

terminates while on LWOP. Used only in Regular reports. Does not affect service credit. Can be used to report subject salary (with contributions) and non-subject

salary (no contributions). Used to report any back pay when it is paid and hours were already reported

for that period. Back pay can be reported for PERS purposes up to 31 days after termination.

Who uses Work Period Begin/End dates?

20

The DTL2 record is submitted with each Regular report, and is used to report wages, hours and contributions. We’ll now review this record from top to bottom. 1) Work Period Begin/End Date: If you are a “local government” employer you must report salary for the period it was worked for your Tier 2 and OPSRP employees. You can also report your Tier 1 employees in this fashion, just to save time and report uniformly. As a “local government” employer you use Work Period Begin/End Dates to indicate the period reported salary was worked. ONLY “local government” employers use Work Period Begin/End Dates. Non- “local government” employers, such as schools, NEVER use Work Period Begin/End Date fields on DTL2 records. How can you determine if your organization is a “local government” employer, and must report salary for the period it was worked? Your first indication is your employer number. Employer numbers 2000-2789 indicate local government status, but you should confirm this status through Oregon Revised Statute (ORS) 174.116. ORS 174.116 is a list of organizations defined as “local government”. You can use a single DTL2 record with Work Period Begin/End Date: and Pay Date fields filled if: A) Pay period begin, pay period end and pay date are in the same month, or B) Pay period begin and end are in one month and the pay date is in the next

month. However, if the pay period begins in one month and ends in the next month, you must use two DTL2 records to report all employees for that pay period, because Work Period Begin/End Dates WILL NOT CROSS monthly boundaries. **PLEASE NOTE: If you are a local government employer submitting two DTL2 records for pay periods crossing monthly boundaries, and you’ve just hired a Tier One/Tier Two P&F (Job Class 2) member who is participating in the Unit program, or have a current Tier One/Tier Two P&F (Job Class 2) member just beginning participation in the Unit program, then please enter unit contributions ONLY IN ONE OF THE TWO DTL2 records. Please DO NOT split the Unit contribution between the two DTL2 records.

1)

Who uses Work Period Begin/End dates?

21

Work Period Begin/End Date: Example: A local government employer has a pay period which begins August 24, 2014, ends September 6, 2014, with a pay date of September 19, 2014. This pay period crosses monthly boundaries, so two DTL2 records must be used to report all employees in this pay period. One of these employees has a salary of $2000.00 for the pay period and works 80 hours. An employer can split wages, hours and contributions for the pay period between the two records any way they choose, but all reported wages, hours and contributions for each reported employee must be covered by the two records. This two-week pay is split in half by the monthly boundary, so the employer elects to split the wages, hours and contributions evenly between the records. The first DTL2 record for our example employee: Work Period Begin: 08/24/2014 Work Period End: 08/31/2014 Hours Worked (Regular): 40 Subject Salary, Regular: 1000.00 Contributions (MPAT in this example): 60.00 Pay Date: 09/19/2014 The second DTL2 record for our example employee: Work Period Begin: 09/01/2014 Work Period End: 09/06/2014 Hours Worked (Regular): 40 Subject Salary, Regular: 1000.00 Contributions (MPAT in this example): 60.00 Pay Date: 09/19/2014

# 1 # 2

Clearing Records: Points to consider • For DTL1 records:

Have you included the status code for the action taking place? (Qualifying or Non-Qualifying Hire, Termination, On Leave, Returning from Leave, etc.)

Have you included the status date? For 02/Termination records, did you include “Last Day Service”? Has the final DTL2 record posted before you submitted the DTL1 Termination

record, and is the DTL2 final pay date within 31 days of the Regular report pay date? If used, is the DTL2 work period end date equal to the DTL1 “Last Day Service”?

For status changes, are status events in date order (Ex: For a termination followed by rehire, are the status events in the correct date order, and don’t overlap)?

If you intended to pay out accrued paid leave, did you wait to put the individual on leave with PERS until you paid out all the accrued paid leave?

For an employee on leave, did you submit the leave record (military leave, legislative leave, family leave, etc) before submitting a DTL1-08/Return from Leave?

For new hires, have you included job class information (Job Class, Average OT Hours, Contract Number of Months for Job Class 9) Note: Job class information should not be included on 02/Termination records.

22

Clearing Records: Points to consider (continued) • For DTL2 records:

For new hires, has the DTL1 new hire record posted before you begin submitting DTL2 records? Did you use a wage code which requires entry of regular hours?

All wage codes except 08 (Contributions, No Service), 06 (Negative Adjustment), 14 (Negative Adjustment, No Contributions), and 16 (Negative Adjustment, USERRA wages) require entry of regular and , if reported, overtime hours.

Did you use a wage code which requires entry of contributions? Contributions should not be included for waiting time periods. Contributions are 6% of total subject salary, made by MPPT, MPAT or EPPT contribution method. Wage codes 01, 04, 05 and 11 require contributions after waiting time. Wage code 08 requires contributions,

but no hours, and will not post during waiting time. Is Gross Salary the sum of all other salary types on the DTL2 record?

Subject Salary, Regular + Subject Salary, Overtime + Non-Subject Salary + Lump-sum Payoff + Lump-sum Vacation Payoff

Leave the job class information blank unless you’re changing the member’s job class on the DTL2 record

If you are adjusting posted DTL2 records: For multiple adjustments to the same record, did you let each adjustment post before submitting the next? Did you do negatives first, then (if required) positives?

23

Clearing Records: .dat files • A .dat file automates reporting of PERS demographic, wage and service data

through payroll software systems • A .dat file:

Is an ASCII ‘text’ file with a specific format Has a specific naming format which includes “0” and the employer’s four digit

PERS employer number, the current report date, and the “.dat” suffix Ex: 09999.01312012.dat

May have any number of data records, but MUST have a “header” record and a “footer” record

24

Clearing Records: common.dat file errors

25

The date in the .dat file name must match the report date in the header record. The .dat file will be rejected in batch if the dates are not identical.

The record count in the footer record includes only data records in the file, and does not include the header and footer record. In this example, there are 732 data records in this .dat file. The file will be rejected in batch if the count is incorrect.

As the end of a PERS career approaches: • The member:

Begin retirement education. Register for member retirement education presentations. Request benefit estimates. Choose a retirement date.

PERS members retire only on the first of any month. Qualified for PERS retirement by age or total service time. Financially able to retire.

Within 90 days of the chosen retirement date: Register for a Retirement Application Assistance (RAAS) session. Submit all PERS retirement forms.

Resign all PERS-covered employment prior to the chosen retirement date. Resignation must be effective no later than the last day of the month prior to the

PERS retirement date. • PERS employers:

Submit DTL1-02/Termination record after member submits resignation. Resignation must be effective no later than the last day of the month prior to the

PERS retirement date. Example: For a July 1st PERS retirement, resignation from all PERS-covered

employment must be effective no later than June 30th. • PERS staff:

Begins member account review at the member’s retirement date.

26

Member termination and retirement: DTL1-02/Termination record

27

• Unused Sick Leave hours are reported only with DTL1-02/Termination records. Any lump-sum payout of unused sick leave is considered non-subject salary for Tier One/Tier Two and OPSRP members, and should be reported as non-subject salary. Unused sick leave hours paid out cannot also be reported as unused sick leave on DTL1-02 records.

• For PERS reporting sick leave accumulates at the lowest accrual rate of any employee entitled to sick leave, with a maximum of 8 hours/month. Employers may allow a greater accumulation amount per month, but a maximum of 8 hours/month can be accrued for PERS reporting (i.e., sick leave is “capped” at that 8 hour/month maximum). Sick leave use rate occurs at the employer specified rate, possibly greater than 8 hours/month.

• Transferred sick leave is an employee’s unused sick leave transferred to you from another employer. A group of employers may agree to allow accumulated sick leave to move between those employers with an individual who changes employment within that group of employers.

• Reinstated sick leave would be hours retained by an employer when an employee departs employment and credited to that employee upon re-employment.

• SB 454, the “sick time” legislation passed in the 2015 legislative session, DOES NOT affect the PERS sick leave program.

02-Termination marks the end of the employer-employee relationship, effective on the Status Date. Last Day Service must be entered on a termination record. Last Day Service is the last date the individual worked or was on paid leave. Last Day Service can be the same as the termination date or before the termination date, but Last Day Service can never be after the termination date.

Final DTL2 Wage and Service

28

When reporting wages, hours and contributions ONLY “local government” employers use Work Period Begin/End Dates. To avoid suspension of the employee’s final DTL2 record the Work Period End Date should be on or before the “Last Day Service” date on the DTL-1/02 Termination record. The pay date for that final record must be within 31 days of the employee’s termination date. Non- “local government” employers, such as schools, NEVER use Work Period Begin/End Date fields on DTL2 records. Non-local government employers need only be sure that the pay date for the employee’s final DTL2 record is within 31 days of the employee’s termination date.

Employer Statement Review.

29

Statement and Invoice Enhancements effective August 2014.

• Why were the enhancements made? Employer payments are credited to the oldest receivables

(outstanding invoices) first and allocation of payments between plans was not clear.

Compliance with IRC 415 reporting requirements. IRC 415 limits contribution and payments made by retirement plans.

• What the enhancements do: Statements are divided by plan with three main areas: IAP. Health insurance subsidies: RHIA & RHIPA. Pension (OPRSP, Tier One/Tier Two, UAL and Side

Accounts).

30

31

Beginning Balance is any remaining balance due carried forward from the last statement period. Deposits will be allocated to the beginning balance. Pension balance represents “normal cost”, the actuarial value of benefits assigned to the next year of service for everyone working for you now and the UAL. RHIA/RHIPA invoice amounts represent retiree health insurance subsidies. The RHIPA subsidy covers only Tier One/Tier Two state employees between the retirement and Medicare eligibility. The RHIA subsidy is available to all Tier One/Tier Two retirees beginning at Medicare eligibility if they also participate in the PERS retiree health insurance program. OPSRP retirees are not eligible for health insurance subsidies. Unfunded Actuarial Liability as part of Pension and RHIA/RHIPA costs can be found through their respective “UAL…” links. Any UAL credits appear in parentheses and may arise from side account credits or negative adjustments made to member records. UAL represents the difference between assets and liabilities.

32

This is UAL information for the Pension and RHIA/RHIPA entries on the previous slide. UAL is the Unfunded Actuarial Liability for these segments of the current invoice. There is no UAL for IAP contributions. The UAL rate for all rate categories (PERS and OPSRP, General Service and Police & Fire) can be found in the “Your Current Contribution Rates” table on the employer’s online statement EDX page, found through the “View Your Statement” link in the Site Navigation area of any EDX page.

33

Invoice statement detail can be found by clicking the invoice number link under the “Invoice Details” heading at the bottom of the statement page. This will give a breakdown of IAP and Pension costs by program for each program member with contributions invoiced on the statement. Negative adjustments will be included in the detail costs, and any UAL adjustments associated with a specific negative record adjustment will be found through the “UAL…” link, identified by invoice number.

EDX E-mail statement notification. • This function was restored January 21, 2016. • This statement reflects correct invoice totals for each named program.

The statement when first opened may indicate different totals for each program. Close and re-open the statement, and totals will match those in the EDX e-

mailed statement notification. A resolution of this problem has been identified and will be scheduled for installation.

Statement notification example:

34

EMPLOYER STATEMENT POSTED 01234 – SMITH-JONES, CITY OF A new statement was posted to your account on 03/04/2016. Please return to the website to take the appropriate action on this statement. Statement Date: 2016-03-04 Due Date: 2016-03-11 Statement IAP Amount: $ 502.19 Statement Pension Amount: $ 0.00 Statement RHIA Amount: $ 37.66 Statement RHIPA Amount: $ 0.00

Invoice Payment • All PERS payments are made electronically by ACH

(Automated Clearing House). • The employer can choose the method of ACH Payment: ACH form(s): www.oregon.gov/pers/emp/pages/index.aspx

> “Employer Forms” (under Paper Reporting-Payroll/Electronic Remittance): “ACH agreement”/ “ACH Debit Authorization” ACH Credit (push): Employers transfer payment to a PERS

bank account to which access has been granted by PERS. ACH Debit (pull): PERS withdraws money from an employer

bank account to which access has been granted by the employer.

35

Invoice Payment • ACH payments are due on the 5th business day after a statement date.

Example: November 5, 2016 falls on Saturday; the 5th-of-the-month statement will be

generated during EDX batch processing Friday evening, November 4. ACH Credit/Debit payment activity will be effective the 5th business day after

statement generation. Veteran’s Day holiday is Friday, November 11, 2016, so ACH Credit/Debit payment activity will be effective Monday, November 14, 2016.

ACH Credit/Debit activity MUST BE DONE by the 5th business day after statement generation. Statement invoice amounts appear on the EDX e-mail statement notification message.

• Employers making payments by ACH Debit receive a notification message through EDX on the 5th business day after a statement date:

36

• Reference: ORS 238.225, 238.075, 238.710. OAR 459-005-0225, 459-009-0100, 459-070-0110

2016 Regular Report Dates, by report frequency:

37

2016 ACH Transfer Dates:

38

Questions?

39