Skip to content

X9 reference

X9.37 file format: record types and fields

The image cash letter format of DSTU X9.37-2003 and ANSI X9.100-187, record by record: how a file is organized, every field layout with its positions, the main code tables and the checks the X9 Viewer runs.

Last updated

On this page

How an X9.37 file is organized

An X9.37 file, or image cash letter, carries checks between banks as fixed records, each starting with a two-digit record type. The records nest: the file holds cash letters, a cash letter holds bundles, a bundle holds the items (checks presented for payment, or returns), and each item carries its addenda and its image views. Every bundle, cash letter and the file itself close with a control record that states their counts and totals.

  1. 01File HeaderOnce, the first record
  2. 10Cash Letter HeaderStarts each cash letter
  3. 20Bundle HeaderStarts each bundle
  4. 25Check DetailOne per check presented (forward collection)
  5. 26 27 28Check Detail Addenda A, B and CAfter their check, before its images
  6. 31ReturnOne per returned item (return cash letters)
  7. 32 33 34 35Return Addenda A to DAfter their return, before its images
  8. 50 52Image View Detail and Image View DataA pair per image view, usually front then back
  9. 54Image View AnalysisOptional, after the view it describes
  10. 61 62Credit recordsWhere the exchange partners use them, in a bundle or cash letter
  11. 70Bundle ControlCloses each bundle
  12. 75 85Box Summary and Routing Number SummaryOptional, after the bundles of a cash letter (40 and 41 in DSTU files)
  13. 90Cash Letter ControlCloses each cash letter
  14. 99File ControlOnce, the last record
Indented records repeat: any number of cash letters per file, bundles per cash letter and items per bundle. A User Record (68) can appear wherever its owner puts one.

Editions and standard levels

“X9.37” is the common name for the format, after the draft standard DSTU X9.37-2003. ANSI X9.100-187 replaced the draft in 2008 and has been revised since, most recently in 2021. The File Header’s Standard Level (positions 3–4) says which edition a file follows, and the X9 Viewer picks each record’s layout from it.

Editions of the X9.37 format
EditionStandard LevelNotes
DSTU X9.37-200303Draft standard for trial use (DSTU) for check image exchange. Replaced by X9.100-187; the Federal Reserve still accepts it.
X9.100-187-200830The US standard that replaced DSTU X9.37-2003. It adds fields in positions the DSTU left reserved.
X9.100-187-201335Revision of the 2008 edition.
X9.100-187-201635Revision of the 2013 edition. From this edition on, return reasons are defined in the separate standard X9.100-188.
X9.100-187-2021 (current)Not confirmedCurrent edition; revises the 2016 edition. Not yet reviewed here, so the Standard Level its files carry and any layout changes are unconfirmed.
  • ANSI X9.100-180: The non-domestic successor of DSTU X9.37 (used in Canada); it defines its own type 61 credit record.
  • ANSI X9.100-181: The TIFF image format for exchanged check images.
  • ANSI X9.100-188: Return reasons for check image exchange and image replacement documents, customer and administrative (current edition 2023).
  • ASC X9 TR 47 (Universal Companion Document): Industry rules for using X9.100-187 between exchange partners (current edition 2022).

Bytes, encodings and record lengths

  • Text is EBCDIC or ASCII. Record text is EBCDIC (code page 037 in the US) or ASCII, and the first record’s type bytes tell which. Image data and digital signatures are binary and never converted.
  • Each record starts with a 4-byte length. The usual transmission format puts the record’s length in four bytes, big-endian, in front of every record. Some files have no prefix (records back to back, or one per line in ASCII exports), an IBM record descriptor word (a 2-byte length and two zero bytes), or a little-endian length written by some PC tools. The X9 Viewer detects all four.
  • Records are 80 bytes, except the 100-byte Credit (62) and four variable-length types whose own length fields say how long they are: the image archive addenda (27 and 34), Image View Data (52) and User Record (68).
  • Numbers are digits only. Amounts are in cents with no decimal point (0000123456 is $1,234.56), dates are YYYYMMDD and times hhmm on a 24-hour clock. Routing numbers carry the ABA check digit; in checks and returns the ninth digit is a field of its own.

Check images

Each view of an item is a pair of records: an Image View Detail (50) that describes it and an Image View Data (52) that carries the bytes. A check usually has two views, front (View Side Indicator 0) then back (1); an Image View Analysis (54) may follow either.

  • TIFF with Group 4 compression is the default. Image View Format 00 (TIFF 6) with compression 00 (CCITT Group 4, a black-and-white fax encoding) needs no agreement between the banks; JPEG, PNG and the other formats do. ANSI X9.100-181 defines the TIFF profile for exchanged images.
  • The image is near the end of the 52. After the fixed fields (to position 105) come the image reference key (X bytes), a 5-digit signature length and the digital signature (Y bytes), then a 7-digit image length and the image (Z bytes). The image data starts at byte 118 + X + Y of the record.
  • The 50 states what the 52 should hold: whether an image is present (Image Indicator), its format and compression, and its size in bytes. The X9 Viewer compares them with the image it finds and decodes TIFF Group 4 views for display.

Totals and counts the viewer checks

Every control record is compared with what the file actually holds. Amounts are compared to the cent.

  • Bundle Control (70): the number of items (checks or returns), their total amount, the total of the checks whose MICR Valid Indicator is 1 (a warning when it is off) and the number of image views (50 records) in the bundle.
  • Cash Letter Control (90): the number of bundles, items and image views in the cash letter, and the items’ total amount.
  • File Control (99): the number of cash letters, the number of records of every type (the 01 and 99 included), the number of items and their total amount.
  • Credits: from the 2008 edition on, the Credit Total Indicator in the 70, 90 and 99 says whether credit records (61, 62) are part of those counts and totals: 1 includes them, 0 leaves them out. With a blank indicator, or in a DSTU file, the viewer accepts either.
  • Items: each check’s or return’s addendum count against the addenda that follow it, and the record numbers of those addenda. A Routing Number Summary (85) is checked against the items for its routing number (a warning).

Record types

The 25 record types the X9 Viewer decodes. Types 61, 62 and 68 are not in DSTU X9.37-2003; 40 and 41 are only in it; and 61 is not defined by either standard: the bank or clearing arrangement sets its layout.

