Banking Image Data Services (BDS)

How to identify this file

1. Delivery consists of a bundle of multiple XML files

2. Entry point is a control file with root tag <control_file>

3. Uses Symcor IFT 2.0 schema

4. Namespace

5. Points to note:

   1. All files are interlinked via the control file

   2. File naming convention is critical for identifying file roles

   3. Processing should always begin with the control file to ensure completeness and correct mapping

File bundle structure

• Control File

  • Root tag: <control_file>

  • Contains <delivery_files> listing all associated files

  • Acts as the master index for the bundle

• Cheque Index Files (*.C0*.xml)

  • Identified by .C0 in file name

  • Contains cheque-level data

  • Typically one file per batch

• Invoice Index Files (*.I0*.xml)

  • Identified by .I0 in file name

  • Contains invoice-level details

• Supporting Document Files (*.S0*.xml)

  • Identified by .S0 in file name

  • Contains supporting or additional document references

Cheque XML fields – (WLBXCHQ Namespace)

1. ProcessingDate: Business date (yyyyMMdd)

2. LockboxNumber: Lockbox identifier

3. BatchNumber: Batch identifier

4. TransactionNumber: Transaction reference within batch

5. ItemSequenceNumber: Sequence of item within transaction

6. ChequeSerialNumber: Cheque number / serial

7. BankTransitNumber: Routing number

8. ChequeAccountNumber: Account number

9. ChequeAmount: Cheque amount

10. UTI: Unique Transaction Identifier (used to link invoices and supporting documents)

11. Images:

    1. Contains list of images

    2. Includes URI, MimeType, Description, and DocumentOrder

12. Note:

    1. UTI is the primary key for linking cheque, invoice, and supporting document records

    2. Image metadata enables retrieval and ordering of cheque images

Control file XML structure

<control_file>

  ├── version, banner, file_source

  ├── customer_information (customer_name, scheduled_date)

  ├── contact

  ├── file_pair_count

  └── delivery_files

        └── file_pair (repeated)

              ├── xml_index_file   ← e.g., "BATCH001.C0.xml"

              ├── xml_index_file_size / crc

              ├── data_file

              └── data_file_size / crc

Key considerations

Format type: Multi-file XML bundle with control file — delivered to S3

Keyed-in (remittance data)? Yes — invoice and supporting document indexes are keyed/structured data linked by UTI

Image files? Yes — URIs in the cheque XML; MimeType specified per image

What is parsed: Check data (amount, routing, account, serial, batch, date, images), invoice data (linked by UTI), supporting documents (linked by UTI)

What is not parsed: DocumentType, PaymentDueDate, AvailableSegment — parsed from XML but not used downstream