Agency Record Inter/InterUnit Transactions (110.3.1)

1

Identify Need for IU Transaction

The Inter/IntraUnit Module allows agencies to perform inter-agency transactions including the following IU transactions:

• Expenditure/Revenue
• Advance Repayment
• Transfer
• General Revenue Transfer
• Federal Funds Transfer
• Revenue to Revenue

The above listed IU transactions have two sides to the transaction. The sending side of the IU transactions is used to record the liability or expenditure of the transaction. The sending side of the transaction is recorded by the Agency IU Sending Processor and is used to send funds to the receiving agency.

The receiving side of the IU transactions is used to record the receivable or revenue of the transaction. The receiving side of the transaction is recorded by the Agency IU Receiving Processor and is used to receive funds from the sending agency.

If an IU transaction is determined to be needed, the sending agency may record either via the Inbound Inter/IntraUnit Interface, the Inbound Inter/IntraUnit Spreadsheet Upload, or via online.

2

Inbound Inter/IntraUnit Interface
(IUI002)

The sending agency who initiates the recording of an IU transaction may do so via IUI002 Inbound Inter/IntraUnit Interface. This standard flat file interface is established with agency business systems and Florida PALM to obtain Inter/IntraUnit (IU) transactions.

All IU transactions interfaced into Florida PALM bypass their agency’s approval and are marked approved systematically through interface processing. The transaction may require DFS BFR and DFS Auditing approval through workflow regardless of method of entry.

The ‘External Reference’ field may be used to capture an agency assigned identifier.

Agencies may interface attachments to the IU transactions via SDI009 Inbound Attachments Interface or upload directly online.

3

Inbound Inter/IntraUnit Spreadsheet Upload
(IUI001)

The sending agency who initiates the recording of an IU transaction may do so via IUI001 Inbound Inter/IntraUnit Spreadsheet Upload. A Spreadsheet Upload is a process to transfer data within a Microsoft Excel spreadsheet systematically into Florida PALM to create transactions.

A user who is assigned both the Agency IU Spreadsheet Upload Processor and the Agency IU Sending Processor role can create an IU Transaction and record the sending side (i.e., liability/expenditure) of the transaction.

The IU transaction may pay against an IU Encumbrance or an IU Accrual. This will lower the remaining balance of the IU Encumbrance/Accrual.

A single-line SpeedKey may be used in the Spreadsheet Upload to populate the distribution lines with ChartField values. Agencies will have the opportunity to define their own SpeedKeys.

The ‘External Reference’ field may be used to capture an agency assigned identifier.

All IU transactions recorded via Spreadsheet Upload bypass their agency’s approval workflow and are marked approved systematically through interface processing. The transaction may require DFS BFR and DFS Auditing approval through workflow regardless of method of entry.

Agencies may interface attachments to IU transactions via SDI009 Inbound Attachments Interface or upload directly online.

4

Perform Interface Error Checking

Interface validations are performed on each interface and Spreadsheet Upload before the data is allowed to load to the Inter/IntraUnit tables.

If the file is rejected, all transactions in the file are rejected and the file must be resubmitted once issues are resolved. Rejected files are managed through the 120.1 Interface Error Handling Process.

If the file is not rejected, edit validations are performed on each transaction before the data is allowed to load for processing in the Inter/IntraUnit module.

Edit Validations include but are not limited to:

• ChartField Validation
• Amount Validation
• Open Period Validation

Additional Interface exceptions may occur when the data is validated against specific interface edits. Examples include duplicate data in the file, incorrect data, and missing required fields.

Transactions with exceptions are rejected and agencies would need to resend the transactions in a future interface if an exception occurred. Rejected transactions are managed through the 120.1 Interface Error Handling Process.

5

Load Inbound IU Transaction Data

Florida PALM loads the IU transaction data and systematically generates the IU transactions.

Agencies may utilize the IUR005 Inter/IntraUnit Transaction Detail Report to view the IU transactions loaded into Florida PALM.

6

Create/Update IU Transaction

The sending agency who initiates the recording of an IU transaction may do so online.

If the sending agency end user has the Agency IU Sending Processor role, the end user may record the sending side (i.e., liability/expenditure) of the transaction.

The IU transaction may pay against an IU Encumbrance or an IU Accrual. This will lower the remaining balance of the IU Encumbrance/Accrual.