X9.37 record types
TypeRecordBytesDSTU 2003X9.100-187What it holds
01File Header Record80 bytesDSTU 2003: YesX9.100-187: Yes80YesYesOpens the file: standard level, test or production, immediate destination and origin, and creation date and time.
10Cash Letter Header Record80 bytesDSTU 2003: YesX9.100-187: Yes80YesYesOpens a cash letter: the bundles sent together for one business day, with collection type, routing numbers and cash letter ID.
20Bundle Header Record80 bytesDSTU 2003: YesX9.100-187: Yes80YesYesOpens a bundle of items within a cash letter, with its business date, ID and sequence number.
25Check Detail Record80 bytesDSTU 2003: YesX9.100-187: Yes80YesYesOne check presented for payment: MICR line data (routing number, On-Us, Auxiliary On-Us), amount and item sequence number.
26Check Detail Addendum A Record80 bytesDSTU 2003: YesX9.100-187: Yes80YesYesBank of first deposit (BOFD) endorsement: return location, BOFD business date, deposit account and payee.
27Check Detail Addendum B RecordVariable lengthDSTU 2003: YesX9.100-187: YesVariableYesYesImage archive reference for the check: microfilm sequence number and a variable-length image reference key.
28Check Detail Addendum C Record80 bytesDSTU 2003: YesX9.100-187: Yes80YesYesA subsequent endorsement, one record per endorsing bank after the BOFD.
31Return Record80 bytesDSTU 2003: YesX9.100-187: Yes80YesYesOne returned item: payor bank routing number, On-Us, amount, return reason and forward bundle date.
32Return Addendum A Record80 bytesDSTU 2003: YesX9.100-187: Yes80YesYesBOFD endorsement on the returned item (same layout as type 26).
33Return Addendum B Record80 bytesDSTU 2003: YesX9.100-187: Yes80YesYesPayor bank details for the return: bank name, item sequence number, business date and payor account name.
34Return Addendum C RecordVariable lengthDSTU 2003: YesX9.100-187: YesVariableYesYesImage archive reference for the returned item (same layout as type 27).
35Return Addendum D Record80 bytesDSTU 2003: YesX9.100-187: Yes80YesYesAn endorsing bank on the returned item (same layout as type 28).
40Account Totals Detail Record80 bytesDSTU 2003: YesX9.100-187: No80YesNoItem count and amount for a key account or account range.
41Non-Hit Totals Detail Record80 bytesDSTU 2003: YesX9.100-187: No80YesNoItem count and amount for items that matched no key account.
50Image View Detail Record80 bytesDSTU 2003: YesX9.100-187: Yes80YesYesDescribes one image view of the item (front or back): format, compression, creator and digital-signature settings. Its Image View Data record follows.
52Image View Data RecordVariable lengthDSTU 2003: YesX9.100-187: YesVariableYesYesCarries the image bytes of the preceding Image View Detail, with the image reference key and optional digital signature.
54Image View Analysis Record80 bytesDSTU 2003: YesX9.100-187: Yes80YesYesImage quality and usability test results for the preceding image view.
61Credit Reconciliation Record80 bytesDSTU 2003: NoX9.100-187: No80NoNoA credit for the deposit, within a cash letter or bundle.
62Credit Record100 bytesDSTU 2003: NoX9.100-187: Yes100NoYesA credit for the deposit, with a 14-digit amount.
68User RecordVariable lengthDSTU 2003: NoX9.100-187: YesVariableNoYesData defined by the record owner: the general format, or format 001 for a payee endorsement.
70Bundle Control Record80 bytesDSTU 2003: YesX9.100-187: Yes80YesYesCloses a bundle with its item count, total amount, MICR-valid amount and image count.
75Box Summary Record80 bytesDSTU 2003: YesX9.100-187: Yes80YesYesTotals for a box of bundles: destination, bundle count and box total.
85Routing Number Summary Record80 bytesDSTU 2003: YesX9.100-187: Yes80YesYesItem count and amount totals for one routing number within the cash letter.
90Cash Letter Control Record80 bytesDSTU 2003: YesX9.100-187: Yes80YesYesCloses a cash letter with its bundle, item and image counts, total amount, ECE institution name and settlement date.
99File Control Record80 bytesDSTU 2003: YesX9.100-187: Yes80YesYesCloses the file with its cash letter, record and item counts and the file total amount.

Record layouts

Every field of every record type, with positions counted from 1 and both ends included. Usage is M (mandatory) or C (conditional: present when it applies). Where a DSTU X9.37-2003 file differs, the differences follow the layout. In variable-length records, X, Y and Z stand for the lengths given in the record’s own length fields.

Data types used in the field tables
TypeCharacters allowed
NNumeric: digits 0 to 9
AAlphabetic: letters
ANAlphanumeric: letters and digits
ANSAlphanumeric and special characters
BBlank
NBNumeric or blank
NSNumeric and special characters
NBSMNumeric, blank and the special MICR characters (the dash, and * for a character that could not be read)
NBSMOSAs NBSM, plus the On-Us symbol (/)
BinaryBytes that are not text: image data and digital signatures

01 File Header Record

Opens the file: standard level, test or production, immediate destination and origin, and creation date and time. 80 bytes. Defined in DSTU X9.37-2003, X9.100-187-2008/2013/2016.

X9.100-187 (2008 to 2016 editions): 80 bytes
PositionFieldLengthTypeUsageDescription
1–2Record Type2NMAlways "01".
3–4Standard Level2NMEdition of the standard the file follows. Standard Level codes
5Test File Indicator1AMWhether the file is test or production.
6–14Immediate Destination Routing Number9NMRouting number of the institution receiving the file.
15–23Immediate Origin Routing Number9NMRouting number of the institution sending the file.
24–31File Creation Date8NMDate the file was created (YYYYMMDD).
32–35File Creation Time4NMTime the file was created (hhmm, 24-hour clock).
36Resend Indicator1AMWhether the file is being resent.
37–54Immediate Destination Name18ANSCName of the institution receiving the file.
55–72Immediate Origin Name18ANSCName of the institution sending the file.
73File ID Modifier1ANCDistinguishes files created on the same date and time between the same institutions.
74–75Country Code2ACCountry of the sending institution (e.g. US).
76–79User Field4ANSCFor use at the discretion of the institution creating the record.
80Companion Document Indicator1ANCIdentifies the companion document (clearing arrangement rules) the file follows. Added in X9.100-187-2008; Reserved in DSTU X9.37-2003.
DSTU X9.37-2003: the fields that differ from X9.100-187 (2008 to 2016 editions)
PositionFieldLengthTypeUsageDescription
80Reserved1BMReserved for future use; blank.

10 Cash Letter Header Record

Opens a cash letter: the bundles sent together for one business day, with collection type, routing numbers and cash letter ID. 80 bytes. Defined in DSTU X9.37-2003, X9.100-187-2008/2013/2016.

X9.100-187 (2008 to 2016 editions): 80 bytes
PositionFieldLengthTypeUsageDescription
1–2Record Type2NMAlways "10".
3–4Collection Type Indicator2NMKind of items in the cash letter. Collection Type Indicator codes
5–13Destination Routing Number9NMRouting number of the institution the cash letter is sent to.
14–22ECE Institution Routing Number9NMRouting number of the institution that created the cash letter.
23–30Cash Letter Business Date8NMBusiness day of the cash letter (YYYYMMDD).
31–38Cash Letter Creation Date8NMDate the cash letter was created (YYYYMMDD).
39–42Cash Letter Creation Time4NMTime the cash letter was created (hhmm).
43Cash Letter Record Type Indicator1AMWhich item and image records the cash letter contains. Cash Letter Record Type Indicator codes
44Cash Letter Documentation Type Indicator1ANCDefault documentation type for the items; Z means each item states its own. Documentation Type Indicator codes
45–52Cash Letter ID8ANMIdentifier assigned by the institution that created the cash letter.
53–66Originator Contact Name14ANSCContact at the institution that created the cash letter.
67–76Originator Contact Phone Number10NCPhone number of the originator contact.
77Fed Work Type1ANCFederal Reserve work type, when the cash letter is sent to the Federal Reserve.
78Returns Indicator1ACKind of returns in a return cash letter. Added in X9.100-187-2008; Reserved in DSTU X9.37-2003.
79User Field1ANSCFor use at the discretion of the institution creating the record.
80Reserved1BMReserved for future use; blank.
DSTU X9.37-2003: the fields that differ from X9.100-187 (2008 to 2016 editions)
PositionFieldLengthTypeUsageDescription
45–52Cash Letter ID8ANCIdentifier assigned by the institution that created the cash letter.
78User Field1ANSCFor use at the discretion of the institution creating the record.
79–80Reserved2BMReserved for future use; blank.

20 Bundle Header Record

Opens a bundle of items within a cash letter, with its business date, ID and sequence number. 80 bytes. Defined in DSTU X9.37-2003, X9.100-187-2008/2013/2016.

X9.100-187 (2008 to 2016 editions): 80 bytes
PositionFieldLengthTypeUsageDescription
1–2Record Type2NMAlways "20".
3–4Collection Type Indicator2NMKind of items in the bundle. Collection Type Indicator codes
5–13Destination Routing Number9NMRouting number of the institution the bundle is sent to.
14–22ECE Institution Routing Number9NMRouting number of the institution that created the bundle.
23–30Bundle Business Date8NMBusiness day of the bundle (YYYYMMDD).
31–38Bundle Creation Date8NMDate the bundle was created (YYYYMMDD).
39–48Bundle ID10ANCIdentifier assigned by the institution that created the bundle.
49–52Bundle Sequence Number4NBCOrder of the bundle within the cash letter.
53–54Cycle Number2ANCPresentment cycle agreed between the exchange partners.
55–63Reserved9BMReserved for future use; blank.
64–68User Field5ANSCFor use at the discretion of the institution creating the record.
69–80Reserved12BMReserved for future use; blank.
DSTU X9.37-2003: the fields that differ from X9.100-187 (2008 to 2016 editions)
PositionFieldLengthTypeUsageDescription
55–63Return Location Routing Number9NCWhere returns for the bundle should be sent. Reserved from X9.100-187-2008 on.

