Payments matched with a reason, and a balance that must agree

Many tools mark invoices paid from a bank statement. Doktally also says why it chose each invoice, never guesses between two, and checks every month's closing balance against the books.

The problem

Automatic matching is common now, and that is exactly the risk: a tool that silently marks the wrong invoice as paid is worse than no tool. And a statement that was never imported leaves no trace at all, so the books look complete while a month of payments is missing.

How Doktally solves it

  1. Import what the bank gives you: CAMT.053, MT940 or the bank's CSV, recognised from the IBAN, and never the same transaction twice.
  2. Every proposal comes with its reason: the invoice number in the reference, the amount still owed, the payer's IBAN or name, and how sure the match is.
  3. Confident single matches are confirmed in one click, all of them at once if you like. When there are two candidates, you decide: Doktally never picks at random.
  4. Every month is reconciled: the statement's closing balance against what Doktally holds. A difference means a missing statement, and it is flagged the same day.

The bank page with the lines to match and the confirm-all action

Each month: statement balance against the books, with the difference shown

Leva and euro are matched at the fixed rate, and an undone match puts the invoice back to unpaid.

The result

Reconciliation becomes a review: the routine 90% is proposed with reasons, the person decides the rest, and the books can't drift away from the bank without someone noticing.

Technologies

Java, Spring Boot, CAMT.053, MT940, Banking