Bank statement import and reconciliation guide

Import a statement, then review what each transaction explains.

In Diwanio Essential or Growth, a supported statement file can be imported into bank transaction records after column mapping and review. Reconciliation is a separate decision: compare the source invoice or expense, confirm valid matches, and leave unexplained activity open.

This three-row CSV example shows a customer payment, a business cost, and a debit that still needs an explanation. Successful file import does not mean every transaction has been reconciled.

Compare Essential and current plan limits

Statement imports start with Essential. Free includes manual records for one bank account and up to 100 bank transactions per month. A live bank feed is separate and depends on a supported provider and workspace configuration.

Product scope checked on 15 October 2026

Three rows, two possible matches, one open question

Follow the statement record through review.

Assume a fictional Demo AED account already exists in the workspace, along with issued invoice DEMO-INV-001 for AED 1,050 and one expense record totalling AED 210. All records use AED.

Illustrative CSV and records only. Names, references, amounts, and dates are fictional. This table is an explanation, not a live product capture or proof of a bank connection.

01
Map and check the import
Choose the bank-transaction data type and a supported import source. Map the CSV columns, confirm the Demo AED account already exists, and review dates, currency, amounts, and credit/debit direction before importing.
02
Review the possible matches
Compare the AED 1,050 credit and its invoice reference with the issued customer invoice. Compare the AED 210 debit with the source expense. Confirm a match only after the currency, amount, source, and business purpose make sense together.
03
Leave the unexplained debit open
The AED 35 debit has no supporting record in this example. Keep it available for follow-up and ask the person who knows the transaction. Import success is not a reason to force a match.

Imported activity with visible review decisions

The first two rows have records to investigate and potentially confirm. The third remains an open item until its source and purpose are known. Suggested links never replace the authorised user’s decision.

This example does not guarantee an automatic match, support for every bank export, or a live feed. Do not import an opening balance or a second copy of the same activity as a new transaction without reviewing the source and existing records.

Decide what each row needs

The amount alone is not enough evidence to confirm a relationship.
Date	Statement activity	Amount and direction	Review decision
2026-10-01	Demo client payment · DEMO-INV-001	AED 1,050 · credit	Compare with the issued invoice; confirm only after review.
2026-10-02	Demo service cost · DEMO-EXP-001	AED 210 · debit	Inspect the expense and payment context before confirming.
2026-10-03	Unidentified debit	AED 35 · debit	Keep open; obtain the missing source and explanation.

The three-row sample CSV

The field identifiers and account value are kept in English so the same sample can be mapped in either interface language. Amounts are positive here; the type column supplies credit or debit. Create or choose the matching demo account before using a test copy.

posted_at,description,amount,type,bank_account,currency,reference
2026-10-01,Demo client payment,1050.00,credit,Demo AED account,AED,DEMO-INV-001
2026-10-02,Demo service cost,210.00,debit,Demo AED account,AED,DEMO-EXP-001
2026-10-03,Unidentified debit,35.00,debit,Demo AED account,AED,

Map source columns to bank transaction fields

Check your actual statement format. These headings match this example; other bank exports may need different mappings.
CSV column	Destination field	Check before import
posted_at	Transaction date	Dates use YYYY-MM-DD; check the bank’s transaction/value-date meaning.
description	Description	Keep enough source wording to identify the activity.
amount + type	Amount and credit/debit direction	Positive amount with explicit credit or debit in this example.
bank_account	Existing bank account	Demo AED account must identify the intended workspace account.
currency	Currency	AED for every row; review differences before matching.
reference	Transaction reference	Preserve the source reference; it is supporting context, not proof on its own.

Import, match, and confirm are separate steps.

The importer accepts supported CSV, TXT, XLS, and XLSX files, subject to the selected source and mapping. Review rejected rows and existing records before rerunning an import. Authorised users confirm invoice or expense links; unresolved transactions stay visible. This guide does not turn statement files into invoices, determine tax treatment, initiate bank transfers, or promise universal bank compatibility.

Bank statement reconciliation questions

Use the source record and the review decision to explain each transaction.

Can I import a bank statement on Free?

Statement imports start with Essential. Free supports manual bank transaction records within its monthly allowance and one bank account, without retained document uploads.

Does importing a statement reconcile it automatically?

No. Import creates transaction records. Review proposed links to invoices or expenses, confirm justified matches, and leave unexplained or ambiguous activity open.

What if two invoices have the same amount?

Inspect the reference, currency, dates, customer context, and source records. An amount shared by two invoices is not a reason to choose one without evidence.

Does this require a live bank connection?

No. The worked example uses a file import. A connected feed is a separate workflow whose availability depends on supported providers and workspace configuration.

Is the sample CSV my bank’s official format?

No. It is a fictional teaching sample. Check your bank’s actual export, map its columns, and review the preview and row results before relying on an import.

Connect the statement to the rest of the month

Use the underlying sales and expense records before preparing the accountant review.