Entering Multiple EmpowHR Actions Within the Same Day 

The following processing tip will assist EmpowHR users when entering multiple actions or documents effective on the same day for the same employee.

Worklist

Users are reminded to view their worklist daily upon login to check the status of each action (e.g., Applied, Suspense, etc.).

Personnel Actions and Address Documents

Agencies may enter accession personnel actions and address documents on the same day for the same employee in EmpowHR.

• Personnel actions and payroll documents process through the Personnel Input and Edit System (PINE).
• Personnel actions process through PINE before payroll documents.
• The address document is tied to the personnel action in EmpowHR, but is a payroll document for PINE processing, requiring the two documents to have separate statuses in EmpowHR.
  • After the personnel action is saved, the status is NFC Ready.
  • After the address document is saved, the status is Ready Future.
• When the accession action fails the PINE edits, the address document is marked Not Applied at NFC, indicating the information will not be found on the National Finance Center's Payroll/Personnel System database.
• After corrective action is taken on the accession action, the action is saved, and it is sent to PINE for processing.
• No action is required for the address document. EmpowHR automatically sends the address document in the same pass of PINE as the accession personnel action. Do not change the status on the address document to NFC Ready and send the document a second time, as this results in PINE placing the document in suspense indicating there are multiple personnel action errors.
• This process continues until the accession action applies. If the address document returns with errors after the accession action applies, make the necessary corrections and change the status to NFC Ready to send it to PINE for processing.

Authentication Dates

Agencies may process multiple personnel actions with the same effective date for the same employee on the same day.

• The Guide to Processing Personnel Actions (GPPA) provides instructions on the correct order for processing personnel actions when multiple actions share the same effective date.
• The GPPA Chapter 3, General Instructions for Processing Personnel Actions, states that no personnel action may be made effective prior to the date on which the appointing officer approved the action.
• PINE uses Authentication Dates to chronologically order actions with the same Effective Date for processing.
• The Authentication Date is the date the Agency’s appointing officer approved the personnel action; however, Agencies may need to adjust that date to place actions with the same Effective Date in chronological order when:
  • More than one personnel action needs to be entered by the Agency.
  • A rollback occurs, and a new personnel action is inserted.
  • A personnel action with a future effective date exists.
• The processing order must be determined when the personnel action is saved and there is a Bi-Weekly Examination Analysis and Reporting System (BEAR)-generated action. For the Nature of Action Codes (NOAC) listed below, the Effective Date is the first day of the pay period (Sunday).
  • NOAC 880, Chg in Tenure Group. The Authentication Date is the same as the Effective Date.
  • NOAC 893, Reg WRI. The Authentication Date is one day prior to the Effective Date (Saturday, the last day of the prior pay period).
  • NOAC 903, Chg In Non CDPF Data Element. The Authentication Date is 2 days prior to the Effective Date (Friday, the second to last day of the prior pay period).

EmpowHR automatically populates the Authentication Date with the current calendar date. The user must change this date to match the date the Agency’s appointing officer approved the personnel action; however, changing the Authentication Date does not affect the order of the personnel actions. EmpowHR uses the Effective Seq field on the Hire Employee page > Data Control tab of each personnel action to chronologically order actions that share the same Effective Date. When the numbers in the Effective Seq field are properly aligned, the Authentication Dates should be chronological. 

Example:

Row	NOAC	Effective Date	Authentication Date	Effective Seq
1	721	01/12/2025	01/12/2025	3 1
2	893	01/12/2025	01/11/2025	2 1
3	894	01/12/2025	12/23/2024	1 1