James Allman | JA Technology Solutions LLC
BAI2 Type Code Reference
Search BAI2 type codes from the BAI file specification: balance status codes, credit codes, and debit codes, with plain-language descriptions.
BAI2 Type Code Reference
Look up any commonly encountered BAI2 type code by number or by description. Type 175 or 451 and the reference normalizes the digits; type a phrase like lockbox or wire and it searches titles and descriptions. Each code shows its title from the BAI specification, a plain-language note on what it means operationally, and its place in the hierarchy: status and balance codes (010 to 099), credit summary and detail codes (100 to 399), and debit summary and detail codes (400 to 699). Filter by level, or switch on the commonly-used filter to see the codes that dominate real bank files: 142 and 165 ACH credits, 175 check deposit packages, 195 incoming wires, 451 and 455 ACH debits, 475 checks paid, 555 returned deposited items, and the ZBA pair 275 and 575. Copy any code with one click. Runs entirely in your browser.
Learn more ↓
Loading interactive explorer...
How Type Codes Drive Cash Application and Reconciliation
Every balance and transaction in a BAI2 bank file carries a three-digit type code, and that code is what downstream automation keys on. A cash application process watches for 142 and 165 ACH credits and 195 incoming wires to match against open receivables; a check reconciliation or positive pay process matches 475 check-paid details against the issued-check register; a treasury position pulls 015 and 045 balances each morning; and ZBA structures show up as the 275/575 credit and debit pair. Getting a type code mapping wrong means payments silently land in the wrong bucket, which is why the mapping table deserves as much review as the code that reads the file.
The Status, Summary, and Detail Hierarchy
The numbering itself encodes the hierarchy. Codes 010 through 099 are status codes: balances and float positions reported on the account record (record 03), not transactions. Codes 100 through 399 are credits and 400 through 699 are debits, and within each range some codes are summaries (totals with counts, like 100 Total Credits and 400 Total Debits) while others are details (individual transactions on record 16, like 175 and 451). A well-formed file's details add up to its summaries, which makes the summary codes natural control totals: if the 475 details do not sum to the 470 total, something was dropped. Banks also extend the table with proprietary codes, commonly in the 9xx range, so an unrecognized code is a prompt to open the bank's implementation guide rather than a parsing error.
Working With the Files Themselves
This reference covers what the codes mean; the companion tools cover the files. The BAI2 File Explorer opens a real bank file in the browser and shows every account, balance, and transaction with its type code decoded, and the BAI2 File Generator builds test files for exercising an import before the bank connection goes live. When the goal is a daily feed that parses BAI2, applies the type code routing, and posts to an ERP or accounting system, that is the kind of pipeline I build. See data pipelines and ETL or integration services.
All tools run entirely in your browser. Your data never leaves your machine.