Open banking, not file imports
Romanian and EU banks connect directly over PSD2. Transactions arrive several times a day, with balance, value date and counterparty details.
If your bank is not covered, or you would rather not grant access, manual import stays available: MT940, CSV, the proprietary formats of the larger banks. The same matching rules apply either way.
How transactions are matched
The engine looks in order: an invoice reference in the description, then an exact amount plus a partner identified by IBAN, then an amount within a window of days around the due date. Confident matches are linked automatically; ambiguous ones land in a short confirmation list with the candidates ranked.
Partial payments and payments covering several invoices at once are handled explicitly — they are not special cases you resolve by hand, they are the normal path.
Rules for whatever repeats
Bank charges, subscriptions, transfers between your own accounts — anything recurring can carry a rule: if the description contains X, post it to Y. The rule applies from the moment it is created onwards; anything already posted stays as it was.
Cash coding for the rest
Whatever matches no invoice is posted straight from the transaction screen to a chosen account, with no intermediate document. That is the ordinary case for fees, interest, taxes and miscellaneous receipts.
Payments, not just reading
Payment orders are generated from supplier invoices — select what is due and get the bulk payment file for your bank. Due dates feed the cash forecast, so you see the gap before you reach it.
Worth knowing
The book balance and the bank balance are two different things, and the system keeps them apart. The difference between them — payments in flight, uncleared items — is shown explicitly rather than absorbed into one figure that looks right.