25 Check Detail Record

One check presented for payment: MICR line data (routing number, On-Us, Auxiliary On-Us), amount and item sequence number. 80 bytes. Defined in DSTU X9.37-2003, X9.100-187-2008/2013/2016.

DSTU X9.37-2003 and X9.100-187 (2008 to 2016 editions), the same layout: 80 bytes
PositionFieldLengthTypeUsageDescription
1–2Record Type2NMAlways "25".
3–17Auxiliary On-Us15NBSMCMICR Auxiliary On-Us field: usually the serial number of a business check.
18External Processing Code1NSCMICR position 44, used for special purposes authorized by X9.
19–26Payor Bank Routing Number8NMFirst 8 digits (TTTTAAAA) of the routing number of the bank the check is drawn on.
27Payor Bank Routing Number Check Digit1NMNinth digit of the payor bank routing number (ABA check digit).
28–47On-Us20NBSMOSCMICR On-Us field: the payor's account number and often the serial number; '/' is the On-Us symbol.
48–57Item Amount10NMAmount of the check in cents.
58–72ECE Institution Item Sequence Number15NBMNumber assigned by the institution that created the record; unique within the file.
73Documentation Type Indicator1ANCWhether an image and/or paper accompanies the item. Documentation Type Indicator codes
74Electronic Return Acceptance Indicator1ANCWhether the institution that created the record will accept electronic returns and return notifications for the item.
75MICR Valid Indicator1NCResult of reading the MICR line. MICR Valid Indicator codes
76BOFD Indicator1AMWhether the ECE institution is the bank of first deposit. BOFD Indicator codes
77–78Check Detail Record Addendum Count2NMNumber of Check Detail Addendum A, B and C records (26/27/28) that follow.
79Correction Indicator1NCWhether and how the MICR line was repaired. Correction Indicator codes
80Archive Type Indicator1ANCHow the item is archived. Archive Type Indicator codes

26 Check Detail Addendum A Record

Bank of first deposit (BOFD) endorsement: return location, BOFD business date, deposit account and payee. 80 bytes. Defined in DSTU X9.37-2003, X9.100-187-2008/2013/2016.

X9.100-187 (2008 to 2016 editions): 80 bytes
PositionFieldLengthTypeUsageDescription
1–2Record Type2NMAlways "26".
3Check Detail Addendum A Record Number1NMPosition of this record among the item’s Addendum A records, starting at 1.
4–12Return Location Routing Number9NMWhere returns and return notifications should be sent; usually the BOFD.
13–20BOFD Business (Endorsement) Date8NMBusiness date of the BOFD endorsement (YYYYMMDD).
21–35BOFD Item Sequence Number15NBCSequence number assigned by the BOFD.
36–53Deposit Account Number at BOFD18ANSCAccount the item was deposited to.
54–58BOFD Deposit Branch5ANSCBranch where the item was deposited.
59–73Payee Name15ANSCName of the payee.
74Truncation Indicator1AMWhether the BOFD truncated the original check.
75BOFD Conversion Indicator1ANCHow the BOFD converted the item. Conversion Indicator codes
76BOFD Correction Indicator1NCWhether and how the BOFD repaired the MICR line. Correction Indicator codes
77User Field1ANSCFor use at the discretion of the institution creating the record.
78–80Reserved3BMReserved for future use; blank.
DSTU X9.37-2003: the fields that differ from X9.100-187 (2008 to 2016 editions)
PositionFieldLengthTypeUsageDescription
4–12Bank of First Deposit (BOFD) Routing Number9NMRouting number of the bank of first deposit.

27 Check Detail Addendum B Record

Image archive reference for the check: microfilm sequence number and a variable-length image reference key. Variable length. Defined in DSTU X9.37-2003, X9.100-187-2008/2013/2016.

DSTU X9.37-2003 and X9.100-187 (2008 to 2016 editions), the same layout: 46+X bytes
PositionFieldLengthTypeUsageDescription
1–2Record Type2NMAlways "27".
3Image Reference Key Indicator1NMWhether an Image Reference Key is present.
4–18Microfilm Archive Sequence Number15NBCSequence number of the item in the microfilm archive.
19–22Length of Image Reference Key4NMNumber of bytes in the Image Reference Key that follows.
23–22+XImage Reference KeyXANSCKey for retrieving the archived image. Its length, X, is the value of field 4 (Length of Image Reference Key).
23+X–37+XDescription15ANSCDescription of the archive reference.
38+X–41+XUser Field4ANSCFor use at the discretion of the institution creating the record.
42+X–46+XReserved5BMReserved for future use; blank.

28 Check Detail Addendum C Record

A subsequent endorsement, one record per endorsing bank after the BOFD. 80 bytes. Defined in DSTU X9.37-2003, X9.100-187-2008/2013/2016.

X9.100-187 (2008 to 2016 editions): 80 bytes
PositionFieldLengthTypeUsageDescription
1–2Record Type2NMAlways "28".
3–4Check Detail Addendum C Record Number2NMPosition of this record among the item’s endorsement addenda, starting at 01.
5–13Endorsing Bank Routing Number9NMRouting number of the endorsing bank.
14–21Endorsing Bank Business (Endorsement) Date8NMBusiness date of the endorsement (YYYYMMDD).
22–36Endorsing Bank Item Sequence Number15NBMSequence number assigned by the endorsing bank.
37Truncation Indicator1AMWhether the endorsing bank truncated the original check.
38Endorsing Bank Conversion Indicator1ANCHow the endorsing bank converted the item. Conversion Indicator codes
39Endorsing Bank Correction Indicator1NCWhether and how the endorsing bank repaired the MICR line. Correction Indicator codes
40Return Reason1ANCReturn reason, when the endorsement is on a returned item. Return Reason codes Meanings as listed in X9.100-187-2008. From the 2016 edition on, return reasons are defined in ANSI X9.100-188 (current edition 2023), which separates customer and administrative reasons and may list other codes; check them against your exchange partner’s list.
41–59User Field19ANSCFor use at the discretion of the institution creating the record.
60Endorsing Bank Identifier1ANCRole of the endorsing bank in the exchange. Added in X9.100-187-2008; Reserved in DSTU X9.37-2003.
61–80Reserved20BMReserved for future use; blank.
DSTU X9.37-2003: the fields that differ from X9.100-187 (2008 to 2016 editions)
PositionFieldLengthTypeUsageDescription
40Return Reason1ANCReturn reason, when the endorsement is on a returned item. Return Reason codes Meanings as listed for DSTU X9.37-2003, where T is Stop Payment Suspect.
60–80Reserved21BMReserved for future use; blank.

31 Return Record

One returned item: payor bank routing number, On-Us, amount, return reason and forward bundle date. 80 bytes. Defined in DSTU X9.37-2003, X9.100-187-2008/2013/2016.

X9.100-187 (2008 to 2016 editions): 80 bytes
PositionFieldLengthTypeUsageDescription
1–2Record Type2NMAlways "31".
3–10Payor Bank Routing Number8NMFirst 8 digits (TTTTAAAA) of the routing number of the bank the item was drawn on.
11Payor Bank Routing Number Check Digit1NMNinth digit of the payor bank routing number (ABA check digit).
12–31On-Us Return Record20NBSMOSCMICR On-Us field of the returned item; '/' is the On-Us symbol.
32–41Item Amount10NMAmount of the returned item in cents.
42Return Reason1ANMWhy the item is being returned. Return Reason codes Meanings as listed in X9.100-187-2008. From the 2016 edition on, return reasons are defined in ANSI X9.100-188 (current edition 2023), which separates customer and administrative reasons and may list other codes; check them against your exchange partner’s list.
43–44Return Record Addendum Count2NMNumber of Return Addendum A, B, C and D records (32/33/34/35) that follow.
45Return Documentation Type Indicator1ANCWhether an image and/or paper accompanies the return. Documentation Type Indicator codes
46–53Forward Bundle Date8NCBusiness date of the bundle in which the item was originally presented.
54–68ECE Institution Item Sequence Number15NBCSequence number from the original forward presentment.
69External Processing Code1NSCMICR position 44, used for special purposes authorized by X9.
70Return Notification Indicator1NMWhether the record is a return or a return notification.
71Return Archive Type Indicator1ANCHow the returned item is archived. Archive Type Indicator codes
72Number of Times Returned1NCHow many times the item has been returned. Added in X9.100-187-2008; Reserved in DSTU X9.37-2003.
73–80Reserved8BMReserved for future use; blank.
DSTU X9.37-2003: the fields that differ from X9.100-187 (2008 to 2016 editions)
PositionFieldLengthTypeUsageDescription
42Return Reason1ANMWhy the item is being returned. Return Reason codes Meanings as listed for DSTU X9.37-2003, where T is Stop Payment Suspect.
72–80Reserved9BMReserved for future use; blank.

