Inter/IntraUnit Period Close (110.4.1)

Business Process Overview

This business subprocess outlines the responsibilities of agencies in monitoring and reviewing Inter/IntraUnit (IU) transactions. It emphasizes proactive reconciliation to minimize agency corrections at month-end, and the need for ongoing monitoring of IU transactions. Various IU WorkCenter reports assist in tracking pending submissions, edit errors, received transactions, denied transactions, pending approvals, and budget-cash check errors. Agencies review and resolve exceptions, collaborating with IU processors to update transactions as needed. The month-end process includes a GL to IU reconciliation to ensure transactions post to the correct period, adhering to the 10.3.1 Perform Month-End Close subprocess. Finally, once both the AR and AP modules close, the IU period also closes, preventing transaction postings to closed periods.

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. 

• IU Reporter: Agency role responsible for monitoring reports for month end period close.

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. 

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.

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.

Interfaces

The table below provides the Interfaces identified on the Business Process.

Forms

The table below provides the forms identified on this Business Process.

Workflows

The table below provides the workflows identified on this Business Process.

Version History