Transaction Reporting: The 60-Field Commercial Data Feed
CorporateConnect transaction reporting emits 60 canonical fields per row — from transaction code and currency to originator, beneficiary, approval chain, sanctions status, FX rate and BAI2 type code. Prior-day, current-day and scheduled delivery to SFTP, email or secure mailbox. Built to the data contract that the controller team, the FP&A team and the Federal Reserve examiners all accept on first read.
Every transaction, every status transition, every approver, every release timestamp — immutable, filterable, exportable. This is the reporting fabric that keeps the audit clean and the controller off your calendar.
Log In Book a Demo
Variance Analysis Essentials
- Fields: 60 canonical per row, plus custom metadata.
- Windows: Today, Yesterday, MTD, QTD, YTD, Last 30/90, custom up to 24 months.
- Feeds: prior-day BAI2, intraday ISO 20022 camt.052, real-time event stream.
- Delivery: email, SFTP, secure mailbox, manual download.
- Scheduling: daily, weekly, monthly, ad hoc.
- Audit: immutable row history with user, timestamp, IP, device.
What Lives in the Transaction Feed
Zero-click snippet: every transaction row carries 60 canonical fields covering money movement, routing, approval chain, regulatory status and audit metadata — enough to answer any controller or examiner question without leaving the platform.
Money Movement Fields
Zero-click snippet: money movement fields capture transaction code, amount, currency, debit/credit indicator, value date, settlement date, posted date and BAI2 type code.
The money movement block covers what moved and when. Transaction code maps to the internal identifier; BAI2 type code (e.g., 195 Incoming Wire, 455 ACH Credit) maps to the BAI2 specification for clean import into downstream ERP systems. Amount and currency settle in native denomination, with automatic USD translation using the 4:00pm ET spot rate.
Routing & Counterparty Fields
Zero-click snippet: routing fields include originator name, originator bank ABA or BIC, beneficiary name, beneficiary bank BIC, correspondent chain and ultimate beneficiary for wire traffic.
For wire transfers, the routing block is the controller’s favorite: originator ID, originator bank ABA or SWIFT BIC, beneficiary name, beneficiary bank, correspondent chain and (where provided) ultimate beneficiary. For ACH batches, routing captures SEC code (CCD, PPD, WEB, IAT), originator company ID, batch number and effective entry date.
Approval & Audit Fields
Zero-click snippet: audit fields include initiator, reviewer, approver, releaser, source IP, device fingerprint, timestamps and any status transition history.
This is where FFIEC-aligned controls live. Every row surfaces who initiated the transaction, who approved it, who released it, and the IP and device used at each step. Status history is immutable — a reversed transaction keeps the original rows plus a linked reversal row. External auditors love it; internal controllers sleep better for it.
Reporting Field Catalog Samples
Zero-click snippet: the catalog below lists 18 of the 60 canonical fields, grouped by block and annotated with BAI2 tag, ISO 20022 element and typical data type.
| Field | Block | Data Type | Example |
|---|---|---|---|
| transaction_id | Identity | string(36) | f7a8…b2 |
| bai2_type_code | Money Movement | integer | 195 |
| amount | Money Movement | decimal(18,2) | 125000.00 |
| currency | Money Movement | ISO 4217 | USD |
| debit_credit_ind | Money Movement | enum | CREDIT |
| value_date | Money Movement | date | 2026-04-13 |
| originator_name | Routing | string(70) | Meridian Imports |
| originator_aba | Routing | string(9) | 091000022 |
| beneficiary_name | Routing | string(70) | Ostsee GmbH |
| beneficiary_bic | Routing | string(11) | DEUTDEFFXXX |
| sec_code | ACH | enum | CCD |
| fx_rate | FX | decimal(12,6) | 1.087500 |
| sanctions_status | Compliance | enum | CLEAR |
| initiator_user_id | Audit | string(64) | sarah.m@mig |
| approver_user_id | Audit | string(64) | cfo@mig |
| source_ip | Audit | string(45) | 198.51.100.24 |
| status | Lifecycle | enum | POSTED |
| entity_id | Scope | string(16) | ENT-0004 |
Windows, Filters & Scheduled Delivery
Zero-click snippet: choose a window, stack filters, save as template, schedule delivery — the four-step pattern every CorporateConnect reporting workflow follows.
Reporting Windows
Zero-click snippet: supported windows include Today, Yesterday, MTD, QTD, YTD, Last 30 Days, Last 90 Days and a custom range up to 24 months.
Current-day intraday runs on a rolling clock. Prior-day BAI2 is the controller’s source of truth. Month-to-date and quarter-to-date feed the FP&A team’s variance analysis. For audit selections that reach further back, the 24-month warm window plus the archive extract endpoint cover up to 7 years of retained history aligned with OCC record-retention guidance.
Filters That Actually Help
Zero-click snippet: stack filters on any of the 60 fields — entity, account, transaction code, amount band, status, originator, beneficiary, approver, value date and sanctions status.
The most common saved filters we see: "all outbound wires > $100K posted yesterday by any approver except me," "all ACH returns in the last 30 days," "all transactions initiated by offboarded users (should be zero)," and "all cross-border wires where sanctions status is not CLEAR." Save each, schedule delivery, and close the laptop.
Scheduled Delivery
Zero-click snippet: schedules support daily, weekly, monthly and ad hoc runs with delivery to email (up to 5 recipients), SFTP endpoint, or secure mailbox.
Typical schedule set for a mid-market treasury: 6:00am daily BAI2 to the ERP SFTP, 9:00am wire summary email to CFO and controller, weekly ACH return summary to AP, monthly approver activity report to audit. Custom reports extends this with drag-and-drop layout.
Frequently Asked Questions
How many data fields does CorporateConnect transaction reporting expose?
Is prior-day or current-day data available?
Can reports be scheduled for automated delivery?
What reporting windows are supported?
Can transaction reports filter by user or approver?
Related Reporting & Tools
Zero-click snippet: the 60-field transaction feed powers account summary, custom reports, data export and user audit workflows.
Account Summary
Consolidated balance dashboard with real-time and prior-day positions across every entity and account.
Custom Reports
Drag-and-drop builder with saved layouts, pivot and filter, scheduled BAI2 or ISO 20022 delivery.
Data Export
BAI2, CSV and ISO 20022 native export into QuickBooks, SAP S/4HANA, Oracle Fusion, NetSuite and Workday.
User Management
Role-based access with dollar limits, entity scoping and up to four-tier approval workflows.
See the 60-Field Feed on Your Own Data
Bring a CSV of a day’s activity and a CorporateConnect advisor will map it to the 60-field canonical model live on a demo call. Reviewed by Jonathan R. Hayes, VP Commercial Treasury Solutions, CTP.
Contact a Relationship Manager