Edit Check (10.2.2)

Business Process Overview

The Edit Check process performs final validations of all accounting entries before the journals are posted to the Ledger. Edit check verifies the following:

• ChartField values and ChartField Combination Edits are valid, as of the date of the journal
• Related accounting period, based on the journal date, is open
• The GL journal is balanced by BU and Fund

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. 

• GL Journal Processor: Agency GL Journal Processor or DFS GL Journal Processor role responsible for initiating and completing the Edit Check process
• GL COA Maintainer: Agency GL COA Maintainer or DFS GL COA Maintainer role responsible for reviewing and assisting with researching Edit Check error

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.

Journal Edit Selection and Journal Status:

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 (U) of the primary line (i.e., expenditure, revenues) with an automated system (S) 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., Appropriations, 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 the Business Process Flow Diagrams. 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.

Note: A complete list of reports may be found in the Reports Catalog.

Interfaces

The table below provides the Interface IDs for each interface identified on the Business Process Flow Diagrams.

Note: A complete list of interfaces may be found in the Interface Catalog.

Forms

The table below provides the Forms identified on the Business Process Flow Diagrams.

Workflows

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

Version History