Update Paysheets (100.3.3)
- 30 Jul 2024
- 3 Minutes to read
-
Print
-
DarkLight
-
PDF
Update Paysheets (100.3.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
The Update Paysheets subprocess loads pay and deduction updates to paysheets during the calculate payroll subprocess, prior to the final calculation.
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, is 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.
- Agency Payroll Approver: Agency role responsible for reviewing and approving (or denying) transactions.
- Agency Payroll Processor: Agency role responsible for ensuring employee's pay is accurate with the ability to view, enter, and update transactions.
- BOSP Payroll Approver: BOSP role responsible for reviewing and approving (or denying) payroll transactions.
- BOSP Payroll Maintainer: BOSP role with the ability to run and monitor payroll cycle processes and update configuration.
- BOSP Payroll Processor: BOSP role responsible for auditing an employee’s pay in the system with the ability to view, enter, and update transactions.
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 | Agency Payroll Processor enters paysheet update change request on the custom paysheet page in Florida PALM. | |
2 | Agency Payroll Processor submits the paysheet update request for approval. The Agency Payroll Approver reviews the request. If approved, the changes are written to the paysheet tables for paycheck recalculation as described in 100.3.2 Calculate Payroll. If not approved, go to step 3. | |
3 | Send Deny Notification to Agency Payroll Processor | Agency Payroll Approver denies the paysheet update change request and a message is sent to the Agency Payroll Processor with the denial. |
4 | Submit Paysheet Change Request | BOSP Payroll Processor enters paysheet update change request on the custom paysheet page in Florida PALM. |
5 | Send Paysheet Change Notification | BOSP Payroll Processor submits the paysheet update request for approval. The BOSP Payroll Approver reviews the request. If approved, the changes are written to the paysheet tables for paycheck recalculation as described in 100.3.2 Calculate Payroll. If not approved, go to step 6. |
6 | Send Deny Notification to BOSP Payroll Processor | BOSP Payroll Approver denies the paysheet update change request and a message is sent to the BOSP Payroll Processor with the denial. |
7 | Update Delivered Paysheet | BOSP Payroll Maintainer enters paysheet updates onto the delivered paysheet. No approval is required. |
8 | Notify Agency of Paysheet Update | BOSP Payroll Maintainer notifies the agency of updates made to employee paysheets. |
9 | Deny Unapproved Paysheet Change | After the payroll calculation processing window closes, the system will automatically deny unapproved paysheet change requests associated with the closed processing payroll cycle. |
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 |
|---|---|---|---|---|
N/A |
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?
