Retirement Data (100.2.3)
- 30 Jul 2024
- 3 Minutes to read
-
Print
-
DarkLight
-
PDF
Retirement Data (100.2.3)
- Updated on 30 Jul 2024
- 3 Minutes to read
-
Print
-
DarkLight
-
PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Business Process Overview
This subprocess outlines enrolling the employee in a Florida PALM “Retirement Plan” for their retirement elections.
Business Process Diagram
Business Roles
The Business Process Flow Diagrams use horizontal swim lanes to depict where activities are performed by different parties or systems. Each swim lane is titled with a role, either agency-based or within DFS, and in some cases, are representative of an external entity or system. The swim lanes may change from page to page within a single business subprocess as more or fewer roles are required to execute sections of the business subprocess.
- Florida PALM: Florida PALM system role that runs various automated processes, reports, and interfaces in a pre-determined schedule.
Business Process Flows Details
The tables below describe steps in each business subprocess as reflected on the Business Process Flow Diagrams. The tables also reflect information associated with each step describing the intent of the specific process. Florida PALM screenshots are included within the sections to allow connections to be made from specific business subprocess steps to screens within Florida PALM. This information should be read in conjunction with the Business Process Flow Diagrams.
Process Step ID | Process Step Title | Description of Process |
|---|---|---|
1 | Inbound Retirement Data File (PRI015) | Inbound interface to receive retirement data from the Human Resource Information Systems (HRIS). This file will contain information regarding employee elections to populate retirement plan data to deduct on the next eligible payroll processing window. |
2 | Perform Interface Error Checking | If file is rejected, all transactions in the file are rejected and the file must be resubmitted once issue is resolved. If the file is not rejected, edit validations are performed on each transaction before the data is allowed to load for processing in the module. Additional edits will be performed during the transaction life cycle. Rejected transactions are managed through the 120.1 Interface Error Handling Process. |
3 | Retirement Data Established / Updated | The employee retirement plan is setup or updated in Florida PALM using an automated entry process. The retirement deduction is then used to calculate the employee and employer retirement contributions on subsequent payrolls. |
4 | Outbound Retirement Plan File (PRI030) | An outbound interface to send retirement reporting data to the Department of Management Services, Division of Retirement. |
Accounting Events
Accounting events originate during transaction processing in the applicable source module. The accounting events impact the source module, Commitment Control ledgers, and the General Ledger (Actuals).
- Source Module accounting entries require user input (I) of the primary line (i.e., expenditure, revenues) with an automated (A) system offsetting line (i.e., payable, receivable) during transaction entry. The source model transaction must pass Edit Check, Budget Check, and Cash Check (on applicable entries) prior to posting the transaction.
- The Run Budget Check (Commitment Control) process automatically affects balances in the appropriate budget ledger (i.e., appropriation, spendable cash) if the transaction passes the budget check process.
- After the transaction is posted in the source module, an automated system process summarizes and posts the entries in the General Ledger module to the Actuals Ledger.
The table below provides the most common accounting events applicable to this business process.
Acct Event ID | Accounting Event | Commitment Control Ledger(s) Impact | Source Module Accounting Entry | General Ledger (Actuals) Entry |
|---|---|---|---|---|
N/A |
Reports
Key Reports are displayed as icons with the Report Number on this Business Process. The table below provides the reports identified to be produced at a particular process step or is used to support the completion of a process step.
Report Number | Report RICEFW ID | Report Description | Report Source | Report Frequency | Audience |
|---|---|---|---|---|---|
N/A |
Interfaces
The table below provides the Interfaces identified on the Business Process.
Interface Number | Interface Description | Interface Frequency | Source | Target |
|---|---|---|---|---|
PRI015 | Inbound Retirement Data File – Inbound interface to receive Retirement Benefits data. | Daily | People First and Legislature’s HRIS | Florida PALM |
PRI030 | Outbound Retirement Plan File – Outbound interface to send retirement reporting data to Department of Management Services, Division of Retirement. | Monthly/Biweekly | Florida PALM | Florida Retirement System |
Forms
The table below provides the forms identified on this Business Process.
Form Number | Form Description | Audience |
|---|---|---|
N/A |
Workflows
The table below provides the workflows identified on this Business Process.
Workflow Number | Workflow Description | Audience |
|---|---|---|
N/A |
Version History
Date | Revision Description |
|---|---|
07/30/2024 | Original Version |
Was this article helpful?
