Bank reconciliation

Reconcile bank evidence against posted accounting journals

Keep statement data distinct from the ledger, then match each bank movement to the accounting record that explains it.

CSV/XLSX import Duplicate control Journal matching Reconciliation status

Make the bank statement and the books explain each other.

A ledger balance can differ from a statement because of missing entries, timing, fees or duplicate recording. Reconciliation is the control that surfaces those differences.

Triplem VIP keeps imported or manually entered bank statement rows separate from Accounting journals. That distinction matters: the statement is evidence from the bank, while the journal is the accounting record.

A bank row therefore does not silently become income or expense. Users review it and match it against a posted journal, preserving a visible reconciliation status.

EvidenceStatement rowsCSV/XLSX import or manual entry.
BooksPosted journalsThe formal accounting side of the comparison.
ControlMatch statusConnect statement evidence to the journal that explains it.

Import, review, match and report.

The workflow keeps bank evidence visible without bypassing the accounting ledger.

01Choose bank contextUse an Accounting cash or bank account where appropriate.
02Import or add rowsBring statement transactions from CSV/XLSX or enter them manually.
03Review duplicatesImported rows are checked for duplicate statement evidence.
04Match journalSelect the posted journal that explains the statement transaction.
05Review statusUse Bank Reconciliation Status to identify matched and unmatched rows.

Reconciliation should explain differences, not manufacture entries.

The current design deliberately separates statement data from journal posting.

No automatic journal from row

Adding a bank transaction does not by itself create income, expense or another accounting journal.

Duplicate detection

Imported statement rows include duplicate controls to reduce accidental re-import.

Explicit matching

A user deliberately connects a statement transaction to a posted journal.

Reviewable status

The reconciliation report shows date, description, reference, status, amount and matched journal.

Currency context

Statement rows retain their currency context while Accounting books also maintain a base currency.

Auditability

Reconciliation sits inside the Accounting workspace alongside the wider audit trail.

A bank charge that exists on the statement but not yet in the ledger.

The statement row tells you something happened; the journal explains it in the books.

Illustrative bank fee journal

AccountReasonDebitCredit
Bank FeesRecognize the cost25.000.00
Bank AccountReduce bank asset0.0025.00

After the journal is posted, the statement row can be matched to it.

Practical questions about bank reconciliation.

The answers below describe the current Triplem VIP Accounting workspace and its present boundaries.

What does bank reconciliation do?

It compares statement-side bank activity with posted Accounting journals so unmatched or unexplained items can be identified.

Can I import a bank statement?

The current Accounting workspace supports CSV and XLSX statement-row import as well as manual bank-row entry.

Does importing a bank row create accounting income or expense?

No. A statement row is reconciliation evidence and does not create a journal by itself.

How are statement rows matched?

The current interface lets users select a posted journal and match it to the statement transaction. Imported rows also include duplicate-detection controls.