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 · Acknowledgments

EDI 980 Functional Group Totals

The X12 document used to transmit selected totals and accumulated totals for each type of transaction set in a functional group.

Sent by
Sender of the functional group
Received by
Receiver of the functional group
Standard
ANSI ASC X12

What is an EDI 980?

The EDI 980 Functional Group Totals is the ANSI X12 transaction set used to transmit selected totals and accumulated totals for each type of transaction set contained in a functional group.

Control totals let the receiver confirm that it has the complete set of transactions and that amounts add up, which matters for financial and statistical data. Where the 831 controls a batch of one transaction type, the 980 summarizes totals by type across a functional group. It suits financial and statistical batches.

How the EDI 980 worksDiagram of the EDI 980 Functional Group Totals. Sender of the functional group sends it to receiver of the functional group. 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: BT1 (Batch Totals). 0 optional loops are listed by their first segment.How the EDI 980 worksFunctional Group Totals: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 980SENDERSender of thefunctional groupRECEIVERReceiver of thefunctional group997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional groupGS … GETransaction set 980ST … SEHEADINGBT1Batch TotalsBlue 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 980. Your trading partner's implementation guide adds its own requirements.
How the EDI 980 worksDiagram of the EDI 980 Functional Group Totals. Sender of the functional group sends it to receiver of the functional group. 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: BT1 (Batch Totals). 0 optional loops are listed by their first segment.How the EDI 980 worksFunctional Group Totals: who sends it, where itfits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 980SENDERSender of thefunctional groupRECEIVERReceiver of thefunctional group997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group (GS … GE)Transaction set 980 (ST … SE)HEADINGBT1Batch TotalsBlue 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 980. Your trading partner'simplementation guide adds its own requirements.

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

  • Sending control totals with a functional group
  • Supporting reconciliation of financial batches
  • Checking completeness of transmitted data

Where it fits in the document flow

This document 980 Functional Group Totals
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 980 (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
  • BT1
  • SE

Practical example

The 980 in practice

A carrier sends a shipper a functional group containing many freight invoices. At the end of the group it includes a 980 with the number of invoices and the total amount billed. The shipper's system checks the totals against the invoices received before loading them for payment.

Implementation

Implementation considerations for the 980

  • Calculate totals from the transactions actually sent.
  • Agree with the receiver which totals are checked.
  • Define how mismatched totals are handled.
  • Distinguish from the 831, which controls a single transaction type.

How ECOM helps

Automate the 980 with ECOM

Solution

EDI Integration

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

Solution

Financial Document Automation

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

Industry

Trucking and Transportation

Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.

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

Related transactions

Related acknowledgments documents

All 9 acknowledgments documents

Need help with the EDI 980?

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

Request a Demo Contact us