How to Import an Intraday Bank Statement in SAP (MT942 and camt.052)

Last updated July 2026.

SAP imports an intraday bank statement in the SWIFT MT942 interim transaction report or the ISO 20022 camt.052 intraday account report, loaded through transaction FF_5 or the Import Bank Statement app. Unlike an end of day statement, an intraday file does not create accounting postings. SAP writes Cash Management memo records instead, because intraday activity can still be cancelled before the day closes. The process is straightforward once the format and the planning level are configured, and most of the trouble people hit is either a missing planning level or a file the parser will not accept.

Why intraday is different from the end of day statement

The electronic bank statement you post from is the end of day file: MT940 or camt.053, final and balanced, which SAP clears against open items and posts to the general ledger. An intraday file answers a different question, which is how much cash is on the account right now. MT942 and its ISO 20022 successor camt.052 carry the day so far, often with pending entries and interim balances instead of a closing balance. Because those entries are provisional, SAP deliberately does not post them. It feeds them into the cash position and the liquidity forecast as memo records so a treasury team can fund accounts and place sweeps on current information, then reconciles and posts from the end of day statement later.

The formats SAP accepts for intraday

Banks send intraday data in a handful of shapes, and SAP reads the common ones. Which one you get depends on your bank and your onboarding.

camt.052 is where most banks are heading. SAP added camt.052 intraday statement processing in newer S/4HANA releases, so if your bank has switched, confirm your release supports it before you plan the cutover.

Step by step: import an intraday statement in SAP

The mechanics mirror the end of day import, with the intraday flag and memo records being the differences.

1. Configure the format. In the electronic bank statement configuration, set up the transaction type and the external transaction codes for your bank, and assign the posting or memo rules. Intraday uses memo record rules rather than posting rules.
2. Maintain the planning level on the bank account. This is the step people miss. Without a planning level on the house bank account, SAP loads the file but generates no memo record, so nothing reaches the cash position.
3. Load the file. Run transaction FF_5 or the Import Bank Statement app, choose the format, and select the intraday variant so SAP treats the file as interim rather than an end of day statement.
4. Check the memo records. Open the cash position and the liquidity forecast to confirm the entries came through as payment advices. Review them in FEBAN or the reprocess app if any lines need attention.
5. Reconcile against the end of day file. When the MT940 or camt.053 arrives, the booked postings replace the provisional intraday view, so the day ties out.

Why is no memo record created for my intraday statement in SAP?

The planning level is almost always the answer. SAP only creates a memo record for an intraday statement when the bank account has a planning level maintained, so a missing or wrong planning level means the file imports with no error yet the cash position stays empty. Check the house bank account configuration, confirm the planning level is assigned, and reload. The second most common cause is a memo rule that is not mapped to the bank's external transaction code, so the line has nowhere to land.

How do I read an MT942 or camt.052 file that fails to import into SAP?

When SAP rejects a file, the error rarely tells you which line is bad. The fastest way to find it is to open the raw file as a spreadsheet and look. A MT942 to Excel converter turns the colon tags into dated rows with value date, amount, debit or credit, transaction code, and the 34F floor limit pulled out, and a camt.052 to Excel converter does the same for the ISO 20022 XML, flagging each entry booked or pending. Seeing the data as rows makes the problem obvious: an unexpected transaction code with no mapping, a format version SAP does not support, a stray character, or a pending entry that inflated the total. Fix the mapping or ask the bank to resend, and keep the spreadsheet as the record of what the file actually contained.

When you only get a PDF intraday report

Not every account is on the automated feed. A newly onboarded entity, an account at a bank outside the cash management setup, or a one-off request often comes back as a PDF intraday report rather than an MT942 or camt.052 file. You cannot load a PDF into SAP, so the practical path is to convert it to structured rows first. The main bank statement converter reads the PDF into the same dated columns, and the SAP bank statement converter page covers mapping the output for import. During an implementation this is also how consultants inspect real files before the live feed is switched on: convert a sample, map the fields, and validate the code assignments against actual data.

From spreadsheet back to the cash position

Once an intraday file is rows, the treasury work is quick: filter to booked entries, sum the debits and credits, and compare against the interim balance the file reported. For the SWIFT side of the same account, the MT940 to Excel converter handles the end of day statement, and for the ISO 20022 side the camt.053 to Excel converter handles the end of day file. If you are not sure which format your bank sent, the bank file format converter compares them side by side. For a deeper walkthrough of the interim report itself, see how to convert an MT942 file to CSV or Excel.