Download
1 / 8
80 likes | 230 Views
Schema Maintenance Explained. TY2005 and TY2006 Corp/Partnership. Things To Know. The 2005 1120 Schema Set is a master field set to be used with the 1120 Corporate Tax Form.
E N D
Schema Maintenance Explained TY2005 and TY2006 Corp/Partnership
Things To Know • The 2005 1120 Schema Set is a master field set to be used with the 1120 Corporate Tax Form. • The 2006 1120/1065 Schema Set is a master field set to be used for both the 1120 Corporate and 1065 Partnership Tax Forms. • States derive their own “State-Specific Schemas” using the master field sets maintained by TIGERS. For example, a state may derive a 1065 schema and a 1120 schema for Tax Year 2006 using the TY2006 1120/1065 master schema set.
TY2005 Additions AllocAndAppor Assets Credits Deductions Estimated Extensions Franchise GeneralInformation Header Income K1 Liabilities PaymentsClaimed Subtractions TaxDueOverpayment TY2006 Additions AllocAndApport Assets Credits Deductions DistributiveShareItems Estimated Extensions Franchise GeneralInformation Header Income Liabilities PaymentsClaimed ShareholderPartner Subtractions TaxDueOverpayment Schemas Maintained by Spreadsheet
TY2005 FS1120ReturnDataState(Top level schema. Rarely modified) State1120eFileTypes(Library of simple/complex types used by TIGERS) efileTypes (IRS provided – not modified by TIGERS) State1120Payment(Rarely modified) TY2006 BusinessReturnDataState(Top level schema. Rarely modified) StateBusinesseFileTypes (Library of simple/complex types used by TIGERS) efileTypes(IRS provided – not modified by TIGERS) State1120Payment(Rarely modified) Schemas Maintained Manually
Spreadsheets Explained • Each category schema that is “maintained by spreadsheet” has a corresponding category spreadsheet with the same name. • Additions.xsd (maintained via Additions.xls) • Credits.xsd (maintained via Credits.xls) • TaxDueOverpayment.xsd (maintained via TaxDueOverpayment.xls) • Etc… • To simplify the process, all of the category spreadsheets have been consolidated into a single AllData.xls spreadsheet. • The AllData spreadsheet is used by states to request all changes required to the “spreadsheet maintained” schemas. • The AllData spreadsheet is parsed back into individual category spreadsheets by the StateMeF contractor. • The StateMeF contractor uses the individual category spreadsheets to generate category schemas.
AllData Spreadsheet Explained • Category – used to help break the allData spreadsheet into the distinct “category” spreadsheets mentioned earlier. • ParentElement – this is the parent element under the specific category when the schema is created. • AgreedUponStateFieldName – this is the name of the element under the parent • MaximumOccurrences – the agreedUponStateFieldName will be set to MaxOccur=unbounded if you put any value over 1. Typically you should enter 1 or unbounded for this column. • EFileType – The category.parent.agreedName for the row must refer to an existing type from either (a) eFileTypes.xsd or (b) the TIGERS maintained library of types. • The rest of the columns in the spreadsheets are used by states to map the partial XML tree that the row represents. • Note: The allData spreadsheet does not represent the full XML path. For this reason, each state must create a separate document that maps the full xml paths for their vendors.
Change Request Process • Determine when the next Schema release is from the StateMeF website. • Download the AllData.xls spreadsheet and the change request form from the StateMeF website. The latest version of the spreadsheet of the appropriate tax year must be used (e.g. TY2006V1.1 requests must be made using TY2006V1.0 allData as a baseline). • Make changes to the allData spreadsheet • Delete – If you wish to delete a row from the spreadsheet you should highlight it RED • Change – If you need to change the eFileType or maxOccur that a category-parent-agreedName refers to, you should highlight the changed row green and document what was changed in the comments section. Please indicate what was changed and whether the row is state-specific. • Me-Too – If you wish to re-use an existing row, you should copy/paste that entire row and highlight it orange. Note: The category, parent, agreedName, eFileType and maxOccurrences columns should not be modified since this element is being shared. • New – If you need to add a new element, highlight the newly added row yellow. • Sort the spreadsheet by state and remove all other states • Change requests for manually maintained schemas must be made directly in the change request form. • Send the spreadsheet, along with a change request form to the StateMeF contractor per the website.
What happens next? • All requested changes are merged together by the StateMeF contractor. Issues found with requests are resolved directly with the states. • The complete package is sent to the SWAT team to review. Specifically, the SWAT team focuses on finding redundant or poorly named elements. The SWAT team works directly with states to resolve issues. In some cases, changes must be made without direct contact, but changes will be documented in the comments. • SWAT changes are sent back to the StateMeF contractor, who then packages up the data and works directly with the SWAT team to resolve any issues. • A draft version of the proposed release are posted on the StateMeF website and reviewed by states. New drafts are posted as fixes/changes are made. • The final version is made official. A change log and updated documentation is posted.
