No, the same instructions as those used for completing paper returns must be used for efiled returns. The only difference is in the method of data submission. Specific requirements for efiling must be followed to submit the data. For more information, see the Software Developers Guide. For IRS specifications on Fed/State MeF, refer to the IRS website at www.irs.gov.
They are listed in the Attachments Directory. For information on whether or not an attachment is required, follow the instructions for paper returns. When attachments are included, they should be indicated in the manifest and must be in PDF format.
See "What is a Set?"
Sets refer to logical relationships on the returns, usually following the pattern, 'If condition, then . . . '. For example, the Amended Return box on the top of the return must contain a value of 1 to 4, on Line 19 of TC-20, Schedule A to have an entry that is valid. So the two items are a Set. Other examples of Sets are Addresses. Domestic addresses must contain a primary address line, City, State and Zip Code. A foreign address must contain a primary address line, City, State, Postal Code and Country.
Yes, addresses are examples of Sets. Domestic addresses must contain a primary address line, City, State and Zip Code. A foreign address must contain a primary address line, City, State, Postal Code and Country
For tax year 2006 only, requirements related to attachments have been relaxed so pdf files can be named however you want – the Tax Commission will not require pdf files to be named according to our specifications.
A completed copy of Form TC-8453C must be scanned and included as a file with a .pdf extension. The Officer's Signature (actual signature) must be included for the signature document to be valid. The officer's signature and the preparer's signature can go on the same TC-8453C.
Each field in the XML file has been assigned a unique identifier called the Form Position [number]. This identifier is referenced in the errors listed in Acknowledgments to help the submitter identify the field that is causing the error.
If the taxpayer doesn't have an above-zero amount to report on a line, the XML field corresponding to the line should be omitted. If a form or Schedule is required only if an amount reported on it is greater than zero, then it should not be filed at all if the amount is equal to or less than zero. For example, if TC-20 Schedule D Line 3 is present in the xml, it must be greater than 0. If the taxpayer does not have an above-zero amount to report on that line, the field it should be omitted, and schedule D should not be filed.
Yes, the test data is intended as a "guide" and to help the Tax Commission efiling Contact determine if the entity submitting the data is adequately prepared to submit live data. However, submitters are encouraged to test with their own data.
After the .xml file has been created, it should be validated against the Utah Schema posted on the website by using a software product such as XMLSPY. If required fields are missing or incorrect, the file will not validate. There may be products other than XMLSPY that provide similar features.
The allowable values should be the same as those permitted on paper returns. These specifications are detailed in the filing instructions for the paper forms. Additionally, the XML file can be checked by using the validation function provided in your XML-compatible software. The file should fail such a test if fields required in the Schema are not present in the file being validated.
XMLSPY has a Validate function (green checkmark icon) that can be used for this purpose. In addition, the submitter should be able to see the list of allowable values in XMLSPY by looking at the Enumerations tab for a specific schema element while in the Schema. Other products may have similar features.
The row entitled, "XML Elements by Form", under each return shows the relationship between each XML element and the form item to which it is related.
