An MT942 is a SWIFT interim transaction report, not an end of day statement, so it carries the day's activity so far and no closing balance to tie against. It is the same colon tag text as an MT940 with a floor limit in tag 34F and debit and credit totals in tags 90D and 90C. Upload the file and BankXLSX reads the tag 61 lines into dated rows with amount, direction, reference, and description. Start free, no credit card.
Upload your bank statement
Drop file here or click to upload
PDF, JPG, PNG, BMP, HEIC, TIFF, MT940
Uploading...
MT942 shares every parsing headache of the MT940 statement, then adds a few of its own because it is an intraday report rather than a closed day.
Every line starts with a colon tag such as :20:, :61:, or :86: instead of sitting in a field, so Excel drops the whole file into one column with no structure.
An MT942 has no tag 60F or 62F. It reports the day so far, so you tie out against the totals in tags 90D and 90C rather than a closing balance.
Tag 34F sets a minimum reported amount, so anything under the floor is left out of the report entirely and your row count will not match the full ledger.
Banks send an MT942 more than once a day, each covering only the period since the last one, so a full picture means combining several files without double counting.
MT942 amounts use a comma as the decimal separator with no thousands separator, so 1250,00 lands in a US Excel install as text or the wrong number.
The counterparty, the payment reference, and the bank's description are all compressed into the free text of tag 86, which wraps across lines.
Upload the MT942 file and the converter reads the interim report structure for you, pairing each statement line with its description and lifting the floor limit and the entry totals into their own fields.
Each statement line lands as its own row with value date, entry date, amount, debit or credit, transaction type code, and references in separate columns.
The wrapped description lines are stitched back together and attached to the transaction they belong to, so nothing is orphaned.
The tag 34F floor limit and the tag 90D and 90C debit and credit counts and sums are lifted into clear fields so you can check the report ties out.
European style amounts like 1250,00 are converted to real numbers so your columns total correctly in a US Excel install.
Download a real .xlsx workbook for analysis or a clean CSV mapped for QuickBooks, NetSuite, SAP, 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 MT942 as plain text, often named .sta, .mt942, or .txt. If yours is not .txt, rename the copy so the uploader accepts it.
Tip: Renaming does not change the data.
Drag the file into the box above. The converter reads the tag 61 statement lines, their tag 86 descriptions, and the floor limit and totals around them.
Tip: MT940 end of day statements work too.
Save as XLSX or CSV, then total your debit and credit rows and check them against the counts and sums in tags 90D and 90C.
Tip: Matching totals prove nothing was dropped.
MT942 exists for one job: seeing cash move during the day instead of waiting for the end of day MT940. The people converting it are almost always positioning cash, funding accounts, or watching liquidity in near real time.
Build an intraday cash position from interim reports so funding and sweep decisions are made on current activity, not yesterday's close.
Combine several MT942 files across the day and across banks into one running view of what has hit each account so far.
Inspect and map real MT942 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 tag 34F, 90D, and 90C content while building an intraday parser or a positioning integration.
MT942 is the SWIFT Interim Transaction Report, a message a bank sends one or more times during the day to show account activity as it happens. Unlike the end of day MT940 statement, it does not close the day out: it has no opening or closing balance, and it usually reports only entries above a threshold called the floor limit. It is plain text built from the same numbered colon tags as MT940, so if you open a file and see lines beginning :20:, :34F:, :61:, and :90D:, you are looking at an MT942 rather than an MT940.
They share a tag structure, so the parsing is similar, but they answer different questions. MT940 tells you what a completed banking day looked like, final and balanced. MT942 tells you what has happened so far today, provisional and unbalanced by design. That is why you reconcile against an MT940 and position cash against an MT942. The table below shows where they part company.
| MT940 | MT942 | |
|---|---|---|
| Purpose | End of day customer statement | Interim transaction report during the day |
| Opening balance | Yes, tag 60F | None |
| Closing balance | Yes, tag 62F | None |
| Floor limit | Not used | Tag 34F, sets the minimum reported amount |
| Entry totals | Not carried | Tags 90D and 90C count and sum debits and credits |
| Date and time | Date only | Tag 13D carries date, time, and time zone of the report |
| Frequency | Once per day | Several times per day |
| ISO 20022 equivalent | camt.053 | camt.052 |
Most of the tags are the same ones MT940 uses. The four that make a file an interim report rather than a statement are 34F, 13D, 90D, and 90C. Here is what each tag carries.
| Tag | Name | What it carries |
|---|---|---|
| :20: | Transaction reference | The bank's reference for this report message. |
| :25: | Account identification | The account the report covers, often IBAN or account plus currency. |
| :28C: | Statement number | Statement and sequence number, used to order the reports across the day. |
| :34F: | Floor limit | The minimum amount reported. It can appear twice, once for debits and once for credits. |
| :13D: | Date and time indication | The date, time, and time zone at which the report was produced. |
| :61: | Statement line | One transaction: dates, debit or credit mark, amount, type code, references. |
| :86: | Information to account owner | Free text description for the transaction above, often wrapped over lines. |
| :90D: | Number and sum of debits | How many debit entries are in the report and their total amount. |
| :90C: | Number and sum of credits | How many credit entries are in the report and their total amount. |
Tag 61 works exactly as it does in an MT940, packing several pieces of data into a single line with no separators. Reading left to right: a six digit YYMMDD value date, an optional MMDD entry date, a debit or credit mark of C, D, RC, or RD, an optional funds code, the amount with a comma decimal, a four character transaction type code such as NTRF or NCHK, and then customer and bank references. The type code is the nearest thing to a category, and the first letter shows the source: N for a non-SWIFT transfer, S for a SWIFT transfer where the next three characters are the message number, and F for a first advice raised by the bank. Because MT942 only reports entries above the floor limit, some real transactions on the account will not appear in tag 61 at all, which is expected rather than a gap.
The floor limit in tag 34F is the single most misread part of an MT942. It tells the bank to report only entries at or above a set amount, so a report with a floor of 10,000 will list a 40,000 wire and skip a 250 card payment. Some banks send two 34F tags, one governing debits and one credits, so the debit and credit floors can differ. This is why an MT942 row count almost never equals the MT940 for the same day and why the tag 90D and 90C totals only cover the reported entries, not the full account. When you convert the file, keep the floor in view: it is the reason the interim numbers and the end of day statement will not match line for line.
In SWIFT's own mapping, MT942 corresponds to camt.052, the ISO 20022 XML intraday account report, just as MT940 maps to camt.053. SWIFT ended MT and ISO 20022 coexistence for cross border payment messages in November 2025, but that deadline covered MT103 and MT202, not the MT9xx reporting messages. MT942 is deprecated and no longer actively maintained, yet banks are still sending it in 2026 and there is no announced hard sunset for the reporting messages. Banks are migrating intraday feeds to camt.052 on their own timelines. The practical reason to move is the same as for statements: camt.052 gives the counterparty, remittance information, and 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, the camt.052 to Excel converter covers the ISO 20022 intraday report that replaces it, and the MT940 to Excel converter covers the end of day side of the same relationship.
Once the interim lines are rows, the rest is ordinary spreadsheet work: sort by amount to see the largest movements first, sum the debits and credits to check against tags 90D and 90C, and stack several reports to build a running intraday position. For a step by step walkthrough of the manual routes as well, see our guide on how to convert an MT942 bank statement file to CSV or Excel. For other bank file types, the BAI to Excel converter handles North American balance reporting, the camt.053 to Excel converter handles ISO 20022 XML statements, 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, map it through the OFX converter or the QuickBooks QBO format, or go straight to the SAP and NetSuite converter pages. If all you were given is the PDF statement, the main bank statement converter produces the same rows.
Converting is rarely the last step. If the destination is QuickBooks Online, a CSV to QBO converter turns the export into a file QuickBooks accepts. 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 this with automated expense capture so nothing is keyed twice.
An MT942 is the SWIFT Interim Transaction Report, a message a bank sends during the day to show account activity as it happens. It uses the same colon tags as an MT940 statement but carries no opening or closing balance, and it usually reports only entries above a floor limit. It is built for software, so it needs converting before Excel can use it.
Rename the file to .txt if it has an extension like .sta or .mt942, upload it to BankXLSX, and download the result as XLSX or CSV. The converter reads each tag 61 statement line into a row, attaches its tag 86 description, converts the comma decimals into real numbers, and lifts out the floor limit and the debit and credit totals.
MT940 is the end of day customer statement with a final closing balance, and MT942 is an interim transaction report sent during the day covering activity since the last report. MT942 has no opening or closing balance and reports only entries above the tag 34F floor limit. Use MT940 to reconcile a closed day and MT942 for intraday cash positioning.
Tag 34F is the floor limit, the minimum amount the bank reports in the interim message. Entries below the floor are left out, so a report with a floor of 10,000 lists large wires and skips small payments. Some banks send two 34F tags so the debit and credit floors can differ.
Tag 90D gives the number and total amount of debit entries in the report, and tag 90C gives the number and total amount of credit entries. They let you check a converted file ties out: sum the debit rows and the credit rows and compare against these two control totals.
By design. An MT942 is a snapshot of activity during the day, not a closed statement, so it has no tag 60F opening balance or tag 62F closing balance. You reconcile against the end of day MT940 instead, and use the MT942 only to see money moving in near real time.
camt.052, the ISO 20022 XML intraday account report, is the equivalent of MT942, 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.
MT942 follows the European convention of a comma as the decimal separator with no thousands separator, so 1250,00 means one thousand two hundred fifty. A US Excel install reads that as text or the wrong number, which is why amounts have to be converted rather than imported raw.
Convert the end of day MT940 statement.
Convert the ISO 20022 camt.052 intraday report.
Convert the ISO 20022 camt.053 statement.
Compare every bank file format side by side.
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 |
