Lockboxes
Use this topic to identify which bank lockbox files are supported by the parser, what formats they use, and whether invoice detail and images are available.
You can determine whether a file delivered by your bank is supported by the parser. Each section in this topic lists the exact files to expect, their format, and what data is and is not extracted.
Images and keyed in information
In lockbox processing, there are actually two independent things happening after a check arrives at the bank:
Scanning — the physical check is photographed → produces a TIFF image
Data keying — an operator reads the remittance stub and manually types invoice numbers/amounts into the bank's system
These two things can exist independently of each other. So you can have four combinations:
Image Reference + Keyed-In Invoice Data
JPMC
Wells Fargo
Truist XML
BIDS (Symcor)
No Image Reference + Keyed-In Invoice Data
Western Bank Alliance
Image Reference + No Keyed-In Data
SVB
Fifth Third Bank
Tophat - CSV Parser
No Image Reference + No Keyed-In Data (this is an incomplete parser)
Truist IDX
Quick reference: File support identification
Truist (IDX): Flat text (no headers), fixed-width → No invoice detail
Truist (XML): Single XML (<Extract> root) → Invoice detail if stubs present
Fifth Third Bank: Flat text (records start with 5/6), fixed-width → No (image refs only)
JPMorgan Chase (JPMC): Comma-delimited (field 7 = C/M/R) → Yes
Silicon Valley Bank (SVB): CSV (no header, 9 columns) → No
Western Bank Alliance: CSV (header, per-invoice rows) → Yes
Tophat: ZIP (*MKE*.csv + TIFF) → No
Wells Fargo: images.dat + fields.dat → Yes (via fields.dat)
BIDS (Symcor): control_file.xml + .C0/.I0/.S0 → Yes
Structured invoice rows or linked files → Yes
Flat cheque-only records → No