TRUIST - IDX Parser

This is an incomplete parser.

A single flat text file with no headers and no delimiters. Each line represents one check payment. No separate invoice/remittance file accompanies it.

How to identify this file: A single flat text file with no headers and no delimiters. Each line represents one check payment. No separate invoice/remittance file accompanies it.

File structure: Format type: Fixed-width, positional — single file

1. Business Date:

   1. Located at positions 0–7

   2. Format: MMddyyyy

   3. Represents the transaction or processing date

2. Cheque Amount

   1. Located at positions 8–17

   2. Fixed length of 10 characters

   3. Last 2 digits represent cents

   4. Decimal point is inserted programmatically during parsing

3. Description / Free Text

   1. Located at position 18 onwards

   2. Contains unstructured text data

   3. Does not include structured invoice-level information

Keyed-in (remittance data)? No — check-level data only, no invoice line items

What is parsed: Check date, amount, description text

What is not parsed: Invoice numbers, invoice amounts, routing/account numbers, batch/lockbox numbers

If your file has invoice line items or multiple rows per check, this parser will not capture them. Use Truist XML instead.

TRUIST XML format

How to identify this file: A single XML file. The root element is <Extract>. It contains a nested hierarchy down to individual check and stub (remittance) data.

XML hierarchy

<Extract>

  └── <Customer>

        └── <Lockbox LockboxNumber="...">

              └── <SubLockbox SubLockboxNumber="...">

                    └── <Batch DepositDate="..." BatchID="...">

                          └── <Transaction TransactionID="...">

                                ├── <Checks>

                                │     └── <Check>

                                │           ├── CheckAmount

                                │           ├── RoutingTransit

                                │           ├── AccountNumber

                                │           ├── CheckNumber

                                │           └── CheckImagePath

                                └── <Stubs>

                                      └── <Stub>

                                            └── <StubDataEntry>

                                                  └── <StubDEField FieldID="..." FieldName="...">

                                                        [invoice number / amount value]

Format type: XML (JAXB-parsed) — single file

Keyed-in (remittance data)? Yes — stub fields are operator-keyed invoice data

Image files? Yes — CheckImagePath is referenced inside the XML

Business date format: yyyyMMdd

Batch number format: {DepositDate}-{BatchID}

What is parsed: Check amount, routing/transit, account number, check number, image path, invoice number (via configurable StubDEField FieldID mapping), invoice amount

What is not parsed: Documents section (<Documents>), transaction total amount header, batch-level totals, second or additional checks per transaction (only the first <Check> is used)

Invoice field mapping is configurable — the FieldID used to identify invoice number and amount must be pre-configured. If not configured, no invoice data will be extracted.