Process bank transactions manually

Modified on Thu, 28 Mar 2024 at 10:54 AM


All screenshots in the article were taken in the Dutch version of Yuki.

All bank transactions uploaded to Yuki end up in the 'Bank transactions to be processed' workflow. For handling bank transactions, there can be three situations:

  • IDR has recognised the bank transaction and suggests a match with a payment
  • IDR has recognised the bank transaction but cannot suggest a direct match to a payment
  • IDR did not recognise the bank transaction, so the transaction must be processed manually.

This article describes the third situation.


A user with the 'Back office' role in the domain can use the Batch Processing function to manually process a number of bank transactions simultaneously.

Only a user with the 'Back office' role in a domain can process bank transactions in the 'Bank transactions to be processed' workflow.

To start processing bank transactions, open the domain. The Back office workflow screen always opens by default. In this screen, click on the Bank tile to open the Bank transactions to be processed workflow.

In the now-opened screen, click on the > in front of a bank transaction line

In the now-opened screen you can now use the Split or Actions button.

Splitting bank transactions is described in article Split bank transaction.

A user with the 'Backoffice' role in a domain can record a bank transaction directly in costs or as revenue (and therefore VAT), split a bank transaction or use the Actions button to process the bank transaction manually.


A user with the role 'Financial administration' or 'External accountant' can only record a bank transaction manually (without VAT) via the outstanding  items debtors or creditors.


To open the list of all possible actions for the bank transaction, click on the Actions button. An action list opens where each action has a specific automatic entry associated with it. Here is the complete action list as far as debits are concerned:

The list above is the action list in case a debit has taken place. With a credit, this list will contain other terms. For example, the Payment to supplier action will change to Refund from supplier. The principle of the action remains the same, only the general ledger account 'Creditors' will now be posted as a debit instead of a credit.

Below you can see the full action list regarding credits:

As you can see, this list is very similar to the list at a debit. However, the difference is in the name of the transactions. For instance, Cash withdrawal has now changed to Cash deposit. The functionality remains the same.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article