A single-line SpeedKey may be used to populate the distribution lines with ChartField values when entering an online IU transaction. Agencies will have the opportunity to define their own SpeedKeys.

A user may send a notification/alert to the receiving agency to communicate if needed. The notification can be done through an individual notification or using the IU processors associated to the receiving agency selected.

Agencies may interface attachments to the IU transactions via SDI009 Inbound Attachments Interface or upload directly online.

Reports available to view established or updated IU transactions include the following:

• IUR005 Inter/IntraUnit Transaction Detail Report
• IUR007 Pending Submission IU Transactions

Reference Figure 1 for a Mock-up of the IU transaction sending entry page.

7

Run Edit Check

IU transactions will be systematically Edit Checked upon saving or submitting the transaction. The Edit Check process will validate that ChartField values are active, validate Combination Edit rules applicable to the transaction, amount validation, open period validation, etc.

8

Resolve Edit Errors

If edit errors are identified, the transaction will not process. The user will receive a message upon saving or submitting if the IU transaction fails edit rules.

Edit errors that occur when an IU transaction is entered online must be resolved prior to the transaction proceeding. The system will not allow the IU transaction to proceed until all the required fields are provided with valid active values.

Processors should confirm the validity of the ChartField values and the ChartField String used on the transaction and make necessary updates. The processors should confirm the date of transaction falls within an open budget or accounting period.

If errors persist after making updates, and a SpeedKey is being used, the processor should consult with the Agency COA Maintainer to determine if the SpeedKey was established accurately.

Alternatively, the processor may determine to cancel the transaction.

If the edit error is not resolved within a specified number of days, the transaction will be auto deleted.

Reports available to view IU transactions edit errors include:

• IUR011 IU Edit Errors (WorkCenter)
• IUR005 Inter/IntraUnit Transaction Detail Report

9

Outbound Inter/IntraUnit Interface (IUI003)

Florida PALM interfaces with agency business systems, as applicable, to provide IU transaction information, including establishment of IU transactions and updates via the IUI003 Outbound Inter/IntraUnit Interface.

10

Identify IU Transactions to Update

The receiving agency who receives an IU transaction from another agency is notified in multiple methods:

• The receiving agency will be notified via their IUI003 Outbound Inter/IntraUnit Interface file of a newly received IU transaction.
• The receiving agency may view the IUR008 Received IU Transactions (WorkCenter) report to see a complete list of received IU transactions.
• The processor within the receiving agency will receive an alert in their WorkCenter Worklist.
• IUR005 Inter/IntraUnit Transaction Detail Report can also be leveraged to identify newly received IU transactions.

Upon identifying a received IU transaction, the processor will be required to update the IU transaction to record their receiving side of the transaction. The receiving agency may update the IU transaction either via the Inbound Inter/IntraUnit Interface, the Inbound Inter/IntraUnit Spreadsheet Upload, or via online.

11

Inbound Inter/IntraUnit Interface
(IUI002)

The receiving agency may update an IU transactions via IUI002 Inbound Inter/IntraUnit Interface to record their side of the transaction. This standard flat file interface is established with agency business systems and Florida PALM to obtain Inter/IntraUnit (IU) transaction data.

All IU transactions interfaced into Florida PALM bypass their agency’s approval and are marked approved systematically through interface processing. The transaction may require DFS BFR and DFS Auditing approval through workflow regardless of method of entry.

The ‘External Reference’ field may be used to capture an agency assigned identifier.

Agencies may interface attachments to the IU transactions via SDI009 Inbound Attachments Interface or upload directly online.

12

Inbound Inter/IntraUnit Spreadsheet Upload

(IUI001)

The receiving agency may update an IU transaction via IUI001 Inbound Inter/IntraUnit Spreadsheet Upload to record their receiving side of the transaction. A Spreadsheet Upload is a process to transfer data within a Microsoft Excel spreadsheet systematically into Florida PALM to create transactions.

A user who is assigned both the Agency IU Spreadsheet Upload Processor and the Agency IU Receiving Processor role can update an IU Transaction to record the receiving side (i.e., receivable/revenue) of the transaction.

The IU transaction may pay against an IU Encumbrance or an IU Accrual. This will lower the remaining balance of the IU Encumbrance/Accrual.

