Triva isn't available right now.
State | Conventions |
|---|---|
Alabama | Specific naming conventions are outlined in the Alabama Business MeF Electronic Filers Handbook. Refer to it for a list of accepted file names. When creating the PDF, the name must match exactly, including capitalization. |
Alaska | None |
Arizona | None |
Arkansas | None |
California | None |
Colorado | Specific naming conventions are outlined in the Colorado Corporate e-File Handbook. Refer to it for a list of accepted file names. |
Connecticut | None. However, Connecticut requests that as few PDF attachments as possible be attached to corporate returns. |
Delaware | None |
District of Columbia | None |
Florida | None |
Georgia | Specific naming conventions are outlined in the Georgia Corporate Guidelines Manual. Refer to it for a list of accepted file names. |
Hawaii | Specific naming conventions are outlined in Publication EF-8, Hawaii Software Developers and Transmitters Handbook for Corporate Modernized e-file. Refer to it for a list of accepted file names. |
Idaho | Specific naming conventions are outlined in the Idaho Corporate e-File Handbook. Refer to it for a list of accepted file names. |
Illinois | N/A |
Indiana | N/A |
Iowa | None |
Kansas | None |
Kentucky | Each PDF attachment should be given a unique file name and may contain letters and numbers. The name should reference the Form/Schedule and line number when possible. |
Louisiana | None |
Maine | None |
Maryland | Specific naming conventions are outlined in the Maryland Corporate e-File Handbook. Refer to it for a list of accepted file names. |
Massachusetts | None |
Michigan | Specific naming conventions are outlined in the Michigan Corporate Income Tax (CIT) Modernized E-file (MeF) Software Developer Guide provided to software vendors. The application checks the PDF file name against the requested naming convention and indicates with an ELF critical diagnostic how to properly rename the file if necessary. |
Michigan Cities | Specific naming conventions are outlined in the City Corporate Income Tax E-file Handbook. Refer to it for a list of accepted file names. |
Minnesota | None |
Mississippi | None |
Missouri | None |
Missouri Kansas City | None |
Montana | Specific naming conventions are outlined in the Montana corporate e-file Handbook. Refer to it for a list of accepted file names. |
Nebraska | None |
New Hampshire | None |
New Jersey | None |
New Mexico | None |
New York | None |
New York City | None |
North Carolina | None |
North Dakota | None |
Oklahoma | None |
Oregon | Specific naming conventions are outlined in the Oregon Corporate e-File Handbook. Refer to it for a list of accepted file names. |
Pennsylvania | None |
Rhode Island | Rhode Island prefers that attachments be named according to the form name and year. In an example, the Historic Preservation Investment Tax Credit form would be named "Credit 286B 2025 .pdf". Rhode Island won’t reject returns with attachments that don’t conform to this naming convention. |
South Carolina | Specific naming conventions are outlined in the South Carolina Corporate E-File Handbook. Refer to it for a list of accepted file names. |
Tennessee | N/A |
Texas | N/A |
Utah | None |
Virginia | None |
Vermont | N/A |
West Virginia | Specific naming conventions have been named by the West Virginia State Tax Department for certain forms that are required to be attached to the electronic file. For those required attachments that the application doesn’t automatically generate, a diagnostic message will alert you to the specific naming convention required for the given PDF attachment. |
Wisconsin | None |