ssdb_received_item_cdc
Pipelined Data Sets
>
Symitar
>
ssdb_received_item_cdc
| Column name | Description | Mode | Type | Length |
|---|---|---|---|---|
| institutionid | This field stores the JH Platform institution identifier | REQUIRED | STRING | |
| sourceeventtime | The timestamp of the change event from the source system (e.g., Debezium's ts_ms field). | NULLABLE | INTEGER | |
| sourceeventdate | The UTC date of the change event, derived from sourceeventtime. | NULLABLE | DATE | |
| operation | The type of operation that caused the change event (e.g., 'c' for create/insert, 'u' for update, 'd' for delete, 'r' for read). This corresponds to Debezium's 'op' field. | NULLABLE | STRING | |
| receiveditemkey | Internal use only; SSDB field | NULLABLE | INTEGER | |
| deleteid | This field stores a soft delete flag where 0=not deleted, 1=deleted | NULLABLE | INTEGER | |
| globalsequence | This field contains a unique number for each global sequence date; the system assigns this number automatically. You cannot change the value of this field | NULLABLE | INTEGER | |
| globalsequencedate | This field stores the date the record was created. You cannot change the value of this field. During manual file maintenance, if you change the status to (0) Received, the system sets this date to the current system date if it is currently blank | NULLABLE | DATE | |
| type | This field stores the type of Received Item: | NULLABLE | INTEGER | |
| status | NULLABLE | INTEGER | ||
| micr1 | This field stores the second 40 characters of the MICR line as read by the MICR reader. If the complete MICR line is up to 40 characters long, the system enters the complete MICR line in the MICR1 field and this field is blank. If the complete MICR line is more than 40 characters, the system enters the first 40 characters in MICR1, and the remaining characters in this field | NULLABLE | STRING | |
| micr2 | This field stores the second 40 characters of the MICR line as read by the MICR reader. If the complete MICR line is up to 40 characters long, the system enters the complete MICR line in the MICR1 field and this field is blank. If the complete MICR line is more than 40 characters, the system enters the first 40 characters in MICR1, and the remaining characters in this field | NULLABLE | STRING | |
| micrauxonus | This information is found on business checks. The numbers used in this field are always surrounded by the E13 B MICR font On Us Symbols. The field content is unspecified, but it generally contains the check's serial number, which occupies character positions 45 (or 46) through 65, when reading the MICR line from right to left. The MICR reader can parse the MICR number and store it here | NULLABLE | STRING | |
| micrepc | This is an optional one-digit field. Its use indicates a requirement for special processing. Use of the field requires permission from ANSI X9B. This character occupies character position 44 or 45, when reading the MICR line from right to left. The MICR reader can parse the MICR number and store it here | NULLABLE | STRING | |
| micrtransit | This field contains the routing and transit number of an item, as read by a MICR reader or entered by a user during teller transactions or in the Received Item Manager | NULLABLE | STRING | |
| micronus | This field can contain up to 18 total characters (or up to 19 characters if position 32 is used). The field structure is unspecified. This field contains the account number, and can contain the check serial number. When reading the MICR line from right to left, characters in this field are located in or between positions 14 and 31 and can extend to position 32, if that position is used. The MICR reader can parse the MICR number and store it here | NULLABLE | STRING | |
| micramount | This is a 12-digit field contains the dollar amount of the check. This field is always bounded by E13 B MICR format Amount Symbols. The system does not store these symbols in this field, which is why it contains only 10 characters. The structure of data in this field is completely specified by MICR standards. This field occupies character positions 1 through 12, when reading the MICR line from right to left. The MICR reader can parse the MICR number and store it here | NULLABLE | STRING | |
| itemacctnumber | This field stores the interpreted account number of this item from the MICR line, as read by a MICR reader or entered by a user during teller transactions or in the Received Item Manager | NULLABLE | STRING | |
| itemchecknumber | This field stores the check or serial number of this item from the MICR line, as read by a MICR reader or entered by a user during teller transactions or in the Received Item Manager | NULLABLE | STRING | |
| itemamount | This field stores the amount of this item, as read by a MICR reader or entered by a user during teller transactions or in the Received Item Manager. When you enter the item amount using teller transactions, the amount is not saved unless the MICR parameters have been properly set | NULLABLE | INTEGER | |
| onusacctnumber | You can optionally set up the MICR reader software to identify on-us items by the R&T number and clear those items immediately. If you do this, the system still stores the item in the Received Item database, but this field contains the on-us account number | NULLABLE | STRING | |
| onusidtype | This field identifies the type of on-us draft: | NULLABLE | INTEGER | |
| onusid | This field stores the on-us share or loan ID for the item. If the item is not an on-us item, this field is blank, and the system sets the On Us Draft ID Type field to (2) None | NULLABLE | STRING | |
| assocaccountnumber | This field stores the associated account number under which the item was received. If there is no associated account number, this field is blank | NULLABLE | STRING | |
| associdtype | This field determines whether the draft is drawn on a share or loan: | NULLABLE | INTEGER | |
| associd | This field stores the associated share or loan ID for this item. If there is no associated share or loan, this field is blank, and the system sets the Associated ID Type field to (2) None | NULLABLE | STRING | |
| usernumber | This field stores the user number of the person or batch program that created this item | NULLABLE | INTEGER | |
| branch | The system updates this field with the branch number associated with the console creating this item | NULLABLE | INTEGER | |
| consolenumber | The system updates this field with the console number (0-8999) associated with the creation of this item. If this item was created by a batch process not associated with a console number, the system stores 9999 in this field | NULLABLE | INTEGER | |
| sequencenumber | The system updates this field with the sequence number of the associated transaction. You cannot change the value of this field | NULLABLE | INTEGER | |
| transeqnumberall_1 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_2 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_3 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_4 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_5 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_6 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_7 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_8 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_9 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_10 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_11 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_12 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_13 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_14 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_15 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_16 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_17 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_18 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_19 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_20 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_21 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_22 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_23 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_24 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_25 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_26 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_27 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_28 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_29 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_30 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_31 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_32 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_33 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_34 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_35 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_36 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_37 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_38 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_39 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_40 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_41 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_42 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_43 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_44 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_45 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_46 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_47 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_48 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_49 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| transeqnumberall_50 | The system determines the transaction associated with each individual check and stores the sequence number for that transaction in the Tran Sequence Number field and the sequence number for all transactions associated with that check in up to 50 Tran Seq Number subfields. These fields each contain the sequence number of a transactions for this check | NULLABLE | INTEGER | |
| bonddenomination | This field stores the denomination of the bond, or $0.00 if your credit union does not use the Bond Redemption Table | NULLABLE | INTEGER | |
| bondinterest | This field stores the redeemed interest amount of the bond, or $0.00 if your credit union does not use the Bond Redemption Table | NULLABLE | INTEGER | |
| bondprincipal | This field stores the principal amount of the bond (also known as the purchase amount of the bond) | NULLABLE | INTEGER | |
| bondrecpssn | This field contains the recipient Social Security Number (SSN) or individual Taxpayer Identification Number (TIN) for bonds redeemed. The system does not currently use this field | NULLABLE | STRING | |
| bondrecpname | This field contains the recipient name for bonds redeemed. The system does not currently use this field | NULLABLE | STRING | |
| bondrecpstreet | This field contains the recipient street for bonds redeemed. The system does not currently use this field | NULLABLE | STRING | |
| bondrecpcity | This field contains the recipient city for bonds redeemed. The system does not currently use this field | NULLABLE | STRING | |
| bondrecpstate | This field contains the recipient state for bonds redeemed. The system does not currently use this field | NULLABLE | STRING | |
| bondrecpzipcode | This field contains the recipient ZIP Code for bonds redeemed. The system does not currently use this field | NULLABLE | STRING | |
| postdate | This field stores the current system date when the received check item was posted or the received bond item was redeemed. The corresponding value for the Status field is Received | NULLABLE | DATE | |
| posttime | This field stores the current system time when a received check item was posted or a received bond item was redeemed | NULLABLE | INTEGER | |
| rejectdate | This field stores the date this item was rejected. During manual file maintenance, if you change the Status to (1) Rejected, the system sets this date to the current system date if the field is blank | NULLABLE | DATE | |
| voiddate | This field stores the date this item was voided in the system. This date is not affected whether or not this item was voided in Interactive Teller Capture (ITC). During manual file maintenance, if you change the Status to (2) Voided, the system sets this date to the current system date if the field is blank | NULLABLE | DATE | |
| reportdate | This field stores the date the Status field of the received item for this record was set to (3) Reported or exported to a file, as set by a custom edit run. During manual file maintenance, if you change the Status field to (3) Reported, the system sets this date to the current system date if the field is blank | NULLABLE | DATE | |
| returndate_1 | This field stores the date the item was returned the first time. There are date subfields for items returned up to three times. During manual file maintenance, if you change the Status to (4) Return 1, the system sets this date to the current system date if the field is blank | NULLABLE | DATE | |
| returndate_2 | This field stores the date the item was returned the second time. There are date subfields for items returned up to three times. During manual file maintenance, if you change the Status to (6) Return 2, the system sets this date to the current system date if the field is blank | NULLABLE | DATE | |
| returndate_3 | This field stores the date the item was returned the third time. There are date subfields for items returned up to three times. During manual file maintenance, if you change the Status to (8) Return 3, the system sets this date to the current system date if the field is blank | NULLABLE | DATE | |
| resubmitdate_1 | This field stores the date the item was resubmitted the first time. There are date subfields for items resubmitted up to two times. During manual file maintenance, if you change the Status to (5) Resubmit 1, the system sets this date to the current system date if the field is blank | NULLABLE | DATE | |
| resubmitdate_2 | This field stores the date the item was resubmitted the second time. There are date subfields for items resubmitted up to two times. During manual file maintenance, if you change the Status to (7) Resubmit 2, the system sets this date to the current system date if the field is blank | NULLABLE | DATE | |
| collectiondate | This field stores the date the item was held for collection. During manual file maintenance, if you change the Status to (9) Held for Collection, the system sets this date to the current system date the field is blank | NULLABLE | DATE | |
| collecteddate | This field stores the date the item was verified as paid or collected. During manual file maintenance, if you change the Status to (10) Collected, the system sets this date to the current system date the field is blank | NULLABLE | DATE | |
| chargeoffdate | This field stores the date the item was charged off as not collectible. During manual file maintenance, if you change the Status to (11) Charged Off, the system sets this date to the current system date if the field is blank | NULLABLE | DATE | |
| returnreason_1 | This field stores the reason the item was returned the first time. There are reason code subfields for items returned up to three times, and each can contain one of the following values: | NULLABLE | INTEGER | |
| returnreason_2 | This field stores the reason the item was returned the second time. There are reason code subfields for items returned up to three times. See Return Reason 1 for a list of codes | NULLABLE | INTEGER | |
| returnreason_3 | This field stores the reason the item was returned the third time. There are reason code subfields for items returned up to three times. See Return Reason 1 for a list of codes | NULLABLE | INTEGER | |
| disposition_1 | This field stores the disposition of the item after the first return. There are disposition code subfields for items returned up to three times, and each can contain one of the following values: | NULLABLE | INTEGER | |
| disposition_2 | This field stores the disposition of the item after the second return. There are disposition code subfields for items returned up to three times. See Disposition 1 for a list of codes | NULLABLE | INTEGER | |
| disposition_3 | This field stores the disposition of the item after the third return. There are disposition code subfields for items returned up to three times. See Disposition 1 for a list of codes | NULLABLE | INTEGER | |
| recordchangedate | The system stores the system date in the Record Change Date field when you create, change, or save the Received Item record. There will be times when the system updates the Record Change Date field because the record was saved, even though there may not be any actual changes in the record | NULLABLE | DATE | |
| itemid | This field stores the item identification number passed to the system from Interactive Teller Capture (ITC) for each item scanned. When a teller scans an item using ITC, ITC stores the value as a Document Identification Number (DIN). This number is unique for each ITC installation | NULLABLE | STRING | |
| transetid | This field stores an identification number, passed to the system from the ImageCenter software, for each transaction set processed. A transaction set is defined as one pass through Interactive Teller Capture (ITC). This number is unique for each ITC installation | NULLABLE | STRING | |
| fraudvendor_1 | These three fields contain the names of up to three fraud vendors passed to the system from Interactive Teller Capture (ITC) | NULLABLE | STRING | |
| fraudvendor_2 | These three fields contain the names of up to three fraud vendors passed to the system from Interactive Teller Capture (ITC) | NULLABLE | STRING | |
| fraudvendor_3 | These three fields contain the names of up to three fraud vendors passed to the system from Interactive Teller Capture (ITC) | NULLABLE | STRING | |
| fraudseverity_1 | These three fields each contain a number representing the severity of a fraud notification passed to the system from Interactive Teller Capture (ITC) for each item scanned. Severity is generic to all fraud vendors. These are the options: | NULLABLE | INTEGER | |
| fraudseverity_2 | These three fields each contain a number representing the severity of a fraud notification passed to the system from Interactive Teller Capture (ITC) for each item scanned. Severity is generic to all fraud vendors. These are the options: | NULLABLE | INTEGER | |
| fraudseverity_3 | These three fields each contain a number representing the severity of a fraud notification passed to the system from Interactive Teller Capture (ITC) for each item scanned. Severity is generic to all fraud vendors. These are the options: | NULLABLE | INTEGER | |
| fraudcode_1 | These three fields each contain a fraud code provided by the fraud vendor for each item scanned. This code is passed to the system from Interactive Teller Capture (ITC). Contact your fraud vendor for details | NULLABLE | INTEGER | |
| fraudcode_2 | These three fields each contain a fraud code provided by the fraud vendor for each item scanned. This code is passed to the system from Interactive Teller Capture (ITC). Contact your fraud vendor for details | NULLABLE | INTEGER | |
| fraudcode_3 | These three fields each contain a fraud code provided by the fraud vendor for each item scanned. This code is passed to the system from Interactive Teller Capture (ITC). Contact your fraud vendor for details | NULLABLE | INTEGER | |
| frauddescription_1 | These three fields each contain a fraud description for each scanned item provided by the fraud vendor and passed to the system from Interactive Teller Capture (ITC) | NULLABLE | STRING | |
| frauddescription_2 | These three fields each contain a fraud description for each scanned item provided by the fraud vendor and passed to the system from Interactive Teller Capture (ITC) | NULLABLE | STRING | |
| frauddescription_3 | These three fields each contain a fraud description for each scanned item provided by the fraud vendor and passed to the system from Interactive Teller Capture (ITC) | NULLABLE | STRING | |
| inputsource | This field holds a code identifying how the received item was entered into the Received Item database | NULLABLE | INTEGER | |
| onus | This field contains a code indicating whether an on-us check is posted (either using the On-us transaction [ON] or the Draft Clearing [DC] transaction if the transaction was performed through Shared Branching | NULLABLE | INTEGER | |
| sbtransequencenumber | This field contains a transaction sequence number assigned by the issuing institution | NULLABLE | INTEGER | |
| sbflag | This field contains a code indicating whether a check is posted through Shared Branching | NULLABLE | INTEGER | |
| itcreported | This field contains a code indicating whether an item has been sent to Interactive Teller Capture (ITC) in the DrawerClose message | NULLABLE | INTEGER | |
| itcstatuscode | This field stores any errors regarding voided ITC-related transactions: | NULLABLE | INTEGER | |
| itcforeignitem | This field identifies whether the item is Canadian: | NULLABLE | INTEGER |
Have a Question?
- Have a how-to question? Seeing a weird error? Get help on our collaborative Discourse page.
- Register for the Developer Office Hours where we answer technical Q&A, in real time, from the audience.
Did this page help you?
Last updated Tue Sep 15 2026