A single-line SpeedKey may be used in the Spreadsheet Upload to populate the distribution lines with ChartField values. Agencies will have the opportunity to define their own SpeedKeys.

The ‘External Reference’ field may be used to capture an agency assigned identifier.

All IU transactions recorded via Spreadsheet Upload bypass their agency’s approval workflow and are marked approved systematically through interface processing. The transaction may require DFS BFR and DFS Auditing approval through workflow regardless of method of entry.

Agencies may interface attachments to IU transactions via SDI009 Inbound Attachments Interface or upload directly online.

13

Perform Interface Error Checking

Interface validations are performed on each interface and Spreadsheet Upload before the data is allowed to load to the Inter/IntraUnit tables.

If the file is rejected, all transactions in the file are rejected and the file must be resubmitted once issues are resolved. Rejected files are managed through the 120.1 Interface Error Handling Process.

If the file is not rejected, edit validations are performed on each transaction before the data is allowed to load for processing in the Inter/IntraUnit module.

Edit Validations include but are not limited to:

• Chartfield Validation
• Amount Validation
• Open Period Validation

Additional Interface exceptions may occur when the data is validated against specific interface edits. Examples include duplicate data in the file, incorrect data, and missing required fields.

Transactions with exceptions are rejected and agencies would need to resend the transactions in a future interface if an exception occurred. Rejected transactions are managed through the 120.1 Interface Error Handling Process.

14

Load Inbound IU Transaction Data

Florida PALM loads the IU transaction data and systematically updates the IU transactions.

Agencies may utilize the IUR005 Inter/IntraUnit Transaction Detail Report to view the IU transaction updates.

15

Update IU Transaction

An IU Transaction is updated online by the receiving agency to record their side of the transaction.

If the receiving agency end user has the Agency IU Receiving Processor role, the end user may record the receiving side (i.e., receivable/revenue) of the transaction.

A single-line SpeedKey may be used to populate the distribution lines with ChartField values when entering an online IU transaction. Agencies will have the opportunity to define their own SpeedKeys.

A user may send a notification/alert to the initiating agency to communicate if needed. The notification can be done through an individual notification or using the IU processors associated to the initiating agency selected.

Agencies may interface attachments to the IU transactions via SDI009 Inbound Attachments Interface or upload directly online.

The IUR005 Inter/IntraUnit Transaction Detail Report can be utilized to view updated IU transactions.

Reference Figure 2 for a Mock-up of the IU transaction receiving entry page.

16

Run Edit Check

IU transactions will be systematically Edit Checked upon saving or submitting the transaction. The Edit Check process will validate that ChartField values are active, validate Combination Edit rules applicable to the transaction, amount validation, open period validation, etc.

17

Resolve Edit Errors

If edit errors are identified, the transaction will not process. The user will receive a message upon saving or submitting if the IU transaction fails edit rules.

Edit errors that occur when an IU transaction is entered online must be resolved prior to the transaction proceeding. The system will not allow the IU transaction to proceed until all the required fields are provided with valid active values.

Processors should confirm the validity of the ChartField values and theChartField String used on the transaction and make necessary updates. The processors should confirm the date of transaction falls within an open budget or accounting period.

If errors persist after making updates, and a SpeedKey is being used, the processor should consult with the Agency COA Maintainer to determine if the SpeedKey was established accurately.

If the edit error is not resolved within a specified number of days, the transaction will be auto deleted.

Reports available to view IU transactions with edit errors include:

• IUR011 IU Edit Errors (WorkCenter)
• IUR005 Inter/IntraUnit Transaction Detail Report

18

Initiate Inter/IntraUnit Workflow (IUW001)

Once both agencies have recorded their side of the transaction and submitted, the Inter/IntraUnit Workflow is initiated to obtain the necessary approvals.

If the sending side (i.e., liability/expenditure) of the IU transaction was entered online, the IU transaction will require approval from the Agency IU Sending Approver. If recorded via interface or Spreadsheet Upload, the transaction will bypass sending approval.

If the receiving side (i.e., receivable/revenue) of the IU Accrual was entered online, the IU Accrual will require approval from the Agency IU Receiving Approver. If recorded via interface or Spreadsheet Upload, the transaction will bypass the receiving approval.

If approval workflow is required, it will be sent to both the Agency IU Sending Approver and Agency IU Receiving Approver simultaneously.

