972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Finance

EDI 811 Consolidated Service Invoice/Statement

The X12 document used to bill or report complex, structured service invoice or statement detail, either consolidated or standalone.

Sent by
Service provider
Received by
Customer or account holder
Standard
ANSI ASC X12
EDIFACT equivalent
INVOIC

What is an EDI 811?

The EDI 811 Consolidated Service Invoice/Statement is the ANSI X12 transaction set for billing or reporting complex and structured service invoice or statement detail. It suits service arrangements whose billing needs more structure than a typical product invoice, and it can be used for consolidated or standalone invoices.

Telecommunications and utility providers are typical users, because their invoices cover many accounts, locations, services and usage charges. The 811's hierarchical structure lets customers load the detail and allocate costs to the right accounts automatically.

How the EDI 811 worksDiagram of the EDI 811 Consolidated Service Invoice/Statement. Service provider sends it to customer or account holder. It usually starts the exchange. It is usually followed by 997 and 820. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BIG (Beginning Segment for Invoice), detail: the required HL loop with HL (Hierarchical Level) and summary: TDS (Total Monetary Value Summary). 14 optional loops are listed by their first segment.How the EDI 811 worksConsolidated Service Invoice/Statement: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 811SENDERService providerRECEIVERCustomer or accountholder997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment820PaymentOrder/Remittance Advice2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code CIGS … GETransaction set 811ST … SEHEADINGBIGBeginning Segment forInvoice+ 2 optional loops, starting with:N1FA1DETAILRequired loop HL · repeats manytimesHLHierarchical Level+ 9 optional loops, starting with:LXNM1ITAIT1SLNTCDUSDIIIFA1SUMMARYTDSTotal Monetary ValueSummary+ 3 optional loops, starting with:ITABALN1Blue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 811. Your trading partner's implementation guide adds its own requirements.
How the EDI 811 worksDiagram of the EDI 811 Consolidated Service Invoice/Statement. Service provider sends it to customer or account holder. It usually starts the exchange. It is usually followed by 997 and 820. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BIG (Beginning Segment for Invoice), detail: the required HL loop with HL (Hierarchical Level) and summary: TDS (Total Monetary Value Summary). 14 optional loops are listed by their first segment.How the EDI 811 worksConsolidated Service Invoice/Statement: whosends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 811SENDERService providerRECEIVERCustomer oraccount holder997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment820Payment Order/Remittance Advice2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code CI (GS … GE)Transaction set 811 (ST … SE)HEADINGBIGBeginning Segment forInvoice+ 2 optional loops, starting with:N1FA1DETAILRequired loop HL · repeats manytimesHLHierarchical Level+ 9 optional loops, starting with:LXNM1ITAIT1SLNTCDUSDIIIFA1SUMMARYTDSTotal Monetary ValueSummary+ 3 optional loops, starting with:ITABALN1Blue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 811. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 811, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 811 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Telecommunications and utility billing
  • Consolidated invoices covering many accounts or sites
  • Service statements with usage and charge detail

Where it fits in the document flow

This document 811 Consolidated Service Invoice/Statement
Usually followed by 997 Functional Acknowledgment820 Payment Order/Remittance Advice

Structure

Mandatory segments in the 811 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • BIG
  • N1
  • FA1
  • FA2
  • HL
  • LX
  • QTY
  • NM1
  • ITA
  • IT1
  • AMT
  • SLN
  • TCD
  • USD
  • III
  • LQ
  • TDS
  • BAL
  • SE

Practical example

The 811 in practice

A company with 300 office locations receives one consolidated telecom bill each month. The provider sends it as an 811 with charges broken down by account, location and service. The company's accounts payable system loads the detail and allocates each location's costs to the right cost center automatically.

Implementation

Implementation considerations for the 811

  • Map the hierarchy of accounts and locations to your own cost structure before go-live.
  • Reconcile consolidated totals with the detail to catch missing or duplicated accounts.
  • Confirm whether the provider sends the 811 as an invoice, a statement or both.

How ECOM helps

Automate the 811 with ECOM

Industry

Telecom and Media

Equipment supply chains, service billing and partner data exchange for telecom and media companies.

Solution

Financial Document Automation

Automate invoices, remittances, payment files and bank statements from capture to posting.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related finance documents

All 58 finance documents

Need help with the EDI 811?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us