32 Return Addendum A Record

BOFD endorsement on the returned item (same layout as type 26). 80 bytes. Defined in DSTU X9.37-2003, X9.100-187-2008/2013/2016.

The layout is that of type 26, Check Detail Addendum A Record, except for the fields below.

X9.100-187 (2008 to 2016 editions): the fields that differ from type 26
PositionFieldLengthTypeUsageDescription
3Return Addendum A Record Number1NMPosition of this record among the item’s Addendum A records, starting at 1.
76BOFD Correction Indicator1NCWhether and how the BOFD repaired the MICR line. Correction Indicator codes
DSTU X9.37-2003: the fields that differ from X9.100-187 (2008 to 2016 editions)
PositionFieldLengthTypeUsageDescription
4–12Bank of First Deposit (BOFD) Routing Number9NMRouting number of the bank of first deposit.

33 Return Addendum B Record

Payor bank details for the return: bank name, item sequence number, business date and payor account name. 80 bytes. Defined in DSTU X9.37-2003, X9.100-187-2008/2013/2016.

DSTU X9.37-2003 and X9.100-187 (2008 to 2016 editions), the same layout: 80 bytes
PositionFieldLengthTypeUsageDescription
1–2Record Type2NMAlways "33".
3–20Payor Bank Name18ANSCName of the bank the item was drawn on.
21–35Auxiliary On-Us15NBSMCMICR Auxiliary On-Us field of the returned item.
36–50Payor Bank Item Sequence Number15NBCSequence number assigned by the payor bank.
51–58Payor Bank Business Date8NCBusiness date of the payor bank (YYYYMMDD).
59–80Payor Account Name22ANSCName on the payor’s account.

34 Return Addendum C Record

Image archive reference for the returned item (same layout as type 27). Variable length. Defined in DSTU X9.37-2003, X9.100-187-2008/2013/2016.

The layout is that of type 27, Check Detail Addendum B Record; only the record type differs.

35 Return Addendum D Record

An endorsing bank on the returned item (same layout as type 28). 80 bytes. Defined in DSTU X9.37-2003, X9.100-187-2008/2013/2016.

The layout is that of type 28, Check Detail Addendum C Record, except for the fields below.

X9.100-187 (2008 to 2016 editions): the fields that differ from type 28
PositionFieldLengthTypeUsageDescription
3–4Return Addendum D Record Number2NMPosition of this record among the item’s endorsement addenda, starting at 01.
DSTU X9.37-2003: the fields that differ from X9.100-187 (2008 to 2016 editions)
PositionFieldLengthTypeUsageDescription
40Return Reason1ANCReturn reason, when the endorsement is on a returned item. Return Reason codes Meanings as listed for DSTU X9.37-2003, where T is Stop Payment Suspect.
60–80Reserved21BMReserved for future use; blank.

40 Account Totals Detail Record

Item count and amount for a key account or account range. 80 bytes. Defined in DSTU X9.37-2003.

DSTU X9.37-2003: 80 bytes
PositionFieldLengthTypeUsageDescription
1–2Record Type2NMAlways "40".
3–11Destination Routing Number9NMRouting number the totals are reported to.
12–29Key Account / Low Account in Key Account Range18ANSMKey account, or the first account of a key account range.
30–47Key Account / High Account in Key Account Range18ANSMKey account, or the last account of a key account range.
48–59Total Item Count12NMItems for the key account (range).
60–73Total Item Amount14NMAmount of the items for the key account (range), in cents.
74–77User Field4ANSCFor use at the discretion of the institution creating the record.
78–80Reserved3BMReserved for future use; blank.

41 Non-Hit Totals Detail Record

Item count and amount for items that matched no key account. 80 bytes. Defined in DSTU X9.37-2003.

DSTU X9.37-2003: 80 bytes
PositionFieldLengthTypeUsageDescription
1–2Record Type2NMAlways "41".
3–11Destination Routing Number9NMRouting number the totals are reported to.
12Non-Hit Indicator1ANMWhich non-hit totals the record reports.
13–24Total Item Count12NMItems that did not match a key account.
25–38Total Item Amount14NMAmount of the items that did not match a key account, in cents.
39–42User Field4ANSCFor use at the discretion of the institution creating the record.
43–80Reserved38BMReserved for future use; blank.

50 Image View Detail Record

Describes one image view of the item (front or back): format, compression, creator and digital-signature settings. Its Image View Data record follows. 80 bytes. Defined in DSTU X9.37-2003, X9.100-187-2008/2013/2016.

X9.100-187 (2008 to 2016 editions): 80 bytes
PositionFieldLengthTypeUsageDescription
1–2Record Type2NMAlways "50".
3Image Indicator1NMWhether an image view is present and whether it shows the actual check. Image Indicator codes
4–12Image Creator Routing Number9NMRouting number of the institution that created the image.
13–20Image Creator Date8NMDate the image was created (YYYYMMDD).
21–22Image View Format Indicator2NCImage file format; 00 (TIFF 6) needs no agreement, the others do. Image View Format Indicator codes
23–24Image View Compression Algorithm Identifier2NCCompression; 00 (CCITT Group 4) needs no agreement, the others do. Image View Compression Algorithm Identifier codes
25–31Image View Data Size7NCNumber of bytes in the image data of the following Image View Data record.
32View Side Indicator1NMFront or back of the item.
33–34View Descriptor2NMFull view (00) or one of the partial views (01-13: date, payee, amount, signature, MICR line, endorsements, ...).
35Digital Signature Indicator1NCWhether the Image View Data record carries a digital signature.
36–37Digital Signature Method2NCAlgorithm of the digital signature. Digital Signature Method codes
38–42Security Key Size5NCLength of the digital signature key in bits.
43–49Start of Protected Data7NCOffset of the first image byte covered by the digital signature.
50–56Length of Protected Data7NCNumber of image bytes covered by the digital signature.
57Image Recreate Indicator1NCWhether the sender can recreate the image view.
58–65User Field8ANSCFor use at the discretion of the institution creating the record.
66Image TIFF Variance Indicator1ANCWhether the TIFF image uses one of the variances allowed by X9.100-181. Added in X9.100-187-2008; Reserved in DSTU X9.37-2003.
67Override Indicator1ANCOverrides an image quality (IQA) test failure; letters identify the failed test. Added in X9.100-187-2008; Reserved in DSTU X9.37-2003.
68–80Reserved13BMReserved for future use; blank.
DSTU X9.37-2003: the fields that differ from X9.100-187 (2008 to 2016 editions)
PositionFieldLengthTypeUsageDescription
66–80Reserved15BMReserved for future use; blank.

52 Image View Data Record

Carries the image bytes of the preceding Image View Detail, with the image reference key and optional digital signature. Variable length. Defined in DSTU X9.37-2003, X9.100-187-2008/2013/2016.

Variable length: the image data starts at byte 118 + X + Y (1-based), where X and Y are the reference key and signature lengths.

