Outbound Payroll with Accounting Detail File (PRI058)
-
Print
-
DarkLight
-
PDF
Outbound Payroll with Accounting Detail File (PRI058)
-
Print
-
DarkLight
-
PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Interface Description
After the payroll has been calculated, the State of Florida’s actuals distribution process will run to designate the payroll accounting distributions for the calculated payroll. Agencies can update funding before the final pay calculation and confirmation. Once payroll is confirmed, the actuals distribution process will run again to generate the final payroll accounting distributions that will be sent to Florida PALM’s General Ledger. The Journal Generator process in Florida PALM’s General Ledger (GL) module will also run to create and post the journals associated with the confirmed payroll.
PRI058 – Outbound Payroll with Accounting Detail File is an interface that will be generated after scheduled and confirmed on-cycle and off-cycle payrolls. The interface program will extract the data from the HR Accounting Line in the payroll module in Florida PALM based on the final payroll accounting distributions. The HR Accounting Line contains multiple rows per paycheck issued in payroll. Each paycheck contains multiple employer charges (earnings, employer deductions, and employer taxes) that could have different funding allocations. The HR Accounting Line will have a row for every unique funding distribution for employer charges. This interface program will map the funding distribution to the earning code, deduction code, or tax class corresponding to the employer charge and other payroll data for agency business systems (ABS).
Click below to view the interface file layout and sample data file.
Business Process Model
This interface can be found in the following business processes:
Selection Criteria
The interface data selection criteria includes the following:
Data Field | Data Field Details |
|---|---|
Process Run Mode | Required |
Pay Run ID | Conditional – required if Company, Pay Group, and Pay End Date are blank. |
Company | Conditional – required if Pay Run ID is blank. |
Pay Group | Conditional – required if Pay Run ID is blank. |
Pay End Date | Conditional – required if Pay Run ID is blank. |
From Date | Optional |
To Date | Optional |
Run Type | Required |
Business Unit | Conditional – required if “Agency” run type is selected. |
File Layout
Field names and descriptions from the interface layout are provided below.
| Data Field Name | Record Type | Data Field Description |
|---|---|---|
| Record Code | Header | Record Code identifying the information on the record for: Header |
| Date | Header | This field is the date that the interface file was created by Florida PALM. |
| System ID | Header | This field indicates the source system of the data on the file and is used for tracking interface files. |
| Filler 1 | Header | This field is reserved for future use in Florida PALM |
| Filler 2 | Header | This field is reserved for future use in Florida PALM |
| Filler 3 | Header | This field is reserved for future use in Florida PALM |
| Filler 4 | Header | This field is reserved for future use in Florida PALM |
| Filler 5 | Header | This field is reserved for future use in Florida PALM |
| Record Code | Detail | Record Code identifying the information on the record for: Detail |
| Employee ID | Detail | Employee ID is a unique employee identifier assigned to each employee in Florida PALM. |
| Employee Record | Detail | Employee Record identifies the employee's job instance for if they had multiple assignments. |
| First Name | Detail | First name of employee. |
| Middle Name | Detail | Middle name of employee. |
| Last Name | Detail | Last name of employee. |
| Position Number | Detail | Position Number is a unique number assigned to the employee's position. |
| Pay End Date | Detail | The Pay End Date is the last day of the pay period for which payroll was processed. This date determined by the pay calendar. |
| Earnings Begin Date | Detail | The Earnings Begin Date is the begin date of the period for which the earnings apply. |
| Earnings End Date | Detail | The Earnings End Date is the end date of the period for which the earnings apply. |
| Earning Code | Detail | Earning Code indicates the type of earnings/wages made by the employee. |
| Tax Class | Detail | Tax Class indicates the type of taxes withheld from the employee's pay or paid by the employer. |
| Deduction Code | Detail | Deduction Code indicates the type of deduction taken from the employee's pay or paid by the employer. |
| Paycheck Number | Detail | Paycheck Number is the unique number assigned to an employee's paycheck (warrant or pay advice) after payroll has been confirmed. |
| Paycheck Date | Detail | The Paycheck Date indicates the date for when the paycheck is paid. |
| Journal ID | Detail | Identifies a journal entry, consisting of a header and one or more lines. The Journal ID itself does not have to be unique, but together with the journal business unit and journal date, it forms a unique journal identifier. |
| Journal Line | Detail | Journal Line identifies the line number of the journal entry created from the accounting distribution. |
| Run Date | Detail | The Run Date indicates the date for when the rows were created on the HR Accounting Line after PAYGL02 was run. |
| Accounting Date | Detail | The Accounting Date indicates the Pay End Date associated to the paycheck. The Pay End Date is the last day of the pay period. |
| Budget Date | Detail | The Budget Date will contain the Fixed Capital Outlay (FCO) budget year for funding out of FCO Categories. If the funding is not out of an FCO Category, the budget year will be the Fiscal Year. The month and day will always be 06/30. |
| Monetary Amount | Detail | Monetary Amount indicates the total amount posted to the ChartField combination. |
| GL Business Unit | Detail | GL Business Unit represents an organization/agency at an appropriation level and is used to define a financial reporting entity for General Ledger reporting. |
| Organization | Detail | Organization ChartField tracks information according to a breakdown of your organization. |
| Account | Detail | Account provides functionality to capture detailed transactional data. Can be specified as a balance sheet account or operating account. |
| Line Description | Detail | Line Description represents the description of the charge posted against the ChartField combination. |
| Fund | Detail | Fund is used to segregate and capture specific activities or classify certain objectives in accordance with special regulations, restrictions, or limitations (e.g., restricted Fund). Legacy Mapping: GAAFR, SF, FID |
| Budget Entity | Detail | Budget Entity ChartField 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 | Detail | Category represents both appropriation categories and revenue source codes. Category in PALM is mapped one-one with the current business system. |
| State Program | Detail | State Program is used to identify the plan for an organization and use of resources to meet specified objectives of the State. Legacy Mapping: State Program Component |
| Grant | Detail | Grant ID value used to track financial assistance that provides support or stimulation to accomplish a public purpose. |
| Contract | Detail | Contract ChartField captures expenditure and revenue transactions for two party agreements. |
| OA1 | Detail | OA1 is a flexible ChartField reserved for tracking for optional reporting or specific use. Legacy Mapping: None |
| OA2 | Detail | OA2 is a flexible ChartField reserved for tracking for optional reporting or specific use. Legacy Mapping: None |
| Project | Detail | 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 | Detail | 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 | Detail | PC Source Type ChartField identifies the purpose or origin of a Project-related transaction. Legacy Mapping: None |
| PC Category | Detail | PC Category ChartField provides more flexibility and granularity in tracking and analyzing financial activity associated with a Project. Legacy Mapping: None |
| PC Subcategory | Detail | PC Subcategory ChartField provides more flexibility and granularity in tracking and analyzing financial activity associated with a Project. |
| Filler 1 | Detail | This field is reserved for future use in Florida PALM |
| Filler 2 | Detail | This field is reserved for future use in Florida PALM |
| Filler 3 | Detail | This field is reserved for future use in Florida PALM |
| Filler 4 | Detail | This field is reserved for future use in Florida PALM |
| Filler 5 | Detail | This field is reserved for future use in Florida PALM |
| Filler 6 | Detail | This field is reserved for future use in Florida PALM |
| Filler 7 | Detail | This field is reserved for future use in Florida PALM |
| Filler 8 | Detail | This field is reserved for future use in Florida PALM |
| Filler 9 | Detail | This field is reserved for future use in Florida PALM |
| Filler 10 | Detail | This field is reserved for future use in Florida PALM |
| Record Code | Trailer | Record Code identifying the information on the record for: Trailer |
| Count | Trailer | This field gives the total number of records in the file, excluding header and trailer rows. |
Version History
Date | Revision Description |
|---|---|
08/21/2024 | Original Version |
Was this article helpful?
