Inbound Journal Spreadsheet Upload (GLI011)
-
Print
-
DarkLight
-
PDF
Inbound Journal Spreadsheet Upload (GLI011)
-
Print
-
DarkLight
-
PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Interface Description
This interface was implemented in CMS Wave and will be updated in Financials Wave. The information in this article is the planned design for Financials Wave.
GLI011 is an Inbound Journal Spreadsheet Upload interface that contains journal entries that are loaded into the Florida PALM system in mass via the Spreadsheet Upload functionality. Journal Spreadsheet Upload interface is one of the ways to post journal entries within the General Ledger (GL). The GL is the module, within Florida PALM, to record, summarize, and report financial data.
Click below to view the interface file layout and sample data files.
Business Process Model
This interface can be found in the following business processes:
Selection Criteria
The interface data selection criteria include the following:
Data Field | Data Field Details |
|---|---|
Number of Data Fields - Required |
|
Character Set – Required |
|
If Journal ID Already Exists – Required |
|
If Journal is Invalid – Required |
|
Add File – Required |
|
Journal Processing Options - Optional |
|
File Layout
Field names and descriptions from the interface layout are provided below.
Data Field Name | Record Type | Data Field Description |
|---|---|---|
Sequence Number | Journal Header | Sequence number is temporary ID to track distinct journal details in Spreadsheet. Sequence number is auto incremented within Spreadsheet. |
Unit | Journal Header | Represents the Business Unit. Used to define an organization or organizational subset that is independent with regards to one or more accounting or operational functions. |
Journal ID | Journal Header | Identifies a journal entry, consisting of a header and one or more lines. A value of NEXT in this field create auto-numbered unique journal IDs in Florida PALM. |
Journal Date | Journal Header | Specifies the transaction date the journal was created. |
Description | Journal Header | Used to provide a short description reflecting the purpose of the journal. |
Ledger Group | Journal Header | One or more ledgers indicating where journal entries will be posted to affect financial balances. |
Ledger | Journal Header | Identifies where the journal entries will be recorded to impact financial balances. |
Source | Journal Header | Identifies the origin of a journal entry to facilitate inquiries and reporting. |
Operator ID | Journal Header | Used to provide Operator ID, which processes XML file and loads journals into Florida PALM. |
Currency Effective Date | Journal Header | Specifies the effective date for selected currency code on journal header. |
Reversal Code | Journal Header | A flag that indicates if a journal entry should be automatically reversed, and if so, with what date. When associated with a reversal entry, it indicates that the entry was created automatically by the reversal process. |
Reversal Date | Journal Header | Specifies the date for an automatic reversal journal entry. |
Auto Gen Lines | Journal Header | Used to define auto generate lines flag. |
Adjustment Entry | Journal Header | Adjusting entry is an entry recorded at the end of the accounting period to record month end or year end adjustments which includes audit adjustments, adjustments performed to support financial reporting like GAAP, Full Accrual etc. |
Adjusting Period | Journal Header | Month-end or Year-end adjustments are segregated from the regular accounting period(s). Adjustment period is used to record the month end or year-end adjustment. |
Journal Line | Journal Line | Uniquely identifies a journal line with a sequence number. Within a single journal entry, the line sequence begins with 1 and automatically increments by 1 for each succeeding journal line. There can be any number of lines associated with a journal header. |
Unit | Journal Line | Represents the Business Unit. Used to define an organization or organizational subset that is independent with regards to one or more accounting or operational functions. |
Ledger | Journal Line | Defines the appropriate Ledger for the transaction. |
Account | Journal Line | Provides functionality to capture detailed transactional data. Can be specified as a balance sheet account or operating account. |
SpeedKey | Journal Line | Code that defines ChartField line information for GL Journals. The full ChartField String as defined in the SpeedKey will be populated onto the GL Journals during the file load process. |
Organization | Journal Line | Organization ChartField tracks information according to a breakdown of your organization. |
Fund | Journal Line | Fund is used to segregate and capture specific activities or classify certain objectives in accordance with special regulations, restrictions, or limitations. |
Budget Entity | Journal Line | Budget Entity represents organizations and/or functions to which appropriations are made and typically represents a program. Budget Entity will retain the same value as in the current business system. |
Category | Journal Line | Category represents both appropriation categories and revenue source codes. Category in PALM is mapped one-one with the current business system. |
State Program | Journal Line | State Program is used to identify the plan for an organization and use of resources to meet specified objectives of the State. |
Grant | Journal Line | Grant ID value used to track financial assistance that provides support or stimulation to accomplish a public purpose. |
Contract | Journal Line | Contract ChartField captures expenditure and revenue transactions for two party agreements. |
OA1 | Journal Line | OA1 is a flexible ChartField reserved for tracking for optional reporting or specific use. |
OA2 | Journal Line | OA2 is a flexible ChartField reserved for tracking for optional reporting or specific use. |
PC Business Unit | Journal Line | Used to define an organization or organizational subset that is independent with regards to one or more accounting or operational functions for Project related ChartFields. |
Project | Journal Line | Project is used to capture a planned undertaking, having a finite beginning and a finite ending, can cross fiscal years, for which expenditures/costs and revenues are to be tracked |
Activity | Journal Line | Activity tracks specific tasks that make up a Project and records transactional details; a Project must have at least one associated Activity ID. |
PC Source Type | Journal Line | The Source Type ChartField identifies the purpose or origin of a Project-related transaction. |
PC Category | Journal Line | The Project Category ChartField provides more flexibility and granularity in tracking and analyzing financial activity associated with a Project. |
PC Subcategory | Journal Line | The Subcategory ChartField provides more flexibility and granularity in tracking and analyzing financial activity associated with a Project. |
Base Amount | Journal Line | Specifies the monetary amount of a debit or credit in the business unit base currency. Debit entries are positive and credit entries are negative. Value includes decimal point and two decimals, i.e., 9999.99. |
Budget Date | Journal Line | Indicates the date within the correlating budget period that the journal is eligible to be budget checked against. |
Reference | Journal Line | Used to store a reference information for a particular line. |
Description | Journal Line | Description of the journal line which is populated with the Account ChartField value description as a default unless a specified value is provided. |
Inter/IntraUnit Group Number | Journal Line | Groups a set of journal lines as a set of InterUnit or IntraUnit transactions. |
Inter/IntraUnit Anchor | Journal Line | Indicates which journal line contains the anchor Business Unit value for the InterUnit or IntraUnit transactions. |
Version History
Date | Revision Description |
|---|---|
11/29/2023 | Original Version |
Was this article helpful?
