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 821 Financial Information Reporting

The X12 document used to report account balances, detail and summary financial transactions and related account information.

Sent by
Bank or financial institution
Received by
Corporate client or treasury system
Standard
ANSI ASC X12

What is an EDI 821?

The EDI 821 Financial Information Reporting is the ANSI X12 transaction set used to report balances, detail and summary financial transactions, and other related financial account information.

Corporate treasury teams use bank reporting to see opening and closing balances, credits and debits on every account each day. The 821 is one way banks deliver that data; many banks also offer BAI2, SWIFT MT940 or ISO 20022 camt statements, so the format is agreed bank by bank. The account analysis (822) covers fees and service charges separately.

How the EDI 821 worksDiagram of the EDI 821 Financial Information Reporting. Bank or financial institution sends it to corporate client or treasury system. 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: B2A (Set Purpose), DTM (Date/Time Reference) and TRN (Trace) and detail: the required ENT loop with ENT (Entity). 5 optional loops are listed by their first segment.How the EDI 821 worksFinancial Information Reporting: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 821SENDERBank or financialinstitutionRECEIVERCorporate client ortreasury system997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code FRGS … GETransaction set 821ST … SEHEADINGB2ASet PurposeDTMDate/Time ReferenceTRNTrace+ 2 optional loops, starting with:LMFA1DETAILRequired loop ENT · repeats many timesENTEntity+ 3 optional loops, starting with:N1ACTFA1Blue 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 821. Your trading partner's implementation guide adds its own requirements.
How the EDI 821 worksDiagram of the EDI 821 Financial Information Reporting. Bank or financial institution sends it to corporate client or treasury system. 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: B2A (Set Purpose), DTM (Date/Time Reference) and TRN (Trace) and detail: the required ENT loop with ENT (Entity). 5 optional loops are listed by their first segment.How the EDI 821 worksFinancial Information Reporting: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 821SENDERBank orfinancialinstitutionRECEIVERCorporate clientor treasurysystem997 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 FR (GS … GE)Transaction set 821 (ST … SE)HEADINGB2ASet PurposeDTMDate/Time ReferenceTRNTrace+ 2 optional loops, starting with:LMFA1DETAILRequired loop ENT · repeatsmany timesENTEntity+ 3 optional loops, starting with:N1ACTFA1Blue 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 821. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 821, 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 821 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 prior-day account balances and transactions
  • Receiving intraday transaction reporting
  • Feeding cash management and reconciliation systems

Where it fits in the document flow

This document 821 Financial Information Reporting
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 821 (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
  • B2A
  • DTM
  • TRN
  • LM
  • LQ
  • FA1
  • FA2
  • ENT
  • N1
  • ACT
  • RTE
  • BLN
  • TSU
  • FIR
  • NM1
  • SE

Practical example

The 821 in practice

A manufacturer holds operating accounts at two banks. Each morning both banks send an 821 with the prior day's balances and every credit and debit. The treasury system consolidates the cash position, and the accounting system matches incoming customer payments to open invoices.

Implementation

Implementation considerations for the 821

  • Confirm which reporting formats each bank offers.
  • Map bank transaction codes for automatic reconciliation.
  • Check that opening balances match the previous closing balances.
  • Secure the channel, since the data is financially sensitive.

How ECOM helps

Automate the 821 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 finance documents

All 58 finance documents

Need help with the EDI 821?

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

Request a Demo Contact us