The EDI 822 is the electronic file banks send to corporate clients in place of a paper account analysis statement. Built on the ANSI X12 standard, it reports your balances, the earnings credit the bank applied, and every service fee charged during the billing period as structured data your treasury or ERP system can read without manual entry. For a company running more than a handful of accounts, it’s how you actually verify what your bank charged and whether the pricing matches your agreement.
What’s Inside an 822 File
An 822 is organized into segments, each carrying one kind of financial data. Entity and account identification segments route the data to the right corporate entity and the right account. Balance segments report your average ledger balance, collected balance, and investable balance for the cycle. Service segments carry every fee the bank charged, broken out by unit cost, volume, and total. Adjustment segments record any corrections the bank posted during the month.
The structure is defined. The ENT segment identifies the entity and related accounts. The BLN segment carries balance information. The SER segment details individual service charges with pricing. The ADJ segment handles balance or service adjustments. Each segment uses qualifiers that your receiving software has to interpret correctly to put the data in the right fields.1National Institute of Standards and Technology. Federal Implementation Guideline for Electronic Data Interchange ASC X12 003040 Transaction Set 822 Customer Account Analysis Implementation Convention
What makes the format useful is the line-item fee detail. Wire transfers, ACH transactions, lockbox processing, account maintenance, and every other service appear as separate items with their own unit price and volume. That’s the audit trail you need to confirm the bank is billing you at your negotiated rates rather than list prices.
How Fees Are Labeled: AFP Service Codes
Most banks don’t rely on free-text descriptions. They tag each balance and charge with an AFP Service Code, a standardized numbering system the Association for Financial Professionals has maintained since 1986.2Association for Financial Professionals. AFP Service Codes The domestic set includes hundreds of codes covering general account services, lockbox, electronic funds transfers, disbursement reconciliation, and more. A separate global standard with over 900 codes covers international banking services.3Association for Financial Professionals. Global AFP Service Codes Committee Review
Standard codes do two things for you. They let you compare pricing across banks directly, because the same service carries the same code regardless of which institution is quoting it. And they let your treasury software route each charge to the right general ledger account automatically, instead of relying on someone to interpret the bank’s phrasing and guess at the right category.
Reading the Earnings Credit
The 822 reports what the bank charged and how much of that was already offset by your earnings credit. Banks apply an earnings credit rate to your investable balance, and the resulting dollar figure reduces what you owe in cash. The formula: average investable balance multiplied by the annualized ECR, multiplied by days in the cycle, divided by days in the year.
Your investable balance begins with your average collected balance (ledger balance less uncollected funds). Historically banks subtracted a reserve requirement before arriving at the investable figure. Federal reserve requirements on transaction accounts have been zero percent since March 2020 and remain at zero for 2026.4Federal Register. Regulation D: Reserve Requirements of Depository Institutions Some banks still apply a notional reserve deduction anyway, which cuts your credit. It’s worth checking the 822 for this, because it quietly reduces the offset against your fees.
The ECR itself moves with interest rates. When rates are high, a reasonable operating balance can cancel most of your monthly charges. When rates are low, you either carry much larger balances or you pay fees in cash. The ECR and investable balance figures on each month’s 822 are the fastest way to tell whether your banking relationship is still priced where you negotiated it.
Setting Up 822 Delivery From Your Bank
Start with your bank’s implementation guide. Every institution customizes how it uses X12 segments, and the guide tells you which qualifiers, code sets, and optional segments that bank sends. You’ll also need the Interchange Sender and Receiver IDs that sit in the ISA and GS envelope segments of the X12 standard, which establish the communication channel between your organization and the bank.5X12. X12 Transaction Sets
From there, your technical team maps the incoming fields to the matching fields in your ERP or treasury system. The map tells your software that a given balance qualifier updates a specific general ledger account, and that a given AFP service code posts to a specific expense category. A bad map doesn’t just produce ugly reports. It can misallocate expenses across departments for months before anyone catches it.
Test transmissions matter. Confirm that your translator handles the bank’s decimal placements, date formats, and optional segments. Confirm it recognizes the start and end of each transaction set so data isn’t truncated. Treasury usually works with IT to settle file naming and directory conventions so incoming files process without anyone touching them.
Transmission and Acknowledgment
Banks deliver the 822 over secure channels. The common options are SFTP, which runs over SSH; AS2, which uses S/MIME encryption and digital signatures and supports message disposition notifications for formal receipt confirmation; and a Value-Added Network, which acts as a managed intermediary handling routing, translation, and connectivity. All three protect the data in transit.
When your system receives the file, it sends back an EDI 997 Functional Acknowledgment confirming the data arrived and met the structural standard. If decryption fails or the structure is corrupted, the system flags it for review rather than silently dropping data. Once the file validates, it flows into your reconciliation module, which compares the bank’s reported charges against your internal activity records.
At month-end, the system can highlight fees above negotiated thresholds, flag balances that fell below required minimums, and generate verified reports for the treasury team. For a company with dozens of accounts across multiple banks, that’s the difference between a one-day close and a week of manual reconciliation.
How Long to Keep the Files
Account analysis files are financial records that back up your tax returns, so federal retention rules apply. The IRS generally requires businesses to keep records for at least three years from the date the return was filed, with longer periods for specific situations.6Internal Revenue Service. How Long Should I Keep Records The IRS also treats machine-readable data from EDI systems as records subject to those rules, and Revenue Procedure 98-25 requires that electronic records be retained as long as their contents may be material to administering any internal revenue law.7Internal Revenue Service. Revenue Procedure 98-25 In practice, most treasury departments keep account analysis files for at least seven years and store both the raw EDI file and the translated, human-readable report, so they can show both what the bank sent and how their system processed it.