Module guide: Bank Import

Non-technical user guide: what the module does, how to use it and how it fits in with Dolibarr.

Bank formats imported5: CSV, OFX, QIF, CAMT.053, MT940
Documents matchedInvoices, deposits, credit notes, salaries, charges, expense reports, donations
Dolibarr paymentCreated only after human validation
CompatibilityDolibarr 18+ - PHP 8+

1. Module overview

Bank Import is a KSIDol module that brings your bank statements into Dolibarr and helps you reconcile each movement with the right accounting document. You import a file provided by your bank (or prepare an API connector profile), the module automatically suggests the customer and supplier invoices, deposits, credit notes, salaries, charges, expense reports or donations that best match each line, then, after your validation, it creates the native Dolibarr payment, settles the document and reconciles the bank entry on its statement. The goal: less manual data entry, faster reconciliation and up-to-date accounting, without ever letting the module act on its own.

  • It relies entirely on native Dolibarr objects: bank accounts, customer and supplier invoices, deposits, credit notes, salaries, social/fiscal charges, expense reports, donations and payment methods.
  • No modification of the Dolibarr core: the module adds its own pages and its own tables, under the Banks | Cash menu.
  • Control stays human: the Dolibarr payment is never created until you have validated the match.
  • Once a bank entry is settled or reconciled, it is locked and no longer suggested, which prevents double payments.
  • Fully processed entries can be archived: they leave the working lists while remaining viewable and restorable, without any payment or entry being modified.

2. Importing bank statements

The Bank import page lets you load a file provided by your bank and turn each operation into an entry ready to reconcile, on the Dolibarr bank account of your choice.

  • Support for 5 formats: CSV, OFX, QIF, CAMT.053 XML and MT940 (.sta files), with an automatic format detection option.
  • Tolerant reading of CSV exports: varied separators, Windows/ISO encodings, old dates and split debit/credit columns.
  • Choice of the destination Dolibarr bank account (a default account can be preselected in the setup).
  • Each imported file becomes an identified import batch, with a fingerprint, to keep track of what has been loaded.
  • Each imported line also appears as a native bank entry on the Dolibarr account: the module reuses an existing movement of the same amount at a close date when it finds one, otherwise it creates the entry — never a duplicate movement. Reconciliation will then attach the payment to that entry.
  • Anti-duplicate protection: the module refuses an operation that is already present (file fingerprint and business key of date + account + amount + label + counterparty).
  • Duplicates between two statement formats (the same statement imported in OFX then in CSV, for example) are also recognised and flagged — see the dedicated section.
  • Display of a diagnostic of the first lines in error, to fix a badly formed file.
  • Security checks: allowed file extensions and configurable maximum import size.

3. Dashboard and import tracking

The module's home page gives an overview of reconciliation activity and quick access to the latest imported operations.

  • Four clickable figure tiles: imported transactions, suggested matches, approved lines and executed payments.
  • A Recent imports panel listing recent batches: date, source, file name, bank account (clickable link to the account card), number of lines imported/read, duplicates and status.
  • A list sortable by column and direct shortcuts to the import, the matches and the import batches.

4. Smart matching of bank entries

