File-Based Information Reporting (Treasury File Reporting)
Automated, secure file transmission enables you to receive files from the bank directly to your back-office processing systems, enhancing efficiency and supporting your information management needs.
Fifth Third will continue to support your information reporting needs through secure BAI2, MT940/942 and XML Wire Confirmation file transmissions with minimal changes unless notified prior and/or notified below.
BAI2
Transmission standards
- Fifth Third and Comerica align to the same standard for BAI transmissions, ensuring consistency in core reporting structure.
Reporting files
- Intraday reporting files at Fifth Third will be consolidated resulting in fewer files and more concise and streamlined reporting.
- Multiple types of activity will be included on one file, rather than the separate files by activity type you receive today.
- All intraday files will have the TWTMICA extension (Example: PCBGO.ABCD_MNG.BAI110920042529.0001.TWTMICA)
- Incremental filename number will always be 0001 and no longer increment. (Example: PCBGO.ABCD_MNG.BAI110920042529.0001.TWTMICA)
- For FileAct delivery customers, the sending BIC code will change to FTBCUS3C
BAI codes
- Most major BAI codes will remain the same.
- Some BAI codes will be consolidated at Fifth Third to provide more efficient and simplified reporting. Many credit and debit transactions have been simplified into BAI codes 399 and 699.
- Account analysis fees will be reported as BAI code 698.
- Description fields are expanded at Fifth Third, resulting in some differences in how transaction details are presented.
- See Resources below for BAI code details.
File timing
Prior Day
- 6:00 a.m. ET
Intraday
- Wire: every 15 minutes from 7:00 a.m. to 7:00 p.m. ET
- Instant Payments: every hour
- ACH: 5:00 a.m., 6:00 a.m., 12:00 p.m., 3:00 p.m., 6:00 p.m., 8:00 p.m. and 10:30 p.m. ET
- Controlled Disbursement: 8:00 a.m. ,10:30 a.m. ET
- Lockbox 9:30 a.m. and 12:30 p.m. ET
SWIFT MT940/942 Reporting
Message content changes
- Basic Header, Sending Institution (01) - will change to FTBCUS30
- Account Identification (25) - account numbers in this field will always be a minimum of 11-digits long with left side leading zeroes added if needed.
- Statement Number (28C) – incremental number will reset to 1 on migration day 1
- Statement Number (28C) – when a statement requires multiple messages to complete, CMA uses a single number for all reports and Fifth Third will increment the statement number with a /n sequence number. See example below with 2 parts:
- Comerica – :28C:44 (statement number 44 for both parts)
- Fifth Third – :28C:44/1 (part 1)
- Fifth Third – :28C:44/2 (part 2)
- Tag 25 (Account Identification)
Message delivery options
| SWIFT–FIN | Supported |
| SWIFT–FileAct | No Longer Supported |
| SFTP | No Longer Supported |
MT940 changes
- Statement Line, Supplementary Details (61) – Transaction descriptions will change
- Information to Account Owner (86) – Transaction descriptions will change
- Floor Limit Indicator (34F) – Will always include a debit and credit 34F field even if zero
- Number and Sum of Entries, Debits (90D) – Will be added to message
- Number and Sum of Entries, Credits (90C) – Will be added to message
- MT942 will be transmitted a total of 6 times per business day during the following windows:
- 6:00 a.m. ET
- 9:00 a.m. ET
- 1:00 p.m. ET
- 3:30 p.m. ET
- 6:30 p.m. ET
- 8:00 p.m. ET
XML Wire Confirmations
Message content changes
- Files will no longer aggregate wires transactions throughout the day. Each data file will contain new wire data only.
- All customers will receive both debit and credit wire activity.
File name changes
- File names will now contain a HHMMSS timestamp. This is to ensure files have unique names and prevent previous files from being overwritten. Example: PCBGO.ABCD_MNG.yymmddHHMMSS.WIREADVICE
Message timing
- File availability service levels: 7:00 a.m. to 7:00 p.m. ET
- Review the updated BAI code specifications to understand any changes or consolidations that may impact your reporting.
- Identify any needs for updates within treasury workstations or internal systems where BAI codes are used.
- Review the expanded description fields so that you are aware of changes to how transaction details are presented.
- Review and update auto-posting and reconciliation logic, particularly where processes rely on unstructured data within expanded detail fields to ensure continued accuracy and efficiency.