A changed IBAN, a double payment, an unusual amount — found before the money leaves
Upload today's payment batch and, if you have it, your payment history. Every payment is compared with what you have paid so far, and each warning says why. Everything is worked out in your browser: the files are not sent anywhere.
Optional. Confirmed IBANs and the payments you stop are kept in this browser for each client separately; with no name they are kept under “No name”.
How do I export the file from my program?
The XML file of payment orders you are about to upload to your bank (ISO 20022 pain.001, from Minimax or a Slovenian e-bank), or a CSV or XLSX file with one payment per row: recipient, IBAN, amount, reference or purpose, date and invoice number. The file is read in your browser and is not sent anywhere.
The columns of your file. Check them, and choose the right one where the guess is wrong.
Optional, and several files at once: earlier XML batches, and your list of received invoices (CSV or XLSX). The more history, the more the checks can tell. With no history, only the checks inside the batch itself work.
Payments to check come first. Tick the ones that go into the cleaned batch: the ones that are OK are ticked already.
| In the cleaned batch | No. | Recipient | IBAN | Amount | Result | Why |
|---|
Check high riskCheck medium riskOK no warning, or only a note
Recipients whose IBAN you confirmed by phone. The list is kept in this browser only, for the client above; nothing is sent anywhere. Export it to carry it to another computer.
Every warning names its reason. With history, a payment is compared with the earlier payments to the same recipient. A recipient is recognised by name, without the legal form (d.o.o., s.p., d.d.), capital letters, spaces and punctuation.
These two are notes: the payment stays OK and does not count among the payments to check.
A changed IBAN or an IBAN of another recipient can be marked “Confirmed by phone”: from then on that recipient with that IBAN is OK, with a note of who checked it and when. A double payment cannot be confirmed.
Without history only the checks inside the batch run: a double payment in the batch, a similar reference and a round amount with no reference. A list of received invoices counts towards double payments only on the rows that have a payment date; without one it still shows which recipients, IBANs and amounts are usual.
From any program that prepares an XML file of payment orders for your online bank (ISO 20022 / SEPA, pain.001), such as Minimax, Vasco, SAOP iCenter or PANTHEON. From another program or from Excel, upload a CSV or XLSX file with one payment per row. How to export the file from your program
Describe it in a few sentences. Točno is in a pilot phase: we read every description personally and reply within two working days on whether and how it could be solved. Free.