Importing a bank statement
Importing turns a file your bank sent you into statements you can read and reconcile.
- Open the external account.
- Select Statements, then Import.
- Fill in Import Statement and select Import.
The sheet stays open after a successful import, so you can read what became of the file before you close it.
One file can report several accounts. Each reported account is handled on its own, so a problem with one does not stop the others.
What you give it
| Field | When you fill it in |
|---|---|
| Source | Always. CAMT.053 (XML), MT940 (SWIFT), CSV, PDF or Excel for a statement. CAMT.052, MT942 or CAMT.054 for a report during the day. |
| Statement File | Always. |
| Account Number Standard | Only for a bare account number. It says how to read the number: IBAN, South Africa, United Kingdom, United States or Generic. Leave it unselected and the file is believed. |
| Bank Identifier, currency, Opening Balance, Closing Balance | Only for CSV, PDF and Excel. |
A CSV, PDF or Excel file carries no account and no statement header of its own, so you give the bank, the currency and the two balances. The file is read through the format profile your organisation approved for that bank and format.
A CAMT.053 or MT940 file reports the account it covers, so you name no account. The account you are importing against is the one whose panel you are on.
What happens to each reported account
flowchart TD
A["One account<br/>reported in the file"] --> B{"Is the account<br/>registered here?"}
B -- "No" --> C["Held<br/>the number is shown"]
B -- "Yes" --> D{"Same period and<br/>statement number<br/>already imported?"}
D -- "No" --> E["New statement"]
D -- "Yes, same figures" --> F["Already imported"]
D -- "Yes, figures differ" --> G["Re-issued<br/>a correction from the bank"]
style A fill:#1e3a5f,color:#ffffff
style B fill:#1e40af,color:#ffffff
style C fill:#b45309,color:#ffffff
style D fill:#1e40af,color:#ffffff
style E fill:#059669,color:#ffffff
style F fill:#374151,color:#ffffff
style G fill:#be123c,color:#ffffff
What the result tells you
The result lists every account the file reported, with its number, how that number was read, and the period. Under each one is what became of it.
| What you see | What it means | What you do |
|---|---|---|
| New statement | The statement was recorded against the registered account. | Work it on reconciliation. |
| Already imported | The same account, period and statement number arrived before, with identical figures. | Nothing. The file was sent twice. |
| Re-issued over | Same account, period and statement number, but the figures differ. | Take it up with the bank. The statement you already hold is kept unchanged. |
| Held: no account is registered for this number | The file names an account nobody registered here. | Register the account, then import the file again. |
| Held: the file did not name this number’s scheme | The number is not an IBAN, and neither the file nor you said how to read it. | Select Account Number Standard and import again. |
| Held: the number’s bank could not be found | The branch or clearing code on the file belongs to no bank your organisation has registered. | Add the bank, then import the file again. |
Held means recorded, not lost. A file naming an account you do not hold is still kept, with the number it named, so you can see that it arrived.
A correction cannot be applied to a statement you already hold. That record of the period stands, and a re-issue is a conversation with the bank.
A statement with no number can import twice
If the bank stamps no statement number on the file, the same file imported twice becomes two statements. Nothing can tell a second delivery from a genuine new period.
Ask the bank to stamp statement numbers when you onboard it. The number read is the legal statement number on a CAMT.053 file, or the statement number on an MT940 file.
Worked example
A CAMT.053 file reports two accounts.
| Reported account | Period | Number | Figures |
|---|---|---|---|
South African account 0123456789, held by Acme Mining, in ZAR |
1 to 30 June 2026 | 41 | Opening 1,000.00, one credit of 250.00 on 10 June, closing 1,250.00 |
GB82WEST12345698765432, in GBP |
1 to 30 June 2026 | 7 | — |
The first account is registered, so the result reads New statement and it is ready to reconcile. The second is not registered, so the result reads Held and shows the number. One statement appears, and the account you do not hold is named rather than dropped.
When the whole file is refused
A defect in the file itself refuses the whole delivery. Nothing is imported.
| What you see | What went wrong |
|---|---|
| A statement was delivered without a page | A statement is reported in full or not at all. Ask the bank for the whole statement. |
| This source reports the account it covers; the import may not name one | An account was named for a format that carries its own. |
| This source reports no account; the import must name the external account it covers | The account was left blank for a CSV, PDF or Excel file. |
| A line is reported in another currency and names no exchange rate | A line in a currency other than the statement’s must carry the rate converting it. |
| The statement payload is not valid base64 | The upload was damaged. Try again. |
| A bank identifier is required, or currency and balances are required | A CSV, PDF or Excel import needs these to find its format profile and read its header. |
Everything else is per reported account, not per file.
Reports during the day
Some banks report an account during the day, before the end-of-day statement. Three formats carry those reports:
| Source | Standard | What it carries |
|---|---|---|
| CAMT.052 intraday report | ISO 20022 camt.052, register row camt.052 (BankToCustomerAccountReport) | The entries so far today and the interim balances |
| MT942 intraday report | SWIFT MT942, register row MT942 (Interim Transaction Report) | The same, in the SWIFT form |
| CAMT.054 notification | ISO 20022 camt.054, register row camt.054 (BankToCustomerDebitCreditNotification) | One debit or credit, as it happens |
A report is a provisional view of the day. It never moves money, and nothing is matched or parked from it. The end-of-day statement replaces it.
An account takes reports only once it is enrolled. See enrolling an account.
What the result tells you for a report
| What you see | What it means |
|---|---|
| Recorded for Tuesday 02 Jun 2026, replaced | The report restates the whole day, so it replaced the one held. |
| Recorded for Tuesday 02 Jun 2026, added | The report carries only new movements, so they were added to the day. |
| … 1 movement already counted | A movement arrived before, so it was counted once. |
| Posted as a statement | The account is posted from each report as it arrives. The report became a statement. |
| Held: this account is not enrolled for intraday reporting | Enrol the account, then import again. |
| Held: older than the report already held | A newer report for that day arrived first. Nothing to do. |
| Held: the date is already confirmed by a close statement | The day is closed. The statement stands. |
The day turns from provisional to confirmed
The Statements panel shows a banner while a day is reported but not closed. It reads Provisional — replaced when the close statement arrives, with the position and where that figure came from.
| Where the figure came from | When |
|---|---|
| Reported by the bank as its booked balance | The report carried a booked balance. |
| Reported by the bank as its available balance | The report carried only an available balance. |
| Derived from the last close and the days since | The report carried no balance. Only booked entries count. |
| The last posted statement’s closing balance | The day is confirmed, or the account is posted from each report. |
When the close statement arrives, the banner loses its amber colour. The day reads from the statement, including any fee the reports never carried.
Dates to chase lists a reported day that went wrong. A later close statement overtook it, another statement already confirmed it, or the bank’s balance disagreed with the posted one.
Worked example: a provisional day
Woodgrove Bank’s CAD account closes Monday 1 June 2026 at 100,000.00. On Tuesday the bank
reports a credit of 25,000.00 and a debit of 8,000.00, both booked (ISO 20022 entry status
BOOK), with no balance.
The banner reads Provisional. The position is CAD 117,000.00 at Tuesday, derived from the last close and the days since: 100,000.00 + 25,000.00 − 8,000.00.
An account posted from each report
Some banks send no end-of-day file. If the account is posted from each report as it arrives, every report becomes a statement and is matched at once. Its position is the last statement’s closing balance, never a reported interim one.
A busy account can post hundreds of statements a day. The panel then lists Statements by day: one row per day a statement posted, with its opening, closing, statement count and how many statements are fully matched. Select Show statements to see that day’s statements.
A row is the day the statement posted, not the day its lines were booked. A line the bank back-dates sits in the row of the day it arrived, with its own booking date.
Example. Woodgrove Bank’s account closes Monday at 100,000.00. On Tuesday the bank pushes three reports: +25,000.00 at 10:00, −8,000.00 booked on Monday at 12:00, and +3,000.00 at 14:00. The Tuesday row reads opening 100,000.00, closing 120,000.00, 3 statements, 2 matched. The 12:00 line sits in Tuesday’s row, though it was booked on Monday.
Enrolling an account for intraday reporting
You enrol your own bank account on its Details panel.
- Open the external account and select Details.
- Select Intraday feed.
- Choose the Connection the bank reports through.
- Choose what Each report carries: every movement so far today, or only the movements since the last report.
- Choose where the account is Posted from: the end-of-day statement file, or each intraday report as it arrives.
- If it is posted from each report and nothing has posted yet, give the Opening balance and the date it was struck.
- Select Save.
The change waits in the settings draft. It applies when a second person publishes it. Enrolment widens what a connection can reach, so it is always checked by a second pair of eyes.
If you move an account from each report back to the file, give a Cutover date. Lines booked from that date come from the file.
A client’s own account
A statement can cover a client’s own account at another bank, not only your own bank account.
A client’s money is the client’s, so its suspense belongs in the client’s books.
- Parking a line to suspense by hand is refused: “This is a client’s own account; its suspense is kept in the client’s books.” The statement still imports, shows and matches.
- The overnight parking sweep skips a client account and records how many it skipped, so one client account cannot stop the night’s sweep for every other account.
- Automatic parking cannot be switched on for a client account.
A client account can be switched out of matching. When you register a client’s own account, the dialog asks Reconcile this account. It is answered yes unless you clear it. Afterwards, Statement matching on the account’s Details panel reads Reconciled or Not reconciled, and the verb of the same name changes it.
Not reconciled means matching never runs on that account’s statements. They are imported and reported, nothing more.
Your own bank account is always reconciled, so it is never asked and cannot be switched off.
If an account registers but the matching answer does not save, the sheet says so and stays open. The account exists; set Statement matching on its Details panel.
What your organisation configures
- The bank register. A South African statement reaches its account through the branch or clearing code on the file, so the bank behind that code must be registered.
- A format profile per bank and format, for CSV, PDF and Excel files.
- Automatic parking, per bank account — see reconciling a bank account.
- Whether a client’s own account is reconciled — asked when you register it, and changeable afterwards.
- Which accounts report during the day, through which connection, what each report carries, and whether the account is posted from the file or from each report.
Three things are platform behaviour and not yours to set. A report never moves money. Matching runs automatically the moment a statement is imported. A hold is per reported account, except for the whole-file defects listed above.
Related: reconciling a bank account, reading an external account, matching money to accounts, tracing a receipt.
From the LedgerTM product guide, as shipped with the software and written with it. Copied from the platform repository on 2026-11-11.