GA Quarterly Wage Report
Overview
The Georgia Department of Labor requires each liable employer to file a Quarterly Contribution and Wage Report. The report must show the worker’s details and the amount of wages paid during a calendar quarter. The generated report contains ‘Electronic Media Tax Record Format’(N record) and ‘Y2K Unemployment Insurance Format’(S record). There can only be a single ‘N’ record for each file followed by zero or multiple ‘S’ records.
The ‘Quarterly Wage Report’ option of the Regulatory Reporting application allows the creation of Quarterly Contribution and Wage reports for the state of Georgia. After all the input data related to the quarterly wages has been entered, the related reports can be obtained.
Report Frequency
Every quarter
Selection Criteria
All employees whose payroll were processed during the reporting period (with check note ‘DP’/’DT’) and having UI Total wage greater than zero are eligible for the quarterly wage report. If certain employee types such as students need not be included on the report, they can be excluded by specifying the employee type(s) to exclude when running the report.
BusinessPLUS Setup
Prior to generating quarterly wage reports, run payroll and all other check maintenance utility tasks in the BusinessPLUS application.
Only pay history records with following check notes are considered:
‘DP’(Distributed and paid check) / ‘DT’(Distributed hand-written check) will be considered; check notes with ‘DR’(Distributed original reverse checks) / ‘DO’(Distributed offset reversal check) will not be picked up.
In case of Check Reversals, manual corrections need to be made and the quarterly wage report need to be generated again.
Setup
Before a report can be generated, the reporting interface must be accessed and necessary data set up completed. This configuration information is used by the Load and Submission processes.
The following options need to be configured under the ‘Setup’ menu:
Site Profile
Report Profile
Crosswalk
Code Value
Additional Setup
Site Profile
Click Site Profile to define entities and their ‘Site Profile’ details. This information is used by the Load and Submission processes for the defined entities. At least one Site Profile record is required.
To add details about a ‘Site’, enter data in the fields of this window as described below.
Field | Description |
Entity* | ID of the entity/employer. The entity should be a valid entry as defined in BusinessPLUS. Once saved, the value cannot be changed. |
Employer Name* | Name of the employer for whom the entity is defined. |
Employer Address* | First line of the employer’s address. |
Employer Address (2) | Second line of the employer’s address. |
Employer City* | City in which the employer is located. |
Employer State* | State in which the employer is located. Click for the list of states. |
Employer Zip Code* | Numeric zip code of the employer’s location. This field accepts only five numeric characters and does not accept if all the five characters are zeroes. |
Employer Zip Code Extension | Numeric zip code extension of the employer’s location. This field accepts only numeric characters of 4 digits or less. |
Columns marked with * are required fields in edit mode.
Report Profile
Click the Report Profile to define the entity’s ‘Report Profile’ details. This information is used by the load and submission processes.
Enter data in the fields of this window as described below.
Field | Description |
Entity* | Select ‘Entity’ as defined in ‘Site Profile’ screen. Once the ‘Report Profile’ is saved for an entity, the value for ‘Entity’ field cannot be changed. Example: ROOT |
GDOL Employer Account Number* | The GDOL (Georgia Department of Labor) Employer Account Number. This should be a valid numeric entry of 8 characters. Hyphens, spaces are not allowed. Example: 11414750 |
UI Multi Unit Number |
|
UI Wage Limit* | Unemployment Insurance Wage Limit. This should be a valid entry between 0 and 999999.99 Example: 12520 |
UI Tax Rate* | Unemployment Insurance Tax Rate. This should be a valid entry between 0 and 99.999999 Example: 0.29 |
Employee Types to Exclude | Comma separated list of employee types who needs to be excluded during the extract. Example: FT,CNST NOTE: Each employee type can be maximum of 4 characters. Spaces should not be entered after/before commas. |
Columns marked with * are required fields in edit mode.
Crosswalk
The Crosswalk tab can be used to map the setup values. The predefined Code Items appear as a list when the ‘Crosswalk’ screen is loaded.
Code Value
Click Code Value to define valid codes.
Additional Setup
Click Additional Setup to define the entity’s ‘Setup’ details. See example below. This information is used by the Load and Submission processes.
Enter data in the fields of this window as described below.
Field | Description |
Entity* | Enter ‘Entity’ defined in ‘Site Profile’ screen. Once the ‘ICESA Setup’details are saved for the entity, the value for ‘Entity’ field cannot be changed. |
Gross Wages Pay Base* | Enter the 4-digit CDH code for calculating ‘Total Gross Wages’. Example: 6002 |
State UI Wages Pay Base* | Enter the 4-digit CDH code for calculating ‘Unemployment Insurance Total Wage’. Example: 6002 |
State Taxable Wages Pay Base* | Enter the 4-digit CDH for calculating ‘State Taxable Wages’. Example: 6004 |
State Tax Withholdings Deduction Code* | Enter the 4-digit CDH for calculating ‘State Income Tax Withheld’. Example: 2016 |
Columns marked with * are required fields in edit mode.
Pay Base values should fall in the range of 6001 - 6042.
Instance
Click Instance to configure a ‘Report Instance’ for each report to be created.
Report instances need to be configured for the extract process.
Enter data in the fields of this window as described below.
Field | Description |
Name* | Name of the report instance as defined by the user. Example: 2011 Quarter 2 Wage Report. |
Year* | Fiscal Year for which submission will occur. Note: Once the instance is created and saved, the ‘Fiscal Year’ value cannot be changed. |
Quarter* | Quarter for which the submission is required. Click for the list of ‘Quarter’. Note: Once the instance is created and saved, the ‘Quarter’ value cannot be changed. |
Status* | Indicates the status of the report instance. Valid choices are: Active, Locked, and Submitted. |
Date Submitted* | Date time stamp when changing to the ‘Submitted’ status. |
Update (Button) | Used to update the selected status. |
Columns marked with * are required fields in edit mode.
Load
Click on the Load to extract and load the generated report instance records into the Maintenance screen.
See the Submission File Layout section for the BusinessPLUS source of the reported data.
To load data for an instance of a report, enter data in the fields as described below.
Field/Button | Description |
Report Instance* | Click for the list of report instances. Select the desired report instance. |
Notes | Enter a note related to report instance or load that is to be performed. |
Entity* | Click to select a specific entity for which the load will be performed. Select ‘ALL’ to extract records of all entities. |
Employee ID(s) | If specific IDs are to be refreshed or reported on, enter in this line, separated by commas. |
Purge Existing Data | If all the existing data for the selected ‘Report Instance’ in the maintenance table needs to be deleted, this checkbox should be checked. This action will also remove new (recent) maintenance records added previously using the maintenance screen for the ‘Report Instance’. |
Load (Button) | Click to load maintenance records into maintenance table. |
Columns marked with * are required fields to Load.
After clicking ‘Load’ the information window appears, to indicate that the ‘Load Process’ has begun. Click on the ‘OK’ button to proceed further.
The selected report instance details appear as described below.
Field | Description |
Report Instance Details | Details of the selected Report Instance. |
Last Load for the Selected Report Instance | The date (Last Load) and user (Created By) who performed the last load and any notes entered for the selected ‘Report Instance’. If the report is loaded for the first time for the selected ‘Report Instance’, this information is blank. |
Maintenance
Click the Maintenance tab to view Load Process results, including generated errors. Data manipulation is allowed on the extracted employee data.
The table below describes the fields in the Maintenance view when selecting report instances.
Field | Description |
Report Instance | Click to select a specific instance. |
Filter By Criteria | Filter the maintenance records based on Employee ID or Employee Last Name. Clear fields to view all the results. |
Employee ID | ID of the employee. |
Employee Last Name | Last name of the employee. |
Apply Filter (Button) | Select the ‘Apply Filter’ button to filter on values entered in either the Employee ID or Employee Last Name. |
Total Record Count | Indicates the total number of maintenance records in the grid. |
Below describes the Error Log fields in the Maintenance view when selecting report instances.
Field | Description |
Error Log By Last | Click to select Load or Submission of the Report Instance. |
Filter Selected Record | Filters the selected maintenance record in the ‘Filter By Criteria’ area above for editing. |
Generate Report (Button) | Runs the ‘Error Log’ out to a generated report. Shows Load ID, Load Notes, Load Date, Error Details as well as the date the report was generated. |
The following actions are available in the Maintenance screen:
Data Changes (to data extracted from the report instance into the maintenance table).
Adding/Inserting Records.
Deleting Records.
Possible Error and Warning Messages
The grid at the bottom of the Maintenance screen displays error messages logged during the load extract/submission package execution. The Load and Submission errors include invalid/missing mandatory field values. These values can be corrected by selecting the specific record from the error log grid and clicking on the ‘Filter Selected Record’ checkbox. Although, the long-term data fix would need to occur in BusinessPLUS, then re-verified on the Report Setup, Site Profile, or Submission Process screens. On clicking the ‘Filter Select Record’ option, only the selected invalid record is filtered in the Maintenance grid, which can then be corrected and saved. On clicking ‘View All Records’, all the maintenance records will be displayed on the Maintenance grid for the selected load extract/submission package.
In a few cases, the error/warning may be informational only and should not significantly affect the Submission Process. See the Submission File Layout section in this user guide regarding the fields in question to verify if they are required or not. The Error/Warning Messages are described below in the Error Log Viewer table.
Type | Error / Warning Message | Resolution |
Load Pkg | No Profile setup found for UI Account Number - <UIAccountNo> | Correct in the Site Profile screen. |
Load Pkg | <Emp ID>: SUI Pay Base accumulator has not been set for the year - <Year> | Correct HR Employee Master and send to PY. |
Load Pkg | No Profile setup found for entity: <Entity> | Correct in the Site Profile screen. |
Load Pkg | <Emp ID>: has invalid(blank) SSN | Correct HR Employee Master and send to PY. |
Load Pkg | <Emp ID>: has invalid(blank) First Name | Correct HR Employee Master and send to PY. |
Load Pkg | <Emp ID>: has invalid(blank) Last Name | Correct HR Employee Master and send to PY. |
Load Pkg | <Emp ID>: has negative UI Total Wages | Correct HR Employee Master and send to PY. |
Load Pkg | <Emp ID>: has negative Total Gross Wages | Correct HR Employee Master and send to PY. |
Load Pkg | UI Wage Limit configuration has not been set for the entity - <Entity> | Correct in the Report Profile screen. |
Load Pkg | Pay Base Accumulator configurations have not been set for the entity - <Entity> | Correct in the Report Profile screen. |
Submission Pkg | <Emp ID>: has invalid(blank) SSN | Correct HR Employee Master and send to PY or in the Maintenance screen. |
Submission Pkg | <Emp ID>: has invalid(blank) First Name | Correct HR Employee Master and send to PY or in the Maintenance screen. |
Submission Pkg | <Emp ID>: has invalid(blank) Last Name | Correct HR Employee Master and send to PY or in the Maintenance screen. |
Submission Pkg | <Emp ID>: has invalid(blank) Middle Name | Correct HR Employee Master and send to PY or in the Maintenance screen. |
Submission Pkg | <Emp ID>: has invalid(blank) State Code | Correct HR Employee Master and send to PY or in the Maintenance screen. |
Submission Pkg | <Emp ID>: has invalid(blank) Unemployment Insurance Total Wage | Correct HR Employee Master and send to PY. Remove? |
Submission Pkg | <Emp ID>: has invalid(blank) GDOL Employer Account No. | Correct in the Site Profile screen. |
Submission Pkg | <Emp ID>: has invalid(blank) Reporting Period Quarter | Correct HR Employee Master and send to PY. |
Submission Pkg | <Emp ID>: has invalid(blank) Reporting Period Year | Correct HR Employee Master and send to PY. |
Submission Pkg | <Emp ID>: has an invalid(characters) First Name | Correct HR Employee Master and send to PY or in the Maintenance screen. |
Submission Pkg | <Emp ID>: has an invalid(characters) Last Name | Correct HR Employee Master and send to PY or in the Maintenance screen. |
Submission Pkg | <Emp ID>: has an invalid(characters) Middle Name | Correct HR Employee Master and send to PY or in the Maintenance screen. |
‘Load’ indicates the message appears during the Load Process, on the bottom of the Maintenance screen.
‘Sub’ indicates the message appears on the Submission report.
The report instances dropdown list is loaded only with report instances for which ‘load’ has happened.
Inserting and deleting records are not allowed if there are unsaved changes in the grid.
If there are unsaved changes in the grid, sorting and filtering of the grid are disabled.
If there are unsaved changes in the grid, a prompt to save the existing changes will be shown, if trying to navigate to another screen.
Submission
After verifying the maintenance data, click Submission to create the file to be submitted to the reporting agency.
To create a report file for submission, data is entered in the fields as described below.
Field/Button | Description |
Report Instance* | Click for the list of report instances. Choose the report instance which is to be submitted. |
Notes | Any notes applicable to the submission job. |
Filename* | System generated or user defined file name for the submission file. The filename should always end with the ‘.txt’ extension. The filename cannot contain these characters ‘\:/*?”<>|’ NOTE: The path where the file is saved is already configured in the application and should not be entered here. In some reports, the report name is auto-generated and hence the text filename cannot be changes for such reports. Example: 2011_Quarter2.txt |
Entity* | Click for the list of entities. If the maintenance records for all the entities are to be submitted, then ‘ALL’ should be selected. |
Remittance | Manually entered by end user at run time based on the DOL-4N ‘Remittance’ worksheet referred from line 10, Total Amount Due. http://www.dol.state.ga.us/pdf/forms/dol4n.pdf. |
Report Instance Details | Details for the selected ‘Report Instance’. |
Last Submission for the Selected Report Instance | The date(Last Submission) and user(Created By) who performed the last submission and the note that was entered for submitting the selected ‘Report Instance’. |
Double Arrow (Button) | Regenerate the Filename. |
Generate Report (Button) | Create report file with data from maintenance table. |
View Report (Button) | View the submission file report. |
Columns marked with * are required fields to ‘Generate Report’.
Only if the ‘Load’ is performed on the report instance, the report instance will appear in the ‘Report Instance’ dropdown list.
If required fields are empty or have an invalid value, an error is logged which can be corrected from the ‘Maintenance’ screen.
Submission File Layout
The following table shows the field numbers, field names, and source within BusinessPLUS and Columns for ‘N’ and ‘S’ records:
Electronic Media Tax Record Format – ‘N’ record
Position | Field | Req. | Type | Size | Source Table | Source Column | Description/Business Logic |
1 | Record Identifier | Y | A | 1 | N/A | N/A | Constant ‘N’. |
2-9 | Account | Y | N | 8 | rr_icesa_profile | ui_account_no | 8-digit GDOL Employer Account Number. Numeric only; omit hyphens, spaces and check digit. |
10 | Quarter | Y | A | 1 | rr_run_def_mstr | quarter | Quarter for which this report applies. 1, 2, 3, or 4 are the only valid entries. |
11-14 | Year | Y | A | 4 | rr_run_def_mstr | year | Four-digit year for which this report applies. |
15-19 | Number Employees |
| A | 5 | Calculated | Calculated | Total Number of covered workers during the pay period that includes the 12th day of the first month of the quarter. For each worker, The pay periods that include 12th of first month of reporting quarter are determined. If count of payroll history records for the employee and pay periods associated with the month with py_check_note among ‘DP’ or ‘DT’ is greater than 0, add 1 to the count. Right justified and zero filled. |
20-24 | Number Employees |
| N | 5 | Calculated | Calculated | Total Number of covered workers during the pay period that includes the 12th day of the second month of the quarter. For each worker, The pay periods that include 12th of second month of reporting quarter are determined. If count of payroll history records for the employee and pay periods associated with the month with py_check_note among ‘DP’ or ‘DT’ is greater than 0, add 1 to the count. Right justified and zero filled. |
25-29 | Number Employees |
| N | 5 | Calculated | Calculated | Total Number of covered workers during the pay period that includes the 12th day of the third month of the quarter. For each worker, The pay periods that include 12th of third month of reporting quarter are determined. If count of payroll history records for the employee and pay periods associated with the month with py_check_note among ‘DP’ or ‘DT’ is greater than 0, add 1 to the count. Right justified and zero filled. |
30-40 | Total Wages | Y | N | 11 | pyx_xtd_dtl | pyx_qtd99 | Sum of all Gross wages before deductions except for federally allowed cafeteria deductions for the reporting quarter. For each worker, Gross Wages is calculated as per below: pyx_qtd99 where 99 is the quarter for which the reporting quarter belongs. Right justified and zero filled. |
41-51 | Non-Taxable Wages | Y | N | 9 | Calculated | Calculated | Sum of all Non-Taxable Wages calculated for each worker for the reporting quarter. For each worker, Non-taxable wages is calculated as per below: if(UI Wage Limit > 0) { if(UI Total Wage YTD > UI Wage Limit) if( UI Total Wage YTD – UI Total Wage) >= UI Wage Limit Non-taxable Wage = 0 else Non-taxable Wage = UI Total Wage YTD – UI Wage Limit else Non-taxable Wage = 0 } Right justified and zero filled. |
52-62 | Taxable Wages | Y | N | 11 | Calculated | Calculated | Taxable wages for the reporting quarter. (Total Wages) – ( Non-Taxable Wages). Right justify and zero fill. |
63-71 | Remittance | Y | N | 9 | pyx_xtd_dtl | pyx_qtd(qtr) | Manually entered by end user at run time based on the DOL-4N ‘Remittance’ worksheet referred from line 10, Total Amount Due. http://www.dol.state.ga.us/pdf/forms/dol4n.pdf Enter amount of remittance from line 10 of Part II of the DOL-4. Right justify and zero fill. Example: Enter $12,432.10 as 001243210 |
72-80 | Constant | Y | A | 9 | N/A | N/A | Blanks |
Data Types
A/N - Alpha Numeric, left justified, and blank.
N - Numeric, right justified, zero, unsigned without decimal point, cents, and dollars.
Record Length: 80 bytes/characters plus one character for carriage return and one character for line feed.
Y2K Unemployment Insurance Format – ‘S’ record
Position | Field | Req. | Type | Size | Source Table | Source Column | Description/Business Logic |
1 | Record Identifier | Y | A | 1 | N/A | N/A | Constant ‘S’. |
2-10 | Social Security Number | Y | N | 9 | hr_pe_mstr | hr_pe_ssn | Employee SSN. |
11-30 | Employee Last Name | Y | A | 20 | hr_pe_mstr | py_emp_l_name | Employee Last Name. left justified, All CAPS, no lower-case characters. |
31-42 | Employee First Name | Y | A | 12 | hr_pe_mstr | py_emp_f_name | Employee First Name, left justified, All CAPS, no lower-case characters. |
43 | Employee Middle Initial | Y | A | 1 | hr_pe_mstr | py_emp_m_name | Employee Middle Initial. All CAPS, no lower-case characters. |
44-45 | State Code | Y | N | 2 | rr_state_codes | state_no | Enter the appropriate FIPS postal numeric code. The Georgia code is ‘13’. |
46-63 | GDOL Wage Filler |
| N | 18 | N/A | N/A | Enter blanks or zeros. |
64-68 | GDOL Wage Filler |
| A/N | 5 | N/A | N/A | Enter blanks or zeros. |
69-77 | State QTR Total Gross Wages | Y | N | 9 | pyx_xtd_dtl | pyx_qtd99 | Quarterly wages subject to all taxes. pyx_qtd99 where 99 is the quarter for which the reporting quarter belongs. Right justified and zero filled. |
78-153 | Blanks | N | A/N | 76 | N/A | N/A | Not required by GDOL. |
154-161 | GDOL Employer Account Number | Y | N | 8 | rr_icesa_profile | ui_account_no | 8-digit GDOL Employer Account Number. No hyphens/spaces. |
162-214 | Blanks | N | A/N | 53 | N/A | N/A | Not required by GDOL. |
215-220 | Reporting Period Month/Year | Y | N | 6 | rr_run_def_mstr | year, quarter | The last month and year for the calendar quarter for which this report applies. Example: 032000 for January-March of 2000. |
221-275 | Blanks | N | A | 55 | N/A | N/A | Not required by GDOL. |
276 | Blanks | N | A | 1 | N/A | N/A | If necessary, enter a blank. |
Record Length: 275 bytes/characters plus one character for carriage return and one character for line feed.
Submission Report
The submission file report can be obtained by clicking Generate Report or View Report buttons on the ‘Submission’ window.
About
The About screen displays system level information about the report such as the version, report name and database details.