Bank Statements is where the firm’s bank transactions come together – read in per accounting organization and matched to cases, participants, and bookings. This is the basis of payment reconciliation: you see which incoming payment belongs to which claim or invoice, and how much of it has already been booked.
Importing transactions
| Element | Function |
|---|---|
| Accounting organization | selects which accounting organization the transactions are shown for. |
| Import bank statements | reads in new bank transactions (file import or automatic bank reconciliation via Konfipay). |
| Batch processing | processes several selected transactions together. |
| Search & filter | as in other overviews, the list can be searched and, via Reset filters, shown in full again – handy for seeing only unbooked transactions from a given period, for example. |
The columns
| Column | Content |
|---|---|
| Date | booking date of the transaction. |
| Payee / payer | the counterparty of the booking. |
| Reference | text of the transfer – often referencing an invoice or case. |
| Source account / Account number/IBAN | the bank accounts involved. |
| Amount | transaction amount (positive = incoming, negative = outgoing). |
| Booked | how much of the transaction has already been matched to a booking – shows open remaining amounts. |
| Case / Participant | the match to case and person. |
Batch processing: booking bank statements
Imported transactions are initially just raw data – they’re only “booked” once a booking has been matched to them. That’s exactly what batch processing does: it opens a focused working view that you click through statement by statement via Back/Next – with a direct view of the associated case right next to it.
The booking dialog
Add booking opens the actual journal entry – debit and credit each with exactly one account (either a general ledger account or a debtor/personal account):
| Field | Meaning |
|---|---|
| Accounting organization | which accounting organization the booking is created for – selecting a different one lets you book the same transaction DATEV-compliant into a different organization. |
| Debit/credit account type | general ledger account (a general booking account, e.g. bank) or debtor account (a participant’s personal account). |
| Debit/credit general ledger or debtor account | the specific account – the picker suggests matching accounts from the accounting organization (e.g. cash-in-transit, clearing, or recourse accounts). |
| Reference type (debit/credit) | what the line item refers to: bank statement, claim, invoice, or free-form text. |
| Debtor booking with invoice reference | shows, for verification, which personal account and which general ledger account (e.g. fees including VAT) the payment hits. |
| Basic data | booking date, amount, and description of the journal entry. |
Creating transfers directly
If a bank statement – say, a payout or reimbursement – needs to become its own transfer, you don’t need to switch to the case first: Add transfer creates it directly from batch processing and automatically links it to the bank statement. For details on the transfer’s further approval workflow, see Transfers & authorization.