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 · Government and regulatory

EDI 152 Statistical Government Information

The X12 document used to report predefined statistical information to government agencies.

Sent by
Business, institution or agency
Received by
Government statistical agency
Standard
ANSI ASC X12

What is an EDI 152?

The EDI 152 Statistical Government Information is the ANSI X12 transaction set used to report predefined statistical government information.

Government agencies collect statistics from businesses and institutions through surveys and mandatory reports, such as production, employment or trade figures. Where the data items are predefined, respondents can submit them electronically from their own systems, which reduces the reporting burden and improves data quality. The data items are defined in advance by the collecting agency, so respondents can map them once to their own systems and report each period without manual forms. Agencies combine the reports into published statistics.

How the EDI 152 worksDiagram of the EDI 152 Statistical Government Information. Business, institution or agency sends it to government statistical agency. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment), the required N1 loop with N1 (Party Identification) and the required GRI loop with GRI (Statistical Government Information). 1 optional loops are listed by their first segment.How the EDI 152 worksStatistical Government Information: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 152SENDERBusiness, institutionor agencyRECEIVERGovernment statisticalagency997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code GRGS … GETransaction set 152ST … SEHEADINGBGNBeginning SegmentRequired loop N1 · repeats up to 1,000N1Party IdentificationRequired loop GRI · repeats up to 100,000GRIStatistical Government Information+ 1 optional loop, starting with:N1Blue 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 152. Your trading partner's implementation guide adds its own requirements.
How the EDI 152 worksDiagram of the EDI 152 Statistical Government Information. Business, institution or agency sends it to government statistical agency. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment), the required N1 loop with N1 (Party Identification) and the required GRI loop with GRI (Statistical Government Information). 1 optional loops are listed by their first segment.How the EDI 152 worksStatistical Government Information: who sendsit, where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 152SENDERBusiness,institution oragencyRECEIVERGovernmentstatisticalagency997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code GR (GS … GE)Transaction set 152 (ST … SE)HEADINGBGNBeginning SegmentRequired loop N1 · repeats up to1,000N1Party IdentificationRequired loop GRI · repeats up to100,000GRIStatistical GovernmentInformation+ 1 optional loop, starting with:N1Blue 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 152. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 152, 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 152 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

  • Submitting periodic statistical surveys
  • Reporting predefined data to agencies
  • Replacing paper statistical forms

Where it fits in the document flow

This document 152 Statistical Government Information
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 152 (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
  • BGN
  • N1
  • GRI
  • SE

Practical example

The 152 in practice

A manufacturer must report quarterly production and shipment figures to a statistics agency. Its ERP extracts the figures and sends a 152 with the predefined data items for the quarter. The agency validates them and includes them in its industry statistics.

Implementation

Implementation considerations for the 152

  • Map survey items to internal data sources.
  • Meet the agency's reporting calendar for each survey.
  • Validate figures to avoid follow-up queries.
  • Check which electronic formats the agency accepts.

How ECOM helps

Automate the 152 with ECOM

Solution

Enterprise Integration

Any-to-any integration across partners, systems, protocols, security requirements, formats and ERPs, in batch or real time.

Industry

Manufacturing

Customer schedules, supplier connectivity and shipping integrated with the ERP for manufacturers.

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 government and regulatory documents

All 29 government and regulatory documents

Need help with the EDI 152?

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

Request a Demo Contact us