The Bank matching page is the heart of the module: it compares each bank line with the open Dolibarr documents and suggests the best matches, without ever deciding for you.

  • Automatic generation of suggestions (candidates) for the entries to process.
  • Documents suggested: customer and supplier invoices, deposits, credit notes, salaries, social/fiscal charges, approved expense reports (on outgoing transactions) and validated unpaid donations (on incoming bank transactions).
  • A relevance score computed on several criteria: amount (exact, close, approximate, gap compatible with fees/rounding, partial payment), invoice reference, third-party name or code, direction of the movement and date proximity.
  • Each suggestion displays its reasons, backed by the evidence found (third-party word, spotted reference...).
  • A partial payment is only suggested when corroborated by a reference or a recognised third party, never on the amount alone.
  • Workflow tabs, each with its counter: To process, Approved to pay, Rejected, Completed, All, plus the Archived tab for entries that have been put away.
  • Detection of the payment type (cheque, card, bank transfer, direct debit, domiciled bill, cash) to prefill the payment method.
  • Guided reconciliation in a dedicated window: validation of a suggested match, manual assignment of a document, or partial receipt with an amount to allocate.
  • Manual assignment across all open documents: the list covers every document awaiting reconciliation and filters as you type the company name, document number or amount — the three common ways of writing the amount are understood (1123,45 · 1123.45 · 1 123,45).
  • When a document is selected, the amount to allocate is automatically filled with its remaining balance, capped at the bank entry amount; the reconciliation window uses the full available width of the screen.
  • A single bank transfer settling several invoices is split between them: each assignment consumes its share of the amount, and the entry is only locked once fully allocated, without overwriting assignments already validated.
  • Alert on a different third party: during a manual assignment, if the bank wording does not mention the third party of the targeted invoice, a warning is displayed. It prevents nothing (a transfer may come from an agent or a parent company), but it makes a payment directed at the wrong third party visible before it becomes an accounting record.
  • The "To check - already settled?" marker: when an entry with no suggestion matches an invoice already settled outside the module, the reconciliation window points it out, names the invoice concerned and the date of its payment, and offers to archive the entry in one click. The marker stays cautious when several invoices could match, and nothing is archived automatically: the decision always remains yours.
  • Entry that can no longer be reconciled: the reconciliation window displays the reason in plain words and offers a way out — archive the entry, flag it as a duplicate of another, or bring it back if it was already put away.
  • Per-line actions: approve, reject, reopen a rejection, cancel an approval, lock after payment.
  • Unlocking: a locked entry with no native payment can be released to be matched again, keeping the assignments already validated; an entry whose payment has been created cannot be unlocked until that payment has been deleted in Dolibarr.
  • If the payment creation fails at validation time, the approval is undone with it: the entry goes back to the "Reconcile" state and a message says what to fix — a line never shows "approved" without a payment actually created.
  • Entries already allocated, settled or locked are no longer suggested in new matching runs.
  • Matching is possible with bank entries already present in Dolibarr: in that case, reconciliation only, never a second payment.

5. Creating Dolibarr payments

Once a match is validated, the module creates the corresponding native Dolibarr payment and updates the document, provided you have the right to do so.

  • A customer invoice is settled through a native customer payment; a supplier invoice through a native supplier payment.
  • Customer and supplier deposit invoices are also supported for payment creation.
  • Unpaid salaries and social/fiscal charges: creation of the native Dolibarr salary or charge payment.
  • Approved expense reports: validation creates the native reimbursement and the associated bank entry; the report is only marked paid once reimbursed down to the last euro, taking payments already recorded into account.
  • Donations received: validated, unpaid Dolibarr donations are suggested on incoming bank transactions, both automatically and in manual selection. Validation creates the native donation payment, linked to the bank account without a duplicate when a native bank entry already exists, and the donation only switches to paid when its balance is zero. A donation is never suggested on an outgoing bank transaction.
  • If a payment created by the module (customer, supplier or donation) is later deleted directly in Dolibarr, the corresponding reconciliation is automatically released and the document becomes matchable again; a warning banner and a "Resync deleted payments" button catch up any lines left stuck.
  • Each validation asks for a payment method and a collection date: the method is prefilled from the detected type or the default method, the date from the bank operation date, and both remain editable.
  • The payment generates the link to the document, the entry on the bank account and the switch to paid status if the document is settled.
  • Partial payment is possible by entering the amount to allocate.
  • Bank reconciliation is set by the module itself: a fully settled entry is reconciled on its statement of the month, with no manual reconciliation in Dolibarr. This reconciliation remains a reversible treasury operation, and it is only set once the full amount of the entry is allocated.
  • Special case of credit notes: they are only matched and locked, without automatic payment creation.

6. Duplicates between two statement formats

The same statement can be imported twice under different formats (in OFX then in CSV, for example): the label and the reference then differ from one format to the other, and the classic anti-duplicate protection cannot link them. The module recognises these cases thanks to a second key, deliberately limited to the account, the date and the amount.

  • The duplicated entry is imported and flagged, never deleted: two genuinely distinct movements of the same amount on the same day can exist, and only you can tell them apart.
  • The list carries a "Duplicate of entry no. x" marker that identifies the original entry, and the line concerned is tinted so it can be spotted at a glance.
  • The reconciliation window displays a warning before any validation on an entry flagged as a duplicate.
  • A "Duplicate, archive" button puts the entry away, out of the working lists, without deleting anything.
  • Pairing is one to one: each duplicate is linked to a single original entry.
  • The import report announces the number of duplicates flagged.
  • Entries already present in the database are caught up automatically when the module is updated: existing duplicates are flagged without any manual work.