19

Review IU Transaction

The Agency IU Sending Approver will receive a notification via Worklist in the IU WorkCenter displaying the transaction is ready to be approved. Alternatively, the approver may access IUR009 IU Pending Approval report in the IU WorkCenter.

The approver reviews the sending side (i.e., liability/expenditure) of the IU transaction and any attached documentation to ensure the transaction is accurate and valid. Based on the documentation, the approver has three options:

• Approve the transaction
• Deny the transaction and recommend updates
• Deny the transaction and recommend deletion

20

Deny IU Transaction

If the Agency IU Sending Approver determines the IU transaction requires updates or recommends deletion, the approver denies the sending side (i.e., liability/expenditure) of the IU transaction and enters a comment for the denial reason.

21

Route to IU Processors

The IU transaction status is set to ‘Denied’ and is routed back to both the sending and receiving processors. Both processors will receive an email notification of the denied transaction.

Refer to Appendix A for a complete list of statuses and descriptions.

22

Review Denied IU Transaction

An IU transaction may be denied by an approver. The Agency Sending IU Processor is notified of the denial via email. The processor reviews the IU transaction and makes updates to their side of the transaction if necessary.

The processor may use the IUR010 Denied IU Transactions (WorkCenter) report to view denied IU transactions.

23

Review Denied IU Transaction

An IU transaction may be denied by an approver. The Agency Receiving IU Processor is notified of the denial via email. The processor reviews the IU transaction and makes updates to their side of the transaction if necessary.

The processor may use the IUR010 Denied IU Transactions (WorkCenter) report to view denied IU transactions.

24

Delete IU Transaction

An IU transaction may be denied by an approver and deem it necessary to delete the transaction. The Agency Sending IU Processor who initiated the transaction may delete an IU transaction if necessary.

Deleted IU transactions do not impact balances and are not able to be altered after deletion.

An IU transaction cannot be deleted if it has successfully passed budget/cash check.

IU transactions in a deleted status may be viewed in the IUR005 Inter/IntraUnit Transaction Detail Report.

25

Approve IU Transaction

IU transactions that pass review are approved by the Agency IU Sending Approver.

26

Review IU Transaction

The Agency IU Receiving Approver will receive a notification via Worklist in the IU WorkCenter displaying the transaction is ready to be approved. Alternatively, the approver may access IUR009 IU Pending Approval report in the IU WorkCenter.

The approver reviews the receiving side (i.e., receivable/revenue) of the IU transaction and any attached documentation to ensure the transaction is accurate and valid. Based on the documentation, the approver has three options:

• Approve the transaction
• Deny the transaction and recommend updates
• Deny the transaction and recommend deletion

27

Deny IU Transaction

If the Agency IU Receiving Approver determines the IU transaction requires updates or recommends deletion, the approver denies the receiving side (i.e., receivable/revenue) of the IU transaction and enters a comment for the denial reason.

28

Route to IU Processors

The IU transaction status is set to ‘Denied’ and is routed back to both the initiating and reciprocating processors. Both processors will receive an email notification of the denied transaction.

Refer to Appendix A for a complete list of statuses and descriptions.

29

Approve IU Transaction

IU transactions that pass review are approved by the Agency IU Receiving Approver.

30

Initiate Inter/IntraUnit Workflow (IUW001)

IU transactions may require DFS BFR approval regardless of method of entry.

Once both sides of the IU Accrual are approved, either through agency Workflow or marked approved via Interface/Spreadsheet Upload, the Inter/IntraUnit workflow is initiated to determine if the IU transaction requires BFR approval based on criteria.

If the transaction does not require BFR approval, the Inter/IntraUnit workflow is initiated again to determine if the IU transaction requires auditing approval based on criteria.

31

Review IU Transaction

The DFS IU BFR Approver will receive a notification via Worklist in the IU WorkCenter displaying the transaction is ready to be reviewed for approval. Alternatively, the approver may access IUR009 IU Pending Approval report in the IU WorkCenter.

The approver reviews both the sending and receiving sides of the IU transaction and any attached documentation to ensure the transaction is accurate and valid. Based on the documentation, the approver has three options:

• Approve the transaction
• Deny the transaction and recommend updates
• Deny the transaction and recommend deletion

32

Deny IU Transaction