DSTU X9.37-2003 and X9.100-187 (2008 to 2016 editions), the same layout: 117+X+Y+Z bytes
PositionFieldLengthTypeUsageDescription
1–2Record Type2NMAlways "52".
3–11ECE Institution Routing Number9NMRouting number of the institution that created the item record.
12–19Bundle Business Date8NMBusiness date of the bundle the image belongs to (YYYYMMDD).
20–21Cycle Number2ANCCycle number from the Bundle Header.
22–36ECE Institution Item Sequence Number15NBCSequence number of the item the image belongs to.
37–52Security Originator Name16ANSCOriginator of the digital signature.
53–68Security Authenticator Name16ANSCAuthenticator of the digital signature.
69–84Security Key Name16ANSCName of the key used for the digital signature.
85Clipping Origin1NBCCorner the clipping coordinates are measured from (0 = no clipping).
86–89Clipping Coordinate h14NCHorizontal start of the clipped area, in pixels.
90–93Clipping Coordinate h24NCHorizontal end of the clipped area, in pixels.
94–97Clipping Coordinate v14NCVertical start of the clipped area, in pixels.
98–101Clipping Coordinate v24NCVertical end of the clipped area, in pixels.
102–105Length of Image Reference Key4NBCNumber of bytes (X) in the Image Reference Key.
106–105+XImage Reference KeyXANSCKey the creator uses to locate the image. Its length, X, is the value of field 14 (Length of Image Reference Key).
106+X–110+XLength of Digital Signature5NBCNumber of bytes (Y) in the digital signature.
111+X–110+X+YDigital SignatureYBinaryCDigital signature over the protected image data (binary). Its length, Y, is the value of field 16 (Length of Digital Signature).
111+X+Y–117+X+YLength of Image Data7NBCNumber of bytes (Z) of image data.
118+X+Y–117+X+Y+ZImage DataZBinaryCThe image view (binary; TIFF Group 4 unless agreed otherwise). Its length, Z, is the value of field 18 (Length of Image Data).

54 Image View Analysis Record

Image quality and usability test results for the preceding image view. 80 bytes. Defined in DSTU X9.37-2003, X9.100-187-2008/2013/2016.

DSTU X9.37-2003 and X9.100-187 (2008 to 2016 editions), the same layout: 80 bytes
PositionFieldLengthTypeUsageDescription
1–2Record Type2NMAlways "54".
3Global Image Quality1NMWhether the image was tested for image quality conditions, and whether any were reported. Global Image Quality codes
4Global Image Usability1NMWhether the image was tested for image usability conditions, and whether any were reported. Global Image Usability codes
5Imaging Bank Specific Test1NMWhether the imaging bank ran tests of its own; their results are reported in the User Field. Imaging Bank Specific Test codes
6Partial Image1NCPart of the item is missing from the image. Image quality tests codes
7Excessive Image Skew1NCThe image is skewed beyond the agreed limit. Image quality tests codes
8Piggyback Image1NCAnother item overlaps the image. Image quality tests codes
9Too Light or Too Dark1NCThe image is too light or too dark. Image quality tests codes
10Streaks and/or Bands1NCThe image has streaks or bands. Image quality tests codes
11Below Minimum Image Size1NCThe image is smaller than the agreed minimum. Image quality tests codes
12Exceeds Maximum Image Size1NCThe image is larger than the agreed maximum. Image quality tests codes
13–25Reserved13BMReserved for future use; blank.
26Image-Enabled POD1NCWhether the image was used in an image-enabled proof of deposit (POD) application. Image-Enabled POD codes
27Source Document Bad1NCFor an unusable image, whether the source document is unusable too. Source Document Bad codes
28Date Usability1NCWhether the date on the image can be used. Image usability tests codes
29Payee Usability1NCWhether the payee name on the image can be used. Image usability tests codes
30Convenience Amount Usability1NCWhether the numeric (convenience) amount on the image can be used. Image usability tests codes
31Legal Amount Usability1NCWhether the written (legal) amount on the image can be used. Image usability tests codes
32Signature(s) Usability1NCWhether the signature on the image can be used. Image usability tests codes
33Payor Name and Address Usability1NCWhether the payor name and address on the image can be used. Image usability tests codes
34MICR Line Usability1NCWhether the MICR line on the image can be used. Image usability tests codes
35Memo Line Usability1NCWhether the memo line on the image can be used. Image usability tests codes
36Payor Bank Name and Address Usability1NCWhether the payor bank name and address on the image can be used. Image usability tests codes
37Payee Endorsement Usability1NCWhether the payee endorsement on the image can be used. Image usability tests codes
38BOFD Endorsement Usability1NCWhether the BOFD endorsement on the image can be used. Image usability tests codes
39Transit Endorsement Usability1NCWhether the transit endorsement on the image can be used. Image usability tests codes
40–45Reserved6BMReserved for future use; blank.
46–65User Field20ANSCFor use at the discretion of the institution creating the record.
66–80Reserved15BMReserved for future use; blank.

61 Credit Reconciliation Record

A credit for the deposit, within a cash letter or bundle. 80 bytes. Bank-defined (not in DSTU X9.37-2003; X9.100-180 defines one).

Type 61 is not a DSTU X9.37-2003 record, and its layout is set by the bank or clearing arrangement. Fields follow a common 80-byte credit layout; a record with a Record Usage Indicator of 5 at position 3, which moves every later field one byte to the right, is read with that layout instead. Check your exchange partner’s specification.

Bank-defined (common credit layout): 80 bytes
PositionFieldLengthTypeUsageDescription
1–2Record Type2NMAlways "61".
3–17Auxiliary On-Us15NBSMCMICR Auxiliary On-Us field of the credit.
18External Processing Code1NSCMICR position 44.
19–27Posting Bank Routing Number9NMRouting number of the bank that posts the credit.
28–47On-Us20NBSMOSCMICR On-Us field of the credit: the account to credit.
48–57Item Amount10NMAmount of the credit in cents.
58–72ECE Institution Item Sequence Number15NBCSequence number assigned by the institution that created the record.
73Documentation Type Indicator1ANCWhether an image and/or paper accompanies the credit. Documentation Type Indicator codes
74Type of Account Code1ANCKind of account being credited.
75Source of Work Code1ANCWhere the deposited work came from.
76Work Type1ANCKind of work the credit covers.
77Debit Credit Indicator1ANCWhether the record is a credit or a debit adjustment.
78–80Reserved3BMReserved for future use; blank.
Bank-defined (Record Usage Indicator at position 3): 80 bytes, the fields that differ from the layout above
PositionFieldLengthTypeUsageDescription
3Record Usage Indicator1ANMHow the record is used: 5 marks a credit/reconciliation record. Its presence means the record follows the layout with this indicator at position 3.
4–18Auxiliary On-Us15NBSMCMICR Auxiliary On-Us field of the credit.
19External Processing Code1NSCMICR position 44.
20–28Posting Bank Routing Number9NMRouting number of the bank that posts the credit.
29–48On-Us20NBSMOSMMICR On-Us field of the credit: the account to credit.
49–58Item Amount10NMAmount of the credit in cents.
59–73Item Sequence Number15NBMSequence number that identifies the credit in the cash letter.
74Documentation Type Indicator1ANCWhether an image and/or paper accompanies the credit. Documentation Type Indicator codes
75Type of Account Code1ANCKind of account being credited.
76–77Source of Work Code2ANCWhere the deposited work came from.

62 Credit Record

A credit for the deposit, with a 14-digit amount. 100 bytes. Defined in X9.100-187-2013/2016.

X9.100-187-2013/2016: 100 bytes
PositionFieldLengthTypeUsageDescription
1–2Record Type2NMAlways "62".
3–17Auxiliary On-Us15NBSMCMICR Auxiliary On-Us field of the credit.
18External Processing Code1NSCMICR position 44.
19–27Posting Bank Routing Number9NMRouting number of the bank that posts the credit.
28–47On-Us20NBSMOSCMICR On-Us field of the credit: the account to credit.
48–61Item Amount14NMAmount of the credit in cents.
62–76Credit Item Sequence Number15NBCSequence number of the credit.
77Documentation Type Indicator1ANCWhether an image and/or paper accompanies the credit. Documentation Type Indicator codes
78Type of Account Code1ANCKind of account being credited.
79–80Source of Work Code2NCWhere the deposited work came from (21-50 are user defined).
81–96User Field16ANSCFor use at the discretion of the institution creating the record.
97–100Reserved4BMReserved for future use; blank.

68 User Record

Data defined by the record owner: the general format, or format 001 for a payee endorsement. Variable length. Defined in X9.100-187-2013/2016 (2008 not verified).

