[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-303072-105":53,"doc-detail-303072-en":130},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":123,"head_meta":125,"extra_data":127,"updated_unix":129},105,"en","edi-technical-specifications-form-year-2026","EDI Technical Specifications - Form Year 2026","","Provide file format instructions for electronic filing of Electronic Data Interface (EDI) Form E-500 and E-536 using the ANSI X12 813 transaction set, Version 4010, for North Carolina Sales and Use Tax Return processing. Define required and conditional segments, including mandatory presence of certain data elements in the NC layout to avoid rejection of the 813 record. Summarize transaction set structure (header, TFS loop, FGS loop, trailer), looping rules by document and county, and programming constraints for rates, tilde separators, and dollar-and-cent formatting.",{"@graph":63,"@context":122},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":36,"@type":70,"position":76},"https://docshare.wps.com/template/forms/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/edi-technical-specifications-form-year-2026/303072/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/edi-technical-specifications-form-year-2026/303072.png","ImageObject",442,249,{"name":88,"@type":89},"McGucket","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-09-26","2026-09-19",true,{"@type":98,"interactionType":99,"userInteractionCount":76},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114,118],{"name":105,"@type":106,"acceptedAnswer":107},"What is the document’s purpose for EDI filing?","Question",{"text":108,"@type":109},"It provides file format instructions and guidance for electronic filing of EDI Form E-500 and E-536 using the specified 813 transaction set and version.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"Which transaction set and version are specified for these forms?",{"text":113,"@type":109},"The document specifies the 813-transaction set with ANSI X12 Version 4010 for the North Carolina Sales and Use Tax Return layout.",{"name":115,"@type":106,"acceptedAnswer":116},"How does the document define the TFS loop and the FGS loop?",{"text":117,"@type":109},"The TFS loop carries return information for a specific sales tax account and filing period. The FGS loop carries tax information tied to specific North Carolina documents (E-500 or E-536) and must be included in each TFS loop with required labeling (E500 and county-specific E536 loops).",{"name":119,"@type":106,"acceptedAnswer":120},"What formatting rules are required for data elements and amounts?",{"text":121,"@type":109},"Dollar amounts must use dollars and cents. The tilde (~) separates data elements, and unused elements require an additional tilde to mark the unused position.","https://schema.org",{"og:url":78,"og:type":124,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":126,"canonical":78},"index,follow",{"doc_id":128,"site_id":56},303072,1790213849,{"code":4,"msg":5,"data":131},{"doc_id":128,"user_id":132,"nickname":88,"user_avatar":133,"doc_module":9,"category_id":35,"category_name":36,"doc_title":59,"doc_description":61,"doc_content":134,"file_id":135,"file_url":136,"file_type":137,"file_size":138,"view_count":76,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":139,"language":140,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":141,"faqs":142,"seo_title":143,"seo_description":61,"update_tm":144,"read_time":145},1236954412713,"https://us-avatar.wpscdn.com/davatar_29158cc5080c5b710cf443261637dec0","EDI Technical Specifications  \nForm Year 2026  \nPurpose of Document  \nThe purpose of this document is to provide the file format instructions and guidance for the electronic filing of Electronic Data Interface (EDI) Form E-500 and E-536.  \nWhat’s New  \n•  Effective July 1, 2026 , the following county: Mecklenburg (060), levied an additional 1.00% tax.  \n*See Appendix B for a list of all announcements.  \nFile Format Requirements  \nThe following pages specify our translation requirements for the 813-transaction set, Version 4010, for the North Carolina Sales and Use Tax Return. Note that some segments and data elements that may be optional in the ANSI X12 standards are mandatory in the NC layout. This means that we require this information, and it must be present in the transaction set to be a valid tax return. If required segments or required information within segments are missing, the 813 record will be rejected. Even if you are not an expert on EDI standards, you should be able to set up your software so that it can create an acceptable 813-transaction set by following the specifications on the next few pages. However, it is strongly recommended that you have some general familiarity with EDI and X12 .  \nTo learn more regarding the ANSI X12 standards, please visit.  \nQuestions about the technical specifications should be directed via email [to](to EDI_SAU@ncdor.gov)[ ](to EDI_SAU@ncdor.gov)[EDI_SAU@ncdor.gov](to EDI_SAU@ncdor.gov).  \nTransaction Set Overview  \nThe following diagram shows the 813-transaction set, and the segments required for our program.  \nHEADER PORTION OF TRANSACTION SET:  \nISA Interchange Control Header GS Functional Group Header ST Transaction Set Header  \nBTI Beginning Tax Information  \nDETAIL PORTION OF TRANSACTION SET:  \nTFS Tax Form (one for each filing period)  \nN1 Name  \nN2 Additional Name Information (if needed)  \nDTM Date Time Reference (period beginning date)  \nDTM Date Time Reference (period ending date)  \nFGS Form Group (for either an E500 or E-536 document) TIA Tax Information and Amount  \n“  \n.  \n“  \n.  \n“  \n.  \nTIA “  \n“  \n.  \n“  \n.  \nTRAILER PORTION OF TRANSACTION SET:  \nSE Transaction Set Trailer  \nGE Functional Group Trailer IEA Interchange Control Trailer  \nNOTES:  \nThere are two “loops” within the detail portion of the transaction set.  \na. The outer loop, called the “TFS loop” carries the tax return information for a specific sales tax account for a specific filing period. If a return is submitted for just one period, then the 813 will have only one TFS loop. If a return is being submitted for multiple periods, then the 813 will have one TFS loop for each filing period.  \nb. The inner loop, called the “FGS loop” carries tax information associated with specific North Carolina sales tax documents (i.e., E-500 or E-536) . You must always include one, and only one, FGS loop labeled “E500” in each TFS loop when you are transmitting sales and use tax return information. All taxpayers are required to file a county breakdown form (E-536) . Each TFS loop must include one FGS loop, labeled “E536” for each county in which the 2% county tax was collected and for each of the counties subject to the 2.25% county tax rate.  \nc. All loops must end with a back slash (\\) .  \nAll segments are required, unless designated otherwise.  \nNOTES:  \nAll dollar amounts must be dollars and cents.  \nThe tilde (~) is used to separate data elements within a segment. Whenever thereis an unused data element within a segment, you must insert an additional tilde to indicate the unused data element.  \nWhen programming the EDI format for the E-500 (Sales and Use Tax Return) accompanied by the E-536 (Schedule of County Sales and Use Tax), we require that the following conditions be met:  \nLine 4-General State Rate: Effective July 1, 2011, the State levies a 4. 75% general rate of tax on the sales price of taxable tangible personal property, services, or digital property that is sold at retail and is not subject to a reduce","cbCaidYDanZONUK8","https://ap.wps.com/l/cbCaidYDanZONUK8","pdf",506705,27,"English","# Purpose of Document\n# What’s New\n# File Format Requirements\n# Transaction Set Overview\n## Header Portion of Transaction Set\n## Detail Portion of Transaction Set\n## Trailer Portion of Transaction Set\n# Notes and Programming Conditions\n## Loop Rules (TFS loop and FGS loop)\n## Data Formatting Requirements","[{\"question\":\"What is the document’s purpose for EDI filing?\",\"answer\":\"It provides file format instructions and guidance for electronic filing of EDI Form E-500 and E-536 using the specified 813 transaction set and version.\"},{\"question\":\"Which transaction set and version are specified for these forms?\",\"answer\":\"The document specifies the 813-transaction set with ANSI X12 Version 4010 for the North Carolina Sales and Use Tax Return layout.\"},{\"question\":\"How does the document define the TFS loop and the FGS loop?\",\"answer\":\"The TFS loop carries return information for a specific sales tax account and filing period. The FGS loop carries tax information tied to specific North Carolina documents (E-500 or E-536) and must be included in each TFS loop with required labeling (E500 and county-specific E536 loops).\"},{\"question\":\"What formatting rules are required for data elements and amounts?\",\"answer\":\"Dollar amounts must use dollars and cents. The tilde (~) separates data elements, and unused elements require an additional tilde to mark the unused position.\"}]","EDI Technical Specifications - Form Year 2026 | PDF",1789799879,9]