A camt.052 is the ISO 20022 intraday account report, the XML replacement for the SWIFT MT942 interim message. It shows money moving during the day, often with both booked and pending entries and interim balances instead of a final close. Upload the file and BankXLSX turns every entry into a clean row with dates, amount, debit or credit, status, description, and balances. Start free, no credit card.
Upload your bank statement
Drop file here or click to upload
PDF, JPG, PNG, BMP, HEIC, TIFF, MT940
Uploading...
A camt.052 file is the ISO 20022 XML intraday account report, the same message family as camt.053 but sent during the day rather than at close, so it carries the day so far and usually no final closing balance. Excel cannot read it as rows because every transaction is nested inside XML tags. To convert it, upload the file to BankXLSX and each Ntry entry becomes one row with booking date, value date, amount, debit or credit indicator, booked or pending status, description, and the interim balances pulled out of the Bal elements. If your bank only sends the report as a PDF, upload that instead and you get the same spreadsheet.
camt.052 was designed for a treasury system to parse in near real time, not for a person to read in a spreadsheet. Open it in Excel and you get raw XML or a schema dialog that flattens the report wrong. Here is what trips people up most.
Open a .xml report in Excel and it offers to build a schema from the source, then spreads one transaction across sheets or repeats parent rows for every child element.
camt.052 can carry both booked and pending entries, marked BOOK or PDNG in the Sts element, so a naive export lumps provisional lines in with settled ones and your totals overstate the position.
Because the day is still open, the balances are interim: ITBD interim booked and ITAV interim available rather than the CLBD closing balance a camt.053 statement carries.
Amounts are always positive numbers. Whether a line is money in or money out sits in a sibling CdtDbtInd tag reading CRDT or DBIT, so a raw export totals everything as a credit.
A report can be a full snapshot of the day so far or only the new entries since the last one, and stacking two snapshots without checking double counts every transaction.
The payment reference you want is inside RmtInf, split into structured (Strd) and unstructured (Ustrd) branches that most spreadsheet exports ignore.
Upload the report and the converter walks the XML for you, then writes every entry into a spreadsheet you can sort, filter, and use to build an intraday cash position immediately.
Each Ntry element lands as its own row with booking date, value date, amount, debit or credit, description, and reference in separate columns.
The Sts value is read so BOOK entries are marked booked and PDNG entries pending, letting you filter provisional lines out of a firm position.
The CdtDbtInd flag is read so DBIT lines become debits and CRDT lines become credits, and your Excel column totals actually foot.
Interim booked and interim available balances are lifted from the Bal blocks into clear fields so you can read the position at the moment the report was cut.
Download a real .xlsx workbook for analysis or a clean CSV mapped for SAP, Kyriba, NetSuite, or your treasury system.
256-bit encryption in transit and you can delete your uploaded files whenever you want.
No software to install and no credit card to start.
Banks deliver camt.052 as an .xml file. Rename the copy to .txt so the uploader accepts it, or upload the PDF report for the same account.
Tip: Renaming does not change the data.
Drag the file into the box above. The converter reads the Rpt block, every Ntry entry, its BOOK or PDNG status, and the Bal balances, and skips the group header.
Tip: One account per report is normal.
Save as XLSX or CSV, filter to booked entries, and total the debits and credits to read your intraday position.
Tip: Keep pending lines separate from firm ones.
camt.052 exists for one job: seeing cash move during the day instead of waiting for the end of day camt.053 statement. The people converting it are almost always positioning cash, funding accounts, or watching liquidity in near real time.
Build an intraday cash position from the report so funding and sweep decisions run on current activity, not yesterday's close.
Combine several camt.052 reports across the day and across banks into one running view of what has hit each account so far.
Inspect and map real camt.052 files during an SAP, Kyriba, or treasury workstation implementation before the intraday feed goes live.
Spot large incoming or outgoing entries early in the day rather than discovering them on the next morning's statement.
Review intraday reporting alongside the end of day statement to confirm nothing posted and reversed inside the day was missed.
Look at real BOOK and PDNG entries and interim balances while building an intraday parser or a positioning integration.
Last updated July 2026
A camt.052 file is the ISO 20022 Bank to Customer Account Report: an XML message a bank sends one or more times during the day to show account activity as it happens. Unlike the end of day camt.053 statement, it does not close the day out, so it usually carries interim balances rather than a final closing balance, and it can include both booked and pending entries. The root element inside the file is BkToCstmrAcctRpt, and each report sits in its own Rpt block. It is the ISO 20022 replacement for the SWIFT MT942 interim transaction report, and banks are migrating intraday feeds from MT942 to camt.052 through 2026 and beyond.
They share the same ISO 20022 XML structure, so the parsing is nearly identical, but they answer different questions. camt.053 tells you what a completed banking day looked like, final and balanced. camt.052 tells you what has happened so far today, provisional by design. That is why you reconcile against a camt.053 and position cash against a camt.052. The table below shows where they part company.
| camt.052 | camt.053 | |
|---|---|---|
| Purpose | Intraday account report during the day | End of day customer statement |
| Root element | BkToCstmrAcctRpt, report in Rpt | BkToCstmrStmt, statement in Stmt |
| Entry status | Booked (BOOK) and pending (PDNG) | Booked only |
| Balances | Interim booked (ITBD) and interim available (ITAV) | Opening (OPBD) and closing (CLBD) |
| Frequency | Several times per day, on interval or schedule | Once per day |
| SWIFT MT equivalent | MT942 | MT940 |
| Use it to | Position cash intraday | Reconcile a closed day |
Most of the structure matches camt.053. The elements that matter when you flatten the report to rows are the entry, its status, the credit or debit indicator, the two dates, and the balances. Here is what each carries.
| Element | Name | What it carries |
|---|---|---|
| Rpt | Report | One intraday report for one account, with its own ID and creation time. |
| Acct | Account | The account the report covers, usually IBAN or account number plus currency. |
| Bal | Balance | Interim balances tagged ITBD and ITAV rather than the closing balances of a statement. |
| Ntry | Entry | One transaction: amount, credit or debit, status, booking and value dates. |
| Sts | Status | BOOK for a booked entry or PDNG for one still pending settlement. |
| CdtDbtInd | Credit or debit | CRDT for money in, DBIT for money out, since the amount itself is always positive. |
| RmtInf | Remittance information | The payment reference, split into structured and unstructured text. |
The single most misread part of a camt.052 is the entry status. Because the report is intraday, a bank can include entries that are still pending settlement, marked PDNG in the Sts element, alongside settled entries marked BOOK. If you sum every line you overstate your firm position, because a pending card authorization or an incoming payment awaiting release can still change or reverse. When you convert the file, keep the status column in view: filter to BOOK for a position you can act on, and treat PDNG lines as a heads up rather than a settled balance. This is also why the interim balance in a camt.052 will rarely tie to the closing balance on that day's camt.053.
Banks configure camt.052 in two ways. A snapshot report lists every entry posted so far that day, so each new report supersedes the last. A delta report lists only the entries since the previous report, so you have to stack them to see the whole day. Reading the report ID and creation time in the Rpt header tells you which one you have. Stacking two snapshots double counts every transaction, and treating a delta as a snapshot leaves entries out, so this is worth checking before you total anything. Once the entries are rows in a spreadsheet, sorting by creation time and de duplicating on the entry reference makes either style safe to combine.
In SWIFT's own mapping, camt.052 corresponds to the MT942 interim transaction report, just as camt.053 corresponds to the MT940 statement. SWIFT ended MT and ISO 20022 coexistence for cross border payment messages in November 2025, but that deadline covered MT103 and MT202, not the reporting messages, so many banks still send MT942 in 2026 while they migrate clients to camt.052. The practical reason to move is the same as for statements: camt.052 gives the counterparty, the remittance information, and the credit or debit direction their own named XML elements, while MT942 compresses them into the free text of tag 86. Until your banks switch, expect to handle both, and the MT942 to Excel converter covers the SWIFT side of the same intraday relationship.
Once the intraday entries are rows, the rest is ordinary spreadsheet work: filter to booked lines, sum the debits and credits, and stack several reports to build a running intraday position. For the end of day side of the same account, the camt.053 to Excel converter handles the ISO 20022 statement, and the MT940 to Excel converter handles the SWIFT statement it replaces. For other bank file types, the BAI to Excel converter handles North American balance reporting and the NACHA file to Excel converter handles ACH payment files. Not sure which one you were sent? The bank file format converter compares them side by side. Loading the data onward, the SAP and NetSuite converter pages map the rows for import. If all you were given is the PDF report, the main bank statement converter produces the same rows.
Converting is rarely the last step. Teams that need reporting on top of the converted data can build it with an AI financial statement generator, and finance teams that also code card spend and receipts alongside the bank data tend to pair intraday reporting with automated expense capture so nothing is keyed twice. For a walkthrough of the SWIFT interim report specifically, see our guide on how to convert an MT942 file to CSV or Excel.
A camt.052 is the ISO 20022 Bank to Customer Account Report, an XML message a bank sends during the day to show account activity as it happens. It carries booked and often pending entries with interim balances rather than a final closing balance, and it is the modern replacement for the SWIFT MT942 interim report. It is built for software, so it needs converting before Excel can use it.
Rename the .xml file to .txt, upload it to BankXLSX, and download the result as XLSX or CSV. The converter reads each Ntry entry into a row, resolves the CdtDbtInd sign, marks each line booked or pending from the Sts element, and lifts the interim balances out of the Bal blocks so your columns total correctly in a US Excel install.
camt.052 is the intraday account report sent during the day, and camt.053 is the end of day statement. camt.052 can include booked and pending entries with interim balances, while camt.053 carries booked entries only with a final closing balance. Use camt.053 to reconcile a closed day and camt.052 for intraday cash positioning.
camt.052 is the ISO 20022 equivalent of the SWIFT MT942 interim transaction report, just as camt.053 is the equivalent of the MT940 statement. Banks are migrating intraday feeds from MT942 to camt.052 on their own timelines, and many still send MT942 in 2026.
BOOK marks a booked entry that has settled to the account, and PDNG marks an entry that is still pending settlement. Because a camt.052 is intraday, it can carry both, so filter to BOOK for a firm position you can act on and treat PDNG lines as provisional, since a pending authorization or release can still change.
By design. A camt.052 is a snapshot during an open day, so it reports interim balances tagged ITBD and ITAV rather than a final CLBD closing balance. You get the closing balance from that day's camt.053 statement, and use the camt.052 only to see money moving in near real time.
Yes, but check whether each report is a full snapshot of the day so far or only a delta of new entries since the last one. Stacking two snapshots double counts every transaction. Once the entries are rows, de duplicate on the entry reference and sort by creation time so either style combines cleanly.
Convert the end of day camt.053 statement.
Convert the SWIFT MT942 interim report.
Compare every bank file format side by side.
Convert BAI and BAI2 balance reporting files.
From the same family of tools
Get started converting bank statements to spreadsheets.
USD
per month
billed as
$288 yearly
Choose speed vs accuracy when extracting
| Base AI Faster | 2,500 pages |
| Pro AI Best accuracy | 500 pages |
Scale statement conversion across your team with automation.
USD
per month
billed as
$888 yearly
Choose speed vs accuracy when extracting
| Base AI Faster | 10,000 pages |
| Pro AI Best accuracy | 2,000 pages |
Enterprise-grade bank statement conversion and controls.
USD
per month
billed as
$ yearly
Choose speed vs accuracy when extracting
| Base AI Faster | pages |
| Pro AI Best accuracy | pages |