X9.100-187-2013/2016 (2008 not verified): 45+X bytes
PositionFieldLengthTypeUsageDescription
1–2Record Type2NMAlways "68".
3Owner Identifier Indicator1ANMHow the record owner is identified (e.g. by routing number).
4–12Owner Identifier9ANSCIdentifier of the record owner.
13–32Owner Identifier Modifier20ANSCQualifies the owner identifier.
33–35User Record Format Type3ANMFormat of the user data (001 = payee endorsement).
36–38Format Type Version Level3NMVersion of the user record format.
39–45Length of User Data7NMNumber of bytes of user data that follow.
46–45+XUser DataXANSMData defined by the record owner. Its length, X, is the value of field 7 (Length of User Data).
Payee endorsement (format 001): 335 bytes, the fields that differ from the layout above
PositionFieldLengthTypeUsageDescription
46–95Name of Payee50ANSCName of the payee who endorsed the item.
96–103Endorsement Date8NBCDate of the endorsement (YYYYMMDD).
104–112Bank Routing Number9NCRouting number of the bank the item was deposited to.
113–132Bank Account Number20ANSCAccount the item was deposited to.
133–152Customer Identifier20ANSCIdentifier of the depositing customer.
153–202Customer Contact Information50ANSCContact information of the depositing customer.
203–210Store / Merchant / Processing Site Number8ANSCWhere the item was captured.
211–235Internal Control / Sequence Number25ANSCCapture site control or sequence number.
236–239Time4NCTime of the endorsement (hhmm).
240–269Operator Name / Initials30ANSCOperator who captured the item.
270–274Operator Number5ANSCNumber of the operator.
275–304Manager / Supervisor Name / Initials30ANSCApproving manager or supervisor.
305–309Manager / Supervisor Number5ANSCNumber of the manager or supervisor.
310–324Equipment Number15ANSCCapture device identifier.
325Endorsement Indicator1ANCKind of endorsement.
326–335User Field10ANSCFor use at the discretion of the institution creating the record.

70 Bundle Control Record

Closes a bundle with its item count, total amount, MICR-valid amount and image count. 80 bytes. Defined in DSTU X9.37-2003, X9.100-187-2008/2013/2016.

X9.100-187 (2008 to 2016 editions): 80 bytes
PositionFieldLengthTypeUsageDescription
1–2Record Type2NMAlways "70".
3–6Items Within Bundle Count4NMNumber of Check Detail (25) or Return (31) records in the bundle.
7–18Bundle Total Amount12NMSum of the item amounts in the bundle, in cents.
19–30MICR Valid Total Amount12NCSum of the amounts of checks in the bundle whose MICR Valid Indicator is 1, in cents.
31–35Images Within Bundle Count5NMNumber of Image View Detail (50) records in the bundle.
36–55User Field20ANSCFor use at the discretion of the institution creating the record.
56Credit Total Indicator1NCWhether credit records (61/62) are included in the totals. Added in X9.100-187-2008; Reserved in DSTU X9.37-2003.
57–80Reserved24BMReserved for future use; blank.
DSTU X9.37-2003: the fields that differ from X9.100-187 (2008 to 2016 editions)
PositionFieldLengthTypeUsageDescription
56–80Reserved25BMReserved for future use; blank.

75 Box Summary Record

Totals for a box of bundles: destination, bundle count and box total. 80 bytes. Defined in DSTU X9.37-2003, X9.100-187-2008/2013/2016.

DSTU X9.37-2003 and X9.100-187 (2008 to 2016 editions), the same layout: 80 bytes
PositionFieldLengthTypeUsageDescription
1–2Record Type2NMAlways "75".
3–11Destination Routing Number9NMRouting number the box is sent to.
12–14Box Sequence Number3NMOrder of the box.
15–18Box Bundle Count4NMNumber of bundles in the box.
19–26Box Number ID8ANMIdentifier of the box.
27–40Box Total Amount14NMSum of the item amounts in the box, in cents.
41–80Reserved40BMReserved for future use; blank.

85 Routing Number Summary Record

Item count and amount totals for one routing number within the cash letter. 80 bytes. Defined in DSTU X9.37-2003, X9.100-187-2008/2013/2016.

DSTU X9.37-2003 and X9.100-187 (2008 to 2016 editions), the same layout: 80 bytes
PositionFieldLengthTypeUsageDescription
1–2Record Type2NMAlways "85".
3–11Routing Number Within Cash Letter9NMRouting number the totals are for.
12–25Routing Number Total Amount14NMSum of the amounts of the items for this routing number, in cents.
26–31Routing Number Item Count6NMNumber of items for this routing number.
32–55User Field24ANSCFor use at the discretion of the institution creating the record.
56–80Reserved25BMReserved for future use; blank.

90 Cash Letter Control Record

Closes a cash letter with its bundle, item and image counts, total amount, ECE institution name and settlement date. 80 bytes. Defined in DSTU X9.37-2003, X9.100-187-2008/2013/2016.

X9.100-187 (2008 to 2016 editions): 80 bytes
PositionFieldLengthTypeUsageDescription
1–2Record Type2NMAlways "90".
3–8Bundle Count6NMNumber of bundles in the cash letter.
9–16Items Within Cash Letter Count8NMNumber of Check Detail (25) or Return (31) records in the cash letter.
17–30Cash Letter Total Amount14NMSum of the item amounts in the cash letter, in cents.
31–39Images Within Cash Letter Count9NMNumber of Image View Detail (50) records in the cash letter.
40–57ECE Institution Name18ANSCName of the institution that created the cash letter.
58–65Settlement Date8NCDate the cash letter settles (YYYYMMDD).
66Credit Total Indicator1NCWhether credit records (61/62) are included in the totals. Added in X9.100-187-2008; Reserved in DSTU X9.37-2003.
67–80Reserved14BMReserved for future use; blank.
DSTU X9.37-2003: the fields that differ from X9.100-187 (2008 to 2016 editions)
PositionFieldLengthTypeUsageDescription
66–80Reserved15BMReserved for future use; blank.

99 File Control Record

Closes the file with its cash letter, record and item counts and the file total amount. 80 bytes. Defined in DSTU X9.37-2003, X9.100-187-2008/2013/2016.

X9.100-187 (2008 to 2016 editions): 80 bytes
PositionFieldLengthTypeUsageDescription
1–2Record Type2NMAlways "99".
3–8Cash Letter Count6NMNumber of cash letters in the file.
9–16Total Record Count8NMNumber of records of every type in the file, including the File Header and File Control.
17–24Total Item Count8NMNumber of Check Detail (25) and Return (31) records in the file.
25–40File Total Amount16NMSum of the item amounts in the file, in cents.
41–54Immediate Origin Contact Name14ANSCContact at the institution that sent the file.
55–64Immediate Origin Contact Phone Number10NCPhone number of the contact.
65Credit Total Indicator1NCWhether credit records (61/62) are included in the totals. Added in X9.100-187-2008; Reserved in DSTU X9.37-2003.
66–80Reserved15BMReserved for future use; blank.
DSTU X9.37-2003: the fields that differ from X9.100-187 (2008 to 2016 editions)
PositionFieldLengthTypeUsageDescription
65–80Reserved16BMReserved for future use; blank.

Code tables

The values of the main coded fields, as the X9 Viewer decodes them. These tables were checked against the Federal Reserve’s DSTU X9.37-2003 documentation and other public sources; coded fields without a table here take values your exchange partner’s specification lists.

Standard Level

Used in 01 field 2.

CodeMeaning
03DSTU X9.37-2003
30X9.100-187-2008
35X9.100-187-2013 or later

Collection Type Indicator

Used in 10 field 2, 20 field 2.

CodeMeaning
00Preliminary forward information
01Forward presentment
02Forward presentment, same-day settlement
03Return
04Return notification
05Preliminary return notification
06Final return notification
20No detail
99Bundles not the same collection type

Cash Letter Record Type Indicator

Used in 10 field 8.

CodeMeaning
NNo electronic check records or image records
EElectronic check records, no image records
IElectronic check records and image records
FImage records for a previously sent electronic (E) cash letter

Documentation Type Indicator

Used in 10 field 9, 25 field 9, 31 field 8, 61 field 8, 61 field 9, 62 field 8.

CodeMeaning
ANo image provided, paper provided separately
BNo image provided, paper provided separately, image upon request
CImage provided separately, no paper provided
DImage provided separately, no paper provided, image upon request
EImage and paper provided separately
FImage and paper provided separately, image upon request
GImage included, no paper provided
HImage included, no paper provided, image upon request
IImage included, paper provided separately
JImage included, paper provided separately, image upon request
KNo image provided, no paper provided
LNo image provided, no paper provided, image upon request
MNo image provided, electronic check provided separately
ZNot the same type (see each item)

