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 822 Account Analysis

The X12 document banks use to send corporate clients detailed balance, service charge and adjustment information, typically monthly.

Sent by
Bank
Received by
Corporate client
Standard
ANSI ASC X12

What is an EDI 822?

The EDI 822 Account Analysis is the ANSI X12 transaction set used to transmit detailed balance, service charge and adjustment information, primarily from a bank to its corporate clients. It can also be used between or within corporations.

Banks charge companies for services such as wire transfers, lockbox processing and account maintenance, often offset by an earnings credit on balances. The account analysis statement shows the volumes and price of each service and the resulting fees, so treasury teams can verify charges and compare banks.

How the EDI 822 worksDiagram of the EDI 822 Account Analysis. Bank sends it to corporate client. 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) and DTM (Date/Time Reference) and detail: the required ENT loop with ENT (Entity). 4 optional loops are listed by their first segment.How the EDI 822 worksAccount Analysis: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 822SENDERBankRECEIVERCorporate client997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code AAGS … GETransaction set 822ST … SEHEADINGBGNBeginning SegmentDTMDate/Time Reference+ 2 optional loops, starting with:N1RTEDETAILRequired loop ENT · repeats many timesENTEntity+ 2 optional loops, starting with:N1ACTBlue 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 822. Your trading partner's implementation guide adds its own requirements.
How the EDI 822 worksDiagram of the EDI 822 Account Analysis. Bank sends it to corporate client. 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) and DTM (Date/Time Reference) and detail: the required ENT loop with ENT (Entity). 4 optional loops are listed by their first segment.How the EDI 822 worksAccount Analysis: who sends it, where it fitsand what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 822SENDERBankRECEIVERCorporate client997 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 AA (GS … GE)Transaction set 822 (ST … SE)HEADINGBGNBeginning SegmentDTMDate/Time Reference+ 2 optional loops, starting with:N1RTEDETAILRequired loop ENT · repeatsmany timesENTEntity+ 2 optional loops, starting with:N1ACTBlue 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 822. Your trading partner'simplementation guide adds its own requirements.

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

  • Receiving monthly bank fee statements
  • Auditing service charges against pricing agreements
  • Comparing bank costs across relationships

Where it fits in the document flow

This document 822 Account Analysis
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 822 (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
  • DTM
  • N1
  • RTE
  • ENT
  • ACT
  • LX
  • BLN
  • SER
  • SE

Practical example

The 822 in practice

A retailer uses three banks for collections and payments. Each month the banks send an 822 listing each service, the volume, unit price, total charge and the earnings credit on balances. The retailer's treasury team loads the statements into a fee analysis tool and finds a lockbox charge billed above the agreed price.

Implementation

Implementation considerations for the 822

  • Use standard service codes so analyses can be compared across banks.
  • Reconcile charges with negotiated pricing schedules.
  • Track volumes to confirm they match actual activity.
  • Agree the delivery schedule and format with each bank.

How ECOM helps

Automate the 822 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.

Industry

Retail

Retail and eCommerce EDI for suppliers and retailers, from purchase order to payment, with compliance built in.

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 822?

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

Request a Demo Contact us