7. Archiving and the "Archived" tab

So that the working lists do not grow forever, fully processed entries can be put away: they leave the working views and end up in their own "Archived" tab.

  • An archived entry leaves all the working lists, including the "All" view, and remains viewable and restorable at any time from the "Archived" tab.
  • Archiving is a mere display flag: no payment, no bank entry and no accounting record is touched.
  • Each archiving keeps its reason, to tell apart a duplicate, a document already settled or a finished reconciliation.
  • Bulk actions: every list lets you tick entries, tick them all at once and archive them together; the "Completed" tab additionally offers an "Archive all settled entries" button, to put everything away in a single gesture.
  • An entry whose reconciliation is not finished cannot be archived: the refusal is checked server-side.
  • A mixed selection states how many entries were left aside and why.

8. Search, sorting and filters

The module's tables can be sorted and filtered like Dolibarr's native lists, to find a specific line even across a large volume of entries.

  • Sorting on every column of every table (bank matching, import batches, lines of a batch, connectors), ascending and descending; sorting keeps the current filters.
  • Searching covers all the entries, with paginated results, not just the displayed page.
  • Search by amount in both notations (1 234,56 or 1234.56) and with comparisons: ">1000" or "<=-500", for example.
  • Search by date in the dd/mm/yyyy, mm/yyyy and yyyy-mm-dd formats.
  • The third-party search also examines the operation wording: useful for CSV statements where the payer's name only appears in the label.
  • The "Action" column can be filtered to isolate what remains to be done: Point, Settle, Unlock, Archive or Nothing to point. The filter works on the whole table, not on the displayed page.
  • The status filter can also isolate flagged duplicates ("Duplicate") or exclude them ("Not a duplicate").

9. Integration into Dolibarr's native Bank pages

The module steps directly into Dolibarr's native bank entries (Bank menu, account, entries), without leaving the usual screen.

  • An "Import a statement" button on an account's entry list: it opens a validation window (bank concerned and statements already imported) then reuses the module's import, with no double entry.
  • A "Pointing" column on each entry: it tells at a glance the lines reconciled through a Bank Import statement import from those reconciled natively in Dolibarr.
  • The "Pointing" column filters for real: the filter applies to the whole list (count and following pages included), not just the displayed page. The column also appears in the column selector and can therefore be hidden like the others.
  • Entries that have been put away show as "Archived" in the bank list, and the "Pointing" column filter offers that state.
  • A "Point" action on an unreconciled entry: it opens the module's matching to link the entry to one or more documents.
  • The "To reconcile" link isolates the entry concerned, ticks it and places the cursor in the statement field: no more hunting for it by hand in the list.
  • No duplicate bank movement: the payment is attached to the existing entry (no new line), then the native reconciliation is ticked automatically once the entry is fully allocated.
  • Match with an entry already present: when a statement line matches a bank entry that already carries its payment, the "Confirm match (nothing to pay)" button links the line to that entry and closes it, without creating a second payment or changing its reconciliation.
  • Two-way operation: reconciliations and matches are shared between the module and Dolibarr's native Bank screen.
  • Active as soon as the module is enabled: after an update, simply disable then re-enable the module to register it, with no manual configuration. The integration can be turned off in the module's setup if needed.

10. Managing import batches

The Import batches page lets you go back over what has been loaded, review its detail and clean up properly, particularly during test phases.

  • A list of batches with reference, source, file, date, number of lines present and protected, and status.
  • Batch detail: line-by-line review of the imported entries.
  • Deletion of a whole batch or of a single import line.
  • Lines already reconciled or paid are protected; forcing their deletion is restricted to administrators and never deletes the Dolibarr payments already created.
  • Useful for resetting a test data set before going live.

11. Bank connectors (API preparation)

The Bank connectors page lets you declare connection profiles to banking APIs, with a view to automating the retrieval of entries.

  • Creation of PSD2/AISP, EBICS or Custom JSON profiles.
  • Entry of the provider or bank, the API URL, the linked bank account and the active state.
  • The secret is never stored in clear text: you enter a secret reference (environment variable or server secret), typed in a protected field.
  • A warning reminds you that a banking API requires a dedicated contract/provider.
  • Point of attention: actual synchronisation requires an adapter specific to the bank or provider; the profiles prepare the integration but do not trigger any automatic import as standard.

