Statements and payments — with any bank

Through the bank API, and where there is none — through files. The accountant gets the same documents either way, and payment signing stays in your bank.

Group accounts07.10 · 09:00

  • [Bank 1] · UA…4417API · statement at 08:55[XXX XXX]
  • [Bank 2] · UA…0921API · statement at 08:58[XX XXX]
  • [Bank 3] · UA…7730API silent for 2 h · file mode[XX XXX]
12 payments received
[XX XXX]
Matched automatically
10 of 12

What it does

  • channels

    API, file, folder, email

    A statement arrives any way it can; the document in the books is the same.

  • switching

    Bank unavailable — files

    The API goes silent — the system switches to files and tells the accountant.

  • duplicates

    No duplicates, with reconciliation

    The same payment from the API, a file and email is created once; balances are reconciled with the bank.

  • matching

    By company ID, IBAN and purpose

    Plus your own rules: "all payments to this account are rent".

  • payments

    Approval with a button in Telegram

    Payment orders in a batch; above the limit — the owner approves.

  • formats

    1C/BAS, ISO 20022, CSV, Excel

    A new bank is added with no changes in accounting.

What it looks like

The morning statement is already sorted, and the owner approves payments from the phone.

Statement · [Bank 1] · 07.10All 12Matched 10Manual 2
TIMECOUNTERPARTYITEM / DOCUMENTAMOUNT
08:12LLC "Gurtpostach"Company ID ✓ · IBAN ✓Supplier paymentReceipt No. 214 →−[X XXX]
08:30Acquiring · barrule: account 2924Card revenue for 06.10Till shift No. 88 →+[X XXX]
08:41Sole trader Kovalenkorule: "rent"Premises rent, OctoberContract No. 7 →−[X XXX]
09:02Private person"for banquet 12.10"Looks like: prepayment, booking No. 31Confirm · Other+[X XXX]
double Hb · Bankbot

Payments to approve · 3

Gurtpostach[X XXX]

Energopostach[XX XXX]

Laundry "Chysto"[X XXX]

Energopostach — above your limit

✓ Approve all

✕ Reject

Review each

✓ Approve all

Done. 3 orders went to [Bank 1]. Signing is in the bank.

The path of an outgoing payment

  1. Order

    The accountant creates it or the system takes it from the supplier invoice.

  2. Approval

    The manager — in the system or in Telegram.

  3. To the bank

    A batch via API or a file for the client-bank.

  4. Signing

    Qualified e-signature and sending — in your bank.

  5. Confirmation

    The next statement closes the payment; a rejected one raises an alert.

In development

Which banks do you work with?

We will connect first the banks our customers need.

Leave a request