If the DFS IU BFR Approver determines the IU transaction requires updates or recommends deletion, the approver denies the IU transaction and enters a comment for the denial reason.

33

Route to IU Processors

The IU transaction status is updated to ‘Denied’ and is routed back to both the sending and receiving processors. Both processors will receive an email notification of the denied transaction.

Refer to Appendix A for a complete list of statuses and descriptions.

34

Approve IU Transaction

IU transactions that pass review are approved by the DFS IU BFR Approver.

35

Initiate Inter/IntraUnit Workflow (IUW001)

The Inter/IntraUnit Workflow is initiated to determine if the IU transaction requires auditing approval based on criteria.

If the transaction does not require Auditing approval, the transaction lifecycle proceeds to run budget and cash check.

36

Review IU Transaction

The DFS IU Auditing Approver will receive a notification via Worklist in the IU WorkCenter displaying the transaction is ready to be reviewed for approval. Alternatively, the approver may access IUR009 IU Pending Approval report in the IU WorkCenter.

The approver reviews both the sending and receiving sides of the IU transaction and any attached documentation to ensure the transaction is accurate and valid. Based on the documentation, the approver has three options:

• Approve the transaction
• Deny the transaction and recommend updates
• Deny the transaction and recommend deletion

37

Deny IU Transaction

If the DFS IU Auditing Approver determines the IU transaction requires updates or recommends deletion, the approver denies the IU transaction and enters a comment for the denial reason.

38

Route to IU Processors

The IU transaction status is updated to ‘Denied’ and is routed back to both the sending and receiving processors. Both processors will receive an email notification of the denied transaction.

Refer to Appendix A for a complete list of statuses and descriptions.

39

Approve IU Transaction

IU transactions that pass review are approved by the DFS IU Auditing Approver.

40

Run Budget/Cash Check

Upon final approval, the IU transaction continues processing through the systematic Budget Check and Cash Check process. The budget check process will run at the designated interval. The budget/cash check checks all budget and cash ledgers to ensure there is a sufficient balance available.

The sending and receiving processors monitor pending IU transactions to ensure resolution of budget and cash check errors.

If the error requires a budget resolution, the transaction is subject to the 20.2.1 Manage Budget Checking business subprocess. If the budget error is not resolved within a specified number of days, the IU transaction will be auto deleted.

If the transaction exceeds the spendable cash balance, the transaction will fail cash checking. Transactions that fail cash checking are subject to 20.2.2 Manage Cash Checking business subprocess.

If the error requires an accounting resolution, the sending and receiving agency processors may edit the transaction as needed.

Each agency has the option to correct IU transaction errors within Florida PALM or correct in the source system and resend the transaction via IUI002 Inbound Inter/IntraUnit Interface or IUI001 Inbound Inter/IntraUnit Spreadsheet Upload.

Neither side of the IU transaction will impact ledgers until both sides of the IU transaction successfully pass.

If a budget, cash, or accounting resolution is unable to be completed, the initiating agency processor may choose to delete the IU transaction.

Reports available to view IU transactions with budget and cash check errors are listed below:

• IUR006 Inter/IntraUnit Budget-Cash Check Errors (WorkCenter)
• KKR058 Budget and Cash Checking Exceptions/Warnings Report

41

Update Ledger Balances

Upon passing the Budget/Cash Check, the appropriate ledgers will be updated in the Commitment Control module.

The Accounting Events section listed below provides Commitment Control ledger impacts for each business event.

42

Post to IU Module

IU transactions that successfully pass all checks (edit check, budget check, and cash check) are posted automatically to the IU Module. Upon posting, the IU transaction status is updated to ‘Posted’. Agencies can query for posted IU transaction details within Florida PALM.

Refer to Appendix A for a complete list of statuses and descriptions.

Reports available to view posted IU transactions include:

• IUR005 Inter/IntraUnit Transaction Detail Report 
• IUR004 Inter/IntraUnit Accrual Report

43

Generate GL Journals

Journal Generator (JGEN) processes posted accounting entry data from the Florida PALM source modules, summarizes the data, and creates journals in the General Ledger. The Journal Generator process will edit, budget check, and post the journal entries created during the process. Please reference 10.2.1 Source Module Journal Entry for more information on source module journal entries.

