Business Processes and Modules
The Florida PALM Knowledge Center will provide a consolidated source for documentation about the functions and use of Florida PALM, including business process models, interfaces, and reports. This central repository will replace the Pathfinder, which has been retired in anticipation of the roll out of the Knowledge Center.
Check back or subscribe to Florida PALM communications for more information as it is released.
The Florida PALM Team categorized the financial management processes used today in thirteen business process groupings. The following groupings will be used to organize and communicate the design of Florida PALM for the State.
Click on the image to see descriptions of each business process grouping.
Business Requirements state desired Florida PALM functionality and technical capabilities, specifying the “what” the solution should do. They are not design specifications, which detail the “how” the requirement will be met. Attachment 5.1 – Business Requirements to the SSI Contract lists all requirements for Florida PALM including the requirements implemented during the CMS wave, requirements to be implemented in the current Major Implementation (Financials and Payroll Waves), and those designated for future Optional Services (future Wave).
Business Process Models
The Business Process Models document the standardized, end-state business processes that will be implemented in Florida PALM. They are associated with the business process groupings and include a process flow and narrative. Check out this helpful video which provides an overview for how to read a Business Process Model. Use the Process Models Key to better help you read the models.
Models for Financials Wave and Payroll Wave
View the draft business process models for both Financials and Payroll Waves below. Additional materials can be found on the Design Meetings page.
Models for CMS Wave
The CMS Wave business process models document the details of the cash management processes for the CMS Wave implementation in July 2021. Select a link below to view the flows and narratives within a business process.
A CMS Wave Summary provides the approach used to develop the business process models, an overview of the models, and a mapping of legacy activities and processes to the CMS Wave activities and processes. The summary serves as a tool for building end-user understanding for adoption of Florida PALM at the CMS Wave.
A module is a segment within Florida PALM that performs specific business functions within an area (i.e., General Ledger). Modules reflect what you see in the Florida PALM system and where the transactions are completed.
Click any module icon below to view a brief description of module functionality.
The Accounts Payable module is responsible for tracking and managing suppliers, voucher invoices and payments. Some users will enter data into the module, while others will check on a status in the module.
The Accounts Receivable module is used to manage and record customer AR items and deposits.
The Asset Management Module is where we will manage agency property over the lifecycle of the asset, establishes the security controls, and performs month and year-end closing activities.
The Cash Management Module is used to manage banking relationships, support bank and general ledger reconciliation, support cash transfers between bank accounts, and maintain revolving fund and clearing fund accounts.
Commitment Control module is used for control, management, and reporting of budget. This module includes ledgers that maintain appropriations, releases, reserves, and Fund cash which controls and tracks budget, cash, expenses, and revenues.
The General Ledger Module is used to establish the statewide accounting framework and agency-specific accounting and reporting needs, manage investments, interest apportionment, support the forecast and management of agency cash balances.
The Purchasing Module allows you create encumbrance based on information recorded on a Purchase Orders and maintain and monitor encumbrance.
Project Costing module is used to establish non-sponsored Project information which results in a Project ChartField value for tracking related transactions.