To: ANSI ASC X12G TG2 and TIGERS Attendees
From: Debbie Johnson
Oklahoma Tax Commission
ASC X12G TG2 Secretary
Date: July 10, 2001
Subject: DRAFT ANSI ASC X12G TG2/TIGERS Meeting Minutes
June 4-6, 2001 St. Louis, MO Trimester Meeting
================================================================
Monday, June 4, 2001 -- Tax Information Group for EDI Requirements
Standardization (TIGERS)
------------------------------------------------------------------------------------------------
The agenda:
Monday, June 4, 2001 – 1:00 pm/3:00 pm
- JCC Initiative Terms of Reference
- Introduction to TIGERS
- Welcome and Introductions
Monday, June 4, 2001 – 3:00 pm/5:00 pm
- Joint Core Components Meeting
Tuesday, June 5, 2001 – 9:00 am/5:00 pm
- XML Document “Superstructure” Development
- Mark Crawford/presentation /Q&A /TIGERS discussion
- Wireless Impact on States
Wednesday, June 6, 2001 – 1:00 pm/5:00 pm
- XML Document “Superstructure” Development (Cont.)
- Wireless (Cont.)
- Next Steps/Next Meeting
Debbie Johnson began the meeting by handing out the Joint Core Components Initiative Terms of Reference for review and later discussion. Also, we reviewed all of TIGERS Transaction Sets to determine if they could be approved for Version 5 of the Standards. (We voted to let Teresa vote her conscience on the JCC Initiative Terms of Reference and approved all Transaction Sets to go to Version 5.)
The meeting was then turned over to Jonathan Lyon who began with the Background Introduction to TIGERS. He also gave the Welcome and Introductions. There was discussion on what the different states were working on and trying to accomplish.
Martin Lasecki with the Wisconsin Department of Revenue said that Wisconsin and North Carolina were working on a way to streamline remote sales, what gets taxed, and what gets reported.
Jeff Fritz and Dave Mazzota with Creative Solutions said their company was being driven by State Government and the IRS to create in XML.
Gus Wing of UNISYS reported they were integrating product offering.
Glenda Hayes of MITRE reported they are working on an XML Schema for the IRS 1120.
Robert Shickora of New Jersey reported they were working on XML for Motor Fuel.
Ray Ivaska of Pennsylvania reported they were developing XML in their Cigarette Tax Licensing. They are not going to use their PA-TIDES Program anymore. Their Motor Fuel Programs will be using E-TIDES for one more year.
Ravaughn Robinson of Mississippi reported they have an EDI system in development for their Sales Tax and Withholding systems.
Tom Pantier, Larry Izzard, and Mary Thomas of Illinois reported that they are interested in the 941 Combined Wage Reporting. They have some signature issues, but like the Vertex Schema with individual components for their XML example.
Jonathan Lyon of FTA explained the Super Schema to Base Schema structures and the tax pieces associated with them.
Rick Nichols of the IRS reported they are looking at XML for future processing.
Stan Whaley of Florida reported they have postponed their XML work for now.
Matt Brown of Intuit is interested in the work to be done on the IRS 1120.
Ken Jaslow of KPMG reported that the XBRL is working off of the general ledger taxonomy.
Marc Midkiff of H & R Block reported that they were interested in building a processing system to tie all systems together.
TIGERS adjourned to the Joint Core Components meeting from 3:00 pm to 5:00 pm.
JCC asked for participation in the joint effort of Core Components.
Their outline was as follows:
Develop draft JCC operating procedures:
- Based on existing UN/CEFACT Operating Procedures
- Focus Put On
· Organization
· Work Area operating procedures
- Work Products
· Draft Charter
· Operating Procedure Document
· Updated Oganizational Chart
· Updated Project Plan
The Joint Approval Process is for two areas:
- Technical Specifications
· Internal
· External
- Core Components
The technical specifications must follow Trade/CEFACT/2000/22 for external approval as CEFACT Technical Specifications.
- Work Product
· Refined Joint Operating Procedures Document.
The JCC Standards will move ebXML Core Component Documents to Technical Specifications.
- Work Products
· Decision on which documents should become technical specifications.
· New Working Drafts
JCC Harmonization held in abeyance.
- Deliverable
· Paper explaining what harmonization will entail
Tuesday, June 5, 2001 -- Tax Information Group for EDI Requirements
Standardization (TIGERS)
------------------------------------------------------------------------------------------------
Jonathan Lyon opened the meeting at 9:00 AM.
John Glaubitz of Vertex presented the Sales Tax Filing Batch Process of the Schema. He broke out the transmission piece into one piece of its own and worked on making more elements than attributes. On the tax filing envelope, they tried to have it open-ended where it could handle multiples. He suggested that TIGERS determine best practices in a guide. The expected value of the Tax Filing Envelope is not known, but used as a placeholder at this time.
The Batch ID which is used to track the Transmitter ID and sequence number was left out in the original base schema. We need to add it back in.
What about amended returns in the Submission Type? It can be handled under TaxFilingType.
The Tax Filing area had a “reference” field in it. It was questioned if this was needed or not and why. There was a suggestion to document an existing EDI for use of fields or nonuse based on meetings.
TaxInformationItem can be anything like the amount, quantitiy, date, etc&. Marc Midkiff asked how the sequence of items would be identified. Michael Roytman suggested an example of the dependent as an item, and the dependent information under that.
In the Period segment, it was decided to add type to the date and make the start and end dates optional.
Mark Crawford, JCC Chair, came in to discuss what was needed from the subcommittees to help make the standards for XML. He said we should start with the Core Components, Methodology, and UML modeling. Break the Core Components down into spread sheets and create a dictionary. Subcommittee C is responsible for creating the XML Design Rules and Conventions.
Subcommittee J is studying the ebXML Technical Architecture and creating a set of naming conventions. Mark suggested that we send out liaisons to JCC, and Subcommittees C and J. They are looking for volunteers to help with the XML effort.
There was a suggestion to use the naming conventions adopted by the JCC to apply to the Base Schema and Derived Schemas and present those findings in Spokane, WA in August. We want to continue to use the existing Sales Tax TIA codes for XML tags as they already have the “meanings” available.
We then went on to discuss the Wireless Sales Tax Task and how it falls within the TIGERS scope of development. We could give the committee information to help develop data formats to give to states to send to developers. The developers would need locations and tax rates for each jurisdiction.
Stan Farmer suggested that an example of submitting the data would be to use a Group 1 Software, combine with other GIS information, find out proper tax rate, and give to a client such as A T & T.
Or we could build a web application that houses the tax rate, wireless customer, jurisdiction and address. States would be allowed to use ZIP+4 if they don’t want to code by FIPS. There was a question on whether Latitude and Longitude are included.
Wednesday, June 6, 2001 -- Tax Information Group for EDI Requirements
Standardization (TIGERS)
------------------------------------------------------------------------------------------------
We discussed that the Base Schema versus the Derived Schema. We can derive but not change the data type. There would be a significant amount of redefines in order to use it.
Naming conventions consist of:
1) An Object Class
2) Property Term
3) Representation Type.
Anything there is a code for has to also have text associated with it.
A draft list of “things to do” is:
1) Continue work on Base Schema
2) Subsidiary Issues – Derive from the derived schemas.
3) Create a taxonomy dictionary
4) Develop a Base Schema User Guide
5) Show Instance Testing
6) Create Naming Conventions
7) Develop a Core Components Dictionary
Our next meeting will be held in Spokane, WA. Tentative dates and times are:
1) August 15, 2001 – 8:00 am to 5:00 pm
2) August 16, 2001 – 9:00 am to 5:00 pm
3) August 17, 2001 – 9:00 am to 12:00 pm