X12 transaction guide · Acknowledgments
EDI 831 Application Control Totals
The X12 document used to transmit totals for a collection of transaction sets of the same type, so the receiver can check completeness.
- Sent by
- Sender of a batch of transactions
- Received by
- Receiver of the batch
- Standard
- ANSI ASC X12
What is an EDI 831?
The EDI 831 Application Control Totals is the ANSI X12 transaction set used to transmit totals associated with a collection of like transactions. All items reported in one 831 must be of the same transaction set type.
Control totals let the receiving application check that it received and processed everything: for example, a bank receiving a batch of payment orders can compare the count and total amount against the 831. It is commonly used with payment batches, where missing or duplicated items have direct financial consequences.
How to read this diagram: the top row shows who sends the 831, 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 831 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.
When it is used
- Sending control totals for a batch of payment orders
- Checking completeness of large transaction batches
- Supporting reconciliation of processed items
Where it fits in the document flow
Structure
Mandatory segments in the 831 (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
- AMT
- SE
Practical example
The 831 in practice
A company sends its bank a batch of 820 payment orders. With the batch it sends an 831 stating the number of payments and the total amount. The bank's system checks the received batch against the totals before processing, and a mismatch would hold the batch for investigation.
Implementation
Implementation considerations for the 831
- Include only one transaction set type per 831.
- Calculate totals from what is actually sent, not from source data.
- Define what happens when totals do not match.
- Agree with the receiver which totals it checks.
How ECOM helps
Automate the 831 with ECOM
Solution
Financial Document Automation
Automate invoices, remittances, payment files and bank statements from capture to posting.
Industry
Financial Services
Secure file transfer and B2B integration for banks and financial institutions.
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 acknowledgments documents
Need help with the EDI 831?
ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.