This page (revision-22) was last changed on 26-Nov-2021 10:22 by Meg McFarland

This page was created on 26-Nov-2021 10:22 by jmyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
22 26-Nov-2021 10:22 8 KB Meg McFarland to previous
21 26-Nov-2021 10:22 8 KB Meg McFarland to previous | to last

Page References

Incoming links Outgoing links
Tax Reporting - FL
Tax Reporting - FL

Version management

Difference between version and

At line 4 added 5 lines
!!What's New for Tax Year 2009?
Florida State does not have State Personal Income Tax.
There were no format change in wage reporting for tax year 2009.
At line 6 changed one line
This document contains abbreviated set up requirements for the State of Florida only. Please refer to the general document ([Tax Reporting - US General]) for other setup procedures that may also be required.
This document contains abbreviated set up requirement for the specific state only, please refer to the general document ([US_Annual_Qtrly_Reporting_GEN]) for other setup procedure that may also be required.
At line 10 changed 2 lines
*[IDGV Variables|IDGV#VariablesTab] tab must be set up with ‘State Registration’ for State/Province: Florida
**‘W2 STATE MEDIA FILING’- Must be ‘02’ to generate the Florida State magnetic media file for Florida State only
*[IDGV Variables Tab must be set up with ‘State Registration’ for State/Province: Florida
At line 13 removed 12 lines
!IDGV - State SUI Registration
*[IDGV] must be set up with ‘State SUI Registration’ for State/Province: Florida
**The Regist# field must contain the Florida UI Account Number (7 characters)
**‘Govt Rate Type’ must be entered with ‘US SUI Max Base Amt’ in order to calculate the UI Taxable Earnings and UI Excess Earnings
*[IDGV Variables|IDGV#VariablesTab] tab must be set up with ‘State SUI Registration’ for State/Province: Florida
*The ‘W2 State Media Filing’ values are:
**00 – Not Required to file magnetic media to the State
**01 – Include State Code RS record in the Federal File, the user can send federal file to the State
**02 – State requires its own File, do not include other State information in the State File
*‘W2 STATE MEDIA FILING’ - Must be ‘02’ to generate UI wage magnetic media file for state of Florida
*For each quarter, the user must manually enter the applicable QTR amounts prior to running [RPYEU] to report for that quarter
*If an existing amount is not applicable for that quarter, that amount should be deleted.
At line 26 changed 7 lines
!!State File Procedures
Florida State does not have State Personal Income Tax. \\
The Florida Department of Revenue accepts the filing of UI quarterly wages via XML format
*The previous filing of UI quarterly wages via magnetic media using MMREF-1 format for record codes: RA,RE,RS,RT are not used
*The quarterly Florida XML file format is defined on [IDIF] and is provided to users similar to [IDFD] Form Code
*Users must register with State of Florida to obtain a User Name and password [http://dor.myflorida.com/dor/eservices/]
*After login, the user should download the ‘Florida XML Schema’ in order to validate the XML file generated by [RPYEU] prior to submission to the government
‘W2 STATE MEDIA FILING’ - Must be ‘02’ to generate FL State magnetic media file for FL State only
IDGV - State SUI Registration
At line 34 changed 4 lines
!!IDIF – HL$US-QTR-FL2010 – XML Format
*The ‘Variable Name’ field indicates where the data is coming from for each XML tag
*This ‘Variable Name’ should be referred to for each tag and [IDFDV] Identifiers should be set up appropriately
*This [IDIF] Florida XML file supports the filing of quarterly wages only. The payment information is not supported in this [IDIF] layout
- IDGV must be set up with ‘State SUI Registration’ for State/Province: Florida
At line 39 changed 3 lines
!!Quarterly UI Wage Reporting - XML Format
!RPYEU
[RPYEU] must be run with the following report parameters and filters selected to generate the Florida State file information: \\ \\
At line 43 removed 9 lines
__RPYEU Report Parameters__
|Annual Form Code|Use standard form code, such as 'HL$US-W2-20YY'
|Quarterly Form Code|Use the standard form code ‘HL$US-QTR-FL20YY. \\Must be entered in order to generate the Florida UI wage file in the XML format
|Govt Interface Format|Mandatory. Enter HL$US-QTR-MM20YY
|Period Type|Mandatory. Defines the period type. Enter "Quarter" for quarterly reporting.
|Period End Date|Mandatory. Defines the end date of the reporting period. Enter in DD-MMM-YYYY format
|Media Format|Mandatory. Set to State SUI File Format \\Defines the Federal file format for SSA reporting (includes 'RW' and 'RS' records).
|Directory Name| Mandatory. Defines the name of the government Magnetic Media file. Must be defined or an output file will not be produced
|Media File Name|Mandatory. Defines the media file name of the data being uploaded. Must be defined or an output file will not be produced
At line 53 changed 2 lines
__RPYEU Report Filters__
|Select State: Florida, USA
- the Regist# field must contain the Florida UI Account Number (7 characters)
- the user must enter an entry on ‘Govt Rate Type’ with ‘US SUI Max Base Amt’ in order to calculate the UI Taxable Earnings and UI Excess Earnings
At line 56 removed 4 lines
!RPYEU – Sample Files Generated
When [RPYEU] is run, if the ‘Govt Interface Format’ is defined, an [IDIF] interface file will be generated with file name ‘_idif’\\[Tax Reporting FL_01.jpg]\\
|FL_QTR_SUI_222601_idif.xml|An interface govt file according to [IDIF] format
|FL_QTR_SUI_222601.xml|An xml file available to print by RPW2
At line 61 changed 3 lines
\\
!Validating Florida XML Files
*The govt xml file must be validated according to the downloaded government xml schema using a validating parser prior to sending to the government. \\
- IDGV Variables Tab must be set up with ‘State SUI Registration’ for State/Province: Florida
At line 65 changed one line
A validating parser from any third party tool will perform the following checks to the govt xml file generated by [RPYEU]:
At line 67 changed 3 lines
# Verify the govt xml document is properly created according to the XML syntax rules, such as the file is well formed, no missing xml tags, etc.
# Verify the govt xml document conforms to the schema downloaded from the government web site
*The validating parser software is not provided by High Line. Organizations must use their own validating parser \\ \\
- the ‘W2 State Media Filing’ values are:
00 – Not Required to file magnetic media to the State
01 – Include State Code RS record in the Federal File, the user can send federal file to the State
02 – State requires its own File, do not include other State information in the State File
At line 71 changed 4 lines
The validating parser is used to validate the xml file for the following validation:
*The Florida XML schema should be downloaded into a directory, such as C:\US States Downloads
*Move the RPYEU generated file FL_QTR_SUI_222601_idif.xml to the schema directory
*Open FL_QTR_SUI_222601_idif.xml with a validating parser
‘W2 STATE MEDIA FILING’ - Must be ‘02’ to generate UI wage magnetic media file for state of Florida
At line 76 removed 2 lines
!XML – Special Characters
The following special characters are not allowed to be stored in the xml file directly. These characters must be translated when writing to the xml file:
At line 79 changed 6 lines
||Special Characters||Value in xml File||Meaning
|<|&lt;|less than
|“|&quot;|double quote
|>|&gt;|greater than
|‘|&apos;|apostrophe
|&|&amp;|ampersand
At line 86 changed one line
Example from govt xml file:\\[Tax Reporting FL_03.jpg]\\
- for each quarter, the user must manually enter the applicable QTR amounts prior to running RPYEU to report for that quarter
- if an existing amount is not applicable for that quarter, the user should delete that amount
At line 52 added 154 lines
STATE FILE PROCEDURES
- Florida State does not have State Personal Income Tax.
- Starting 2007 quarterly reporting, the Florida Department of Revenue accepts the filing of UI quarterly wages via XML format
- The previous filing of UI quarterly wages via magnetic media using MMREF-1 format for record codes: RA,RE,RS,RT are not used
- the quarterly Florida XML file format is defined on IDIF screen and is provided to users similar to IDFD Form Code
- The user must register with State of Florida to obtain the User Name and password http://dor.myflorida.com/dor/eservices/
- After login, the user should download the ‘Florida XML Schema’ in order to validate the XML file generated by RPYEU prior to submission to the government
IDIF – HL$US-QTR-FL2008 – XML format
- the ‘Variable Name’ field indicates where the data is coming from for each XML tag
- the user should refer to this ‘Variable Name’ for each Tag and set up IDFDV Identifiers appropriately
- this IDIF Florida XML File supports the filing of quarterly wages only, the Payment information is not supported in this IDIF layout
QUARTERLY UI Wage Reporting – XML format (Starting 2007 Quarterly reporting)
Select State - mandatory, must be Florida
Annual Form Code - mandatory, must specify the most current year’s W2 Form Code from IDFDV
Govt Interface Format - mandatory, must specify the IDIF format that is available for Florida quarterly reporting
Period Type - mandatory, must be ‘Quarter’, and the user must enter the appropriate Period End Date
Media Format - mandatory, must be ‘State SUI File Format’ for quarterly reporting
Please enter the other parameters appropriately.
RPYEU – Sample Report
RPYEU – Sample Files generated
- when RPYEU is run, if the ‘Govt Interface Format’ is specified, an IDIF interface file will be generated with file name ‘_idif’
FL_QTR_SUI_222601_idif.xml - an interface govt file according to IDIF format
FL_QTR_SUI_222601.xml - an xml file available to print by RPW2
FL_QTR_SUI_222601.txt - the govt file in EFW2 format (used prior to 2007 XML file)
RPYEU – Sample Florida XML Files
Validating Florida XML Files
- the user must validate the govt xml file according to the downloaded government xml schema using a validating parser prior to sending to the government
- a validating parser from any third party tool will perform the following checks to the govt xml file generated by RPYEU
(1) - verify the govt xml document is properly created according to the XML syntax rules, i.e. the file is well formed, no missing xml tags etc
(2) - verify the govt xml document conforms to the schema downloaded from the government web site
- the validating parser software will not be provided, the user must use the validating parser of their own
- the following is a list of some of the parsers available on the market:
XML editors that provide a validating parser:
XML Spy (http://www.altova.com/products_ide.html)
Stylus (http://www.stylusstudio.com/)
XRay (http://architag.com/xray/)
XMLMind (http://www.xmlmind.com/xmleditor/)
Cooktop (http://www.xmlcooktop.com/)
- the XMLSPY editor is being used to validate the xml file for the following validation
- user should download the Florida XML schema into a directory, e.g. C:\US States Downloads
- move the RPYEU generated file FL_QTR_SUI_222601_idif.xml to the schema directory
- open FL_QTR_SUI_222601_idif.xml with the validating parser, e.g. XMPSPY
In XMLSPY, if the user encounters this message, click ‘DTD/Schema’ and choose ‘Assign Schema’ and select the schema location.
Follow the XMLSPY instructions to select the schema location:
After the Schema location is assigned, then click ‘Revalidate’.
The user may click the ‘Yellow Tick’ toggle to check if the file is well-formed.
The user may click the ‘Green Tick’ toggle to check if the file is valid according to the Assigned Schema.
After the XML file is validated, the user can send to the State government.
XML – Special Characters
- the following special characters are not allowed to be stored in the xml file directly, these characters require to be translated when writing to the xml file
Special Characters Value in xml file Meaning
< &lt; less than
“ &quot; double quote
> &gt; greater than
‘ &apos; apostrophe
& &amp; ampersand
Example from govt xml file:
At line 90 changed 6 lines
<BusinessAddress>\\
<BusinessName>HIGH LINE CORPORATION</BusinessName>\\
<AddressLine>283 MAJOR ELLIOT WAY UNIT 200</AddressLine>\\
<City>LINDENBERG</City>\\
<StateOrProvince>OH</StateOrProvince>\\
<ZipCode>937433333</ZipCode>\\
<BusinessAddress>
<BusinessName>HIGH LINE &amp; CATHY&apos;S USA CORPORATION</BusinessName>
<AddressLine>283 MAJOR ELLIOT WAY UNIT 200</AddressLine>
<City>LINDENBERG</City>
<StateOrProvince>OH</StateOrProvince>
<ZipCode>937433333</ZipCode>
At line 98 removed 4 lines
!!Quarterly UI Wage Reporting – XML Format
[RPYEU] must be run and the following selected to generate Florida State file information:
|Media Format: State SUI File Format
|Select State: Florida, USA
At line 103 removed 2 lines
%%information NOTE: The following ‘Not Required’ fields may or may not always contain blanks.%% \\
%%information NOTE: Columns with FL indicates it is a Florida specific requirement which is not the standard record format.%%
At line 106 changed 2 lines
!!State Magnetic Media Reporting - XML Specification
__Please note that only mandatory tags are provided with 'Source'. Most optional tags, if required, can be populated with constant values.__
At line 109 changed one line
*If an organization has more than one State Registration Number, High Line recommends that RPYEU be run with one state registration number at a time, as the XML file does not appear to allow more than one state registration number to be submitted at the same time.
QUARTERLY UI Wage Reporting – MMREF-1 format (Not Used after 2007)
At line 112 changed 69 lines
!XML Record Specifications
||XML tag|
|<Jurisdiction>
|<Transmission Id>
|<Transmission Timestamp>
|<Tranmitter ETIN>
|<Processing Type>
|<Origin Id>
|<Originator Timestamp>
|<OriginManifest itemCount>
|<ItemReference contentLocation>
|<Agent/Employer ID Number>
|<Origintor EFIN>
|<EFIN Type>
|<Quarter Ending>
|<Quarter Year>
|<Software Id>
|<Return Type>
|<Form Type>
|<Filing Action>
|<Filing Reason>
|<Employer's FEI Type>
|<Employer's FEI Number>
|<State EIN Type>
|<RT Account Number>
|<Employer's Name>
|<Mailing Address>
|<City>
|<State>
|<ZIP Code>
|<Telephone Number>
|<Contact First Name>
|<Contact Middle Name>
|<Contact Last Name>
|<Contact Name Suffix>
|<Contact Phone>
|<Contact Email Address>
|<Final Return>
|<Gross wages paid this quarter>
|<Excess wages paid this quarter>
|<Taxable wages paid this quarter>
|<Contribution Rate>
|<Contribution Due (Tax Due)>
|<Interest due>
|<Penalty due>
|<Total amount due>
|<Employee's Social Security Number>
|<Employee First Name>
|<Employee Middle Initial>
|<Employee Last Name>
|<Employee Name Suffix>
|<Employee's Gross Wages Paid This Quarter>
|<Employee's Taxable Wages Paid This Quarter>
|<Out of State Total Wages>
|<Out of State Taxable Wages Paid Year to Date>
|<Tax State>
|<Educational Wages>
|<Number of Employees>
|<Covered Workers - 1st Month>
|<Covered Workers - 2nd Month>
|<Covered Workers - 3rd Month>
|<Payment Method>
|<ACH Routing Transit>
|<Account Number>
|<Account Type>
|<Corporate or Personal Account Type>
|<Payment type>
|<Payment Amount>
|<Settlement Date>
- The user must run RPYEU and select the following to generate Florida State file information:
Media Format: - State SUI File Format
Select State: - Florida, USA
At line 228 added 173 lines
QUARTERLY UI Wage MAGNETIC MEDIA MMREF-1 format (Not Used after 2007)
(Please note that the following ‘Not Required’ fields may or may not always contain BLANKS).
Note: Columns with FL indicates it is a Florida specific requirement which is not the standard record format
Record name: Code RA - Transmitter Record
Column Description
1-2 - Record Identifier
- Constant "RA"
3-11 - Submitter’s Employer ID number (EIN)
- Numeric only
- Derived from IDFDV screen, Field Identifier: ‘SUB-ER-EIN’
12-19 FL - Agent or Employer Identification Number
- Derived from IDFDV screen, Field Identifier: ‘SUB-PIN-NUMBER’
20-37 FL - Blanks
38-94 - Company Name
- Derived from IDFDV screen, Field Identifier: ‘SUB-COMP-NAME’
95-395 FL - Blanks
396-422 - Contact Name
- Derived from IDFDV screen, Field Identifier: ‘SUB-CONT-NAME’
423-437 - Contact Phone Number
- Derived from IDFDV screen, Field Identifier: ‘SUB-CONT-TEL’
438-442 - Contact Phone Extension
- Derived from IDFDV screen, Field Identifier: ‘SUB-CONT-TEL-EXT’
443-445 - Blanks
446-485 - Contact E-mail
- Derived from IDFDV screen, Field Identifier: ‘SUB-CONT-EMAIL’
486-488 - Blanks
489-498 - Contact FAX
- Derived from IDFDV screen, Field Identifier: ‘SUB-CONT-FAX’
499-512 FL - Blanks
Record name: Code RE - Employer Record
Column Description
1-2 - Record Identifier
- Constant "RE"
3-7 FL - Blanks.
8-16 -Employer/Agent EIN
- System derived the applicable Federal reporting EIN, from IDGV or IDGR
17-39 FL - Blanks
40-96 - Employer Name
- Derived from IDFDV screen, Field Identifier: ‘W2-ER-NAME’
97-118 FL - Blanks
119-140 - Employer Delivery Address
- Derived from IDFDV screen, Field Identifier: ‘W2-ER-DELIV-ADDR’
141-162 - Employer City
- Derived from IDFDV screen, Field Identifier: ‘W2-ER-CITY’
163-164 - Employer State Abbreviation
- Derived from IDFDV screen, Field Identifier: ‘W2-ER-STATE’
165-169 - Employer ZIP Code
- Derived from IDFDV screen, Field Identifier: ‘W2-ER-ZIP’
170-173 - Employer ZIP Code Extension
- Derived from IDFDV screen, Field Identifier: ‘W2-ER-ZIP-EXT’
174-512 - Blanks
Record name: Code RS - Supplemental Record
Column Description
1-2 - Record Identifier
- Constant "RS"
3-4 - State code, appropriate FIPS postal numeric code
- system Derived from the State being reported, from IDFDV sequence 7000.
- e.g. Florida is code "12"
5-9 - Taxing Entity Code
- if County, City or School district tax is reported, this field is derived from IDGV 'W2 TAXING ENTITY' field for the County, City or School district tax being reported
10-18 - Social Security Number
- Derived from IDFDV screen, Field Identifier: ‘W2-EE-SSN’
- if an invalid SSN is encountered, this field is entered with zeroes.
19-33 - Employee First Name
- Derived from IDFDV screen, Field Identifier: ‘W2-EE-FIRST-NAME’
34-48 - Employee Middle Name or Initial
- Derived from IDFDV screen, Field Identifier: ‘W2-EE-MIDDLE’
49-68 - Employee Last Name
- Derived from IDFDV screen, Field Identifier: ‘W2-EE-LAST-NAME’
69-72 - Employee Suffix
- Derived from IDFDV screen, Field Identifier: ‘W2-EE-SUFFIX’
73-196 FL - Blanks
197-202 - Reporting Period MMCCYY
- From user specified Period End Date converted to MMCCYY for the quarter
- e.g. Period End Date = ‘31-Dec-2005’, then reporting period is ‘122005’
203-213 - State Quarterly Unemployment Insurance Total Wages
- Derived from IDFDV screen, Field Identifier: ‘W2-ST-WAGE-HOME’ and ‘W2-ST-WAGE-WORK’
- note that the IDFDV Identifier ‘W2-SUI-WAGE-ER’ is not used to report this field because the value of Identifier ‘W2-SUI-WAGE-ER’ may already been capped by Vertex during the US Tax calculation in UPCALC and therefore for employees who exceed the maximum wage base, this Identifier will contain no SUI Insurance wages, therefore RPYEU is using the State Taxable wages from Identifier ‘W2-ST-WAGE-HOME’ and ‘W2-ST-WAGE-WORK’ that are related to the employee Home GEO and Work GEO code to report SUI Total Wages
214-224 - State Quarterly Unemployment Insurance Taxable Wages
- this amount is derived from State Quarterly Unemployment Insurance Total Wages and the SUI Maximum wage base as defined by the State government
- please read document PR_US_QTR_MMREF_Generic.doc for detail for quarterly reporting
225-247 FL - Blanks
248-267 - State Employer Account Number
- Derived from IDFDV screen, Field Identifier: ‘W2-STATE-REGIST’ for the reporting State
- When RPYEU is run, if the Media Format = ‘State SUI File Format’, then this field contains the SUI Registration Number from IDGV screen for the SUI Registration of the State
268-512 FL - Blanks
Multiple Code RS records:
Multiple code RS records are generated for an employee if there are applicable county, city or school district tax information to be reported for a State. In this case, the State wages and tax will be zero for the subsequent code RS records.
Record name: Code RT - Total Record
Column Description
1-2 - Record Identifier
- Constant "RT"
3-9 FL - Blanks
10-24 - Wages, Tips and Other Compensation
- Derived from IDFDV screen, Identifier: ‘W2-FIT-WAGE’, total of all code "RW" records since last "RE" record
25-480 FL - Blanks
481-491 FL - Total Payment Due.
- .
492-498 FL - Month-1 Employment for employer.
- Total number of employee covered by UI worked or receive pay for the pay period including the 12th day of the first reporting month.
499-505 FL - Month-2 Employment.
- Total number of employee covered by UI worked or receive pay for the pay period including the 12th day of the second reporting month.
506-512 FL - Month-3 Employment.
- Total number of employee covered by UI worked or receive pay for the pay period including the 12th day of the third reporting month.
At line 404 added 5 lines
This page (revision-22) was last changed on 26-Nov-2021 10:22 by Meg McFarlandTop