Bank reconciliation in Dolibarr: tick off your statements without spending hours

Why manual ticking costs so much

Line-by-line ticking almost always follows the same script. You open the statement, look for the payment in Dolibarr, tick it, move to the next line. An hour later, a grouped transfer matches no invoice and you lose track. Time is not the only cost. A payment entered twice, a receipt assigned to the wrong invoice or a forgotten bank fee can stay invisible for weeks. They surface at year-end closing, when everything has to be redone. The problem rarely comes from the tool. It comes from reconciling too rarely, on data typed by hand, with no method to isolate discrepancies. Dolibarr has what you need: bank accounts, statement import, entries linked to payments, reconciliation by statement. What remains is to chain these pieces in the right order, and that is what the rest of this article covers.

Prepare the bank account before the first import

Fast reconciliation starts with a clean bank account. Check that every real company account exists in Dolibarr, with its IBAN, currency and start date. The opening balance must match the balance of the first statement you process, otherwise the gap carries through every later period. Also check your payment methods: transfer, direct debit, card, cheque. Each one must point to the right account, or payments land elsewhere and are missing where you look for them. Finally, decide on a rhythm. A weekly check on a few dozen lines takes minutes. A quarterly check on hundreds of lines becomes a chore. If you are taking over a backlog, start with the oldest unreconciled period and move forward in chronological order, without skipping a month.

Import statements instead of retyping them

Retyping is the first source of errors. Dolibarr can create bank entries, but your bank almost always provides an export in a standard format that you can import. If your version offers statement import, use it. If not, the approach stays the same: get the file, check it, load it as a batch. Before validating, open the file and look at the dates, the signs of the amounts and the labels. A misread decimal separator can invert a whole statement. Import one month at a time and compare the resulting closing balance with the one printed on the statement. If it differs, tick nothing: first look for the missing or duplicate line. For neobank accounts, a direct connection avoids the file. The DolicraftRevolut module imports transactions from the API and lets you reconcile from Dolibarr.

Match payments and entries in the right order

The time saving comes from the order of processing. Start with the obvious lines: a receipt whose amount and reference match a payment already recorded on an invoice. Tick them in bulk. Then handle the medium cases, such as transfers that settle several invoices from the same customer, or partial payments. In these situations, first record the payments on the relevant invoices, then match the single bank line against all of them. Keep for last the movements with no invoice: bank fees, interest, contributions, refunds. Create these entries directly on the account, with a consistent category, so the next month runs the same way. Never force a match just to make a balance fit. A line wrongly assigned today becomes a customer dispute tomorrow, with an invoice wrongly marked as paid or an unpaid invoice that no longer shows up.

• Tick first the lines whose amount and reference exactly match a recorded payment.
• Record grouped payments invoice by invoice before matching the bank line.
• Create fees and commissions as account entries, with a constant category.
• Leave any doubtful line pending rather than assigning it at random.

Spot quickly what does not add up

A good reconciliation is judged by its ability to isolate discrepancies, not by how fast you tick. After each statement, compare three figures: the statement balance, the reconciled balance in Dolibarr and the sum of the lines still to be matched. If the difference is zero, move on to the next month. If not, search by category. A gap equal to one precise amount often points to a forgotten or duplicated line. A gap that changes every month rather suggests a flaw in method, for example payments recorded at the invoice date instead of the value date. Also examine customer invoices marked as paid with no bank line against them, and bank lines with no linked payment. These two lists are the most useful: they show exactly where your records and the bank diverge, without rereading the whole statement.

Set up a monthly routine and take action

Once the method is in place, turn it into a routine. Each week, import the new movements and tick the obvious lines. At month end, settle the special cases, check the three control figures and archive the supporting statement with the reconciliation. Name one person in charge, with a deputy, to avoid double entries. If your accountant works in another tool, a clean reconciliation upstream makes the exchange much simpler. For companies that synchronise their entries, our article on synchronisation with Pennylane shows how to keep both sides consistent. The next step is simple: take the last closed month, import its statement and measure the gap with your balance. If the task looks heavy, describe your situation on the contact page and we will review your bank setup together.