What Is an Intraday Bank Statement? (MT942, camt.052, BAI2)

An intraday bank statement is an interim report of the transactions posted to an account so far during the current business day, delivered one or more times before the final end-of-day statement. Corporate treasury teams use it to see their cash position in near real time, so they can sweep balances, fund accounts, and cover exposures without waiting until tomorrow morning. The three formats you will meet are MT942 on the SWIFT network, camt.052 in ISO 20022, and the intraday variant of a BAI2 file.

Last updated July 2026.

Intraday versus end-of-day, in one line

An end-of-day statement is the official, complete record of a full business day, delivered once after the bank closes its books. An intraday statement is a snapshot taken while the day is still running, so it is provisional and can be delivered several times a day. You reconcile against the end-of-day file; you make same-day cash decisions off the intraday one.

MT942: the SWIFT intraday report

MT942 is the SWIFT Interim Transaction Report. Where an MT940 gives you the closed, end-of-day statement with opening and closing booked balances, an MT942 lists the transactions posted since the last report and carries a floor limit and a debit and credit summary rather than a final closing balance. Banks push it on a schedule (often hourly, or every time a batch posts) so a treasurer can watch money move during the day. If you need those interim lines in a spreadsheet for a same-day position or an ad hoc check, you can convert an MT942 file to CSV or Excel and work with the rows directly. For how it stacks up against the end-of-day message, see MT940 vs MT942.

camt.052: the ISO 20022 account report

camt.052 is the ISO 20022 BankToCustomerAccountReport, the modern XML equivalent of an MT942. It reports account activity intraday and can include booked and pending entries, which makes it richer than the fixed-tag MT format. As banks migrate cash management from SWIFT MT to ISO 20022, camt.052 is replacing MT942 for intraday reporting the same way camt.053 replaces MT940 for end-of-day statements. The data model is the same idea, just expressed in structured XML with more room for detail.

BAI2 intraday files

BAI2 is the bank-administration format common with US banks. A BAI2 file can be a previous-day file (the settled, end-of-day picture) or a current-day or intraday file that reports activity as it posts. The type codes inside the file tell your treasury or ERP system which balances and transactions are booked versus intraday. If you receive BAI2 and want it in a sheet, the process is the same as any bank file: pull the records into rows, keep the type codes, and reconcile. Start from how to get a BAI2 or MT940 file from your bank.

What treasurers actually do with intraday statements

Intraday reporting exists for one job: knowing where your cash is before the day ends. A corporate treasury team pulls intraday statements across its bank accounts to build a live cash position, then acts on it. That means sweeping idle balances into a concentration account, funding a payroll or accounts payable run only once the covering deposit has landed, drawing or repaying on a line of credit, and confirming that expected wires and ACH credits have actually posted. Because payment runs are timed against real balances, treasury teams that automate their accounts payable lean on intraday data to release batches at the right moment rather than guessing.

How intraday statements differ from an ACH or NACHA file

It is worth separating two things that both show up in treasury inboxes. An intraday statement reports what has posted to your account. A NACHA file is not a statement at all: it is the fixed-width batch file you send to originate ACH debits and credits, or receive to process returns. One is a report of account activity; the other is a payment instruction. If a NACHA file is what you are staring at, the workflow is different, and you can open a NACHA file in Excel or convert it to CSV to read it. Keeping the two straight avoids reconciling a payment instruction against a balance report, which never ties out.

Getting intraday data into a spreadsheet

Whatever the format, the practical need is usually the same: get the transactions out of a machine-readable bank file and into columns you can total, filter, and reconcile. MT942, camt.052, and BAI2 are all structured text, so a converter turns them into date, description, amount, and balance rows the same way it handles a statement PDF. Once the data is in Excel or CSV you can build a same-day position, check off expected receipts, and feed the numbers into whatever cash worksheet your treasury runs. The general bank statement converter handles these bank formats alongside PDFs, so one upload covers the file you happen to receive.

The bottom line

An intraday bank statement is your same-day view of cash, delivered as an MT942, a camt.052, or a BAI2 current-day file depending on your bank and how far along it is in the ISO 20022 migration. Use it for real-time positioning and payment timing, reconcile against the end-of-day statement, and do not confuse it with a NACHA payment file. When you need the numbers in a sheet, convert the file to rows and work from there.