90.1.7 Manager Transaction Review for PCard Process

Business Process Overview

PCard transactions within Works will have the ability to capture PC BU, Project, and Activity, however the PC Source Type, PC Category and PC Subcategory is not captured in PCard Works. Users may still capture this detailed information within the Project Costing module using the Manager Transaction Review (MTR) Process.

The MTR process allows a user with appropriate roles to assign values to PCard transactions once the transaction has been approved and GL Journal Generator and Project Costing Cost Collection processes have completed.

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 PC Adjustment Processor: agency role responsible for entering Project adjustment transactions or new transactions within the Project Costing module of Florida PALM

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. 

Manager Transaction Review Page

Cost Review of transactions

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