Documentation

Bank

Bank statements

Updated 16/09/2026

In the Bank statements menu you import statements, and the programme matches the transactions with invoices in both directions: customers’ payments with your issued invoices, and your payments with the received supplier invoices.

Importing PDF statements

Banks in Serbia most often send statements by email as a PDF — and that is enough. Click “Import PDF statement” and choose the file (one at a time).

  • The first statement from a bank: the programme reads the table and asks you what each column means (date, description, inflow, outflow, payment reference…) and next to which label in the header the previous and the new balance stand. It recognises most of it by itself — you only check and confirm. With the “Remember the mapping for this bank” tick box on, that is saved, so subsequent statements from the same bank go through without questions.
  • The balance check is mandatory: previous balance + inflows − outflows must give the new balance from the statement. If the statement has no new balance printed (UniCredit), you mark the daily debit and credit turnover instead — the sum of the outflows and inflows must match them, and the programme derives the new balance. If it does not match, the import is refused until you correct the mapping — so a misread row cannot slip quietly into the records. When the bank changes the layout of its statement, the check fails and the wizard opens again.
  • The programme also reads statements printed in landscape (a rotated page) and transaction descriptions spread over several lines — the date and the amount do not have to be in the same row.
  • A scanned PDF (an image without text) cannot be imported — ask the bank for an electronic statement.
  • The same statement cannot be imported twice (it is recognised by the account, statement number and statement date).

Importing XML statements

If your e-banking offers an XML export, click “Import XML statements” and choose the files — at most 20 at a time. Currently Raiffeisen XML statements (dinar and foreign currency) are supported; for another bank, send us one of its XML files through the contact page.

The file is discarded after reading (both PDF and XML): we keep only the transaction data. The original stays with you, at the bank and in your email.

Automatic matching

On import, certain matches are matched by themselves, without a single click: when the transaction’s payment reference EXACTLY matches the number (or the payment reference) of an invoice and the amount is exactly the same:

  • a customer’s payment → your invoice moves to the “paid” status (it disappears from “Outstanding”), and the document history keeps a record of which statement it came from;
  • your payment → the received supplier invoice gets the “Paid” badge.

Suggestions with the “needs review” marker

The “To match” section shows the transactions that were not recognised with certainty, with a suggestion when there is one:

  • invoice number in the description — typically foreign-currency remittances;
  • by amount and company name — when the payment reference is missing or mistyped;
  • a combined payment — a group of invoices from the same company whose total is exactly the transaction amount (e.g. three invoices of 1.000 paid as 3.000).

Such suggestions carry the yellow “needs review” marker — have a look before confirming. If the amount differs from the invoice (a partial payment, a typing error), the suggestion says so clearly.

Manual matching (and several invoices at once)

Every transaction has “Match manually”: search the open invoices, tick one or more of them, and a live total shows whether the selection matches the transaction amount. Confirming marks all the selected invoices as paid (opening balance items have no status — they are closed by the posting).

An outflow to customs you match with a customs debt assessment (import): in the selection it is listed under the assessment number with the amount customs duty + other duties + VAT, automatically with an exact payment reference and amount; matching records the payment date that is the condition for deducting import VAT, and undoing deletes it.

The selection also includes the open documents from the partners’ opening balance (invoices from the time before the programme, entered in the Accounting add-on) — they are marked “opening balance”. They are matched by the same rules (an exact document number in the payment reference + the exact open amount automatically, the rest with a click), and the payment closes the item on the partner ledger.

Transactions that will never have an invoice

The “To match” section is a list of things to resolve — the record is the statement itself, and every transaction on it stays permanently recorded, matched or not. For transactions that have no invoice in the programme (and never will), use “Ignore”:

  • bank fees, taxes, contributions — they never have an invoice;
  • foreign-currency payments to foreign suppliers — a foreign supplier does not send through SEF (the national e-invoicing system), so the received invoice will not appear in the programme; the accountant posts the expense from the original bank statement;
  • lost/stray invoices — ignore them until they turn up.

Ignoring is reversible: on the statement page an ignored transaction stands greyed out with a “Restore” button — if the invoice arrives later, bring it back into the queue and match it. A wrong match is also undone on the statement page (✕ next to the link) — all the linked invoices return to unpaid.

The rule for every day: match what has an invoice, ignore what never will — everything is reversible.

Supported banks

PDF: any bank whose statement is a table with text — you set up the layout once through the wizard. XML: Raiffeisen (dinar and foreign currency); other banks from a sample you send us.