Journals created from the Inter/IntraUnit module will contain Affiliate and Fund Affiliate fields. These fields help manage InterUnit and IntraUnit transactions and facilitate mapping transactions between related Business Units and Funds.

44

Outbound Inter/IntraUnit Interface (IUI003)

Florida PALM generates and exports a data file through IUI003 Outbound Inter/IntraUnit Interface for agency business systems, as applicable, to provide IU transaction information, including posted IU transactions.

IU01

Record Unencumbered Expenditure/Revenue

(Applicable to Expenditure/Revenue transactions)

Sending

Debit: Expenditure (U)

Credit: Cash (S)

Increases:

• Expense

Decreases:

• Available Appropriations balance
• Allotments balance
• Releases balance
• Spendable Cash

Debit: Expenditure

Credit: Cash

Receiving

Debit: Cash (S)

Credit: Revenue (U)

Increases:

• Collected Revenue
• Spendable Cash

Debit: Cash

Credit: Revenue

IU02

Record Encumbered Expenditure/Revenue

(Applicable to Expenditure/Revenue transactions)

Sending – Relieve Encumbrance

N/A

Increases:

• Available Appropriations
• Allotment balance

Decreases:

• Encumbrance

N/A

Sending

Debit: Expenditure (S)

Credit: Cash (S)

Increases:

• Expense

Decreases:

• Available Appropriations
• Releases balance
• Reserves balance
• Allotments balance
• Spendable Cash

Debit: Expenditure

Credit: Cash

Receiving

Debit: Cash (S)

Credit: Revenue (U)

Increases:

• Collected Revenue
• Spendable Cash

Debit: Cash

Credit: Revenue

IU03

Expenditure/Revenue Against Accrual

(Applicable to Expenditure/Revenue transactions)

Sending

Debit: Accounts Payable (S)

Credit: Cash (S)

Increases:

• N/A

Decreases:

• Spendable Cash

Debit: Accounts Payable

Credit: Cash

Receiving

Debit: Cash (S)

Credit: Accounts Receivable (S)

Increases:

• Collected Revenue
• Spendable Cash

Debit: Cash

Credit: Accounts Receivable

IU04

Refund for Payment of Goods/Services

(Applicable to Expenditure/Revenue transactions)

Sending

Debit: Revenue (U)

Credit: Cash (S)

Increases:

• N/A

Decreases:

• Collected Revenue
• Spendable Cash

Debit: Revenue

Credit: Cash

Receiving

Debit: Cash (S)

Credit: Expenditure (U)

Increases:

• Available Appropriations
• Releases balance
• Reserves balance
• Allotments balance
• Spendable Cash

Decreases:

• Expense

Debit: Cash

Credit: Expenditure

IU05

Unencumbered Transfer

(Applicable to Transfer, Federal Funds Transfer, and General Revenue Transfer transactions)

Sending

Debit: Expenditure (U)

Credit: Cash (S)

Increases:

• Expense

Decreases:

• Available Appropriations
• Allotments balance
• Releases balance
• Spendable Cash

Debit: Expenditure

Credit: Cash

Receiving

Debit: Cash (S)

Credit: Revenue (U)

Increases:

• Collected Revenue
• Spendable Cash

Debit: Cash

Credit: Revenue

IU06

Encumbered Transfer

(Applicable to Transfer, Federal Funds Transfer, and General Revenue Transfer transactions)

Sending – Relieve Encumbrance

N/A

Increases:

• Available Appropriations
• Allotments balance

Decreases:

• Encumbrance

N/A

Sending

Debit: Expenditure (S)

Credit: Cash (S)

Increases:

• Expense

Decreases:

• Available Appropriations balance
• Allotments balance
• Releases balance
• Spendable Cash

Debit: Expenditure

Credit: Cash

Receiving

Debit: Cash (S)

Credit: Revenue (U)

Increases:

• Collected Revenue
• Spendable Cash

Debit: Cash

Credit: Revenue

IU07

Transfer Against Accrual

(Applicable to Transfer, Federal Funds Transfer, and General Revenue Transfer transactions)

Sending

Debit: Accounts Payable (S)

Credit: Cash (S)

Increases:

• N/A

Decreases:

• Spendable Cash

Debit: Accounts Payable

Credit: Cash

Receiving

Debit: Cash (S)

Credit: Accounts Receivable (S)

Increases:

