[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-335109-105":53,"doc-detail-335109-en":127},{"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":120,"head_meta":122,"extra_data":124,"updated_unix":126},105,"en","x12v4010-post-delivery-invoice-810-version-20-specification","X12V4010 Post-Delivery Invoice-810 - Version 2.0 - Specification","","X12/V4010 810 Post-Delivery Invoice Specification defines the invoice transaction set format and the required data contents for electronic data interchange (EDI) billing of goods and services. It describes the functional group, transaction set purpose, and mandatory interchange/group segment requirements. It specifies document structure including ST, BIG, N1, ITD, and item-level detail loops, plus totals via TDS and trailer via SE. It also lists relevant data type codes and provides segment field definitions with example interchange strings.",{"@graph":63,"@context":119},[64,80,102],{"@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":21,"@type":70,"position":76},"https://docshare.wps.com/template/invoices/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/x12v4010-post-delivery-invoice-810-version-20-specification/335109/",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/x12v4010-post-delivery-invoice-810-version-20-specification/335109.png","ImageObject",442,249,{"name":88,"@type":89},"Levi","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-17","2026-09-21",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",6,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115],{"name":106,"@type":107,"acceptedAnswer":108},"What does the X12/V4010 810 Post-Delivery Invoice transaction set specify?","Question",{"text":109,"@type":110},"It establishes the format and data contents for the 810 invoice transaction set used in EDI billing for goods and services.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"Which segments are required in the invoice heading portion?",{"text":114,"@type":110},"The specification states mandatory requirements for the ST transaction set header, BIG beginning segment for invoice, N1 name segment, and ITD credit terms segment.",{"name":116,"@type":107,"acceptedAnswer":117},"How are totals and the end of the transaction set handled?",{"text":118,"@type":110},"It includes a TDS total monetary value summary loop and concludes with the SE transaction set trailer segment.","https://schema.org",{"og:url":78,"og:type":121,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":123,"canonical":78},"index,follow",{"doc_id":125,"site_id":56},335109,1790460190,{"code":4,"msg":5,"data":128},{"doc_id":125,"user_id":129,"nickname":88,"user_avatar":130,"doc_module":9,"category_id":20,"category_name":21,"doc_title":59,"doc_description":61,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":101,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":30,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":140,"read_time":101},7971461740909,"https://ap-avatar.wpscdn.com/davatar_155a257f0dc6eb9ab79c44ca47cae57d","BeerBoard  \n810 Post-Delivery Invoice  \nX12/V4010/810 : Post-Delivery Invoice  \nVersion: 2.0  \nBeerBoard Version 2.0 10/17/2019  \n810 Post-Delivery Invoice  \nFunctional Group= IN  \nPurpose: This X12 Transaction Set contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to the billing for goods and services provided.  \nNote: Standard Interchange and Group Segments required.  \nHeading:  \nId  Req  Segment Name  Max Use  Max Loop  Loop ID Usage  \nST Y Transaction Set Header 1 Must Use  \nBIG Y Beginning Segment for Invoice 1 Must Use  \nLOOP ID-N1 200  \nN1 Y Name 1 Must Use  \nITD Y Credit Terms Segment for Invoice 1 Must Use  \nDetail:  \nLOOP ID- IT1 2000  \nIT1  \nPID  \nPO4  \nSAC  \nY  \nY  \nN  \nN  \nBaseline Item Data (Invoice) Product/Item Description Item Physical Details  \nService, Promotion, Allowance, or Charge Information  \n1  \n1  \n1  \n10  \nMust Use Used  \nUsed  \nUsed  \nSummary:  \nTDS Y Total Monetary Value Summary 1 Must Use  \nLOOP ID-SAC  \nSAC N Service, Promotion, Allowance, or 10 Used  \nCharge Information  \nSE Y Transaction Set Trailer 1 Must Use  \nData Type Codes  \nN-Numeric, AN-Alphanumeric,(x) -X Number of Decimals, ‘x’ -use X in this field, Date(yyyyMMdd)  \nBeerBoard Version 2.0 10/17/2019  \nX12V4010 Post-Delivery Invoice-810  \nSegment: ST Transaction Set Header  \nLoop: N/A  \nLevel: Heading  \nUsage: Mandatory  \nMax Use: 1  \nPurpose: To indicate the beginning of an invoice transaction set and transmit identifying  \nnumbers and dates  \nSegment Position Field Name Description Length Data Type Req?  \nST  \nST  \n1 Transaction Set Identifier Code  \n2 Transaction Control Number  \nCode identifying the type of transaction  \nCodeList Summary  \n(Total Codes: 318, Included: 1)  \nCode Name  \n810 Invoice  \nThis is the control number of the document. Same as SE_02  \n3/3 N Y  \n4/9 N Y  \nSemantics:  \n1. The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g. , 810 selects the Invoice Transaction Set) .  \nBeerBoard Segment Example:  \nST*810*194900001~  \nBeerBoard Version 2.0 10/17/2019  \nX12V4010 Post-Delivery Invoice-810  \nSegment: BIG Beginning Segment for Invoice  \nLoop: N/A  \nLevel: Heading  \nUsage: Mandatory  \nMax Use: 1  \nPurpose: To indicate the beginning of an invoice transaction set and transmit identifying  \nnumbers and dates  \nSegment Position Field Name Description Length Data Type Req?  \nBIG  \nBIG  \nBIG  \nBIG  \nBIG  \n1 Date  \n2 Invoice Number  \n3 Purchase Order Date  \n4 Purchase Order Number  \n7 Transaction Type Code  \nInvoice Date  \nIdentifying number assigned by issuer  \nDate of Purchase Order  \nIdentifying number for Purchase Order assigned by the orderer/purchaser  \nCode specifying the type of transaction  \nCode  Name  \nCR Credit  \nDI Debit  \n8/8  \n1/22  \n8/8  \n1/22  \n2/2  \nDate(yyyyMM dd)  \nAN  \nDate(yyyyMM dd)  \nAN  \nAN  \nY  \nY  \nY  \nY  \nN  \nBeerBoard Segment Example:  \nBIG*20190424*W-1234567*20190423*5267326***DI~  \nBeerBoard Version 2.0 10/17/2019  \nX12V4010 Post-Delivery Invoice-810  \nSegment:  \nLoop:  \nLevel:  \nUsage:  \nMax Use:  \nPurpose:  \nN1 Name  \nHeading Mandatory 1  \nTo identify a party by type of organization, name, and code  \nSegment Position Field Name Description Length Data Type Req?  \nN1  \nN1  \nN1  \nN1  \n1 Entity Identifier Code  \n2 Name  \n3 Identification Code Qualifier  \n4 Identification Code  \nCode identifying an organizational entity, a physical location, property or an individual  \nCode  Name  \nRE Remit To  \nFree-form Name  \nCode designating the system or method of code structure used for Identification Code  \nCode  Name  \n9 Supplier’s DUNS+4  \nCode identifying a party or other code  \n2/2  \n1/60  \n1/1  \n9/13  \nAN  \nY  \nY  \nY  \nY  \nNote:  \nIf No DUNS, Zero fill  \nBeerBoard Se","cbCaib1VpMslCnJn","https://ap.wps.com/l/cbCaib1VpMslCnJn","pdf",135317,"English","# Functional Group and Purpose\n## Transaction Set Overview\n# Data Types and Coding Rules\n## Data Type Codes\n# Segment Definitions (Heading)\n## ST Transaction Set Header\n## BIG Beginning Segment for Invoice\n## N1 Name Segment\n## ITD Credit Terms Segment\n# Detail and Item-Level Structure\n## IT1 Baseline Item Data (Invoice)\n## Item Description and Charge/Allowance Elements\n# Summary and Trailer\n## TDS Total Monetary Value Summary\n## SE Transaction Set Trailer","[{\"question\":\"What does the X12/V4010 810 Post-Delivery Invoice transaction set specify?\",\"answer\":\"It establishes the format and data contents for the 810 invoice transaction set used in EDI billing for goods and services.\"},{\"question\":\"Which segments are required in the invoice heading portion?\",\"answer\":\"The specification states mandatory requirements for the ST transaction set header, BIG beginning segment for invoice, N1 name segment, and ITD credit terms segment.\"},{\"question\":\"How are totals and the end of the transaction set handled?\",\"answer\":\"It includes a TDS total monetary value summary loop and concludes with the SE transaction set trailer segment.\"}]","X12V4010 Post-Delivery Invoice-810 - Version 2.0 - Specification | PDF",1790009689]