Monitor CMIA (90.2.4)
-
Print
-
DarkLight
-
PDF
Monitor CMIA (90.2.4)
-
Print
-
DarkLight
-
PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Business Process Overview
Users within DFS will upload CMIA funding data that is provided from agencies to Florida PALM. Florida PALM will use this information to produce the clearance pattern report for applicable ALNs. The clearance pattern report will calculate the time a payment was issued to the time the payment clears the State Treasury for all payments recorded with matching CMIA funding found within the CMIA Funding table of the custom ALN/CSFA page.
Change Impact:
There is no process change for Agencies. Agencies will continue to track and report on CMIA as they do today and will continue to follow any instructions provided by Treasury on the process.
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.
- Agency GM Processor: agency role responsible for ensuring accurate grant and budgetary information is recorded, including CMIA funding information.
- Agency GM Maintainer: agency role responsible for ensuring accurate grant information is recorded, including CMIA funding information.
- Treasury CMIA Maintainer: DFS role responsible for ensuring accurate Federal Assistance Listing Numbers (ALN) and Catalog of State Financial Assistance (CSFA) information is recorded, including CMIA reporting indicators. This role is also responsible for uploading ALN/CSFA Spreadsheet to add or modify grant information.
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. This information should be read in conjunction with the Business Process Flow Diagrams.
Process Step ID | Process Step Title | Description of Process |
|---|---|---|
1 | Request CMIA Funding Spreadsheet | The Treasury CMIA Maintainer will request the CMIA funding for the current year tracking period. Timeline example: August 2026 CMIA funding requested is based on the federal programs identified in the FY26/27 Treasury Service Agreement (TSA) |
2 | Submit CMIA Funding Spreadsheet | Agency GM Maintainers will submit their CMIA funding via spreadsheet, to Treasury. This process remains the same as the current day process. Timeline example: |
3 | Upload CMIA Funding Information (GMI010) (DFS only interface.) | The Treasury CMIA Maintainer uses the ALN/CSFA Spreadsheet Upload tool, GMI010, to upload the CMIA funding data received from the Agencies to Florida PALM. Timeline Example: The Upload of the FY26/27 tracking data occurs in or around August of 2026. |
4 | Perform Interface Error Checking | If the file is rejected, all transactions in the file are rejected and the file must be resubmitted once the 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 Grant Information Pages. Additional edits will be performed during the transaction life cycle. Rejected transactions are managed through the 120.1 Interface Error Handling Process This error checking process will validate the following information:
|
5 | Load CMIA Funding Information | If the file passes the edit checks successfully, the data will be loaded to Florida PALM and can be viewed on the ALN/CSFA Custom page for the associated ALN. Timeline Example: The Upload of the FY26/27 tracking data occurs in or around August of 2026. |
6 | Record Florida PALM Financials | Agency GM Processor monitors CMIA transactions recorded in various Florida PALM modules. Timeline Example: Agencies will transact normally within the financial system during the FY26/27 CMIA Tracking period. |
7 | Load Data to DW | Expenditure information, including Payment Schedule Date and Payment Clearing Date will be loaded to the Data Warehouse. Timeline Example: The transactional details and payment information for payments issued between Sept. 2026 and Nov. 2026 will be loaded to the Data Warehouse and be available for calculation of the Clearance Pattern report in step 13, in support of creating the FY27/28 CMIA report due Dec. 2027. |
8 | Request Interest Liability Calculation | The Treasury CMIA Maintainer will request Interest Liability Calculation for the previous year’s TSA from each agency. Timeline Example: |
9 | Submit CMIA Interest Liability Calculation | Each Agency will submit their Interest Liability Calculation to Treasury. Timeline Example: |
10 | Review Interest Liability Calculation | The Treasury CMIA Maintainer will review the Interest Liability Calculation as submitted by the Agencies. |
11 | Compile Data | The Treasury CMIA Maintainer will utilize the Clearance Pattern Report, the Interest Liability Calculation, and other supporting documentation to populate the Annual CMIA report outside of Florida PALM. Timeline Example: |
12 | Input CMIA Data to Federal Website | The Treasury CMIA Maintainer will input the CMIA report to the Federal Website. If the CMIA report indicates that interest is due to, or from, the Federal Government, the Treasury CMIA Maintainer will work with the appropriate staff to create a voucher to issue the payment using 30.3.1 Process Vouchers business subprocess or create a receivable using 60.1.1 Record AR business subprocess. Timeline Example: |
13 | Calculate Clearance Pattern | The Clearance Pattern report for the next CMIA reporting period will be generated based on the CMIA funding received in Steps 1 through 5. The Clearance Pattern Report will measure the time between Payment Scheduled date and the date the payment is cleared from State Treasury, for all payments issued within the period detailed in the TSA, with matching COA ChartField Strings provided in the CMIA funding upload. Timeline Example: |
14 | Receive Audited SEFA | The Treasury CMIA Maintainer will receive the previous Fiscal Year’s audited SEFA. This information is used by Treasury to identify federal programs that are CMIA reportable per 31 CFR Part 205, for the upcoming Fiscal Year. Timeline Example: The audited SEFA is received in April 2027, covers the transactions that occurred within FY25/26, and will be used to establish the major programs listed in the FY27/28 TSA. |
15 | Create New TSA Based on SEFA | The Treasury CMIA Maintainer will review the audited SEFA. The audited SEFA data will be utilized to identify the major federal programs per CFR 31 part 205(5). These major programs will be identified within the next fiscal year’s TSA. Timeline Example: The FY27/28 TSA is developed and submitted by June of 2027. The SEFA for FY25/26 will be used to identify the major programs to be included in the new TSA, and those programs will be tracked Sept. 2027 through Feb. 2028 with the final CMIA report being submitted in December 2028. |
16 | Review ALNs Based on Audited SEFA | The Treasury CMIA Maintainer will compare the information received in the audited SEFA to the data within Florida PALM to ensure all Assistance Listing Numbers (ALN) are correctly marked as CMIA reportable as noted by the TSA. Timeline Example: Using the SEFA received within April 2026, Treasury will update the ALNs which are CMIA reportable for the newly created FY27/28 TSA. |
17 | Update CMIA ALNS Based on New TSA | If updates are needed to the CMIA reportable indicator on the ALNs within Florida PALM, the Treasury CMIA Maintainer will update the ALN using the custom ALN/CSFA page within Florida PALM using 90.2.2 Add or Modify ALN or CSFA business subprocess. Timeline Example: |
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 |
|---|---|---|---|---|---|
R6 | APR027 | Payment Summary – report used to compute the number and dollar amount of payments made by warrant and/or ACH run day, per month, or other user-defined time-period. | Data Warehouse | As needed | Treasury |
R7 | APR064 | Clearance Pattern Report – report that details the clearance pattern for designated projects. | Data Warehouse | As Needed | Treasury |
Interfaces
The table below provides the Interfaces identified on the Business Process.
Interface Number | Interface Description | Interface Frequency | Source | Target |
|---|---|---|---|---|
GMI010 | Inbound ALN/CSFA Spreadsheet Upload – Inbound Interface to allow DFS to update ALN/CSFA data and CMIA funding in the ALN/CSFA tables via spreadsheet (Excel) upload. (DFS only interface.) | Daily | DFS | Florida PALM |
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 |
|---|---|
02/05/2024 | Original Version |
| 08/30/2024 | Removed APR118 per Decision 336 |
Was this article helpful?