MICR Valid Indicator

Used in 25 field 11.

CodeMeaning
1Good read
2Good read, missing field
3Read error encountered
4Missing field and read error encountered

BOFD Indicator

Used in 25 field 12.

CodeMeaning
YECE institution is the BOFD
NECE institution is not the BOFD
UUnknown

Correction Indicator

Used in 25 field 14, 26 field 11, 28 field 8, 32 field 11, 35 field 8.

CodeMeaning
0No repair
1Repaired (form of repair unknown)
2Repaired without operator intervention
3Repaired with operator intervention
4Undetermined whether repaired

The BOFD Correction Indicator of a Return Addendum A (32) may also be 5 (BOFD routing number repaired by the Federal Reserve).

Archive Type Indicator

Used in 25 field 15, 31 field 13.

CodeMeaning
AMicrofilm
BImage
CPaper
DMicrofilm and image
EMicrofilm and paper
FImage and paper
GMicrofilm, image and paper
HElectronic check instrument
INone

Conversion Indicator

Used in 26 field 10, 28 field 7, 32 field 10, 35 field 7.

CodeMeaning
0Did not convert physical document
1Original paper converted to IRD
2Original paper converted to image
3IRD converted to another IRD
4IRD converted to image of IRD
5Image converted to an IRD
6Image converted to another image (e.g. transcoded)
7Did not convert image (same as source)
8Undetermined

Return Reason

Used in 28 field 9, 31 field 6, 35 field 9.

Meanings as listed in X9.100-187-2008. From the 2016 edition on, return reasons are defined in ANSI X9.100-188 (current edition 2023), which separates customer and administrative reasons and may list other codes; check them against your exchange partner’s list. The current edition of X9.100-188 is a free download from ANSI (opens in a new tab).

CodeMeaning
ANSF: not sufficient funds
BUCF: uncollected funds hold
CStop payment
DClosed account
EUTLA: unable to locate account
FFrozen / blocked account
GStale dated
HPost dated
IEndorsement missing
JEndorsement irregular
KSignature(s) missing
LSignature(s) irregular, suspected forgery
MNon-cash item (non-negotiable)
NAltered / fictitious item, suspected counterfeit
OUnable to process (e.g. mutilated item)
PItem exceeds stated maximum value
QNot authorized
RBranch / account sold (wrong bank)
SRefer to maker
TItem cannot be re-presented
UUnusable image
VImage fails security check
WCannot determine amount
XRefer to image
YDuplicate presentment
ZForgery
1Warranty breach
2RCC warranty breach
3Forged and counterfeit warranty breach
4Retired / ineligible routing number

In DSTU X9.37-2003 files, T is “Stop payment suspect” rather than “Item cannot be re-presented”.

Image Indicator

Used in 50 field 2.

CodeMeaning
0Image view not present
1Image view present, actual check
2Image view present, not an actual check (e.g. IRD or carrier document)
3Image view present, cannot determine whether it is an actual check

Image View Format Indicator

Used in 50 field 5.

CodeMeaning
00TIFF 6
01IOCA FS 11
20PNG
21JFIF (JPEG)
22SPIFF
23JBIG data stream
24JPEG 2000

Image View Compression Algorithm Identifier

Used in 50 field 6.

CodeMeaning
00Group 4 facsimile (CCITT T.6)
01JPEG baseline
02ABIC
21PNG
22JBIG
23JPEG 2000

Digital Signature Method

Used in 50 field 11.

CodeMeaning
00DSA with SHA-1
01RSA with MD5
02RSA with MDC2
03RSA with SHA-1
04ECDSA with SHA-1

Global Image Quality

Used in 54 field 2.

CodeMeaning
0Not tested for image quality conditions
1Tested; one or more image quality conditions reported
2Tested; no image quality conditions reported

Global Image Usability

Used in 54 field 3.

CodeMeaning
0Not tested for image usability conditions
1Tested; one or more image usability conditions reported
2Tested; no image usability conditions reported

Imaging Bank Specific Test

Used in 54 field 4.

CodeMeaning
0No user-defined tests
1Other conditions tested; one or more reported in the User Field
2Other conditions tested; none reported in the User Field

Image quality tests

Used in 54 field 5, 54 field 6, 54 field 7, 54 field 8, 54 field 9, 54 field 10, 54 field 11.

CodeMeaning
0Condition not tested
1Condition present
2Condition not present

Image usability tests

Used in 54 field 27, 54 field 28, 54 field 29, 54 field 30, 54 field 31, 54 field 32, 54 field 33, 54 field 34, 54 field 35, 54 field 36, 54 field 37, 54 field 38.

CodeMeaning
0Not tested
1Unusable
2Usable

Image-Enabled POD

Used in 54 field 25.

CodeMeaning
0Unknown whether the image was used for image-enabled POD
1Image not used for image-enabled POD
2Image used for image-enabled POD

Source Document Bad

Used in 54 field 26.

CodeMeaning
0Not tested
1Image unusable; source document unusable
2Image unusable; source document may be usable

Validation checks

The 64 checks the X9 Viewer runs, with the code it shows for each: E for an error, W for a warning and I for information, then the check’s number. An error breaks a rule of the format, such as a total that does not match; a warning points to something a receiver may reject or that looks wrong, though the file still reads; info is worth knowing. Some checks are reported at more than one severity, depending on the field.

Framing

Whether the bytes split into records at all (codes 1 to 6).

  1. Empty file

    ErrorE001

    The file has no bytes.

  2. Not an X9 file

    ErrorE002

    The file does not start with an X9 File Header (type 01) in EBCDIC or ASCII, with or without length prefixes. The message says so when the file looks like a NACHA or BAI2 file, a PDF, an image or a ZIP archive.

    X9 files start with a File Header (type 01), optionally after a 4-byte length.

  3. File truncated

    ErrorE003

    The last record needs more bytes than the file has left: the file was cut short, often in transfer.

    The file was cut short in transfer; request it again.

  4. Unreadable bytes

    ErrorE004

    A length prefix or record type cannot be read. When a valid record turns up further on, reading resumes there; otherwise the rest of the file is not read.

    A length prefix or record type is corrupt.

  5. Bytes between records

    ErrorE005

    Bytes between two records do not form a record and were skipped, such as block descriptors or damaged data.

    Block descriptors or corruption between records.

  6. Padding after the last record

    InfoI006

    Filler follows the last record: zeros, blanks, line breaks or an end-of-file byte.

Record order and records