• Collected Revenue
• Spendable Cash

Debit: Cash

Credit: Accounts Receivable

IU08

Residual Equity Transfer

(Applicable to Residual Equity Transfer transactions)

Sending

Debit: Transfer Out - Residual Equity (U)

Credit: Cash (S)

Decreases:

• Spendable Cash

Debit: Transfer Out – Residual Equity

Credit: Cash

Receiving

Debit: Cash (S)

Credit: Transfers In - Residual Equity (U)

Increases:

• Spendable Cash

Debit: Cash

Credit: Transfers In - Residual Equity

IU10

Revenue to Revenue Transfer

(Applicable to Revenue to Revenue Transaction)

Sending

Debit: Revenue (U)

Credit: Cash (S)

Decreases:

• Collected Revenue
• Spendable Cash

Debit: Revenue

Credit: Cash

Receiving

Debit: Cash (S)

Credit: Revenue (U)

Increases:

• Collected Revenue
• Spendable Cash

Debit: Cash

Credit: Revenue

IU12

Advance Repayment

(Applicable to Revenue to Repayment Transaction)

Sending

Debit: Transfer Out - Advance Payable (S) (U)

Credit: Cash (S)

Decreases:

Spendable Cash

Debit: Transfer Out - Advance Payable

Credit: Cash

Receiving

Debit: Cash (S)

Credit: Transfer In - Advance Receivable (S)

Increases:

• Collected Revenue
• Spendable Cash

Debit: Cash

Credit: Transfer In - Advance Receivable

R1

IUR005

Inter/IntraUnit Transaction Detail Report – A report that lists transaction details for Inter/IntraUnit module transactions including Inter/IntraUnit expenditures, revenues, transfers, advances, reclassifications, encumbrances, and accruals.

PeopleSoft

Periodic, Monthly, Annually

Agency

R2

IUR007

Pending Submission IU Transactions (WorkCenter) – A report in the WorkCenter used to display a list of initiated IU transactions that are pending submission.

PeopleSoft

Periodic

Agency

R3

IUR011

IU Edit Errors (WorkCenter) – A report that provided edit errors for IU transactions that require action.

PeopleSoft

Periodic

Agency

R4

IUR008

Received IU Transactions (WorkCenter) – A report in the WorkCenter used to display a list of IU transactions that are received and ready for the reciprocating information.

PeopleSoft

Periodic

Agency

R5

IUR010

Denied IU Transactions (WorkCenter) – A report in the WorkCenter used to display a list of IU transactions submitted and are pending approval.

PeopleSoft

Periodic

Agency

R6

IUR009

IU Pending Approval (WorkCenter) – A report in the WorkCenter used to display a list of Inter/IntraUnit transactions submitted and are pending approval.

PeopleSoft

Periodic

Agency

R7

IUR006

Inter/IntraUnit Budget-Cash Check Errors (WorkCenter) – A report in the WorkCenter used to display a list of Inter/IntraUnit transactions with budget and cash check exceptions that require action.

PeopleSoft

Periodic

Agency

R8

KKR058

Budget and Cash Checking Exceptions/Warnings Report – A report that lists transactions budget and cash check exceptions and warnings along with transaction amounts, to include the type of exception and where an override was applied.

PeopleSoft

Periodic, Monthly, Annually

Agency, DFS

IUI001

Inbound Inter/IntraUnit Spreadsheet Upload - Inbound interface to load Inter-IntraUnit transactions via the spreadsheet (Excel) upload functionality. This interface is used for Inter/IntraUnit expenditure, revenue, transfer, advance, reclassifications, encumbrances, and accrual transactions.

Daily

Agency Business System

Florida PALM

IUI002

Inbound Inter/IntraUnit Interface - Inbound interface used to record or update Inter/IntraUnit expenditures, revenues, transfers, advances, reclassifications, encumbrances, and accruals.

Daily

Agency Business System

Florida PALM

IUI003

Outbound Inter/IntraUnit Interface - Outbound interface containing established/updated IU Encumbrances, and posted/received Inter/IntraUnit expenditures, revenues, transfers, advances, reclassifications, and accruals.

Daily

Florida PALM

Agency Business System

N/A

IUW001

IU Transaction Workflow – Workflow to route IU transactions (including IU Accruals) for approval.

Agency, DFS

07/23/2024

Original Version