
⏱ About a 5-minute read. Click “Read more” or “Sample file” whenever you want the details.
Sree deposits a $320 check with the bank’s mobile app. No paper goes anywhere, just a picture and some data.
- Not a banker? Just look at the pictures and read the “In one line” boxes. That is enough to get the idea.
- Work in banking or operations? Open “Read more” under each file and each payment type.
- Product owner? Read the status codes, the “Status, rules, security and data” boxes and the product owner rows. Those are the decisions that land on your desk.
- Developer? Open every “Sample file”, then read the data mapping section and the developer rows.
- Operations or support? Use the runbook table: what to watch at each file, and who acts.
- Tester? Use the “What to test” rows as your starting checklist.
- Forward deployed engineer? Jump to “For forward deployed engineers”. It covers what to ask the client, set-up, testing, go-live and where things usually go wrong.
How checks work
In one line: Checks are cleared as pictures in X9.37 files. Checks from other countries are sent for collection.
- Coming in: check pictures and data from a branch, the mobile app, an ATM or a lockbox.
- Going out: an X9.37 image file to the Fed or The Clearing House.
- Coming back: return image files and positive pay exceptions.
Status, rules, security and data
| Status flow | Captured → Read (MICR) → On hold → Sent in image file → Paid Side paths: Returned (NSF, fraud), Duplicate image, Positive pay exception |
| Regulation and rules | Regulation CC, which sets when deposited money must be available. Check 21. UCC Articles 3 and 4. Federal Reserve Operating Circular 3. |
| Security standards | Check image quality and catch duplicates. Offer positive pay to business clients. Keep strong controls on mobile deposits. |
| Data governance | Check images show names, addresses and account numbers. Protect them, and keep them only as long as your records policy says. |
Read more: Checks (cheques)
For tech teams, product owners and testers
| For developers | Read the MICR line, check the images, build X9.37 files and process return files. |
| For product owners | The hold policy, mobile deposit limits, and whether to offer positive pay. |
| What to test | The same check deposited twice. The amount read wrongly. A return after the money was released. A check from another country. |
Step by step
- Sree photographs the front and back of the check in the app. (It could also go in at a branch, an ATM or a lockbox.)
- The bank reads the MICR line and the amount, and checks the check was not deposited before.
- The bank puts a hold on the money, following Reg CC, and tells Sree when it will be available.
- The bank sends the check picture and data in an X9.37 file to the Fed or The Clearing House.
- The paying bank checks it (including positive pay for business accounts), then pays it or sends it back.
- Returns come back as image files. The bank matches what it sent out with what was deposited.
When things go wrong: rejected, returned, cancelled
Not every payment goes through. On Checks, there are three ways a payment can fail. Each one means something different for the money.
Rejected. The bank can refuse a deposit straight away: the picture is too dark or cut off, the check was already deposited, or it’s over the mobile deposit limit. Nothing is sent out, and Sree can try again or go to a branch.
Returned. Days later, the paying bank can send the check back: not enough money, a stop payment, a closed account or a suspected fraud. The return arrives as an image file. Sree’s bank takes the money back out of Sree’s account and sends a notice (sometimes with a fee).
Cancelled. The person who wrote the check can place a stop payment before it’s paid. The paying bank then returns it. Business clients using positive pay get a list of checks that don’t match what they issued, and decide to pay or return each one.
Codes you will see: Common return reasons: not enough money (NSF) · stop payment · account closed · refer to maker · altered or fictitious
Which files carry the bad news?
Each path has its own file or message. Here is what travels, who sends it, and what is inside.
| Path | File or message | From → to | What it says |
|---|---|---|---|
| Rejected | App or branch message | Bank → depositor | Bad image, duplicate, over limit |
| Returned | X9.37 return file (record 31 + addendum) | Paying bank → Fed/TCH → your bank | Return reason and the check images |
| Returned | Return notice + statement line | Bank → depositor | Deposit reversed |
| Cancelled | Stop payment (in the bank’s system) | Check writer → paying bank | Do not pay check no. … |
| Positive pay | Issue file in, exception report out | Company ↔ bank | Which checks are real, pay or return |
Sample file: X9.37 return file
Fictional data, shortened. Real files carry more fields.
Record 01 File header Sree's bank <- paying bank
Record 10 Cash letter header collection type: returns
Record 20 Bundle header
Record 31 Return record routing 123456780 account 9876543210
check no. 1047 amount 320.00
return reason: A (A = NSF, C = stop payment, D = closed account)
Record 32 Return addendum A bank of first deposit, deposit date
Record 50 Image view detail front and back
Record 52 Image view data the check pictures
Record 70 Bundle control count 1, total 320.00
Record 90 Cash letter control
Record 99 File controlSample file: Positive pay issue file (CSV)
Fictional data, shortened. Real files carry more fields.
account,check_number,amount,issue_date,payee,void
1112223334,1047,320.00,2026-11-18,JOHN SMITH,N
1112223334,1048,1250.50,2026-11-18,ACME SUPPLIES INC,N
1112223334,1049,0.00,2026-11-18,,Y
Bank's exception report next morning:
check 1050 amount 2,900.00 not in issue file -> PAY or RETURN?Checks runbook: what to watch at each file
This is the day-to-day runbook for the files above, in the same order. For each step: the file you are looking at, what “good” looks like, what to do when it isn’t, and who acts. L1 is the service desk, L2 is payment operations and app support, and L3 is engineering.
| Step | File | Check | If it goes wrong | Who |
|---|---|---|---|---|
| 1. Deposit | Check image and data | Image clear, MICR read, amount right. | Bad image? Ask for a new photo before accepting. | L1 |
| 2. Duplicate check | Internal record | The check wasn’t deposited before. | Duplicate? Refuse it and flag the account. | L2 with fraud team |
| 3. Hold | Reg CC hold notice | Hold set and the customer told when money is available. | Wrong hold? Fix it and send a corrected notice. | L2 |
| 4. Send | X9.37 image file | File accepted by the Fed or The Clearing House. | Rejected file? Fix the records and resend before the deadline. | L2, L3 if it’s technical |
| 5. Positive pay | Issue file and exception report | Business clients decide on every exception in time. | No decision? Apply the client’s default (pay or return). | L2 |
| 6. Returns | X9.37 return file | Returns sent by the midnight deadline, deposits reversed. | Late return? The bank may be stuck with the loss. Escalate. | L2 |
Golden rules
- Paying banks must return a check by midnight of the next banking day.
- Catch duplicates at deposit, not after the money is gone.
- Check images hold names and account numbers. Protect them.
Want the full picture, from building it to running it live? Read the Check and Remote Deposit Capture Runbook.
For forward deployed engineers (FDE)
As an FDE, you sit with the client and make the integration actually work. Here is your checklist for this rail.
| First call with the client | Branch, mobile, remote deposit or lockbox? Daily deposit limits? Do they want positive pay for the checks they write? |
| Set up and connectivity | Scanners or the mobile SDK, image quality settings, deposit limits, and the positive pay file format and delivery time. |
| Test and certify | Good and bad images, duplicate deposits, a wrong amount and returns. Then image exchange testing with the Fed or The Clearing House. |
| Go-live and hypercare | Watch duplicates and returns in the first few weeks. Adjust hold rules within Reg CC. |
| Where it usually breaks | The same check deposited twice. Poor images. Positive pay files sent late, so problems are missed. |
The files on this rail
Each file below shows how it starts, what is inside, its status codes and a sample. For all the other files, see the full guide: how payment files are processed in US banks.
X9.37 (X9.100-187): check image files
In one line: The file banks use to clear checks as pictures instead of paper.
- How it starts: someone scans a check at a branch, an ATM, a mobile app or a lockbox. The bank reads the MICR line along the bottom (routing number, account and check number) and the amount.
- What is inside: headers, one record for each check, pictures of the front and back, and control totals.
- How it travels: to the Fed or The Clearing House image exchange, then on to the paying bank. Returned checks come back in the same format.
Sample file: X9.37 (X9.100-187)
Made-up data, shortened. Real files have more fields.
X9.37 / X9.100-187 image cash letter (binary: data records + TIFF images)
01 File header from bank 222333445 to Fed / TCH, date 20261120
10 Cash letter header cash letter ID, business date
20 Bundle header bundle of items
25 Check detail MICR: routing 123456780, account 9876543210, check no 1045, amount 0000032000
50 Image view detail front image, back image
52 Image view data the TIFF image bytes
70 Bundle control item count, total amount
90 Cash letter control total items, total amount
99 File control total cash letters, total items, total amountRead more: X9.37 (X9.100-187)
For tech teams, product owners and testers
| For developers | Check the image quality (not too dark, not cut off), the MICR line and the amount. Catch the same check being deposited twice, for example once by mobile and once at a branch. |
| For product owners | Set hold rules that follow Reg CC, set mobile deposit limits, and decide what happens with duplicate deposits. |
| What to test | A duplicate image. The written amount and the read amount do not match. A poor image. A return after the money was already made available. |
BAI2: the classic US statement
In one line: An older text statement format. Many US companies still use it to reconcile their accounts.
- How it starts: the bank produces it every morning for the previous day, and sometimes during the day for the current day.
- What is inside: each line starts with a code. 01 is the file header, 02 the group and 03 the account and balances. 16 is one transaction. 49, 98 and 99 are the account, group and file totals.
- Type codes tell you what each line is. For example, 010 is the opening balance, 015 the closing balance and 495 an outgoing wire.
Sample file: BAI2
Made-up data, shortened. Real files have more fields.
01,222333445,SREECORP,261120,0600,001,,,2/
02,SREECORP,222333445,1,261119,2400,USD,2/
03,1112223334,USD,010,5000000,,,015,4874950,,/
16,495,125050,0,OUT-000123,INV-7781,WIRE TO ACME SUPPLIES INC/
49,10000000,3/
98,10000000,1,5/
99,10000000,1,7/Read more: BAI2
For tech teams, product owners and testers
| For developers | Check the control totals in records 49, 98 and 99. A line can carry on in an 88 record. Amounts have no decimal point, so 125050 means $1,250.50. |
| For product owners | BAI2 carries less detail than camt.053. Plan the move for clients who need full remittance data. |
| What to test | 88 continuation lines. Totals that do not match. An account with no activity. A negative balance. |
Read next
- All payment files, one by one (pain.001, pain.002, pain.008, NACHA, ISO 20022)
- Check and Remote Deposit Capture Runbook
Sources: Federal Reserve Financial Services; The Clearing House; Nacha Operating Rules; Swift. Sample files are fictional and shortened.
Working on a payments project?
I help banks and fintechs deliver real-time payments, ISO 20022, and AI-driven AML and compliance change, from strategy to go-live.
Connect on LinkedInSee how I can help