Whether every record sits where it belongs in the file, cash letter, bundle and item, and has the right length (codes 101 to 131).

  1. File Header not first

    ErrorE101

    The File Header (01) is not the first record.

  2. Second File Header

    ErrorE102

    A second File Header (01) appears in the file.

    Two files may have been concatenated.

  3. No File Header

    ErrorE103

    The file has no File Header (01).

  4. No File Control

    ErrorE104

    The file has no File Control (99).

    The file may be truncated.

  5. Second File Control

    ErrorE105

    A second File Control (99) appears in the file.

  6. Records after File Control

    ErrorE106

    Records follow the File Control (99).

    Two files may have been concatenated.

  7. Cash letter not closed

    ErrorE107

    A cash letter has no Cash Letter Control (90) before the next Cash Letter Header, the File Control or the end of the file.

    Each Cash Letter Header (10) needs a Cash Letter Control (90).

  8. Bundle not closed

    ErrorE108

    A bundle has no Bundle Control (70) before the next bundle, the cash letter’s control or the end of the file.

    Each Bundle Header (20) needs a Bundle Control (70).

  9. Bundle outside a cash letter

    ErrorE109

    A Bundle Header (20) is not inside a cash letter.

  10. Item outside a bundle

    ErrorE110

    A Check Detail (25) or Return (31) is not inside a bundle.

  11. Addendum without an item

    ErrorE111

    An addendum record has no check or return before it.

  12. Wrong addendum type

    ErrorE112

    An addendum of the wrong family: a check (25) takes addenda 26, 27 and 28; a return (31) takes 32, 33, 34 and 35.

    Checks take addenda 26/27/28; returns take 32/33/34/35.

  13. Addendum after image records

    WarningW113

    An addendum comes after the item’s image records. Addenda come first, then the image views.

  14. Image view without an item

    ErrorE114

    An Image View Detail (50) has no check, return or credit record before it.

  15. Image View Data missing

    ErrorE115

    An Image View Detail (50) is not followed by its Image View Data (52).

    Every Image View Detail (50) is followed by an Image View Data (52).

  16. Image View Data without detail

    ErrorE116

    An Image View Data (52) has no Image View Detail (50) of its own before it.

  17. Image View Analysis out of place

    WarningW117

    An Image View Analysis (54) does not follow an Image View Data (52), or a view already has one.

  18. Credit outside a cash letter

    ErrorE118

    A credit record (61 or 62) is not inside a cash letter.

  19. Bundle Control without header

    ErrorE119

    A Bundle Control (70) has no open bundle to close.

  20. Cash Letter Control without header

    ErrorE120

    A Cash Letter Control (90) has no open cash letter to close.

  21. Summary record outside a cash letter

    ErrorE121

    A summary record (40, 41, 75 or 85) is not inside a cash letter.

  22. Summary record inside a bundle

    ErrorE122

    A summary record (40, 41, 75 or 85) sits inside a bundle; it belongs after the Bundle Control (70).

  23. Unknown record type

    WarningW130

    A record type that neither X9.100-187 nor DSTU X9.37-2003 defines. The record is kept as it is.

  24. Wrong record length

    ErrorWarningE131 / W131

    A record is not the length its type calls for: 80 bytes for most types, 100 for type 62, and what their own length fields say for 27, 34 and 68. It is a warning when the file has one record per line and the record is short, as when an export trims trailing blanks.

    Fixed records are 80 bytes (type 62: 100); variable records follow their length fields.

Totals and counts

The controls compared with what the file holds (codes 201 to 215). Credit records (61 and 62) count toward item counts and amounts when the Credit Total Indicator is 1, not when it is 0; with a blank indicator or in a DSTU file, either reading is accepted.

  1. Bundle item count

    ErrorE201

    The Items Within Bundle Count (70) is not the number of checks or returns in the bundle.

    Items Within Bundle Count (70) counts the 25/31 records of the bundle.

  2. Bundle total amount

    ErrorE202

    The Bundle Total Amount (70) is not the sum of the bundle’s item amounts.

    Bundle Total Amount (70) is the sum of the item amounts in the bundle.

  3. MICR valid total

    WarningW203

    The MICR Valid Total Amount (70) is not the sum of the amounts of the checks whose MICR Valid Indicator is 1.

    MICR Valid Total Amount (70) sums the checks whose MICR Valid Indicator is 1.

  4. Bundle image count

    ErrorE204

    The Images Within Bundle Count (70) is not the number of Image View Detail (50) records in the bundle.

    Images Within Bundle Count (70) counts the Image View Detail (50) records.

  5. Cash letter bundle count

    ErrorE205

    The Bundle Count (90) is not the number of bundles in the cash letter.

  6. Cash letter item count

    ErrorE206

    The Items Within Cash Letter Count (90) is not the number of checks or returns in the cash letter.

  7. Cash letter total amount

    ErrorE207

    The Cash Letter Total Amount (90) is not the sum of the item amounts in the cash letter.

  8. Cash letter image count

    ErrorE208

    The Images Within Cash Letter Count (90) is not the number of Image View Detail (50) records in the cash letter.

  9. File cash letter count

    ErrorE209

    The Cash Letter Count (99) is not the number of cash letters in the file.

  10. File record count

    ErrorE210

    The Total Record Count (99) is not the number of records in the file, File Header and File Control included.

    Total Record Count (99) includes the File Header and File Control.

  11. File item count

    ErrorE211

    The Total Item Count (99) is not the number of checks and returns in the file.

  12. File total amount

    ErrorE212

    The File Total Amount (99) is not the sum of the item amounts in the file.

  13. Addendum count

    ErrorE213

    The addendum count of a check (25) or return (31) is not the number of addendum records that follow it.

    The 25/31 record states how many addenda follow it.

  14. Addendum record numbers

    WarningW214

    The record numbers of an item’s addenda (26, 28, 32 or 35) do not run 1, 2, 3 in order within their type.

  15. Routing number summary

    WarningW215

    A Routing Number Summary (85) does not match the count or total amount of the cash letter’s items for that routing number.

Image records

The Image View Detail and Image View Data records and the image bytes (codes 301 to 310).

  1. Unreadable image length field

    ErrorE301

    A length field of an Image View Data (52) record is not a number, so its image cannot be located.

  2. Image data truncated

    ErrorE302

    The Length of Image Data in a 52 promises more bytes than the record holds.

    Length of Image Data says more bytes than the record holds.

  3. Extra bytes after image data

    WarningW303

    Bytes follow the image data inside a 52 record.

  4. Image size differs from Image View Detail

    WarningW304

    The Image View Data Size in a 50 differs from the Length of Image Data in its 52.

  5. Image Indicator says no image

    WarningW305

    A 50 says no image view is present (Image Indicator 0), yet its 52 carries image data.

  6. Image view without image data

    WarningW306

    A 50 says an image view is present, yet its 52 carries no image data.

  7. Image format differs from its indicator

    WarningW307

    The image bytes are in another format than the one the 50’s Image View Format Indicator names.

  8. Unrecognised image format

    WarningW308

    The image data is not TIFF, JPEG, PNG, GIF or JPEG 2000.

  9. Item without images

    WarningW309

    An item has no image views although its cash letter says it carries images (Cash Letter Record Type Indicator I or F).

    The cash letter says it carries images (Record Type Indicator I or F).

  10. Front or back image missing

    WarningW310

    An item has image views, but no front or no back.

Fields and other checks

Field values in every record, plus the notes on MICR reads, test files and long issue lists (codes 401 to 501, and 900).

  1. Mandatory field blank

    ErrorE401

    A mandatory field is blank. The viewer checks a set of the standard’s mandatory fields: routing numbers, dates, amounts, counts and the main indicators.

  2. Non-numeric value in a numeric field

    ErrorWarningE402 / W402

    An amount, count, length or phone number holds something other than digits: an error in a field the viewer requires, a warning in others.

  3. Invalid date

    ErrorWarningE403 / W403

    A date is not a real YYYYMMDD date: an error in a field the viewer requires, a warning in others.

    Dates are YYYYMMDD.

  4. Invalid time

    ErrorWarningE404 / W404

    A time is not a valid hhmm time on a 24-hour clock: an error in a field the viewer requires, a warning in others.

    Times are hhmm on a 24-hour clock.

  5. Invalid routing number

    ErrorWarningE405 / W405

    A routing number fails the ABA check digit or is not nine digits, an error in a required field (every payor bank routing number is one) and a warning elsewhere; or it holds unreadable MICR characters (*) or starts with a prefix outside the Federal Reserve’s ranges, a warning.

    ABA check digit: 3·d1 + 7·d2 + d3 + 3·d4 + 7·d5 + d6 + 3·d7 + 7·d8 + d9 is a multiple of 10.

  6. Value not in the code list

    WarningW406

    A coded field holds a value outside its list. Fields whose lists are open, such as return reasons from the 2008 edition on, are not checked this way.

  7. MICR read problem reported

    InfoI407

    A check’s MICR Valid Indicator reports a read problem: 2 (good read, missing field), 3 (read error) or 4 (both).

  8. Test file

    InfoI501

    The File Header marks the file as a test file (Test File Indicator T).

  9. More issues not listed

    InfoI900

    A rule found more than 1,000 issues of one severity. The first 1,000 are listed and the rest counted.

Sources

The layouts follow ANSI X9.100-187 (positions as the 2016 edition prints them) and the Federal Reserve’s documentation of DSTU X9.37-2003, and were checked against bank image cash letter specifications. ASC X9 publishes the standards through ANSI; the descriptions on this page are our own. Exchange partners agree on the details in their own specifications, so check the one that applies to your files.

NACHA Navigator is independent and not affiliated with ASC X9, ANSI or the Federal Reserve. This page is for information only and is not legal or compliance advice.