Process Bank Cash Transfers (70.4)

Business Process Overview

The Department of Financial Services (DFS), Division of Treasury (Treasury) processes bank transfers and bank transfer requests on behalf of agencies. During the CMS Wave, the Process Bank Cash Transfer business process addresses how Treasury and agencies request, record, and process bank to bank cash transfers. In Florida PALM, agencies initiate bank transfer requests to wire money between bank accounts. These requests go through an internal organizational workflow for review and approval, and then are routed to Treasury for final approval. Once Treasury receives and approves the cash transfer requests, the wires are processed in the banking partner’s web portal. After the bank has completed the wires, Treasury records the wire details and accounting within Florida PALM.

Business Process Diagram

Dependencies and Constraints

Wire requests are processed directly in the banking platform and are not generated via an interface.

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. 

• Bank: (Non-Florida PALM role) The banking partner that process wire cash transfers
• Cash Transfer Approver: COM End User or DFS role responsible for approving transfers between bank accounts
• Cash Transfer Processor: COM End User or DFS role responsible for requesting transfers between bank accounts
• DFS CM Accounting Approver: DFS Treasury role responsible for reviewing and approving accounting exceptions
• DFS Transfer Approver: DFS Treasury role responsible for approving transfers between bank accounts

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