ࡱ> 7 gbjbjUU w7|7|7cZl555566647\\\h,]$P]7mT@^p^(^^^$aZ~aa$ n6a``@aai55^^'iiia&5l^6^iaivio طZX6,6^4^ &ܻ7$\f2< =0m6lOZhOi6r75555EMBED StaticMetafile Using XML for Tax Transactions White Paper Abstract Tax XML is a sample schema for tax data. The schema is a model to be used by standards organizations, industry partners, and government agencies in their investigation of the use of XML in a tax setting. This schema is further intended to provide thought leadership and the first steps toward creating an open standard for tax transactions. The Tax XML Schema is integral because it defines the data to be stored and processed by applications and the supporting infrastructure. Collaboration on an open standard will result in the specification necessary for competition on implementation. This paper is directed to those involved in fostering the use of XML who would like to see it applied to the field of taxation. It may also provide insight to those investigating the possibility of using XML in other business applications that are highly complex with a large number of distinct data items. 2000 Microsoft Corporation. All rights reserved. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This white paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. Other product and company names mentioned herein may be the trademarks of their respective owners. Microsoft Corporation One Microsoft Way Redmond, WA 98052-6399 USA 0x99 Introduction Overview Using XML for tax transactions is a strategy whose time has come! Already the United Kingdoms Inland Revenue uses an XML schema for the filing of individual returns and has done so since 1999. Extensible Markup Language (XML) is a technology that promises to free business and tax data from application infrastructure. The data-centric approach of XML allows the communication of data regardless of the platform, operating system, or underlying technology of existing systems. The keystone to the use of XML for tax is the Tax XML Schema that describes the specific tax data items and their relationship to each other. The long-term goal of this schema is to define an international standard with which all tax transactions would comply. The current thinking is that the schema would be comprised of namespaces owned and maintained by governmental agencies and merged into a single schema. A standards organization similar to the World Wide Web Consortium (W3C) would be established to provide hosting services, version control, and guidance to the tax administrations around the world for the master schema. There is a need for urgency associated with the completion of the Tax XML Schema. As mentioned above, the UK is currently using this methodology. Other national governments around the world are planning the creation of e-government systems that use XML. State and local tax administrations within the US also have development projects underway. With no standard in place, however, each of these groups will develop divergent schemas. This will complicate the communication of information between groups, and will hamper implementation efforts by requiring customization of data storage and handling at each site. To avoid such a proliferation of approaches a standard should be pursued swiftly. Current Scope of Tax XML The current scope of Tax XML is to present a small sample of a schema based on US taxes in order to provide a starting point for collaborative work. The current work that has been done focuses on three areas: Federal individual, Federal corporate, and California individual. For detail of data included in this work, see the Taxonomy section below. This work has been done for modeling purposes, rather than as a specific example of the content to be included. Also within the scope of this project is the investigation of the best type of schema to use. Several approaches are explored in this paper including: The first approach is to use a schema comprised of elements distinctly named to represent the data contained in each element. This approach is exemplified by the UK schema and is consistent with the schema promulgated by the W3C. A second approach is demonstrated by the eXtensible Business Reporting Language (XBRL) organization in a schema used for financial reporting. This strategy uses a very limited number of elements and includes the identification of the data through attributes instead. Another approach investigated but not displayed focuses on an EDI-related schema that uses separate elements to identify the data. Background Consider the process of an individual preparing to file his federal income tax return for the year. Tax information must first be gathered from multiple sources. Employers must provide Form W-2 with wage information to the taxpayer and to the tax agency. Financial institutions must send Form 1099-INT with interest income, again both to the taxpayer and the tax agency. Another form contains mortgage interest expense, and once more is required to be sent to both places. Still other information is required from other payers, local governments, and state agencies. Then this information must be accurately entered from these documents into the return, so that it matches the data sent by the same source to the tax agency. If the taxpayer plans to file electronically, extra data must be entered to ensure correct matching of these documents. For example, the taxpayer must re-enter his name and address for each Form W-2 exactly as it appears on the paper W-2 even if it is incorrect! The same requirement also exists for Form 1099-R and Form W-2G. The taxpayer must then send the tax return to the IRS, either as a printed return or electronically, using the IRSs proprietary system. Because of the format of the forms, much of the data is included in the return more than once. For example, the total of itemized deductions appears on both Schedule A and Form 1040. Another exampled mentioned above is that the taxpayers name and address may be included in the return multiple times. These redundancies increase the data storage requirements at the IRS and make the data vulnerable to inconsistency and error. If the taxpayer resides in a state or city with its own income tax, the information must be sent to there as well often with a copy of the same information sent to the IRS. Even within a tax agency, data that was received electronically from the taxpayer may be manually entered into a separate application due to incompatibilities of applications and platforms. Once stored, the information is usually difficult to access across various legacy systems of the agency. Even just modernizing systems within a tax agency will not fully solve these issues. Replacing legacy systems with fully integrated systems may enable effective data transfer within the agency, but it does not address the redundancies within the data itself nor the issues of communicating data among the taxpayer, employer, financial institution, and tax administration. The Tax XML Schema provides a solution to these issues. Standardization of data so that it can be communicated electronically without ambiguity will change the processes of tax preparation. Employers will be able to provide data electronically in a format that will be readable by taxpayers, income tax software providers, and the IRS. The information will be automatically entered into tax software to eliminate the errors that can occur during manual entry. Matching data in a tax return with the same information sent to the IRS becomes a nearly fail-safe task. There are other efforts underway that can do some of these same tasks. For instance, Intuit has a process that allows information from participating companies to be downloaded into a tax return being prepared using its products. However, this is a proprietary system designed only for this specific transfer. Tax XML, on the other hand, offers complete sharing of data based on an open standard and XML technology, as well as data redundancy eliminated by separating data from the government forms. Technical Overview The technical overview summarizes the work that has been done for Tax XML. This section includes information about the taxonomy, schema, and instance files developed as part of Tax XML. The Taxonomy XML focuses on data. Therefore, the first work done for Tax XML was to create a hierarchy, or taxonomy, of the tax data to be included in the schema. The goal of the taxonomy is to streamline and reorganize tax data to make it more logical in order, independent of the presentation on the existing government tax forms, and to eliminate redundancy. In order to accomplish this, a review was done of the data contained on forms and in the electronic filing record layouts, where they were available for a form. The review focused on the following tasks: Arrange data into logical groups. Data was moved from its location on the form and included where it would allow the data to flow functionally from a computational perspective. Exclude computed amounts. Data was included if it was an entered field, but usually not if it was a computed amount. Computed amounts were sometimes included if they were key check totals or placeholders for parts of the taxonomy not yet completed. Include data only once. Duplication increases the possibility of error and requires additional storage. If data appeared in more than one place, the data was captured in the hierarchy in the place that represented its source entry point. Tax Forms Included in Tax XML It is somewhat misleading to speak in terms of forms, but it is a helpful reference for identifying the scope of the work done to date. Tax XML includes the information from the following income tax forms and schedules, although the data is reorganized and computed amounts are not included. Although Tax XML is intended to be a single schema, the work done has been grouped into individual income tax and corporate income tax for ease of analysis and is presented in those parts throughout this document. Individual Forms Form 1040Form 1040AForm 8815 Schedule A Schedules 1, 2, and 3Form 8828 Schedule BForm 1040EZForm 8829 Schedule CForm 2210-FForm 8839 Schedule E (pg.1)Form 2441Form 8863 Schedule EICForm 4255Form 9465 Schedule FForm 4562Form W-2 Schedule HForm 4797Form 1099-INT Schedule JForm 4835Form 1099-DIV Schedule RForm 8606Form 1099-MISC Schedule SEForm 8615Form 1099-RThe Forms 1099-INT, 1099-DIV, and 1099-MISC are included above, even though these forms are not currently included in the paper filing or electronic submission of forms to the IRS. The reason for this is to show an example of what the future might hold where financial institutions and employers would also use this schema to transmit their information to the government, and then on to the taxpayer for inclusion in the individuals income tax return. The seamless integration of data transfer in such a system shows the extended possibilities of Tax XML beyond just the filing of income tax returns. Corporate Forms Form 1120Form 1120 (continued)Form 4255 Schedule A Schedule KForm 4562 Schedule C Schedule LForm 4797 Schedule E Schedule M-1 Schedule J Schedule M-2Form 1120 covers much of the data included so far. The additional forms listed are available from the work done on individual income tax. Because the goal of Tax XML is to define a data structure that crosses different types of tax returns, the tag names and data organization are consistent and reusable whether the tax type is corporate, individual, or another type. Data Hierarchy for Tax XML The beginning of the hierarchy is the same for all types of tax. This list shows the relationship of the individual and corporate tax branches to the entire tree. TaxML Authentication Identification KeyID TaxYear+ Version+ IndividualTax+ CorporateTax The TaxML element serves as the top level, or root, of the hierarchy. Below TaxML are lower levels of the tree. The + sign preceding an element indicates that there are levels below this item. If there is no + sign, the element contains data rather than child elements. The Authentication and Identification elements are shown only as placeholders. Security and verification of identity are beyond the current scope of Tax XML. Building a Data Hierarchy for Individual Taxes The first part done in the Tax XML project was work on individual income taxes. A data hierarchy was developed that had many levels and named the data elements with descriptive names designed to clearly identify the information they held. Element structures were developed, such as Name, to hold a set of elements and that could easily be reused. Groups of elements that could occur more than once were labeled as lists for easy identification. Some of these structures were not included in the best practices that are shown below, but they still represent a viable approach and are included for that reason. The elements that comprise the IndividualTax element are shown below. - IndividualTax- IndividualTax (continued) + Taxpayer + FarmIncomeAveraging + Spouse Tax + Address + ChildCare + FilingStatusInformation RetiredDisabledCredit + DependentList ChildTaxCredit + Wages + Adoption + InvestmentIncome ForeignTaxCredit StateLocalIncomeTaxRefund + OtherCreditsList AlimonyReceived TotalCredits + ActivityList + SelfEmploymentTax CapitalGainLoss + AMT + SaleOfBusinessProperty SocialSecurityAndMedicareTaxOnTips + RetirementOrIRA TaxOnRetirementPlans + MiscellaneousIncome + HouseholdEmploymentTaxes TotalIncome + ITCRecaptureList + StudentLoanInterestList + OtherTaxesList MedicalSavingsAccountDeduction TotalTax MovingExpenseDeduction + TaxPayments SEHealthInsuranceDeduction AddChildTaxCredit KeoghSepSimpleDeductions Refund PenaltyOnEarlyWithdrawal + Bank + AlimonyPaidList AppliedtoNextYearES AGI + BalanceDue ExemptionAmount UnderpaymentPenalty StandardDeduction + UnderpaymentPenaltyFarmers + ItemizedDeductions EstimatedTaxPenalty TaxableIncome + Preparer EducationCreditRecapAmount + PriorYearInformation + KiddieTax + StateIndividualTax Arrange Data into Logical Groups The Taxpayer element is a good example of data being grouped together logically. The element is comprised of the data fields shown in the following table. This information was drawn from various tax forms and combined here. Before this rearrangement of data, these pieces were scattered across five separate forms. - Taxpayer- Taxpayer (continued) IDNumber PresidentFund + Name Exemption DateOfBirth PINTPSignature Blind Occupation MilitaryIndicator Disabled HomePhone PriorYearStatementIndicator BestTimeToCallHome QualifiedCurrentYearExpensesForHopeCredit WorkPhone QualifiedExpensesForLifetimeLearningCredit BestTimeToCallWork Reuse Element Groups Two methods were employed in the individual tax branch to make elements reusable. The first is demonstrated by the Name element. The Name element is comprised of the data fields shown in the following table. Once the Name element is defined under the Taxpayer element as having these parts, it can be referred to simply as Name with the sub-elements implicitly included. For example, when the Name element is used later in the hierarchy under Wages, it will only need to be identified as Name without reference to its parts; i.e., FirstName, LastName, etc. - Name FirstName MiddleInitial LastName Suffix CompleteName NameControl The second method involves the Activity element. This element combines tax information for businesses, rentals, farms, and farm rentals into a single branch rather than in four branches as would result from following the associated tax forms. Since the information on each of these four forms is very similar, a type code was implemented to identify what type of activity was being reported. The table below is abbreviated. There are 245 elements and sub-elements under ActivityList, so being able to reuse an element group in this way is significant. - ActivityList BusinessIncomeLoss FarmIncomeLoss RentalIncomeLoss FarmRentalIncomeLoss Activity Type Identify Repeating Groups Some data structures will repeat more than once when reporting tax data. An example of a repeating structure is shown in the preceding table. The ActivityList element indicates that a repeating structure follows. In this case, the repeating element is Activity. ActivityList may occur only once and is the parent for the element Activity that may repeat an unlimited number of times. Data Hierarchy for Corporate Taxes The CorporateTax branch of the tree represents data used in corporate income tax returns. A sample of the elements that comprise the CorporateTax element are shown below. - CorporateTax- CorporateTax (continued) + entityInformation + balanceSheets + income + incomeReconciliation + deductions + analysisOfRetainedEarnings + taxAndPayments + preparer Data Organization Best Practices These best practices were developed during work on the corporate tax branch of the taxonomy. Organize data to follow the logical flow of tax information. Tax data follows a predictable sequence that is comprised of the following common concepts. These concepts underlie tax transactions regardless of locale. Dealing with data at this level makes it possible to define a hierarchy that can be used globally. Common Concepts Identifying data names, location, other information about the taxpayer Income Deductions Tax Payments Credits Balance tax due or refund Preparer information Insert data into its functional location. This is a corollary of the item above. In the current IRS forms model, supporting data is gathered on separate pages that follow the main form (1040, 1120, etc.). In the Tax XML organization, the data is included in the flow where the summary total would appear on the IRS main form. For example in a corporate 1120 return, all of the information for Cost of Goods Sold would be included after Gross Receipts or Sales as opposed to its location on the tax form (Form 1120, page 2.) Gather information into logical blocks. For example, all the information for a taxpayer was gathered and stored together. This data includes the taxpayers name, identification, and other information about the taxpayer. Capture data at its source and only once. Including the same piece of data in more than one place often leads to errors because the data changes in one location and not the other. By capturing data at its source, and only once, these problems are eliminated. An example of this is that many forms used to calculate tax credits include data from elsewhere on the return. In this model, that information would not be included again. Only new, unique data would be included in the data related to the credit. Avoid including unnecessary data. Do not include data that can be inferred reliably from other data. For example, many forms ask a Yes/No question that if answered yes requires the next field to be completed. The data in the field following the Yes/No question effectively provides the Yes/No answer. If the data exists, the answer is yes. If the field is blank, the answer is no. Include only key totals. In general, the goal is to include the source data needed for computations, not the computed amounts. This reduces the file size for transmission and for storage. The computations would then be done by the government agency and the results checked against the taxpayers results using key totals. These key totals are crucial to ensuring the correct transmission of a tax return and would be included. Examples of such items are taxable income and tax. Name the data with descriptive tags. Use complete meaningful names for the tags. Avoid abbreviations or jargon. Data names should use the camel case convention, be 40 characters or less, and not include spaces or special characters. Camel case is a convention that begins a data name with a lower case letter. For example: corporateTax. Combinations of parent-child names must be unique. The reason for creating unique parent-child combinations is that it provides an absolute reference for the location of this combination within the hierarchy and the namespace. The advantage of this is the ability to send subsets of data without the entire schema, or large parts of the schema, needing to be included. For example, suppose that in order to gain loan approval, a financial institution requires a companys income and deductions to be submitted. This feature allows this data to be transmitted without all the grandparent data up to and including the root of the schema. The Schema Schema Best Practices Use separate namespaces for different tax entities. Tax XML is intended to include all tax transactions. To accomplish this, it is necessary to create separate namespaces for entities such as individual, corporate, partnership, etc. This recognition is the result of two factors: size and maintainability. Combining all entities into one schema or taxonomy without employing namespaces results in a document of unmanageable size. By separating the information into namespaces, the creation and maintenance of the various parts can be done by different parties. This allows the work to be done by different tax agencies, and then combined into a whole. To indicate the parent of a list of items append an s at the end of the parent element name. The following child element is then named with the singular version of the same name. Parent elements hold data that can be calculated i.e. the total of detail items. Example of Multiple Items Parent ElementChild ElementmaxOccursDataTypeincomeotherIncomes1monetaryotherIncomesotherIncome*monetaryotherIncomedescription1string No fields are set as required in the schema; i.e., minOccurs = 1. This will allow a piece of the return to be communicated. Schema in Two Different Formats TaxML was presented in normal XML schema format and in eXtensible Business Reporting Language (XBRL) format. Normal XML Schema Format The normal XML format produces a structured hierarchical schema. Data is contained within an element, named with description of its contents. Advantages Highly hierarchical structured format allows easy view of structure. XSLT applies easily to a hierarchical document instance. A normal XML parser is able to validate the structure, required data and data format of a document instance. eXtensible Business Reporting Language (XBRL) Format The XBRL XML format produces a flat schema without order requirements. Data is contained within an item element with a name attribute that describes its contents. Advantages Without order constraints, the XML document instance can easily be split apart with each piece being valid XML. XBRL can be stored and extracted in a database using normal XML queries. Since tax data items are numerous and change with tax law changes, it is impractical to store each data type in separate columns. Since XBRL data is stored in the item element instead of its own distinctly named element, data can be stored in a database in one column named item. Data Types monetary (decimal)Numeric. Used for money fields. Example: 5123.13 indicates $5,123.13.floatNumeric. Format specified on a field basis to show placement of decimal. Used for percentages. Example: 50.32 indicates 50.32%.booleanUsed for Yes/No situations. Example: 0 indicates No and 1 indicates Yes.dateUsed for dates unless a word such as various is allowed. Example: 2000-11-02 indicates November 2, 2000.intUsed for numeric fields other than percentages or money. Example: 5123 indicates 5,123.stringUsed for anything that is not included in the above. Text is probably obvious, but also used for ID numbers, calendar years, dates that allow words as well as numbers, and anywhere else that you want to be able to control the format of the information. Resources Web Sites  HYPERLINK "http://www.w3c.org/" http://www.w3c.org/ This is a link to the Worldwide Web Consortium. This group was created in October 1994 to lead the World Wide Web to its full potential by developing common protocols that promote its evolution and ensure its interoperability.  HYPERLINK "http://www.xml.org/" http://www.xml.org/ XML.ORG is an independent resource for news, education, and information about the application of XML in industrial and commercial settings.  HYPERLINK "http://www.xmlu.com/" http://www.xmlu.com/ A website presented by Architag International Corporation, a leader in XML education.  HYPERLINK "http://www.msdn.microsoft.com/xml" http://www.msdn.microsoft.com/xml This is the link for Microsofts developer network web link.  HYPERLINK "http://www.xbrl.org/" http://www.xbrl.org/ Xbrl stands for extensible Business Reporting Language. This organization promotes XML for financial reporting data.   Tax XML Schema White Paper  PAGE 10 Tax XML Schema White Paper  PAGE 11 v>Am''a(z(Z)q)q,z,{,,,,,,,,,,,--,---O-P-o-p-------------..n0000000001133c8d8 CJOJQJ CJOJQJ<CJ<CJOJQJPJPJaJ CJPJaJCJPJ5\ 0JhB*ph B*ph6j[7 UV jUF9EN  j ) X,0$0$d^67ggg]DP  "$$$x%%&'a(Z)H*f*+`,q,Z"q,{,,,,,,,,,,,,,,yyyY$$IflF G  =P6    4 lac;$If; h8$If^`8; hG$If^`G,---"-,---;-E-O-P-\-f-o-p-yyy; h8$If^`8; hG$If^`GY$$IflF G  =P6    4 lac;$Ifp-|------------yyyY$$IflF G  =P6    4 lac;$If; h8$If^`8; hG$If^`G ---..^0n0x00sqodQ; h8$If^`8 ; h$IfY$$IflF G  =P6    4 lac;x$If; h8x$If^`8; hGx$If^`G000000000000000yypyp; h8$If^`8; hG$If^`GY$$IflF G  =P6    4 lac;$If0111122F3L3sqoqa#V$If^V`Y$$IflF G  =P6    4 lac;x$If; h8x$If^`8; hGx$If^`GL3M3]3^3n3o3v3w33333333334`55DD (,HD# V$If^V`@$$IflhB  64 l` a5778G8c8d8p8888888888DdS$$Ifl0 $ " $64 lal; h$If^`; h$If^`d8888888889 999F9G9w9x9999999::D:E:x:y:::::::; ;Q;R;v;w;;;;;;;<<5<6<Y>Z>u>v>>>>>>>>> ? ?AAAAAAABBB BBBBBBBB B,B-B.B0B;BB>Y>~; h$If^`S$$Ifl0 $ " $64 lal; h$If^`Y>Z>e>u>v>~>>>>>>>>>>>pTX; h$If^`; h$If^`S$$Ifl06 6  64 lal>>> ? ?!?M?N?Z???????\; h$If^`; h$If^`S$$Ifl06 6  64 lal??AAAAABBBBBB-B.BBfD4D0(@<:$$Ifl  64 lal; h$If^`^fDuDvDDDDDDDDDDDDDDD{FFIGXHP`0$:$$Ifl  64 lal; h r$If^`xDDDDDDDDDDDDDDDDDDDDsGtGGGGGGG H HR!SZZ2^6^__ecfczc{c|ccccccdddddddddd^e_eePJ^JjPJU^JPJCJPJ CJPJaJ jU^J0JY^Jj`U^J jU^JOJPJQJ^J OJQJaJ6]@h CJOJQJ^JJFJbJwJJLLaMM\O~OPPRR*SSOPZ$S T>TVVVV6YY?ZYZhZvZZZ=$IfQ$ZZZZZZZZZZZZnhhhhn^^hh RV$If^VR$If$$Ifl\@ Vl8064 la ZZZZZZZZ4[n[ndd^^nXVTZ$^R$If Rd$If^d$$Ifl\@ Vl8064 la n[o[[[\\\-]]]r^}^^O`P`\`o``R$IfZ & FZ$```.<']蕒Ђhxe>o9 0lgT]wd c"C-C0]$/jX2߿pC :fL+vD*fU* 0'WzyL,f$s8Mtӑ*4g#]N%3F4iMsdX~y1홉9.>]}):l}L{E=N1)tړ8.hv} ӱ=i;ͬojo(?f;AMŞ'9Do٤;Lthn9Nu?zSSRz2NlJLĤL\I43F(+i4e'ޤqDH^oBJHyFB < JH3AǮ4zѽɖJF;M@-~^s,J7 *Ck 2j++-I&suT)R'K( H=~4e//Z[ QZ,"@4f5o#6zP`6sc9}Ee>3Nl'M,O#1#z=s[b1vhr&gdGR٩&hf65 bQ~d׾Wkۍj؟,A'gȎ!v0;x;?~ĎPu򡪗v|;ීs \M5y`|"raS}^>*` GTq@&m 2p^SˠdQα] Zm垷r7[{;mܕ6dn? }0 2>g)oCwZ}|eȃ.X>~yGBRlJ Ll|Pg%y{ݦ7['m'qwAlWfӬ=3g5ڎNQOh--{L@?=DyK yK (http://www.w3c.org/DyK yK (http://www.xml.org/DyK yK *http://www.xmlu.com/DyK yK Dhttp://www.msdn.microsoft.com/xmlDyK yK *http://www.xbrl.org/  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVXYZ[\]^adefghijklmnpqrstuvwxz{|}~Root Entry  FHܻcData WWordDocument wObjectPool @ܻHܻ_931945241F@ܻ0ܻOle CompObj^ObjInfo  !"#$%&'()*+,-./0123456789:<=>?@ABDEFGHIJKLMNOPQS FPicture (Metafile)StaticMetafile9qƚ@\E <&WordMicrosoft Word  Y  -@Times New RomanS- &W.CONTENTS 1TableoOSummaryInformation( ;DocumentSummaryInformation8C  - "-YX  L&WordMicrosoft Word L  -@Times New Roman- &N.  - "-LL &WordMicrosoft Word   -@Times New Roman-   &.  - "-  &WordMicrosoft Word   - @"Arial -  & "-- *$ $;Ri  i R;$  "--&&2--<8  2"2#Z52Q2A.6V"V PFcF^]aXeRhNkJpHtFyE~EEFHHJMNRV\FFMJHFFFPJHEEEFILMPTY^dgooqtuvvvutqpolkjgcb_]ZUQMJHFEEE FHIJMQUZZYVUTRRRTUVXYZ\] _abdgjbZU N%J*H0E7E;E?FBHEIGJJMLQMTOHXHXEY@Z<\9_7a5d4i3o3s3p>o>m>k@jEiHpHt99HHVV|m{q{r|tttvomkj~i}hzhviooVfV^LUVNVO]OfMlLpJrIvFyA~;6/)&"~|xtpuy}   ~|yutqvz~~zupkc_Z]^afooty}|xrniea}_y]u\p\jXEPFR=T2h2f=R=m^^\XU~T|TzTxVuXt\r_qcpgplppqrtuuuxuzr|p}mmuutqmjfb^YVUTTUX\_cgkprtuu0u2u5t7q9m:j;f<b<^<Y;V9U7T5T2U0X.\,_*c*g)k*p,r,t-u0uXVVURNLJIFFFHILNRTUVXUUTQNLJIHIJLNQTUUTJJJLNPTTPPTTNNMLLLN--&-  - "- '&'-    - "- '&- - "-'&-Oh+'0< LX t   Using XML for Tax TransactionsiOpen XML standard for taxioJackXMLTax, XML, Standards!Windows 2000 Server Template.dotrosJackws 13kMicrosoft Word 9.0 @U@G@G7@Z.Ȼ (P՜.+,D՜.+,l( px   White paperMSFT pa)c Using XML for Tax Transactions Title< 8@ _PID_HLINKSAVRhttp://www.xbrl.org/A "http://www.msdn.microsoft.com/xmlFQ http://www.xmlu.com/a7http://www.xml.org/?7http://www.w3c.org/  FMicrosoft Word Document MSWordDocWord.Document.89q i<@< NormalCJOJQJ_HmH sH tH d@d Heading 1,$d@ &#$./@&;CJKHOJQJB@B Heading 2$d@& CJOJQJ>@> Heading 3$d@& CJOJQJD@D Heading 4$d@&56CJOJQJL@L Heading 5<@&^6CJOJQJ]HH Heading 6 & FA<@&6CJOJQJDD Heading 7 & FA<@& CJOJQJHH Heading 8 & FA<@&6CJOJQJJ J Heading 9 & FA<@&56CJOJQJ<A@< Default Paragraph Font((Logo mHnHuJJ Company name dH5@CJ,OJQJB>@B Title@&]5KHOJQJJ!"J Product Namedl` @CJHKH8fO2f Product Descriptord8^6OJQJ_HmH sH tH POBP Subject Titlehd(x]h CJ OJQJ\OR\ Abstract Titled(x$d]5CJOJQJXObX Abstract Textd CJOJQJ_HmH sH tH jOj Legalese-Spacedt6F0$^6CJ OJQJ_HmH sH tH 0Oq0 Legalese X$$ ContentsNNTOC 1 P d;CJOJQJmHnHuHHTOC 2 PdCJOJQJmHnHu,@, Header  !, @, Footer  !jOj Body-no indent dx1$]CJOJQJ_HmH sH tH 2B2 Body Text<5CJDCD Body Text Indent h<^hCJ$O$ New term6XO"X Bullet 1*" & F hd1$^h` CJOJQJRO2R Bullet 2## d1$^` CJOJQJdOBd Bullet 3/$ & F %d1$^`%5CJOJQJ\R Bullet 4% & F d1$>T ^` CJOJQJ(Qb( Bullet 5&lrl Bullet body indent second' d1$^ CJOJQJZ!Z Bullet-body indent#( & F hm^`mZZCallout)&d! /5CJOJQJmHnHu^^ Caption1 Small*&d8<1Z  6CJOJQJJJ Caption2 Med+d8<6CJOJQJVV Caption3 Large,`d8<^`6CJOJQJ.. CODE-dL CJOJQJVV DOS Prompt#.d1$]^ CJOJQJVOV Footer-even"/ ! 5d$d^5 CJOJQJXOX Footer-odd%0 !5d$d^5 CJOJQJVV Picture1 Small1$1Z  &a$6CJOJQJ^^ Note/Caution#2 dx1$]5CJOJQJ2 Number3 & F (d1$>T .^`( CJOJQJ61B6 number indent 4]^]&)@Q& Page NumberHOH Picture2 Med 6$xCJmHnHuTTPicture3 Large7$`x^`CJmHnHuNON Table Body 28sd((]s CJOJQJVV Table Bold 29sd<]s^5CJOJQJLOL Table Bullet 1: & Fh^h`TOT Table Bullet 2%; & F hh^h`HH Table Bullet 3< & F@(^@BOB Table Head =d<5CJOJQJLLTOC 3> Pd^CJOJQJmHnHuLLTOC 4? d^CJOJQJmHnHu&& TOC 5 @^&& TOC 6 A^&& TOC 7 B^&& TOC 8 C^&& TOC 9 D^dd Document TitleE($1$^5CJOJQJ_HmH sH tH XbX Logo-ConnectivityFd1$^_HmH sH tH PrP Body-top of 1st pageG]ud1d Footer-page oneHd1$^CJOJQJmH sH uff Footer-Odd.I !@(0*xd$d1$^x5CJOJQJu828 MastheadJ1$_HmH sH tH PP Masthead-smallK1$0 CJJOJQJu414 Number-SpaceLuLL Table BoldM1$d((5CJOJQJu00 Table BodyNOJQJROR Bullet 6#O *d1$^*` CJOJQJbb Abstract Text-1st LineP1$dpCJOJQJuNON Table-HeadQd<1$^5CJOJQJJO"J Table-BodyR1$d((CJOJQJu<2< Contents Head S1$@& uAB twT & F h>T ^`u<&@Q< Footnote ReferenceCJH*HbH Footnote Text V1$dCJOJ QJ uZ"Z Caption(W$dxx~& /1$a$6CJOJQJuNN Code#XdV1$]`CJOJ QJ u(U@( Hyperlink>*B*>O> BodyZdx^CJOJQJhJYJ Document Map[1$d-D CJOJ QJ u6'@6 Comment ReferenceCJ00 Comment Text]CJTP@T Body Text 2^ pdx1$]p CJOJQJpp Ns<_$d&d5$7$8$9DH$P]^B*CJ _HmH phsH tH F^F Normal (Web)`dd[$\$ OJQJaJ>V@> FollowedHyperlink >*B* ph&X@!& Emphasis6]LL Tr"c$$d$dNa$CJ_HmH sH tH BBB Thd$d$<^5CJOJQJFRF Tp#e 0d$<^ CJOJQJ"Qb" Tpf f^"AB" Thf g^(_@( HTML Acronym44 Text i & F}x OJQJaJFF Normal Indent j^@CJOJQJB B Index 1k8^`8@CJOJQJd,d Table of Authoritiesl  ^`@CJOJQJP.P TOA Headingm8d^85@CJKHOJQJH/H Listn$d^`a$5@OJQJJ0J List Bullet!o$ & F ^a$:1: List Numberp & F^J2J List 2q$@ `^@ ``a$5B*\^Jph@3"@ List 3r$,^,`a$ 5CJ\(42( List 4 s ^ (5B( List 5 t@ ^@ 66R6 List Bullet 2 u^67b6 List Bullet 3 vp^p68r6 List Bullet 4 w ^ 696 List Bullet 5 x@ ^@ 6:6 List Number 2 y^6;6 List Number 3 zp^p6<6 List Number 4 { ^ 6=6 List Number 5 |@ ^@ fJf Subtitle/}$dT<x$d@& N]@CJ(OJQJ\6D6 List Continue ~`:E: List Continue 2 p^p:F: List Continue 3  ^ :G: List Continue 4 @ ^@ :H": List Continue 5  ^ pI2p Message Header2$ Hp8dx]p^8`5CJOJQJDQBD Body Text 3@B*CJOJQJphZRRZ Body Text Indent 2 8^8@B*CJOJQJphZSbZ Body Text Indent 3 ^@B*CJOJQJph4Zr4 Plain Text CJOJQJ Block Quotationw$Xd$d %d &d 'd -DM N O P Q ]^Xa$@CJOJQJRR Body Text Keep8d^85@OJQJ:r: Picture 8^8@CJOJQJ Part Labelb$dhE&#$$d%d+D8-D/0$M NO]a$@B*CJEHOJQJph Part TitleU$dE&#$%d+D8-D/0$M O]a$@B*CJTEHOJQJphVV Heading Base$8d^8@CJKHOJQJ44 Chapter Subtitlebb Company Name$$d&P#$+DH/0$@CJ KHOJQJ Chapter TitleZ$8dE&#$%d+D8-D/M O]^8a$@B*CJTEHOJQJphP P Footnote Base$8d^8@CJOJQJ<" < Table Text<@CJOJQJvv Title Cover9 d$d0N0]^5@CJ@OJQJ01 B 0 Document LabelZR Z Header Base$ !8d^8;@CJOJQJdb d Footer Even($8dX$dN^8;@CJOJQJfr f Footer First($8dX$dN^8;@CJOJQJb b Footer Odd($8dX$dN^8;@CJOJQJd d Header Even($8dX&dP^8;@CJOJQJh h Header First*$$8d$dN^8a$;@CJOJQJb b Header Odd($8dX&dP^8;@CJOJQJN N Index Basehd^h`@CJOJQJF F Table Header $<a$@CJOJQJVV Part Subtitle8hx^86@CJKHOJQJf f Return Address,$ pd(&#$+DH0$ CJOJQJ Section Heading3$$$xd&#$^x5;@CJEHH*KH\`` Section Label#h&dP^@CJ6OJQJz1 z Subtitle Cover8 d$dN]^5@CJ0OJQJF2 F TOC Base P d@CJOJQJ*(@A * Line NumberCJ6*@Q 6 Endnote ReferenceH*@Oa @ Lead-in Emphasis@CJOJQJ*Oq * Slogan6@CJ]0O 0 Superscript 5H*\0 0 Index 5d^0 0 Index 4d^0 0 Index 38d^80 0 Index 2d^D#1 D Table of Figures^`,+ , Endnote TextX!X Index Heading$d^@CJKHOJQJN N Level1$$ 8x]^8a$ CJOJQJd d Level2,$ 8<]^8`a$B*CJOJQJ^JphH" H Example8d^8:@CJOJQJ2 2 2 Level3  `,B , List 2 endxROQ RLPersonal Compose StyleCJOJQJ^JphNOa NLPersonal Reply StyleCJOJQJ^Jph2Or 2 AfterTable dcc"K "zz @z@z@z@z@z@z@z@z@ z@ z@ zP`(W0M9FAHRpWQ\c5k5 9ENj) ]DP  x!!"#a$Z%H&f&'`(q({(((((((((((((()))"),)-);)E)O)P)\)f)o)p)|))))))))))))))**^,n,x,,,,,,,,,,,,,,,,----..F/L/M/]/^/n/o/v/w//////////0`11374G4c4d4p44444444444445 555535F5G5c5w5x5555555555566-6D6E6\6x6y666666666677 7=7Q7R7m7v7w777777777778885868L8b8c8s888888888887:B:Y:Z:e:u:v:~::::::::::::: ; ;!;M;N;Z;;;;;;;;=====>>>>>>->.><>=>>>f@u@v@@@@@@@@@@@@@@@{BBICXCsCtCCCCCCCCCCC D D D,DDDEEF&F1F5F>FFFbFwFFHHaII\K~KLLNN*OO P>PRRRR6UU?VYVhVvVVVVVVVVVVVVVVVVVVVV4WnWoWWWXXX-YYYrZ}ZZO\P\\\o\\\\<]=]E]]]]^^^`^a^h^e_f_g_q_{_`^aab4c5c6c7c9c:c>?fDIG HSZZn[`fcg689:;<=>?@BCDEFGHIJKMNOPQRSTg7{___```^aaaa!bCbbbbc:XTXTXTXTXT"),LSV\!!@  EC@ B0( L B S  ?( .2 b  C ?3" b  C ?3" c\0k0k _Toc396470201 _Toc488470202 _Toc488470203c cmwp/u/x//////4494F4I4V4s444444444445"52555E5I5b5f5v5z555555555555566,6/6C6H6[6_6w6{6666666666666777"7<7?7P7T7l7y7777777777788884898K8N8a8e8r8v8~888888888\:d:g:t:::::::::: ;; ;#;L;P;Y;\;;;;=======> >> >,>0>;>@ @h@t@x@@@@@@@@AAB BBB#C/CKCWCZCfCwCCCCCCCCCCDDbFjFO PvVVVVVVVVVVVV%W.WWWYY=]D]^^aabb7ccc7'A'BCwCCCCCCCCCCCCCCDDvVVVVVVVVVVVVVVVVVVVV1W2WYY\\d\\\\\*]3]=]D]]]^^a^g^7ccc:::::::::::::::::::::::::::::::RR6U6U<\M\\\]\d\n\\\=]>]]]^^a^b^7c7c=cKchcvccccLesley AndersoncC:\WINNT\Profiles\leslea\Application Data\Microsoft\Word\AutoRecovery save of TaxML White Paper.asdLesley AndersoncC:\WINNT\Profiles\leslea\Application Data\Microsoft\Word\AutoRecovery save of TaxML White Paper.asdLesley Anderson7D:\My Documents\TaxML white paper\TaxML White Paper.docLesley Anderson7D:\My Documents\TaxML white paper\TaxML White Paper.docLesley AndersoncC:\WINNT\Profiles\leslea\Application Data\Microsoft\Word\AutoRecovery save of TaxML White Paper.asdJack.M:\NewTaxML\White Paper\TaxML White Paper2.docJack@\\172.31.29.100\MLshare\TaxML\White Paper\TaxML White Paper2.docJack@\\172.31.29.100\MLshare\TaxML\White Paper\TaxML White Paper2.docJack@\\172.31.29.100\MLshare\TaxML\White Paper\TaxML White Paper2.docJack@\\172.31.29.100\MLshare\TaxML\White Paper\TaxML White Paper2.doc|`͜},nq~2JƏ4i\$`xh0d@Un;F1t.m|  k+ #(X  @ 87 2   4#  8_ wl&D{J  | ^# X TnVH |  Xb @4O†<e! ) V! KQ!t." 9N$# S_Q$8vbIN& ! & J5( 9_ ($9: (]E( g)dFs*2 + m+ AY - g. i. X.  <1 F2 O3 w[4 Ri6 &66V$6 T97ڦI 7 "8 p: 2z:: =e< orr< I= e>"^@ڦIS@ E@ h=B CC YD ?D vyG rG ymG a%KH Ht.QIڦImYJ J |gK GFL $VM TCN v.N kJN @PGcTP"^[Pb2GuEUt.[oU h#U i9WF@[t.U[ g\Ym] a_t._%  .C` yxa 7a EIb"^Cb uc kcdv( g -6h 6qhDiFj Mjk R1l <~mBN(10t,2i yx WGz dUzڦI6r{ t:2} e}pw"c@ p(  ^`.^`.88^8`.^`. ^`OJQJo( ^`OJQJo( 88^8`OJQJo( ^`OJQJo(hh^h`. hh^h`OJQJo(*@(^`(CJOJQJo(. hh^h`OJQJo(hh^h`. hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo(h^`.h  ^ `.h L ^ `L.hxx^x`.hHH^H`.hL^`L.h^`.h^`.hL^`L. hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo(hh^h`.h ^`OJQJo(h pp^p`OJQJo(oh @ @ ^@ `OJQJo(h ^`OJQJo(h ^`OJQJo(oh ^`OJQJo(h ^`OJQJo(h PP^P`OJQJo(oh   ^ `OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo(@(^`(CJOJQJo(. hh^h`OJQJo(hh^h`o(. ^`OJQJo( ^`OJQJo(o pp^p`OJQJo( @ @ ^@ `OJQJo( ^`OJQJo(o ^`OJQJo( ^`OJQJo( ^`OJQJo(o PP^P`OJQJo( hh^h`OJQJo( hh^h`OJQJo(hh^h`. hh^h`OJQJo(h pp^p`OJQJo(h @ @ ^@ `OJQJo(oh ^`OJQJo(h ^`OJQJo(h ^`OJQJo(oh ^`OJQJo(h PP^P`OJQJo(h   ^ `OJQJo(oh ^`OJQJo(hh^h`o(.hh^h`o(-^`o(.^`.pLp^p`L.@ @ ^@ `.^`.L^`L.^`.^`.PLP^P`L. hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( m^`mOJQJo( hh^h`OJQJo(XX^X`o() hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo(^`.^`.pp^p`.@ @ ^@ `.^`.^`.^`.^`.PP^P`.hh^h`. hh^h`OJQJo(@](^]`(CJOJQJo(.XX^X`o() hh^h`OJQJo( hh^h`OJQJo(hh^h`. hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo(hh^h`. hh^h`OJQJo( hh^h`OJQJo(hh^h`.@](^]`(CJOJQJo(.XX^X`o() hh^h`OJQJo( hh^h`OJQJo(hh^h`. hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo(hh^h`.XX^X`o(.@](^]`(CJOJQJo(.^`.^`.pp^p`.@ @ ^@ `.^`.^`.^`.^`.PP^P`.@(^`(CJOJQJo(.hh^h`.hh^h`. ^`OJQJo( ^`OJQJo(o pp^p`OJQJo( @ @ ^@ `OJQJo( ^`OJQJo(o ^`OJQJo( ^`OJQJo( ^`OJQJo(o PP^P`OJQJo(@(^`(CJOJQJo(.hh^h`.h ^`OJQJo(h^`.h pp^p`OJQJo(h @ @ ^@ `OJQJo(h ^`OJQJo(oh ^`OJQJo(h ^`OJQJo(h ^`OJQJo(oh PP^P`OJQJo( hh^h`OJQJo(@(^`(CJOJQJo(.P^`P@@^@`.0^`0..``^``... ^` .... ^` ..... ^` ...... `^``....... 00^0`........ hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo(@(^`(CJOJQJo(. hh^h`OJQJo( hh^h`OJQJo( ^`OJQJo( ^`OJQJo(o pp^p`OJQJo( @ @ ^@ `OJQJo( ^`OJQJo(o ^`OJQJo( ^`OJQJo( ^`OJQJo(o PP^P`OJQJo( hh^h`OJQJo( hh^h`OJQJo(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJQJo(@ @ ^@ `CJOJQJo(^`CJOJQJo(^`CJOJQJo(^`CJOJQJo(^`CJOJQJo(PP^P`CJOJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( m^`mOJQJo(h^`.h ^`OJQJo(oh pp^p`OJQJo(h @ @ ^@ `OJQJo(h ^`OJQJo(oh ^`OJQJo(h ^`OJQJo(h ^`OJQJo(oh PP^P`OJQJo( hh^h`OJQJo( hh^h`OJQJo(XX^X`o() hh^h`OJQJo(hh^h`. hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo(e}&6<~m9_ (@4Ye>e>dZe>ZEIbEIb<[TPTP[TP\\R1lMjk|gK[oUAY -GFLU["8#(Xt:2}?Dh=Ba%KHT97! &| F2.C`w[4@QIdUz@Pm]O3p(9N$#E(kJNI=2h#U <1c@rG 2z::J5(D{J rr<XvyG87"S@Fj_g)\4# YD yxCbv.NbIN&H]]TCNg.uc6r{]P^ g^ __)|i.m+CC^#$VM +E@ymGXb-6hm|Ri66@X.k+yxa 7e!J7aWGzV!p:_mYJGuEUa_6qhKQ!@[1Fs*g\H (10t@`kc~}|=e<=e<` [P[P` i9WS_Q$8_ TnVZ 3@p^`pCJOJQJo(pZ @](^]`(CJOJQJo(.Z @](^]`(CJOJQJo(.H[ @@(^`(CJOJQJo(.[ @](^]`(CJOJQJo(. \ @](^]`(CJOJQJo(.\ @h h^h`OJQJo(\ @h h^h`OJQJo(T] @@ OJQJo(] @@ OJQJo(] @p^`pCJOJQJo(\^ @p^`pCJOJ QJ o(^ @p^`pCJOJQJo(,_ @p^`pCJOJ QJ o(_ @p^`pCJOJQJo(_ @h OJQJo(L` @(^`(CJ @ @0@ 0                                                                        :Pe0hQHv{٤ Fx         @H&f&q({(((((((((((((()))"),)-);)E)O)P)\)f)o)p)|))))))))))))))**n,x,,,,,,,,,,,,,,,,----F/L/M/]/^/n/o/v/w/////////74G4c4d4p44444444444445 555535F5G5c5w5x5555555555566-6D6E6\6x6y666666666677 7=7Q7R7m7v7w777777777778885868L8b8c8s8888888887:B:Y:Z:e:u:v:~::::::::::::: ; ;!;M;N;Z;;;;;;=====>>>>>>->.><>=>f@u@v@@@@@@@@@@@@@ICXCsCtCCCCCCCCCCC D D?VYVhVvVVVVVVVVVVVVVVVVVVV\\o\\\\<]=]E]]]]^^^`^a^h^e_f_c@6c6cls6c6c{c0@UnknownGz Times New Roman5Symbol3& z ArialW& ??Arial Unicode MSTahomaMCentury Schoolbook?& Arial BlackA& Arial NarrowE5  Lucida Console?5 z Courier New1"Helv9MS Serif3Times7Courier5& z!Tahoma7&  Verdana7Tms Rmn;Wingdings5"Geneva#AhFQ&Qf1Qf (P )L t>0dc 2QPC:\WINDOWS\Application Data\Microsoft\Templates\Windows 2000 Server Template.dotUsing XML for Tax TransactionsOpen XML standard for taxTax, XML, StandardsJackJackCompObjRjRoot Entry  Fw] c@Data WWordDocument wObjectPool @ܻHܻa  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVXYZ[\]^efghijkpqrstuvwxz{|}~  !"#$%&'()*+,-./0123456789:<=>?@ABDEFGHIJKLMNOPQTSUVWXrsburghCONTENTS 1TableoOSummaryInformation( ;DocumentSummaryInformation8C!Windows 2000 Server Template.dotrosJackws 13kMicrosoft Word 9.0 @U@G@G7@Z.Ȼ (P՜.+,D՜.+,l( px   White paperMSFT pa)c Using XML for Tax Transactions Titled@< _PID_HLINKS_AdHocReviewCycleID_EmailSubject _AuthorEmail_AuthorEmailDisplayNameAVRhttp://www.xbrl.org/A "http://www.msdn.microsoft.com/xmlFQ http://www.xmlu.com/a7http://www.xml.o  FMicrosoft Word Document MSWordDocWord.Document.89qrg/?7http://www.w3c.org/JWhite paper on Tax XMLpeterhor@microsoft.comPeter Ho