12. Module configuration

The setup screen adapts the module's behaviour to your company and to the way you reconcile.

  • Default bank account used for imports and payments.
  • Default payment method offered at validation.
  • Amount tolerance to absorb rounding or small fees (0.02 by default).
  • Strong candidate score and minimum matching score, to tune how fine the suggestions are.
  • Maximum number of invoices scanned and number of candidates kept per entry (performance).
  • Maximum size of imported files.
  • Options to enable/disable: also search salaries, also search social/fiscal charges, suggest expense reports, and filter on amount gap (prevents suggestions whose amount bears no relation).
  • A dedicated setting for matching donations received: it enables or disables the suggestion of validated unpaid donations on incoming bank transactions.
  • Integration into the native Bank pages: a checkbox enables or disables the import button and the pointing in Dolibarr's Bank screens.
  • Display of the reconciliation panel: by default, it loads on demand for the one entry being reconciled, which keeps the matching list light even on a high-volume account; an option restores the former per-row display of the panel.
  • The module's settings are kept even when it is disabled then re-enabled, notably during an update.

13. Access rights (permissions)

The module provides distinct Dolibarr permissions to separate viewing, importing, matching and the accounting action.

  • Read Bank Import: view the dashboard and the entries.
  • Import bank statements.
  • Generate and validate matches.
  • Create Dolibarr payments (accounting action).
  • Administer Bank Import: setup and connectors.
  • This separation allows, for example, letting a colleague import and reconcile without authorising them to create the payments.
  • Suggested expense reports respect Dolibarr's native partitioning: each user only sees their own reports and those of their subordinates, unless they hold the right to read everyone's.
  • Donation matching requires the Dolibarr Donations module to be enabled and the user to hold the corresponding permissions.

14. Links with Dolibarr

The module does not work in isolation: it integrates with the native building blocks of Dolibarr.

  • Bank accounts (Banks | Cash) : Each import targets a Dolibarr bank account and each imported line appears there as a native bank entry, with no duplicate of the movements already present; at payment time, that entry is attached through the native flow, and the account remains clickable from the dashboard.
  • Customer invoices : Incoming entries are matched with open customer invoices; validation creates a native customer payment and settles the invoice if the amount is complete.
  • Supplier invoices : Outgoing transactions are matched with supplier invoices; validation creates a native supplier payment and updates the invoice.
  • Deposits and credit notes : Customer/supplier deposit invoices can generate a payment; customer and supplier credit notes are only matched and locked, without automatic payment.
  • Third parties (companies) : The module recognises the third party in the bank wording (name, keywords, code) to suggest the right documents, relying on Dolibarr third parties.
  • Salaries and social/fiscal charges : Optionally, unpaid salaries and social/fiscal charges are suggested; validation creates the native Dolibarr salary or charge payment.
  • Expense reports : Approved, unreimbursed expense reports are suggested on outgoing transactions; validation creates the native reimbursement and settles the report once reimbursed down to the last euro. Suggestions respect the native partitioning of expense reports: everyone only sees their own and their subordinates', unless they hold the right to read them all.
  • Donations (Donations module) : When the Dolibarr Donations module is enabled and the user holds the rights, validated unpaid donations are suggested on incoming bank transactions, never on an outgoing one. Validation creates the native donation payment, linked to the bank without a duplicate if a native entry already exists; the donation only switches to paid at zero balance, and the native deletion of its payment releases the reconciliation in the module.
  • Payment methods : The suggested payment method comes from the dictionary of active Dolibarr payment methods (c_paiement), and can be pre-detected from the operation type.
  • Accounting and document status : As payments are created through Dolibarr's native mechanisms, they feed standard accounting and switch settled invoices to paid status, with the associated bank line.
  • Bank / Reconciliation : The module integrates into the native bank entries page (Bank, account, entries): an import button, a pointing column filterable across the whole list and hideable through the column selector, an "Archived" state, a "Point" action and a "To reconcile" link that isolates the entry, ticks it and places the cursor in the statement field. Payments created attach to the existing entry with no duplicate movement, and the native reconciliation is set automatically on the statement of the month as soon as the full amount is allocated — a treasury operation that remains reversible.
Need help? WhatsApp Phone: 07 45 15 75 87 Phone: 07 43 52 58 29 Email Open the form